The Journey of a Scrum Master: Unveiling the Secrets of Agile Success
The Journey of a Scrum Master: Unveiling the Secrets of Agile Success
Hi there!
Agile/Scrum has been around in Da Nang city for about 15 years. I would love to take this chance to write some notes about this concept. Let us start with the situation above:
Option #1. While seeking assistance from others can be a temporary solution, it may not address the root cause of the problem. It is essential to empower the Scrum Master to fulfill their role effectively and support the team independently.
Option #2. Coaching the Scrum Master is a proactive approach that can help her develop the necessary skills and knowledge to address blocking issues. However, if despite coaching and support, the Scrum Master continues to struggle and is unable to meet the team's needs, it might be necessary to consider a replacement.
Option #3. While the Product Owner plays a crucial role in prioritizing and managing the product backlog, their primary focus is on maximizing the value of the product. It is not their responsibility to directly resolve the team's blocking issues. However, the PO can collaborate with the SM to identify and mitigate any impediments that may hinder the team's progress.
The most effective solution would be a combination of options #1 & #2. By providing support and coaching to the Scrum Master, you can help her develop the skills and knowledge necessary to address blocking issues independently. Additionally, if despite coaching and support, the Scrum Master remains unable to fulfill her role effectively, considering a replacement might be necessary to ensure the team receives the assistance they need.
By definition, Scrum is an agile project management framework that helps teams structure and manage their work through a set of values, principles, and practices. By definition, Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.
A Scrum Master to foster an environment where:
A Product Owner orders the work for a complex problem into a Product Backlog.
The Scrum Team turns a selection of the work into an Increment of value during a Sprint.
The Scrum Team and its stakeholders inspect the results and adjust for the next Sprint.
Repeat.
Scrum is founded on empiricism and lean thinking.
Then, here it comes, the mighty PDCA.
Plan-Do-Check-Act (also known as “PDCA”) is a cyclic process that was conceptualized by Walter Shewhart and widely promoted by Edward Deming – two founders of most of the quality philosophies that are followed today. This concept is a cycle for bringing about a change which, when implemented and repeated, would yield repeated improvements in any process.
PDCA cycle should be used in following cases:
When opting for continuous improvement.
When initiating a new improvement project.
When making a new or modified design of a process, product or service.
When defining a repetitive work process.
When preparing data collection and analysis so as to verify and prioritize problems or root causes.
When applying any change.
💡 How about you? Why are you using Agile/Scrum? Let me know in comment section below.