Difference between revisions of "Snapshot delivery"
Jump to navigation
Jump to search
m (Typo.) |
m (terse/full) |
||
Line 3: | Line 3: | ||
|theme=Agile, Scrum | |theme=Agile, Scrum | ||
|context=one or more {{p|squad}}s and/or {{p|tribe}}s working had to get things done. | |context=one or more {{p|squad}}s and/or {{p|tribe}}s working had to get things done. | ||
|wish | |goal=easy, flexible planning | ||
| | |wish=Always being able to release new features and changes makes planning easier and more flexible. | ||
|wish=Always being able to release and deploy new features and changes makes planning easier and more flexible. | |so=Make sure that everything that comes out of the build cycle is ready to release so that you effortlessly can deploy it. | ||
|therefore=Make sure that everything that comes out of the build cycle is {{p|ready to release}} so that you effortlessly can deploy it on any date. | |wish full=Always being able to release and deploy new features and changes makes planning easier and more flexible. | ||
|therefore full=Make sure that everything that comes out of the build cycle is {{p|ready to release}} so that you effortlessly can deploy it on any date. | |||
|new=Consider the end of a {{p|sprint}} as a {{p|snapshot delivery}}. Even finer granularity: consider getting a single work item as a {{p|snapshot delivery}}. | |new=Consider the end of a {{p|sprint}} as a {{p|snapshot delivery}}. Even finer granularity: consider getting a single work item as a {{p|snapshot delivery}}. | ||
}} | }} |
Latest revision as of 10:31, 16 June 2013
…one or more squads and/or tribes working had to get things done.
✣ ✣ ✣
Always being able to release and deploy new features and changes makes planning easier and more flexible.
Therefore:
Make sure that everything that comes out of the build cycle is ready to release so that you effortlessly can deploy it on any date.
✣ ✣ ✣
Consider the end of a sprint as a snapshot delivery. Even finer granularity: consider getting a single work item as a snapshot delivery.
✣ ✣ ✣