There are seldom scenarios in which it is deemed okay to have ambiguous requirements; non-Agile IT projects are not one of them. It is pertinent to the delivery of the product that requirements are explicitly written down and create clarity. In a post for A Girl’s Guide to Project Management, Elizabeth Harrin elaborates on how to compose necessities.
Required of Good Requirements
Harrin gives three tips to begin the composition of business requirements:
- No ambiguity
- Be specific
- Verify with the customer.
There should be absolutely no ambiguity in the requests because that will only create confusion down the road. Perhaps conduct a brainstorming meeting in which everyone can elaborate on the portion of the project they wish to be in charge of. This is also the time to gain clarity on what the customer wants, even if it may be implausible. The brainstormed list should be as specific as possible, down to the color of the materials desired. Lastly, before a finalized list of necessities is sent to anyone, be sure it is indeed what the customer wanted. The stakeholders provide a unique perspective and if something looks off they can see it before the project begins.
If you do not wish to take on the task of making this list, there is always the option to call in the professionals. A business analyst has great knowledge on business processes, and they can help to eliminate any ambiguity. This list is an important building block to other elements of the project formation, so take it seriously and find the best way to tackle it.
Despite how beneficial the requirements phase is to a project, it is not unheard of for people to skip it in its entirety. If there is simply not enough time for this phase, it is imperative that you continuously work alongside your team to make adjustments as you go, so there is as much accuracy in the end result as possible. You can read the original post here: http://www.girlsguidetopm.com/2015/11/how-to-compile-business-requirements/