3 tips to improve requirements management
November 14, 2007 | Author: PM Hut | Filed under: Communications Management
3 tips to improve requirements management
By Craig Brown
Darren tells us that user requirements are at the top of the list of reasons why project fail. No surprises there.
But he elaborates; it’s not the elicitation of the requirements, it’s the communication of them to the developers, and the dev team’s understanding of them that is where the problem is occurring.
It’s no surprise when you consider the long liked communications process that often occurs, especially in large organisations. It’s even more obvious when you consider outsourced development houses that don’t have much business or even industry domain knowledge. How does a fresh develop with no history with the client organisation fill in the gaps in the communicated requirements?
Avoid requirements failure by doing these things;
- Have developers feed back their interpretation of requirements to the stakeholders and clients. Do it early and often. Use workshops, wireframes, prototypes, or documents, but do it.
- Bring the subject matter experts and requirements owners into the same room as the developers. Get them talking to each other. If you can’t be in the same room, arrange regular meetings. Don’t rely on written communication.
- Make sure your BAs are trained and highly skilled at requirements management (ie not just elicitation, but the whole shebang.)
Business Analysts are the main key to successful projects. Pay them more and pat them on the back when they do a good job.
Craig Brown has worked as a project manager and business analyst mainly in the Australian ITC and the banking industries. He has also worked in the law, education and welfare industries, including starting a law firm. Craig now has a Master’s degree in project management from RMIT university, and is currently working with a Melbourne based IT consulting firm called OptimiseIT. Craig’s personal blog can be found at http://betterprojects.blogspot.com.
Related Articles
- A Project Management Primer - Scope - Requirements
- A Project Management Primer - Scope - Requirements - Stakeholders
- A Project Management Primer - Scope - Requirements Capture - Introduction
- A Project Management Primer - Scope - Requirements Capture - Interviews
- A Project Management Primer - Scope - Requirements - Functional Requirements
No comments yet.
feel free to leave a comment
Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!
XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
All fields marked with " * " are required.










