How to easily understand the agile release and sprint planning process. Simple diagrams based on six sigma principles to clearly convey the goals of the planning process including the understanding of the customers as well as the inputs and outputs required for Agile Release and Sprint Planning ant tactics for success.
Scope and Questions on Agile Planning • At the end of this presentation youAgile and Waterfall will be able to answer theseAgile Framework questions about Agile Planning: • Where is the planning executed?Release Planning • Who is part of the planning? • When is the planning executed? (E.g. 1Sprint Planning time?) • How is the planning performed? • What is required for the planning meetings and what is expected as an outcome from the meetings?
Agile FrameworkStrategicPlanning Release Planning Sprint Planning Planning and estimating depend on a key metric: velocity, which describes how much work the team can get done per sprint. 5
Release PlanningGoal: Establish the overall release schedule and determine in what sprint stories will likely bedelivered. • Who: Scrum Coach, Product Owner, Scrum Release Plan Team, Scrum Master, Key Stakeholders Product Vision • When: before release n+1 begins (.5 -2 days) • How / Topic(s): Selected stories • PO presents the vision, strategy and for the release High level goals. prioritized goals & • PO present key dates and milestones. roadmap • PO presents draft of the prioritized Prioritized product backlog. backlog • Discussion to understand user stories. Product Backlog • Review rough estimates + prioritized (priority draft) features. Stakeholder • Agreement on Sprint length (in weeks) consensus and target release dates. Rough Estimates • Release Plan is organized by scope (functionality) or time (release every N sprints). Key risks and • Continual Planning. The initial release assumptions plan is a ‘blueprint’ to get started and will be revised. “Sprint towards Change” 6
Sprint (Iteration) PlanningGoal: Team to plan and agree on backlog items they can complete and confirm the tasksrequired to support acceptance. • Who: Scrum Coach, Product Owner, Release Plan Sprint Plan Scrum Team, Scrum Master. • When: before Sprint n+1 begins (2-3 hrs).Prioritized product • How / Topic(s): Selected stories backlog • PO presents the backlog items in for the sprint priority order for review. • Stories with failed acceptance testsTeams capabilities from prior sprints are added*. Key risks and (hours) • Discuss story creation for defects from assumptions prior sprints*. Prior Velocity • Review and clarify user stories. Stakeholder • Breakdown larger stories and each consensus story into tasks and acceptance Story Effort criteria. Estimation • Tasks are estimated in hours. • 1 developer and tester assigned to be on point per story. Schedule risks / • Process continues until all available Business hours are used for the sprint. conditions 7
Note on Experience Challenges Problem: The team does not have past experience of Sprint planning, capacity is not known and story points may be inaccurate. Over time estimation of capacity and story sizing will improve.Tactics, look at variation: Determine the Sprint variation (Estimated Capacity in Story Points Vs.. Actual Completed Story Points) at the end of each sprint. Determine Story Point variation for each story (No of hours expected Vs.. No of Hours used to complete). 8
Agile Planning RecapFor both Release and Sprint planning sessions we addressed• Where in the framework the planning is executed.• Who is part of the planning sessions.• When the planning sessions are executed.• How is the planning performed.• What is required for the planning session and what is expected as anoutcome. 9