This is my checklist I have in a doc and occasionally review (normally after something goes wrong).
I find over time you internalise these questions and they just 'pop up' at the right time but in the beginning I kept them with me most of the time.
When something goes wrong I do a review and normally come up with a question.
Some of these will obviously be specific to my situation/organisation but have kept everything as it may trigger something helpful for you :)
Understanding the requirement
- What’s the problem?
- What solution are you suggesting?
- What’s the ultimate purpose?
What are we trying to achieve?
Prioritising the request
- How does this add value to the company?
- How important is this to you?
- Is this urgent?
- Is there time sensitivity? Is there a deadline?
- When will this be complete?
- Define ‘done’
- Write the UAT with the stakeholder if possible..
- What are the must-haves?
- What are the like-to-haves?
- So, if it does ABC you’ll be happy?
- Are there any specific technical requirements?
- What are the edge-cases?
- How many different ways will people use this?
- Are there any points of confusion?
- Anything I don’t understand?
- Can you explain what this means? Can you explain what you mean by that?
implement the story in your mind
- How will we do this?
- What decisions does it require?
- What obstacles could we come up against?
- get necessary info from the stakeholder
Note, this is the 'full list' for big projects. I rarely ask all these questions but once you get used to them you get a feel for what should be asked.
I think more important than the list is your process of reviewing what went wrong, finding the right question for you and having a system to remind you to ask it at the appropriate time.