Implementing Change

This is my real-time experience on how I thought of implementing a small change in my team and how we succeeded in the project as a whole team.

In the Agile Software development process, when you follow the Scrum framework, you become a critical part of the Scrum team even if you are a developer or a tester.

When a new sprint starts, you will have a Sprint Planning meeting where all the scrum team members are invited and Scrum Master or sometimes Business Analyst takes you through the user stories from the Product Backlog.

As you go through each user story, Scrum Master or B. A asks the team if they have any clarifications or any questions. And, if the team (or as a Tester) says No then it’s NOT a good sign. It shows either you lack understanding, and you are hesitant to raise any concerns, OR you have a clear understanding of what needs to be tested?

Being a senior member of my team was observing this continuous pattern in my team for quite some time. I, pondered over this for a long time on how this should be handled so that it won’t give any disrespect to any individual in my team. I, myself was a little hesitant at first but confident ( of my team).

I knew it was challenging for me to implement what I had in my mind. But I had to start from somewhere. I had to take risks (calculated).