Hans Samios' Knowledge Base

... absolutely #noabsolutes ...

User Tools

Site Tools


how_should_we_initially_track_sprint_progress

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
how_should_we_initially_track_sprint_progress [2020/06/02 14:21]
127.0.0.1 external edit
how_should_we_initially_track_sprint_progress [2020/06/04 08:13] (current)
hans Removed LINKBACK
Line 1: Line 1:
 ====== How Should We Initially Track Sprint Progress? ====== ====== How Should We Initially Track Sprint Progress? ======
- 
-====== Premise ====== 
  
 In general the best approach to tracking Sprint progress when you get started is through a manual big visible chart showing tasks moving through "To Do", "In Progress", and "Done" steps, and a chart showing the Sprint Burn-down, also manual. The reason we do this is so that teams can learn and understand how a Sprint is supposed to work without having to also learn the nuances (and potential changes in behavior) required by a tool. In general the best approach to tracking Sprint progress when you get started is through a manual big visible chart showing tasks moving through "To Do", "In Progress", and "Done" steps, and a chart showing the Sprint Burn-down, also manual. The reason we do this is so that teams can learn and understand how a Sprint is supposed to work without having to also learn the nuances (and potential changes in behavior) required by a tool.
Line 35: Line 33:
 {{tag>Consultant Tools SprintBurndown Interruptions FirstSprint FAQ}} {{tag>Consultant Tools SprintBurndown Interruptions FirstSprint FAQ}}
  
- 
-~~LINKBACK~~ 
-~~DISCUSSION~~ 
/home/hpsamios/hanssamios.com/dokuwiki/data/pages/how_should_we_initially_track_sprint_progress.txt ยท Last modified: 2020/06/04 08:13 by hans