Alas, we are reaching the end of 2022 in a matter of days 🙂
Here in this last post of my 2022 scrum master experience, I would like to thank all my fellow readers and wishing everyone a Happy New Year in advance and may your new year resolutions be made real.
Going back through all the months in 2022, there were a lot of learnings, challenges and throwbacks that can be summarized. I would present it in a form of a retrospective below :
| What went well | What didn’t go so well | What can be improved |
| 1. Estimating story points taking into account skillsets, holidays, leaves contributes holistically to the calculation of story points. 2. Established best practices for planning and conducting sprints, including setting clear goals and objectives, creating a product backlog, and tracking progress. 3. Having a positive team culture is important in determining the success of the product. Clearing any ambiguities, answering any questions all leads to the inculcation and promotion of close collaboration, transparency and inclusiveness within the team. | 1. Sprints maybe affected by urgent issues mid sprint. 2. Disruptions as a result of team members leaving. Even though knowledge transfer was done, some details tend to be missed out and only realized after the team member has left. 3. Stakeholder resistance to agile methodologies which usually stems from understanding and communication issues | 1. Prioritization of incidents and issues mid sprint to ensure timely completion of stories (in the absence of a dedicated support team) 2. Knowledge repository for all technical details either in stories or in separate document. 3. Measures of demonstrating the value of agile methodologies, including key metrics and performance indicators to track the overall progress and success of the product and product team. |
 |  |  |
