Timeline for Can I break a user story down after work as already started?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 30, 2016 at 12:36 | history | edited | Ewan | CC BY-SA 3.0 |
added 219 characters in body
|
| Jun 29, 2016 at 17:45 | comment | added | Alexander Averchenko | Never had problems with it. Perhaps its a project architecture and industry dependent. | |
| Jun 29, 2016 at 17:40 | comment | added | Ewan | yes, even then. Just leave it alone and wait | |
| Jun 29, 2016 at 17:31 | comment | added | Alexander Averchenko | If it is the microservices then no. | |
| Jun 29, 2016 at 17:30 | comment | added | Ewan | No. Its a very bad idea. You will screw up the architecture | |
| Jun 29, 2016 at 17:29 | comment | added | Alexander Averchenko | I get your point, but in most case's you see what has been committed to git, and present on CI, and hear the progress on daily standups, so you can chop the story's that are not affected. It's a rare things to see, that developers start to implement everything in a big story at once. Typically they make their own undocumented split. | |
| Jun 29, 2016 at 17:27 | comment | added | Ewan | Its equivilant to saying, spend a week redoing that bit so we can split this 2 week task into 2 1 week tasks | |
| Jun 29, 2016 at 17:25 | comment | added | Ewan | because work.has already started so some of those components will be written. If you change requirements you are pulling the rug out from under the team | |
| Jun 29, 2016 at 17:23 | comment | added | Alexander Averchenko | Why, I can add interface requirements to new story's and throw them to backlog. | |
| Jun 29, 2016 at 17:20 | history | answered | Ewan | CC BY-SA 3.0 |