Timeline for Scrum Standup Format Improvements
Current License: CC BY-SA 2.5
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 29, 2010 at 23:06 | comment | added | Adam Porad | @timothymcgrath - How long are your sprints? Perhaps if you made the sprints shorter with less items, it might mitigate the problem of lower-priority tasks being worked on before the higher priority task are done. Also, you could try letting team members self-select the stories as they go during the sprint so they can pick the highest priority task remaining instead of assigning stories to the team at the beginning and hope that all the high pri tasks are done before the low pri tasks. Or if tasks need to be assigned then assign half at the start and then assign the rest half way through. | |
| Nov 27, 2010 at 12:49 | comment | added | Mahesh Velaga | @tim issue tracker covers for most of the stuff, it depends on how extensively/potentially we make the use of it. If the status of the case reflects the issue that it has, then its visible to the project manager. He can then have a take on it (probably that will come up in standup, if it needs to be discussed with the team). | |
| Nov 25, 2010 at 18:56 | comment | added | timothymcgrath | I agree that we make these decisions in the Planning Meeting. But one week into the Sprint, at one point do you ensure that everybody is on track and working on the correct items? Do you do this in standup? What if we have one developer working on an item of low priority because he finished all the high priority items that were assigned to him and is just working down his list. But there are more important tasks that he could be working on that are assigned to someone else? We use Microsoft TFS to track our items... | |
| Nov 25, 2010 at 18:12 | history | answered | Mahesh Velaga | CC BY-SA 2.5 |