Timeline for Should I remove a User Story from a Sprint in progress if I know we can't complete it?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 18, 2020 at 8:23 | history | edited | CommunityBot |
Commonmark migration
|
|
| S May 2, 2019 at 12:36 | history | suggested | Toby Speight | CC BY-SA 4.0 |
Spelling and grammar fixes, and some small readability improvements
|
| May 1, 2019 at 16:21 | review | Suggested edits | |||
| S May 2, 2019 at 12:36 | |||||
| May 6, 2015 at 11:03 | history | edited | jessehouwing | CC BY-SA 3.0 |
added 4 characters in body
|
| May 6, 2015 at 3:38 | vote | accept | Lalit Singh Rana | ||
| May 6, 2015 at 3:38 | vote | accept | Lalit Singh Rana | ||
| May 6, 2015 at 3:38 | |||||
| May 5, 2015 at 12:02 | history | edited | jessehouwing | CC BY-SA 3.0 |
added 1527 characters in body
|
| May 5, 2015 at 10:33 | comment | added | David Arno | @LalitSinghRana, if the story is dropped, then the burndown will show you finishing early. The sprint review should then cover this and the reason why (a story had to be dropped). The retrospective should then examine the reasons why the story had to dropped and how to avoid scheduling a story too early in future. | |
| May 5, 2015 at 9:32 | comment | added | Lalit Singh Rana | Thanks, but I was thinking that it should not be allowed altogether (to drop a story midsprint). Now suppose we do it, what would be the impact on a) burndown b)Sprint Review report - we would be showcasing a reduced planned velocity, which we are able to achieve and all would look green? | |
| May 5, 2015 at 8:15 | history | answered | jessehouwing | CC BY-SA 3.0 |