To be successful in requirements gathering and to give Client projects an increased likelihood of success, DCPN have developed and implemented the following requirement gathering rules:
1. Don't assume you know what the Client wants - always ask and receive confirmation that DCPN’s understanding is correct.
2. Involve the all interested parties (i.e. stakeholders and users) from the start.
3. Define, agree and document the scope of the project with any changes going through formal change management so all parties understand the implications of the change are fully understood.
4. Make sure requirements and defined outcomes are SMART – (specific, measurable, agreed upon, realistic and time-based)
5. Gain clarity if there is any doubt.
6. Create a clear, concise and thorough requirements document and share it with the Client.
7. Confirm the Client’s understanding of the requirements alongside the Client and how they meet the Client’s documented and agreed outcomes.
8. Avoid talking technology or solutions until the requirements are fully understood.
9. Get the requirements agreed with all interested parties before the development project starts
10. Create a prototype, if necessary, to confirm or refine the Client’s requirements.
