Difference between revisions of "Scrum jumpstart"
Jump to navigation
Jump to search
m (→Improvement Suggestions: {{tag|process}}) |
({{usage|yesterday’s weather}}) |
||
| Line 1: | Line 1: | ||
To jumpstart {{p|scrum}}, use: | To jumpstart {{p|scrum}}, use: | ||
#{{ | #{{usage|stable team}}. | ||
#{{ | #{{usage|yesterday’s weather}}. | ||
#{{p|daily clean code}} to get defect free at the end of the {{p|sprint}}. | #{{p|daily clean code}} to get defect free at the end of the {{p|sprint}}. | ||
#{{p|first things first}} to get stuff done. | #{{p|first things first}} to get stuff done. | ||
Revision as of 15:15, 18 May 2013
To jumpstart scrum, use:
- stable team to sustain maximum results of human assets.
- yesterday’s weather to successfully pull product backlog items into a sprint and get them done.
- daily clean code to get defect free at the end of the sprint.
- first things first to get stuff done.
- start what you finish and finish what you start to really get things done.
- andon cord to deal with emergencies.
- boom buffer to deal with interruptions during the sprint.
- scrumming the scrum to ensure you continuously improve.
- happiness index to get teams to have fun while accelerating.
- teams that finish early accelerate faster to get hyperproductive.
Joined at the hip with scrum shock therapy.
Fuse with a healthy product jumpstart.
Poster
Sources
- http://www.targetprocess.com/articles/agile50months/
- Jeff' Sutherland's CSM slide deck.
Improvement Suggestions
- Create a wiki bus tour through all the steps.