Course Overview
This comprehensive course covers all aspects of Scrum methodology, including key terminologies, roles, and best practices. Through interactive tools, videos, quizzes, and a simulation game, you'll gain practical understanding of how Scrum works in real-world projects.
Scrum Terminologies
Interactive Scrum Glossary
Click on each term to learn more about it:
Sprint
A sprint is a time-boxed iteration in Scrum, typically lasting 1-4 weeks, during which a usable and potentially releasable product increment is created.
Key characteristics:
- Fixed duration that cannot be shortened or lengthened
- Goal is defined at the sprint planning meeting
- No changes are made that would endanger the sprint goal
- Scope may be clarified and re-negotiated between the Product Owner and Development Team
Product Backlog
An ordered list of everything that is known to be needed in the product, maintained by the Product Owner.
Features:
- Dynamic and constantly evolving
- Prioritized by business value
- Contains user stories, features, requirements, enhancements, and fixes
- Items at the top are more refined than those at the bottom
Sprint Backlog
The set of Product Backlog items selected for the Sprint, plus a plan for delivering them.
Components:
- Selected Product Backlog items
- Tasks needed to deliver those items
- At least one process improvement identified in the previous Retrospective
- Owned by the Development Team
Sprint Review
A meeting held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed.
Purpose:
- Inspect the work completed during the sprint
- Collaborate on what to do next
- Adjust the Product Backlog based on feedback
- Time-boxed to 1 hour per week of sprint (e.g., 2 hours for a 2-week sprint)
Retrospective
An opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.
Typical agenda:
- What went well during the sprint?
- What could be improved?
- Action items for improvement in the next sprint
- Time-boxed to 45 minutes per week of sprint (e.g., 1.5 hours for a 2-week sprint)
Roles in Scrum
Scrum Role Explorer
Click on each role to see responsibilities and characteristics:
Product Owner
The Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team.
Key Responsibilities:
- Clearly expressing Product Backlog items
- Ordering the items in the Product Backlog to best achieve goals and missions
- Optimizing the value of the work the Development Team performs
- Ensuring the Product Backlog is visible, transparent, and clear
- Ensuring the Development Team understands items in the Product Backlog
Scrum Master
The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide.
Key Responsibilities:
- Ensuring Scrum is understood and enacted
- Removing impediments to the Development Team's progress
- Facilitating Scrum events when needed
- Coaching the Development Team in self-organization
- Helping the Product Owner with techniques for effective Product Backlog management
Development Team
The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of "Done" product at the end of each Sprint.
Characteristics:
- Self-organizing - no one tells them how to turn Product Backlog items into Increments
- Cross-functional - collectively have all skills needed to create a product Increment
- No titles - no sub-teams, regardless of domains needing to be addressed
- Accountable as a whole for delivering work each Sprint
- Typically 3-9 members
Scrum Team Dynamics
The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master. Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team. Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team.
Best Practices of Scrum
Daily Scrum Tips
- Time-box: Keep it to 15 minutes, no matter the team size
- Stand up: Literally stand to keep energy high and meeting short
- Three questions: Focus on "What did I do yesterday?", "What will I do today?", "What impediments do I have?"
- Problem-solving: Take discussions offline with only relevant people
Sprint Planning Advice
- Ensure the Product Owner comes prepared with a prioritized backlog
- Break down large items into smaller, manageable pieces
- Don't overcommit - it's better to underpromise and overdeliver
- Define a clear sprint goal that guides decision-making
Retrospective Techniques
- Vary the format to keep it fresh (e.g., Start-Stop-Continue, Mad-Sad-Glad, Sailboat)
- Focus on actionable improvements, not just complaints
- Follow up on action items from previous retrospectives
- Create a safe space for honest feedback
General Scrum Best Practices
- Maintain a sustainable pace (no heroics)
- Keep work visible (physical or digital task board)
- Limit work in progress to focus on completing items
- Inspect and adapt regularly
- Focus on delivering value, not just completing tasks
Video Resources
Introduction to Scrum
Scrum Roles Explained
Running Effective Scrum Ceremonies
Test Your Scrum Knowledge
1. What is the primary responsibility of the Product Owner?
2. Which of these is NOT a Scrum event?
3. What is the ideal size for a Development Team?
Scrum Simulation Game
Experience Scrum in action through this interactive simulation. You'll play the role of a Scrum Master guiding a team through a sprint.
Product: Develop a Mobile Task Management App
Sprint Duration: 2 weeks
Product Backlog
View and prioritize backlog items
Sprint Planning
Select items for the sprint
Daily Scrum
Coordinate daily work
Sprint Review
Demonstrate completed work
Retrospective
Improve team processes
Impediments
Address blockers
Welcome to the Scrum Simulation! Click on any card to begin.