This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note

Page References

Incoming links Outgoing links
Iteration Planning
Iteration Planning

Version management

Difference between version and

At line 1 added 42 lines
!!! Overview
[{$pagename}] is for the [Delivery Team] to __commit__ to the completion of a set of the highest-ranked product [backlog] items.
This commitment defines the [Sprint Backlog] and is based on the team's [velocity] or capacity and the length of the [Iteration].
!! Who Is Involved?
[{$pagename}] is a collaborative effort involving these roles:
* [Scrum Master]: Facilitates the meeting
* [Product Owner]: Represents the detail of the product backlog items and their acceptance criteria
* [Delivery Team] ([Scrum Team]): Define the tasks and effort necessary to fulfill the commitment
!! Before The [{$pagename}]
Before getting started, ensure:
* The items in the [Product Backlog] [backlog] have been sized by the [Scrum Team] and assigned a relative story point value
* The [Product Backlog] is stack ranked to reflect the priorities of the [Product Owner]
* There is a general understanding of the acceptance criteria for these ranked [Product Backlog] items
!! Equal Opportunity [Backlog]
The [Product Backlog] addresses new functionality and fixes to existing functionality. The order in which a [Product Backlog] item is scheduled is completely independent of its ancestry.
For the purpose of [{$pagename}], the important characteristics for a product [backlog] item are:
* It is small enough to be completed in the [Iteration]
* We can verify it has been implemented correctly
!! Right-Size [Backlog] Items
[Product Backlog] items too large to be completed in an [Iteration] need to be split into smaller pieces. The best way to split [Product Backlog] items is by [Business value], not by process.
If we can split a [Product Backlog] item so that its children deliver value, then our [iterations] incrementally deliver value. If you split by process, then we impact time-to-market because value is not delivered until all the children are complete.
Compound stories can be easily split through disaggregation. Complex stories present a different challenge. Bill Wake enumerates [twenty techniques|http://xp123.com/xplor/xp0512/index.shtml|target='_blank']
!! Using [Velocity] and [Capacity] for [{$pagename}]
Mature teams can use Using [Velocity] and [Capacity] for [{$pagename}]
!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
----
* [#1] - [iteration-planning|https://help.rallydev.com/iteration-planning|target='_blank'] - based on information obtained 2016-12-08-
* [#2] - [Iteration-planning/|https://www.scaledagileframework.com/iteration-planning/|target='_blank'] - based on information obtained 2019-11-14
This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthorTop