Timeline for how to estimate multiple stories with less complexity?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 19, 2018 at 21:13 | comment | added | Daniel | Since the suggestion actually gets to the person who is looking for the information, it seems like nvoigt's approach is perfectly in line with User Stories. | |
| Jun 19, 2018 at 17:00 | comment | added | nvoigt | Maybe, I don't know. It's my experience of what works. I don't know any resource or guideline suggesting I cut it into three stories. INVEST only says "small", not "as small as possible". | |
| Jun 19, 2018 at 16:56 | comment | added | maverick | any resource or guideline which backs up this approach or backs up what you are recommending? | |
| Jun 19, 2018 at 16:54 | comment | added | nvoigt |
Ah, I guess if that is that easy, just proceed to the second part. Wrap it into one story "As a sysamin, I want to see user-tracking data in my reports so I can..." and proceed. Maybe it's a 1 then or a 2. Nobody forces you to combine three stories of 1 into a 3. Those numbers are not good for calculating, their only use is to determine which one is larger.
|
|
| Jun 19, 2018 at 16:51 | comment | added | maverick | This screen is already done and on production. We just want to track it, as mentioned in the first line "We want to track user activity on this screen " | |
| Jun 19, 2018 at 16:49 | history | answered | nvoigt | CC BY-SA 4.0 |