Timeline for How will handle multiple users in a user story
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 17, 2018 at 9:20 | vote | accept | Jithin Antony | ||
| Oct 12, 2018 at 15:39 | comment | added | AAT | I'm not trying to argue against your main point at all -- aiming for clarification and also to put a little more meat on the approach of splitting to more User Stories before the Team takes the work into a Sprint. My point about Tasks is just that we need to keep that in the Team's scope as a detail of how they implement the agreed Stories, again I am just looking to clarify rather than disagree. It's a good answer! | |
| Oct 12, 2018 at 15:11 | comment | added | daLegacy | 1) In terms of devs owning tasks- I said that in my answer and agree :) "the dev team may choose" (2) On your main point that the discussion to split or combine user stories is highly dependent on the exact environment - also agree. The details provided in the original question were laser focused and sparse - and I tried to frame my answer that "if there is truly only one thing that rises to a user story". That may have not come across clearly in my answer | |
| Oct 12, 2018 at 14:54 | comment | added | AAT | BTW we should not talk about Tasks unless we are on the Development Team. And even if a User Story is implemented as multiple Tasks, I do not think that means we should split it across multiple Sprints. User Stories must be completed within a Sprint except in (very!) exceptional circumstances. | |
| Oct 12, 2018 at 14:52 | comment | added | AAT | I think it would be possible, maybe advisable, that the PO and Team would agree - especially if the Story has quite a high estimate as it stands - to split this and create separate User Stories (for Trader and Adviser). That improves traceability, makes it more likely that one of those User Stories can be completed within a Sprint, gives us the option to drop the variant behaviour if the other role is not important enough, and gives a precedent for adding more Users who have special functionality later. | |
| Oct 12, 2018 at 13:48 | history | answered | daLegacy | CC BY-SA 4.0 |