| Delivery Process: Release |
| |
 |
| Phases, sprints and tasks to roll-out during a release production. |
|
Scope
Scrum does not describe all the software development activities (analysis, design, coding, testing) and must be considered,
rather than a full process, more as a process pattern to use for project and requirement management.
Scrum does not provide help to achieve development technical activities. |
Purpose
Relationships
Description
The production of a software version (Release) is usually
done in a couple of months. Potential release features are collected in a the product backlog and prioritized. The product
owner is in charge of updates to this backlog.
The release is produced with a series of iterations from 2 to 4 weeks called Sprints. A Sprint
content is defined by the product owner, taking both priorities and team capabilities into consideration . The team defines
required tasks to develop selected features for the Sprint.
Within a sprint, progress checkpoints are performed during Daily Scrums. This enables the ScrumMaster to figure work
progress in regards to Sprint goals and to suggest adjustments to ensure Sprint success.
At the end of each Sprint, the team produces a Product increment potentially releasable, which evaluation drives a backlog update for the next Sprint. |
Properties
| Event-Driven |  |
| Multiple Occurrences | |
| Ongoing | |
| Optional | |
| Planned |  |
| Repeatable | |
Staffing
| A Scrum team is composed of 3 to 10 persons. |
Key Considerations
Scrum contributes to strengthen teaming during projects, with a collection of best practices close to those which one
can find in team sports, rugby in particular.
|
More Information
|
