Professional email to send to Boss

Good Morning Sarah/ HR team, Hope you had a good weekend. :) I wanted to thank you for sharing your reasons with me regarding the corrective plan. However, I’ve accounted below the same along with how I’ve felt it to be unfair to be put on the plan. 1. First and foremost, I believe there has been a misunderstanding regarding the sharing of KT with me. I worked with the team for 4-6 weeks initially, when the team required an extra person’s help. The work/stories i picked along with it’s KT (for 2 stories) were given to me by Vaidhavi. Please note KT was given to me only on the stuff that she had given for me to complete. As you are aware, the claims reporting team have more than 40-50 reports and whose enhancements keep coming up. When the changes come in, the IT team has to create a story for every change. Hence, KT wasn’t provided to me by anybody on the entire business of claims reporting. I was switched to the team with the assumption that since I worked with the team for 3-4 weeks previously, I would have an idea about the whole process. Kindly note that I have never received the KT on the entire process of claims reporting. The problem arose with the misunderstanding of believing the KT to be given to me initially and then again when I was switched by Vaidhavi. For future reference (or insert whatever technical word ) the dilemma can be avoided if the management team can come up with a plan, so there’s a clarity and transparency with the sharing of Knowledge transfer with a new team member. I have worked the best I could to deliver the stories I’ve picked. When a new person joins a team and they’re not given any KT on the entire process, it takes time for them (usually 5-6 months) to understand the business process. I learned the business process through the work that I picked up. I also worked at the same speed as the other team members and picked up the same amount of stories as others. Learning the process as well as keeping up with the speed and picking up stories as others was a double task on my end. 2. The test case issue I’m aware of the team informing me regarding the test cases in ALM, they also asked me to complete the update as needed which i did. Test cases were created by me when I couldn’t find them in ALM. As per my knowledge, I don’t see any issue with that and how it came up in the corrective plan. Please advise in case otherwise. 3. May 31, 2022 Kindly note that there’s no set standard of writing test cases by the test management team. Whenever I write test cases, I write them based on the story. The scenario I validated, the reporting team hadn’t outlined in ALM. It was a different scenario that i was going to validate and the test cases that were there initially did not cover those scenarios which is why I had to create my own test cases separately. The test cases of the story had already gone to production and business had no issues. They also reviewed my test cases and the test results and couldn’t find any issues. The same was reviewed by my manager Sarah (insert name) and in case of any issues at the time, I believe I should have been notified by my peers or by the manager. 4. July 5, 2022 Every team has a different work culture. When i joined the team, the scrum master usually linked the stories to releases. The date mentioned where I didn’t tag the story didn’t come under my responsibilities as per the team. It was supposed to be done by the scrum master. He was informed by me to put a release tag on the story as i do for every story that I pick up. The incident which has been reported for July 5th ( i had also joined the team only 2 months prior) occurred only once. I’ve delivered so many stories until now to production. There hasn’t been a repetition of the incident since then as I’ve always let the scrum master know every time I pick up a story. Even then I deleivered everything to production on time with no issue in production. I am not just understanding this reason as part of corrective plan. You were also on that email where I sent things to UAT for Validation. I have also included EUAT as well in that email so they knew that they need to do validation but they didn't reach out to me till the last day and they didn't even inform the team regardin tag and as I said its not my responsibility in team. Scrum master usually tag releases on story. You may check with team as well and I was new to the team and I did what I supposed to do in my previous team. nobody instructed me about UAT location. There is no proof that location was shared to me by my team members. Usually our developers send things to UAT for business to validate and when I joined team even then developer was sharing files with business for UAT. in the middle when things change from QA management that QA has to share files to business thats when I sent out an email for UAT to business and I used previous approach that I used in Quality team where I used to send files for UAT some common location where end users have access. I used a location where we usually keep files and before I sent files to busienss I opened a file from my end. I am not sure why it didn't open from business side. this incident happened only once and never repeated again. If this thing keep happening that I think it would be part of corrective plan but since this never repeated, it shouldn't be a part of corrective plan. YEs I understand about assining the stories to yourself when you pick it up which I always do it. I have been working with Caresource and in agile environment from last 6 years and I know the process that was just one time when I picked up a story and didn't assign to myself which I later did it while I was working on it. This incidednt never happend again till now. So this is not valid statement for corrective plan. 5.