RECENT Posts

Many times, I get into conversation of “Where not to use Scrum.” There seems a common belief and some level of agreement amongst Scrum practitioners about where not to use Scrum from product perspective – Scrum is best suited when “Certainty is High and Agreement is Low” or when “Certainty is low and Agreement is High”. If both Certainty and Agreement are High (Defined process) or if both are Low (Chaos), Scrum may not be a good choice. I agree with this and also believe that Scrum can bring the

My goal is to share interesting concepts, situations and ideas in Agile and Scrum adoption, through my Blog.
So here is one – I recently met someone whose first statement to me as he approached me was, “I have a problem.” This immediately got my attention, “How can I help? What is your problem?”
He said, “I used to be a Scrum Master. My team liked me and I enjoyed it as well. However, our Product Owner decided to move on, and since I was coaching the product owner, I had a fair idea about what

A few months ago, I met a software developer who had absorbed the essence of Scrum and had also helped his team use it effectively. The reason he reached out to me was because of my interest and experiments in taking Scrum beyond software. He had been trying to do something similar and wanted to share his learnings and ideas as well as gain some insights.
Here was his challenge:
"I volunteer at a non-profit for kids. My son also participates in their fund-raising events. Since the funds are

I am working with a client for past 9-10 months. As soon as I started, I noticed knowledge and information silos and utter lack of team spirit in multiple teams. Even within a team under the same manager, members did not know what the other member did. With the team that I started working with, my first instinct was to get the team to create a product backlog. With each member working on 20 different things, everyone was pulled in multiple directions at the same time and subsequently

When I was coaching at Coaches Clinic at San Diego Global Scrum Gathering in April 2017, one of the attendees who stopped by was there with her Scrum Master husband. She expressed a desire to become a Scrum Master too and wanted some guidance to navigate the organization and transition from QAE to Scrum Master.
Every action or decision usually has a motivation or inspiration. So I asked her what her motivation was? Her answer was intriguing, "It is because Scrum Master job is easy."
Having

I still remember the days when Development team built a functionality. QA did not know anything about the functionality, and tried to test it. Bugs were found late in the game. Development and Product Management did not collaborate on what functionality to build? Product Management provided Product requirements document, which was a contract to measure success of the Development and QA teams. Product Development sometimes drove the requirements, and sometimes was a recipient of the