Timeline for How to deal with constantly (~daily) changing requirements?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Nov 19, 2018 at 11:40 | history | suggested | user16244 | CC BY-SA 4.0 |
spelling and punctuation
|
| Nov 19, 2018 at 6:15 | review | Suggested edits | |||
| S Nov 19, 2018 at 11:40 | |||||
| Apr 10, 2017 at 12:55 | comment | added | Gryph | Yes, in an ideal world I'd agree with you - I'd prefer we sprint to finish all of the documentation, then determine work product from there. Unfortunately, you'll note in my question that this isn't really an option; we have ongoing processes that can't stop now to wait on the investigative portion. So what I need is a model or a tool for regaining some control, or at least facilitating decision making as a group. Kanban would work if it had enough buy-in, but management (and myself included), put the rapid changes down to making it not responsive enough. | |
| Apr 9, 2017 at 13:22 | history | answered | Ewan | CC BY-SA 3.0 |