Difference between revisions of "Daily standup"
Jump to navigation
Jump to search
(Goal.) |
(+Therefore: daily intent.) |
||
| Line 14: | Line 14: | ||
*too much horizon for planned tasks makes you forget about them; | *too much horizon for planned tasks makes you forget about them; | ||
*too little horizon for planned tasks makes you lose direction. | *too little horizon for planned tasks makes you lose direction. | ||
|therefore full=Have a short inspect-adapt meeting, that lasts at most 15 minutes, every day. | |therefore full=Have a short inspect-adapt meeting, that lasts at most 15 minutes, every day. Reemphasize both the {{p|intent at least two levels up}} and today’s intent so everyone adjusts to each other based on what they know to be the intentions for the day. | ||
}} | }} | ||
==To process== | ==To process== | ||
Revision as of 10:44, 23 December 2013
…the development team is working within a sprint.
✣ ✣ ✣
Keeping track of the status of outstanding work keeps everyone's eye on the ball and helps planning your day.
Forces:
- too much time between meetings and you lose track;
- too little time between meetings creates too much overhead;
- too much detail about the status takes too long and sucks the energy out;
- too little detail about the status takes you in the dark;
- too much horizon for planned tasks makes you forget about them;
- too little horizon for planned tasks makes you lose direction.
Therefore:
Have a short inspect-adapt meeting, that lasts at most 15 minutes, every day. Reemphasize both the intent at least two levels up and today’s intent so everyone adjusts to each other based on what they know to be the intentions for the day.
✣ ✣ ✣
✣ ✣ ✣
To process
- use a ‘talking ball’ to self-organize who speaks and give everyone attention;
- discuss who can be at the standup and their etiquette
- PO must be there regularly;
- SM may or may not attend; team can be autonomous, not needing SM;