Difference between revisions of "Snapshot delivery"
Jump to navigation
Jump to search
(Zeroth version.) |
m (Typo.) |
||
| Line 4: | Line 4: | ||
|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 in a single line=Always being able to release new features and changes makes planning easier and more flexible. | |wish in a single line=Always being able to release new features and changes makes planning easier and more flexible. | ||
|therefore in a single line=Make sure that everything that comes out of the build cycle is | |therefore in a single line=Make sure that everything that comes out of the build cycle is ready to release so that you effortlessly can deploy it. | ||
|wish=Always being able to release and deploy 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. | ||
|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. | |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. | ||
Revision as of 12:46, 3 April 2013
…one or more squads and/or tribes working had to get things done.
✣ ✣ ✣
{{{wish full}}}
Therefore:
{{{therefore full}}}
✣ ✣ ✣
Consider the end of a sprint as a snapshot delivery. Even finer granularity: consider getting a single work item as a snapshot delivery.
✣ ✣ ✣