aaah that's a great template! I've used some that are similar, but recently I found myself finishing a feature with use cases that were approved, but on testing we find out it's not operationally allowed! Which is why I'm now asking for flowcharts for almost everything 🙈
on testing we find out it's not operationally allowed!
Without a concrete example it sounds like the existing system is too inflexible to satisfy the actual needs (i.e. approved use cases) of the user-base.
So while the flowcharts may prevent "wasting effort" they're just covering symptoms that are going to get worse as time goes on.
Also sometimes it's necessary to gather user stories to understand the needs better. Regardless of where these tactics may have originated from or where they are currently being used, it can be at times useful to "cherry pick" approaches without buying the whole farm.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Tried this yet? Alistair Cockburn: Basic Use Case Template (1996)
If anything, it gets across the multitude of decisions that have to be made.
aaah that's a great template! I've used some that are similar, but recently I found myself finishing a feature with use cases that were approved, but on testing we find out it's not operationally allowed! Which is why I'm now asking for flowcharts for almost everything 🙈
Thank you so much for sharing!
Without a concrete example it sounds like the existing system is too inflexible to satisfy the actual needs (i.e. approved use cases) of the user-base.
So while the flowcharts may prevent "wasting effort" they're just covering symptoms that are going to get worse as time goes on.
Also sometimes it's necessary to gather user stories to understand the needs better. Regardless of where these tactics may have originated from or where they are currently being used, it can be at times useful to "cherry pick" approaches without buying the whole farm.