From be1b48e795ed8a0fe5f074478de238bffa123cd4 Mon Sep 17 00:00:00 2001 From: lizcamp Date: Tue, 16 Apr 2019 20:56:39 -0400 Subject: [PATCH] Added more details to each level (#33092) Elaborated on each of the 5 levels --- .../agile/five-levels-of-agile-planning/index.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/guide/english/agile/five-levels-of-agile-planning/index.md b/guide/english/agile/five-levels-of-agile-planning/index.md index 5230dd6db7..54d809bf50 100644 --- a/guide/english/agile/five-levels-of-agile-planning/index.md +++ b/guide/english/agile/five-levels-of-agile-planning/index.md @@ -14,15 +14,15 @@ Agile planning is always continuous and should be revised at least every three m ## Brief Synopsis of the Five Levels of Agile Planning - Product Vision: What (Summary of the major benefits & features the product will provide), Who (Stakeholders), Why (Need & Opportunity), When (Project scheduling & time expectations), Constraints and Assumptions (impacts risk & cost). + 1. Product Vision: What (Summary of the major benefits & features the product will provide), Who (Stakeholders), Why (Need & Opportunity), When (Project scheduling & time expectations), Constraints and Assumptions (impacts risk & cost). The product vision should remain very high level and be easy to describe. - Product Roadmap: Releases - Date, Theme/Feature Set, Objective, Development Approach. + 2. Product Roadmap: Releases - Date, Theme/Feature Set, Objective, Development Approach. The product roadmap is a key tool in driving the priority of user stories in the development backlog. - Release Planning: Iteration, Team Capacity, Stories, Priority, Size, Estimates, Definition of Done. + 3. Release Planning: Iteration, Team Capacity, Stories, Priority, Size, Estimates, Definition of Done. When necessary, it is more common for the scope of a release to change, rather than the release date. - Sprint Planning: Stories - Tasks, Definition of Done, Level-of Effort, Commitment + 4. Sprint Planning: Stories - Tasks, Definition of Done, Level-of Effort, Commitment. This level of planning is driven by the Scrum development team members. Only the development team can determine what items are pulled from the product backlog to the sprint backlog. This is based on team capacity and level of complexity of the backlog items. - Daily Planning: What did I do yesterday? What will I do today? What is blocking me? + 5. Daily Planning: What did I do yesterday? What will I do today? What is blocking me? This daily meeting keeps the team on track to accomplish the sprint goal, and over time, bring the product vision in to reality. ### Visual Representation