Difference between revisions of "Daily standup"

From Pearl Language
Jump to navigation Jump to search
m (terse/full)
(Goal.)
Line 1: Line 1:
{{Oyster
{{Oyster
|goal=keep track of work in progress, and move it towards the finish quickly
|stage=Germ
|stage=Germ
|theme=Agile, Scrum
|theme=Agile, Scrum

Revision as of 13:31, 26 May 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.

✣  ✣  ✣



✣  ✣  ✣

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;