Timeline for Do we need to update time estimates when we estimate based on story points?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 27, 2017 at 11:58 | history | edited | Sergey Kudryavtsev | CC BY-SA 3.0 |
added 442 characters in body
|
| Jul 27, 2017 at 8:03 | history | edited | Sergey Kudryavtsev | CC BY-SA 3.0 |
added 55 characters in body
|
| Jul 27, 2017 at 7:51 | comment | added | Sergey Kudryavtsev | I have updated my answer. Please, update your question too. Your comment strongly clarifies the original question. | |
| Jul 27, 2017 at 7:42 | history | edited | Sergey Kudryavtsev | CC BY-SA 3.0 |
added 1006 characters in body
|
| Jul 27, 2017 at 7:00 | comment | added | Sergey Kudryavtsev | In that case you need to add second layer of estimation. Estimate your tasks by time and use these estimations for tracking progress during Sprint. As for Story Points, you can still use them for Release Burndown Chart. | |
| Jul 26, 2017 at 21:09 | comment | added | panyvi | Thanks for the answer.The structure of our teams are that they have stories and they break it down to several tasks, so a story might takes more than one sprint while people are working on different tasks below the story. In this way story point based burn down chart can't show any progress during the sprint. ( since the story might takes multiple sprints). That's why I need to work with (remaining time based burn down chart). Do you have any idea what would be the best solution for our team? | |
| Jul 25, 2017 at 7:17 | history | answered | Sergey Kudryavtsev | CC BY-SA 3.0 |