A requirement gathering is a vital element of any project organization. What project will deliver is significant to its success but it is difficult to understand. This is the area where everyone has to provide more concentration. If person doesn't comprehend the clients need appropriately then that project starts with the barest headline list of requirements. This type of problem is very serious as well as it is widespread because most of the time many projects experience this.
The following document will guide to the main requirements of the project:
- A concise prerequisite specification for organization purposes.
- A statement of key objectives – a "cardinal points" specification.
- An explanation of the atmosphere in which the system will work.
- Background information and references to other relevant material.
- Information on major design constraints.
The contents of the statement of requirements should be constant or change moderately gradually.Once you have formed your report of requirements, ensure the client and all other stakeholders sign-up to it and appreciate that this and only this will be delivered. Lastly, make sure you have cross-checked the prerequisites in the statement of requirements with those in the project description report to ensure there is no disparity.
Here, we listed some common mistakes which usually occur:
- Basing an explanation on compound or critical edge technology and then realizing that it cannot simply be rolled out to the 'real world'.
- Not prioritizing the User Requirements, for example 'must have', 'should have', 'could have' and 'would have,' known as the Moscow principle.
- Not sufficient conversation with real users and practitioners.
- Resolving the 'problem' before you know what it is.
- Missing a clear understanding and creating suppositions rather than inquiring.
A requirement gathering is about creating a clear, concise and agreed set of customer requirements that allow you to provide exactly what they are looking for.
To be successful at prerequisites gathering and to give your project an increased possibility of success, follow these rules:
- Don't assume you know what the customer wants, always ask.
- Involve the users from the start.
- Define and agree the scope of the project with user.
- Ensure requirements are specific, realistic and measurable.
- Gain clarity if there is any doubt.
- Create a clear, concise and thorough requirements document and share it with the customer.
- Confirm your understanding of the requirements with the customer.
- Avoid talking technology or solutions until the requirements are fully understood.
- Get the requirements agreed with the stakeholders before the project starts.
- Create a prototype if necessary to confirm or refine the customers' requirements.
by Preeti DG