Difference between revisions of "Daily standup"

From Pearl Language
Jump to navigation Jump to search
(To process)
m (+= Day-switch-poster.png)
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Oyster
{{Oyster
|goal=keep track of work in progress, and move it towards the finish quickly
|stage=Germ
|stage=Germ
|image=Day-switch-poster.png
|theme=Agile, Scrum
|theme=Agile, Scrum
|context=the {{p|development team}} is working within a {{p|sprint}}.
|context=the {{p|development team}} is working within a {{p|sprint}}.
|wish in a single line=Keeping track of the status of outstanding work keeps everyone's eye on the ball and helps planning your day.
|therefore in a single line=Have a short inspect-adapt meeting, that lasts at most 15 minutes, every day.
|wish=Keeping track of the status of outstanding work keeps everyone's eye on the ball and helps planning your day.
|wish=Keeping track of the status of outstanding work keeps everyone's eye on the ball and helps planning your day.
|background=Forces:
|so=Have a short inspect-adapt meeting, that lasts at most 15 minutes, every day.
|wish full=Keeping track of the status of outstanding work keeps everyone's eye on the ball and helps planning your day.
|background=The {{p|daily standup}} is intended to be a high energy team building and planning event.
 
Forces:
*too much time between meetings and you lose track;
*too much time between meetings and you lose track;
*too little time between meetings creates too much overhead;
*too little time between meetings creates too much overhead;
Line 13: Line 17:
*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=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==
Line 20: Line 24:
*PO must be there regularly;
*PO must be there regularly;
*SM may or may not attend; team can be autonomous, not needing SM;
*SM may or may not attend; team can be autonomous, not needing SM;
==Sources==
{{WebSourceListItem
|url=http://leankit.com/blog/2014/09/run-effective-standups-retrospectives/
|site=LeanKit
|person=Chris Hefley
|title=How to Run Effective Standups and Retrospectives
}}
{{WebSourceListItem
|url=https://blogs.blueskyline.com/2012/12/08/short-standups/
|site=Blue Skyline
|person=Andy Longshaw
|title=Short standups
}}
{{Source}}
{{Source}}

Latest revision as of 16:33, 22 March 2018

Day-switch-poster.png

…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.

The daily standup is intended to be a high energy team building and planning event.

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;

Sources