Difference between revisions of "Agile shock therapy"
Jump to navigation
Jump to search
(Zeroth version.) |
({{p|daily scrum}},) |
||
Line 6: | Line 6: | ||
*Use Story Points Only for all estimates. | *Use Story Points Only for all estimates. | ||
*Use {{p|physical information radiators}} only. | *Use {{p|physical information radiators}} only. | ||
*Limit the weekly {{p|sprint review meeting}}, {{p|sprint retrospective meeting}} and {{p|sprint planning meeting}} to a total of four hours. | *Limit the {{p|daily scrum}}, weekly {{p|sprint review meeting}}, {{p|sprint retrospective meeting}} and {{p|sprint planning meeting}} to a total of four hours. | ||
*{{p|first things first}}—work in priority order only. | *{{p|first things first}}—work in priority order only. | ||
*{{p|single piece flow}}—work single-tasking only. | *{{p|single piece flow}}—work single-tasking only. |
Revision as of 09:54, 10 May 2013
The core of Jeff Sutherland » Scrum “Shock Therapy” How To Change Teams FAST:
- Organize Scrum Training for Everyone.
- Opt for One Week Sprints.
- Start with a precooked ready to build (Defintion of Ready) and evolve it.
- Start with a precooked ready to ship (Definition of Done) and evolve it.
- Use Story Points Only for all estimates.
- Use physical information radiators only.
- Limit the daily scrum, weekly sprint review meeting, sprint retrospective meeting and sprint planning meeting to a total of four hours.
- first things first—work in priority order only.
- single piece flow—work single-tasking only.
- start what you finish and finish what you start
Joined at the hip with scrum jumpstart.