Timeline for Frustrating on time tracking
Current License: CC BY-SA 4.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jan 20, 2023 at 15:10 | history | edited | Thomas Owens♦ | CC BY-SA 4.0 |
deleted 84 characters in body
|
Mar 24, 2022 at 20:42 | history | edited | Thomas Owens♦ | CC BY-SA 4.0 |
deleted 522 characters in body
|
May 3, 2018 at 9:58 | history | edited | Thomas Owens♦ | CC BY-SA 4.0 |
deleted 149 characters in body
|
Apr 5, 2016 at 7:44 | comment | added | Bart van Ingen Schenau | @Love: Yes, you can add new sub-tasks to a story mid-sprint. You should mention in the daily standup that you found something that was overlooked in the planning (which will happen) and that such-and-such task is also needed to complete the work. | |
Apr 4, 2016 at 19:22 | comment | added | Love | @ThomasOwens, thanks. If I find I need to add something to the story. Can I create a new sub-task during the middle of the sprint? | |
Apr 4, 2016 at 18:26 | comment | added | Thomas Owens♦ | @RobertHarvey No, there's no direct and consistent translation from Story Points into Actual Hours. Personally, I don't believe in "Story Points or Nothing" - estimating in hours is totally OK, as long as it includes all necessary tasks and the team comes up with the estimate. The advantage to Story Points is that it can't be tied to hours, so it helps management make the transition to a more agile thinking by eliminating old ways. | |
Apr 4, 2016 at 18:24 | comment | added | Robert Harvey | Do Agile story points eventually translate into actual hours via some formula or other mechanism? I'm not sure how moving from vague estimates in real hours to vaguer estimates in fictional story points improves matters. | |
Apr 4, 2016 at 16:56 | vote | accept | Love | ||
Apr 4, 2016 at 16:43 | comment | added | user53141 | A key point is that in Agile it is all about team performance, not individual performance. | |
Apr 4, 2016 at 16:20 | history | answered | Thomas Owens♦ | CC BY-SA 3.0 |