2. Scrum - A Practical Approach to Agile Project Management
Now that we've introduced agile methodologies and explored different flavors of agility, let’s focus on Scrum, one of the most commonly referenced frameworks when discussing agility.
What is Scrum?
Scrum is a framework for managing and completing complex projects, based on three core pillars: transparency, inspection, and adaptation. Developed in the late 1980s and refined in the 1990s and early 2000s, Scrum is built around the concept of delivering work iteratively and incrementally. The goal is to allow teams to handle uncertainty, remain focused, and continuously deliver value.
Scrum is often associated with the following values:
- Commitment: Team members should be dedicated to the task at hand.
- Focus: Scrum encourages focusing on a specific task during a time-boxed period called a sprint.
- Respect: Without mutual respect within the team, creating solutions becomes difficult.
- Courage: Teams need the courage to embrace change and pivot when necessary.
The Pig and Chicken Analogy
One famous Scrum analogy is the story of the pig and the chicken discussing starting a restaurant together. The chicken suggests naming it “Ham and Eggs,” to which the pig responds, “No thanks, I’d be committed, but you’d just be involved.” This highlights the idea that some team members are deeply committed to delivering results, while others are simply involved.
In Scrum teams, it’s crucial to have “pigs” (those who are committed) rather than “chickens” (those who are just involved) to ensure the team is invested in solving problems and delivering value.
Key Elements of Scrum
Product Backlog
The product backlog is a prioritized list of tasks or features that the team must deliver. It serves as the source of work for the Scrum team, and from this backlog, the team selects items for each sprint. The most important tasks are refined and clarified as they approach the top of the backlog.
Sprint Planning
During sprint planning, the team selects the most critical items from the product backlog to work on during the upcoming sprint. A sprint can last seven days, two weeks, or even a month, depending on the project. Once the sprint begins, the team commits to delivering the chosen backlog items by the end of the sprint.
Daily Standups
Every day, the team holds a daily standup meeting to ensure everyone is aligned. Team members discuss what they worked on yesterday, what they plan to do today, and whether they face any obstacles.
Sprint Review
At the end of the sprint, the team holds a sprint review to demonstrate the work completed. This session evaluates whether the team delivered on its commitments.
Sprint Retrospective
Following the review, the team holds a retrospective to reflect on the sprint. The goal is to identify lessons learned and opportunities for improvement in future sprints.
Practical Tips for Running Scrum
Refining the Backlog
The product backlog is never perfect, but items at the top should be well-refined and ready to work on. Here’s a simple checklist to use before sprint planning:
- Refine the backlog: Work with the team to define clear acceptance criteria and scope for high-priority items.
- Prioritize effectively: Ensure the team agrees on which items are most important. If everything is a priority, nothing is.
- Provide context: Use metrics and product data to explain why certain tasks are important.
- Focus on impact: Question whether the items at the top of the backlog will truly generate value.
A well-prepared backlog allows the team to effectively manage their workload and ensure each sprint starts with clear, actionable tasks.
Running Effective Daily Standups
To keep daily standups efficient, focus on three key questions:
- What did the team complete since the last meeting?
- What will we focus on today?
- Are there any obstacles or impediments?
A helpful technique is to review the board from right to left. This approach ensures the team focuses on completing tasks rather than starting new ones. Ask the team what has been finished, then review items in progress and identify any dependencies or blockers.
Asynchronous Daily Standups
For teams that may find synchronous meetings difficult, consider using an asynchronous standup via tools like Slack. A bot can prompt team members to answer questions such as:
- How are you feeling today?
- What tasks are you working on?
- Are there any risks or blockers?
- Would you like to share anything with the team?
This approach allows teams to collaborate effectively without the need for everyone to be online at the same time.
Sprint Reviews: Focus on the Product
Sprint reviews should focus on tangible results, not presentations. Instead of creating slideshows, teams should demonstrate the product, allowing stakeholders to interact with and validate the work done.
Sprint Retrospectives: Define Goals and Actions
Retrospectives should have clear objectives, structure, and outcomes. Focus on:
- Objective: Why are we holding the retrospective?
- Mechanics: What format will we use to facilitate the discussion?
- Closing: What actions will we take to improve in the next sprint?
One useful framework is the fun retrospectives approach, which makes the session engaging and productive, focusing on actions rather than complaints.
Conclusion
Scrum is a powerful framework for managing projects, with key rituals like sprint planning, daily standups, reviews, and retrospectives. By following best practices, you can ensure your team stays focused, delivers value, and continuously improves its process.
Whether you’re a product manager or part of a Scrum team, implementing these tips will help you get the most out of your Scrum process and keep your team aligned and productive.