Timeline for Daily Scrum when the team is just fixing bugs
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 5, 2013 at 0:34 | comment | added | Balog Pal | only if you execute some anti-SCRUM really, the daily SCRUM must be natural as breathing and take zarro overhead. Ok, I allow a full minute. If you have more, I suggest working on that. Finding a good time-point when work is not done anyway is a good start ;-) | |
| Jun 5, 2013 at 0:12 | comment | added | Bryan Oakley | While the actual meeting costs 15 seconds, the anticipation of the meeting and the loss of flow (and subsequent need to get back into a flow) can cost some developers a half hour or considerably more. | |
| Jun 4, 2013 at 13:01 | history | answered | Balog Pal | CC BY-SA 3.0 |