Estimation methods
Common estimation methods include Planning Poker, T-shirt sizing, and relative sizing using story points or ideal days. These techniques help teams understand work complexity and plan Sprint capacity. Estimation focuses on relative effort rather than absolute time, enabling better planning decisions. Teams improve estimation accuracy through experience, regular calibration, and retrospective analysis of actual versus estimated effort.
Daily Scrum
The Daily Scrum is a 15-minute synchronisation meeting where Development Team members coordinate work and identify impediments. Participants typically discuss yesterday’s progress, today’s plans, and any obstacles. This ceremony promotes transparency, enables quick problem-solving, and maintains team alignment. While structured, Daily Scrums should adapt to team needs whilst maintaining focus on Sprint Goal achievement.
Value-based prioritization
Value-based prioritisation ensures teams work on highest-impact items first, maximising return on investment and customer satisfaction. This approach considers business value, customer feedback, market opportunities, risk mitigation, and strategic alignment. Product Owners balance immediate needs with long-term vision whilst considering technical dependencies and team capacity. Regular reprioritisation adapts to changing circumstances and new information.
Sprint Review
Sprint Reviews demonstrate completed work to stakeholders and gather feedback on the product increment. The Development Team presents working software whilst the Product Owner explains what was accomplished and what remains. Stakeholders provide input on future direction. This ceremony fosters collaboration, validates assumptions, and informs subsequent planning decisions through direct stakeholder engagement and product inspection.
Technical debt management
Technical debt represents shortcuts and compromises that speed immediate delivery but create future maintenance costs. Effective management involves identifying, measuring, and systematically addressing debt through refactoring, code quality improvements, and architectural enhancements. Teams balance new feature development with debt reduction, ensuring sustainable development pace and maintainable codebases whilst meeting business objectives.
Sprint Retrospective
Sprint Retrospectives provide teams with structured opportunities to reflect on their working practices and identify improvements. Teams examine what went well, what could be better, and specific actions for enhancement. This ceremony occurs after Sprint Reviews, focusing on process and team dynamics rather than product features. Effective retrospectives require psychological safety, honest communication, and commitment to implementing improvements.
Release planning
Release planning aligns product increments with business milestones, market opportunities, and customer needs. It involves grouping Sprint deliverables into coherent releases, coordinating dependencies, and communicating timelines to stakeholders. Effective release planning balances predictability with flexibility, enabling regular value delivery whilst adapting to changing requirements and market conditions throughout development.
Timeboxing principles
Timeboxing creates fixed periods for activities, promoting focus and preventing endless perfectionism. Scrum events have maximum durations: Sprints (1-4 weeks), Sprint Planning (8 hours for 4-week Sprints), Daily Scrums (15 minutes), Sprint Reviews (4 hours), and Retrospectives (3 hours). Timeboxes create urgency, ensure regular progress, prevent over-engineering, and provide natural inspection points for adaptation and improvement.
Product Backlog
The Product Backlog is an ordered list of features, functions, requirements, enhancements, and fixes needed for the product. Items are ordered by value, risk, priority, and dependencies. The Product Owner maintains this dynamic document, continuously refining and updating it based on stakeholder feedback, market changes, and learning. Well-maintained backlogs provide transparency and guide Sprint Planning decisions.
Creation and refinement
Product Backlog creation begins with initial product vision and stakeholder requirements. Refinement is an ongoing activity where the Product Owner and Development Team collaboratively add detail, estimates, and order to backlog items. This process includes breaking down large items, clarifying acceptance criteria, removing outdated items, and ensuring upcoming work is appropriately detailed for Sprint Planning.