Timeline for What work items would look like related to support for a solution in production already?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 18, 2020 at 8:23 | history | edited | CommunityBot |
Commonmark migration
|
|
| Apr 6, 2018 at 16:41 | comment | added | Barnaby Golden | It is probably best to do what the team and Product Owner feel most comfortable with. It's worth noting that making work items sub-tasks of stories doesn't make them any less important. In some ways it emphasises how important they are: we NEED to understand and document the system as it is critical to delivering business stories. It stops there being a conversation where it is suggested that understanding/documenting can be delayed while business value is delivered. | |
| Apr 6, 2018 at 12:07 | comment | added | BrooklynSon | Thank you Barnaby, it seems I always get two very polar answers for User Stories, some say it's only for Business Value, some are more flexible by using alternative stories such as "As a system admin,...". Even on google searches I get different answers, it's seems to just be a style approach. | |
| Apr 6, 2018 at 9:01 | history | answered | Barnaby Golden | CC BY-SA 3.0 |