Timeline for A User Story that crosses components
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 11, 2014 at 19:29 | comment | added | Sklivvz | @user1888440 I've flagged and removed your comment. Please remember to keep your comments on topic and your tone constructive. | |
| Feb 10, 2014 at 21:22 | comment | added | Dave Hillier | @user1888440 to be fair, your question contains the assumption that you should split the work between the two teams in a particular way. You're really only for confirmation of what you already know. Sklivvz answer actually does answer your question, but it isnt what you wanted to hear. | |
| Feb 7, 2014 at 0:14 | comment | added | Sklivvz | I did answer the question in the other 4 paragraphs | |
| Feb 7, 2014 at 0:11 | comment | added | robert_difalco | Okay, so you are just generally commenting not answering the question. | |
| Feb 7, 2014 at 0:09 | comment | added | Sklivvz | @user1888440: I don't mean to imply that this is the case in this question! | |
| Feb 7, 2014 at 0:07 | comment | added | robert_difalco | I'm not sure what you are saying. Who said anything about fixing agile? I was just asking about the best way to handle stories with a remote team in a multi-component/multi-tiered environment. That's all. | |
| Feb 6, 2014 at 21:25 | history | answered | Sklivvz | CC BY-SA 3.0 |