Please enable JavaScript.
Coggle requires JavaScript to display documents.
ADAPTIVE PLANNING - Coggle Diagram
ADAPTIVE PLANNING
-
- Release Planning
a group of iterations
HOW
• Assess the prioritized backlog and review the sizing of stories, resizing them as needed.
• Sort the stories by release, selecting those that will be in the upcoming release, the next release, and future releases.
• Refine our initial outline or roadmap for the upcoming release, changing it as needed.
• Slice the stories that will be done in the upcoming release into pieces of work that are small enough to be completed within one iteration.
Slicing Compound Stories
Slicing Complex Stories
=> Conditions of satisfaction -> estimating user stories -> prioritizing user stories -> selecting release date.
OUTPUT
Release goal, A list of the stories, A roadmap for completing those stories, A rough outline
-
TOOLS: affinity estimating, product roadmap, release Backlog, Refining (Grooming) the Backlog, Story Point
-
-
WHY • Determine which stories will be done in which iterations for the upcoming release and, in less detail, for the subsequent releases
-
-
WHO: the delivery team, PO, có thể có các bên liên quan, hoặc subject matter experts nếu cần.
TOOLS: User story, Story Point, Planning Poker, Iteration Backlog
Spike (Architectural Spike,Risk – based Spike), Fast Failture
HOW?
- Discuss the user stories in the
backlog
- Select the user stories for the
iteration
- Define the acceptance criteria and write the
acceptance tests for the stories
- Break stories into tasks
- Estimate the tasks
ITERATION PLANNING
- 1st half of the meeting: PO trình bày backlog mới, sprint goal, cần làm những gì
- 2nd half of the meeting: team làm thế nào để thực hiện,sizing, estimate=> Sprint backlog
ITERATION
là một giai đoạn phát triển ngắn, có khung thời gian (a short – timeboxed development period), thường là từ 1 đến kéo dài 4 tuần
Types of Iteration: Iteration 0, Iteration H, Development Iterations
Tools: Spikes: Architectural Spike, Risk – based Spike
Fast Failure
-
HOW
- Identifying and roughly sizing the product features and user stories
- Create our initial coarse-grained estimates
OUTPUTS
An updated, prioritized backlog
High-level (coarse-grained) relative estimates
A release goal
A target date for the release
WHO: product owner, sponsor, key members of the delivery team, major stakeholders
TOOLS: affinity estimating, T-shirt sizing, story maps, and the product roadmap
HOW
- Stand-ups are for realizing there are problems – not for solving them. Time-box: 15 minutes, Daily
- 3 question
What have you worked?
What do you plan to finish today?
Are there any problems or impediments?
- Ground rules
-
-