Forgetting to ask the "why" of a request, especially of features. Sometimes, the feature is actually a workaround for a bug that needs fixing.
Also, if you're in an industrial-manufacturing setting, always ask them to define in a flowchart what the heck they want, JEEEEEEEEZ (any other tips for this are welcomed sdjhfksdjhkdj)
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.
100% agree. Asking why someone wants something is really important.
A lot of customers I've had find it hard to be precise and abstract at the same time. They'll say things like "and then Johnny sends the document to Maria" while they mean "and then the reviewer uses system X to send the document to the archivist" or something. A flowchart can help but it's usually too much to ask (or seen as your job).
Yes, it's pretty nice how so much divination work can easily be cut out just by asking why someone wants something!
In my case since I work in an industrial setting, I need to know what context of the changes they want on a machine. I found myself finishing a feature only to be told that it's not operationally allowed, so, from now on if they want a change in process, I need to see a flowchart with the change. If it's just small changes then I can do those without a flowchart, but major features that affect how a machine is operated? you better give me a flowchart 😂
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.
Forgetting to ask the "why" of a request, especially of features. Sometimes, the feature is actually a workaround for a bug that needs fixing.
Also, if you're in an industrial-manufacturing setting, always ask them to define in a flowchart what the heck they want, JEEEEEEEEZ (any other tips for this are welcomed sdjhfksdjhkdj)
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.
100% agree. Asking why someone wants something is really important.
A lot of customers I've had find it hard to be precise and abstract at the same time. They'll say things like "and then Johnny sends the document to Maria" while they mean "and then the reviewer uses system X to send the document to the archivist" or something. A flowchart can help but it's usually too much to ask (or seen as your job).
Yes, it's pretty nice how so much divination work can easily be cut out just by asking why someone wants something!
In my case since I work in an industrial setting, I need to know what context of the changes they want on a machine. I found myself finishing a feature only to be told that it's not operationally allowed, so, from now on if they want a change in process, I need to see a flowchart with the change. If it's just small changes then I can do those without a flowchart, but major features that affect how a machine is operated? you better give me a flowchart 😂