Timeline for How can I manage both user stories and other non-backlog tasks if using VersionOne?
Current License: CC BY-SA 3.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 12, 2013 at 5:06 | history | edited | jmort253 | CC BY-SA 3.0 |
moved VersionOne as part of the question title so it doesn't look like a tag in the question
|
| S Sep 11, 2013 at 18:18 | history | suggested | Danny Varod | CC BY-SA 3.0 |
This question seems to be specific to a tool: VersionOne, with other tools the question is not relevant.
|
| Sep 11, 2013 at 15:16 | history | tweeted | twitter.com/#!/StackProjects/status/377812942496210944 | ||
| Sep 11, 2013 at 14:31 | review | Suggested edits | |||
| S Sep 11, 2013 at 18:18 | |||||
| Sep 10, 2013 at 14:06 | answer | added | SpoonerNZ | timeline score: 0 | |
| Sep 6, 2013 at 18:39 | history | edited | Todd A. Jacobs♦ | CC BY-SA 3.0 |
Clarify question and retrofit for the Q&A format; reformatting; retagging; grammatical and semantic edits.
|
| Sep 6, 2013 at 18:32 | answer | added | Todd A. Jacobs♦ | timeline score: 3 | |
| Sep 6, 2013 at 18:01 | comment | added | TaskTracker | @CodeGnome Thank you for these insightful links! | |
| Sep 6, 2013 at 18:00 | vote | accept | TaskTracker | ||
| Sep 6, 2013 at 14:04 | comment | added | Todd A. Jacobs♦ | Work is work. See pm.stackexchange.com/a/6513/4271, pm.stackexchange.com/a/8618/4271, and pm.stackexchange.com/a/8682/4271 for some related answers on that topic. | |
| Sep 6, 2013 at 13:06 | answer | added | Aziz Shaikh | timeline score: 0 | |
| Sep 6, 2013 at 10:13 | comment | added | TaskTracker | @CodeGnome Do the really? Shouldn't backlog items have a measurable contribution to the shipping product (I.e. shouldn't they be "features")? Training does not fall into this definition. As for bugs - there are many of those, and many of them are very small, so we usually allocate a bulk time slot for bugs. Customer cases are handled similarly. As for research, my problem with adding it to the backlog is that it is dev-driven rather than product-driven. As I said, we're just starting with agile so we may be looking at this wrong. | |
| Sep 6, 2013 at 9:08 | comment | added | Todd A. Jacobs♦ | A user story is just a format for work items. Why can't you write user stories for your bugs, training, and research? They belong on the Product Backlog, too. | |
| Sep 6, 2013 at 8:29 | review | First posts | |||
| Sep 6, 2013 at 10:42 | |||||
| Sep 6, 2013 at 8:14 | history | asked | TaskTracker | CC BY-SA 3.0 |