10 Rules for Successful Requirements Gathering

To be successful at requirements gathering and to give your project an increased likelihood of success, we suggest following these simple rules:

1. Don't assume you know what the customer wants - ask.
2. Involve the users from the start – they are generally the ones with the most relevant and valuable opinions.
3. Define and agree the scope of the project up-front, it makes it far easier when it comes to tracking and measuring success at a later date.
4. Ensure requirements are specific, realistic and measurable.
5. Gain clarity if there is any doubt – a tight brief makes for an easier project.
6. Create a clear, concise and thorough requirements document and share it with the customer, ideally gaining sign-off early on.
7. Confirm your understanding of the requirements with the customer (play them back).
8. Avoid talking technology or solutions until the requirements are fully understood.
9. Get the requirements agreed with the stakeholders before the project starts.
10. Create a prototype if necessary to confirm or refine the customers' requirements.

Remember, requirements gathering is about creating a clear, concise and agreed set of customer requirements that allow you to provide exactly what they are looking for.  Bear this in mind throughout the project and you won’t go far wrong.

Comments

[Pete Doyle]

Really useful list Jamie, thanks. I'd just add a further one "Agree a process with your customer for what happens if or when requirements change". Particularly I'm finding in today's climate that businesses need to be flexible and change direction to seize opportunities. For me it's about embracing that fact but making sure there's an agreed way to support that and properly assess risk and impact to the bigger plan!

Pete