Transition to Agile

I can remember very clearly those Old Days when we were transitioning from WaterFall to Agile. At that time, I was leading teams and was involved in some serious product development. Then I got to know that I have to unlearn what I have learned as I was the one who will play the role of Scrum Master. Thanks to the management that they gave me the opportunity to enter and explore into this new world.

Often, on traditional projects (i.e., waterfall), team members create email trails, Use command and control, Create disciplines and silos, Sign off on a detailed requirements document, be plan driven etc..

On the other hand, Scrum values communication and collaboration among team members, team members learn to take collective ownership of the project, each member has to unlearn the tendency to specialize and instead should use pair programming and role sharing to expand his or her understanding, team adjusts the top line of the project, customer’s requirements and priorities will change, the work environment for the team will change—the plan must change in response.

As a Scrum Master, my focus is on creating smart teams with strong skills in self-organization and a drive for progressive improvement. Give Support to Product Owner in visualising team’s progress & creating a transparent Product Backlog.

With more than 2 years of experience as Scrum Master, I want to share My Day of working:-

– Usually , I Start my day with an open and curious mind(With a cup of Green Tea)

– A good first question to consider is “How can I improve the live of the Scrum Team by facilitating creativity and empowerment?”

– My agenda is as good as empty! Except for the Daily Scrum and maybe some other Scrum events

– Attend the Daily Scrum as an observer. Listen to what is and isn’t being said.

– Based on the observations determine your next steps. This might be coaching, facilitating, mentoring, problem solving, conflict navigating or… just sitting with the team, listening and watching the team.

– Doing “nothing” is a perfect activity for me! The biggest pitfall for a Scrum Master is being too busy and not noticing what is really going on.

Some of the Handy Key points that i usually refer:-

1. No Interference from outside to the team.
2. More clear and small user stories.
3. All team members should have a very clear understanding of Scrum.
4. A VERY CLEAR definition of DONE.
5. No place for extra Process.
6. Allow the team to be on its own velocity and never try to press the accelerometer.
7. No task switching in between Ongoing task.
8. Sprint Backlog should be ready before the sprint planning meeting.
9. Encourage pair programming wherever needed.