Timeline for How do you reduce card size and limit scope creep in R&D tasks?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 20, 2017 at 13:10 | vote | accept | Balala | ||
| Oct 17, 2017 at 19:42 | comment | added | Balala | Thanks for your comments. I guess I don't mean to speed up research as much as I want to reduce card size. We're just finding it a bit hard to decompose those cards into smaller chunks, which as @CodeGnome suggests should be possible most of the time. | |
| Oct 16, 2017 at 20:41 | answer | added | Todd A. Jacobs♦ | timeline score: 6 | |
| Oct 16, 2017 at 15:31 | comment | added | Alan Larimer | Which is most valuable, speed or outcomes? (a bit rhetorical) | |
| Oct 16, 2017 at 15:29 | answer | added | David Espina | timeline score: 1 | |
| Oct 16, 2017 at 15:23 | comment | added | Thomas Owens♦ | "Scrum is a framework for developing and sustaining complex products" (from the Scrum Guide). Kanban has its roots in manufacturing and product development. I think that both can give a useful foundation for managing research efforts, but are you sure that you're using the right tools? It seems like you're trying to speed up research. If you're doing something closer to pure research, should you be trying to speed it up? | |
| Oct 16, 2017 at 15:15 | history | asked | Balala | CC BY-SA 3.0 |