Purpose
- The Scrum Guide defines Scrum as a framework for delivering value through adaptive solutions to complex problems.
- Developed in the 1990s, Scrum emphasizes transparency, inspection, and adaptation.
- It is cross-functional, self-managing, and accountable for delivering a valuable Increment each Sprint.
- The Scrum Team comprises 10 or fewer members, consists of a Scrum Master, a Product Owner, and Developers.
Definition
Scrum Team
Product Owner
- Being a single-person role, representing stakeholders’ needs in the Product Backlog
- Maximizing the value of the product resulting from the work of the Scrum Team
- Varying widely across organizations, Scrum Teams, and individuals
- Developing and explicitly communicating the Product Goal
- Creating and ensuring transparent, visible and understood for the Product Backlog items
- Ordering Product Backlog items
- Authorized to change the Product Backlog required
Scrum Master
- Coaching the team members in self-management and cross-functionality
- Helping the Scrum Team focus on creating high-value Increments that meet the Definition of Done
- Causing the removal of impediments to the Scrum Team’s progress
- Ensuring that all Scrum events take place and are positive, productive, and kept within the timebox.
- Helping find techniques for effective Product Goal definition and Product Backlog management
- Helping the Scrum Team understand the need for clear and concise Product Backlog items
- Helping establish empirical product planning for a complex environment
- Facilitating stakeholder collaboration as requested or needed.
- Leading, training, and coaching the organization in its Scrum adoption
- Planning and advising Scrum implementations within the organization
- Helping employees and stakeholders understand and enact an empirical approach for complex work; and,
- Removing barriers between stakeholders and Scrum Teams.
Developers
- Creating a plan for the Sprint, the Sprint Backlog
- Instilling quality by adhering to a Definition of Done
- Adapting their plan each day toward the Sprint Goal
- Holding each other accountable as professionals.
Scrum Events
Sprint
- A new Sprint starts immediately after the conclusion of the previous Sprint, fixed length events of 1 month or less to create consistency.
- Only the Product Owner has the authority to cancel the Sprint.
- During the Sprint:
- No changes are made that would endanger the Sprint Goal
- Quality does not decrease
- The Product Backlog is refined as needed
- Scope may be clarified and renegotiated with the Product Owner as more is learned.
Sprint Planning
- Sprint Planning initiates the Sprint by outlining the work to be done, involving the entire Scrum Team.
- The Product Owner ensures attendees are prepared to discuss important Product Backlog items aligned with the Product Goal.
- Sprint Planning covers three main topics:
- Establishing the Sprint Goal, communicating the Sprint’s value to stakeholders.
- Selecting items from the Product Backlog to include in the Sprint.
- Planning the work necessary for each selected Product Backlog item to meet the Definition of Done.
- Developers have the autonomy to plan how to turn Product Backlog items into Increments of value.
- The outcome of Sprint Planning is the Sprint Backlog, consisting of the Sprint Goal, selected Product Backlog items, and the plan to deliver them.
- Sprint Planning is timeboxed to a maximum of 8H for a 1 month Sprint, with shorter Sprints having shorter planning sessions.
Daily Scrum
- Purpose: Inspect progress toward the Sprint Goal and adapt the Sprint Backlog.
- Duration: 15 minutes.
- Frequency: Held daily, same time and place, throughout the Sprint.
- Attendees: Developers of the Scrum Team; Product Owner or Scrum Master participate as Developers if actively working on Sprint Backlog items.
- Flexibility: Developers can choose meeting structure and techniques.
- Focus: Progress toward the Sprint Goal and creating actionable plans for the day’s work.
- Benefits: Improves communication, identifies impediments, promotes quick decision-making, reduces the need for additional meetings.
- Adaptation: Not the only opportunity for plan adjustments; Developers may convene throughout the day for more detailed discussions.
Sprint Review
- Purpose: Inspect the outcome of the Sprint and determine future adaptations.
- Attendees: Scrum Team and key stakeholders.
- Focus: Presentation of Sprint results, discussion of progress toward the Product Goal, and review of changes in the environment.
- Collaboration: Attendees collaborate on what to do next based on Sprint outcomes and environmental changes.
- Adjustments: Product Backlog may be adjusted to seize new opportunities.
- Format: Working session, not limited to a presentation.
- Timing: Second to last event of the Sprint, timeboxed to a maximum of 4 H for a 1 month Sprint. Shorter for shorter Sprints.
Sprint Retrospective
- Purpose: Plan ways to increase quality and effectiveness.
- Attendees: Scrum Team.
- Focus: Inspect how the last Sprint went regarding individuals, interactions, processes, tools, and Definition of Done.
- Discussion: Review what went well, problems encountered, and solutions.
- Identify Changes: Identify helpful changes to improve effectiveness, address impactful improvements promptly.
- Conclusion: Concludes the Sprint.
- Timing: Timeboxed to a maximum of 3H for a 1 month Sprint, shorter for shorter Sprints.
Scrum Artifacts
Scrum’s artifacts represent work or value and maximize transparency.
Each artifact has a commitment to enhance transparency and focus:
Product Backlog
- Aligned with the Product Goal.
- An emergent, ordered list of what is needed to improve the product.
- Product Backlog items ready for selection in Sprint Planning are refined.
- The Product Goal describes the long-term objective.
- It provides a basis for work undertaken by the Scrum Team.
Sprint Backlog
- Aligned with the Sprint Goal.
- Composed of the Sprint Goal, selected Product Backlog items, and an actionable plan.
- Created and managed by the Developers for the Sprint.
- The Sprint Goal provides flexibility and coherence to the Sprint Backlog.
Increment
- Aligned with the Definition of Done.
- A formal description of the state of the Increment when it meets quality measures.
- Ensures transparency and shared understanding.
- Conforming to the Definition of Done is mandatory for Developers and Scrum Teams.
- A concrete stepping stone toward the Product Goal.
- Each Increment is additive and thoroughly verified.
- It must meet the Definition of Done to be considered part of the product.
Scrum Values
- Commitment: Scrum Team commits to achieving goals and supporting each other.
- Focus: Primary focus is on Sprint work to make progress toward goals.
- Openness: Scrum Team and stakeholders are open about work and challenges.
- Respect: Team members respect each other’s capabilities and independence.
- Courage: Team members have the courage to do the right thing and tackle tough problems.
Would you like to read more articles by Tekos’s Team? Everything’s here.
Author
