Timeline for How do I capture business workflow in a user story?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 3, 2019 at 20:49 | vote | accept | sgb1960 | ||
| Mar 2, 2019 at 11:09 | answer | added | Todd A. Jacobs♦ | timeline score: 3 | |
| Mar 1, 2019 at 11:03 | comment | added | sgb1960 | @ToddA.Jacobs - in our organisation's adoption of agile, it would seem that stories are specifications. They are what we test against, carry out UAT on and finally declare as DONE. I think if they were only conversation starters then UAT and DONE etc would need to be done against some other artefact. Having said that, I agree with you that actually they should be that. But if that is the case, then where do you recommend holding the detail that gets generated from the conversations you have started? | |
| Mar 1, 2019 at 11:00 | comment | added | sgb1960 | @TiagoCardoso - backend stories, I think. They are around the workflow path to be followed based on the initial captured parameters. To add a little more detail this is a document signature process - sometimes it requires 2 parties to sign, sometimes 1 and the order of signing can vary. Depending on the parameters captured the automation has to drive the sequence accordingly. | |
| Mar 1, 2019 at 2:23 | comment | added | Todd A. Jacobs♦ | Stories are not specifications. They are conversation starters. | |
| Feb 28, 2019 at 23:00 | comment | added | Tiago Cardoso | Hi, I'm not sure if these stories are backend or frontend oriented. I'd guess they're backend but would be good if you could confirm that. | |
| Feb 28, 2019 at 6:45 | answer | added | Bart | timeline score: 2 | |
| Feb 28, 2019 at 0:51 | answer | added | Daniel | timeline score: 2 | |
| Feb 28, 2019 at 0:05 | review | First posts | |||
| Feb 28, 2019 at 8:56 | |||||
| Feb 28, 2019 at 0:00 | history | asked | sgb1960 | CC BY-SA 4.0 |