Requirements Gathering in Software Projects
June 8, 2009 | Author: PM Hut | Filed under: Project Management Best Practices, Requirements Management
Requirements Gathering in Software Projects
By Dave Nielsen
Capturing requirements can be the most challenging part of a software development project. If you don’t get the requirements right, or miss key requirements, your project is in vain. Even if you do meet budget and schedule objectives, your project will fail to deliver the benefits your sponsors envisioned for it.
Here are some simple tips to follow in order to avoid a disaster. Be forewarned: these tips sound simple and straightforward but can be very tricky to implement. This is not meant to be a complete set of instructions for managing requirements on any project, it is meant to help you avoid some common pitfalls.
- Identify the right stakeholders to contribute requirements. The key stakeholders are the ones that will be using the software to conduct their business, the ones who will be maintaining it after deployment, and the business sponsor. Exclude those who wish to influence the outcome of the project but who don’t have a stake in the success of the project. If you’re given a list of stakeholders who should be included, verify that the list includes all the stakeholders.
- Identify the right requirements capture tools and techniques. You should choose techniques that are a fit for the stakeholders who will be defining their requirements and are suitable for the organization’s makeup. For example, if your stakeholders are a geographically diverse group, techniques such as storyboarding or brainstorming will not work.
- Work with your stakeholders to capture requirements in plain English. Requirements should speak to some aspect of the business benefit to be derived from the project. The requirement should be feasible (that is they should be possible to code by the development team). They should also be verifiable. To ensure a requirement is verifiable, ask the question: How are you going to test the requirement? If you don’t get an answer to that question, you need to work on the requirement to convert it into something that is verifiable.
- Define a schedule for the requirements gathering exercise that will allow building to start on time, and then stick to the schedule. Hold the stakeholders responsible for meeting their scheduled deadlines. Make sure the team understands that delivering requirements late will delay the project end date.
- Identify the approver, or approvers, for the requirements. This is the person, or people, who your business sponsor empowers to speak on their behalf, if the sponsor is not to be responsible for sign off. You will have to hold these people accountable for meeting the schedule deadlines. Don’t proceed to the build phase without the requirements having been approved.
- Identify each requirement with a unique id. This is the key to traceability. The id should be tracked in the functional specs, design specs, and tests.
These six simple tips build on the project management knowledge you will acquire with your PMP certification.
Dave is a principal with three O Project Solutions, the vendors of AceIt©. Dave was also the key architect responsible for the creation of the product. AceIt© has prepared Project Managers from around the world to pass their PMP® exams. You can find endorsements from some of his customers on three O’s web site (http://www.threeo.ca/).
Dave has over 20 years of experience managing projects of every size and training IT resources for companies like Nortel Networks and 724 Solutions. He most recently led a $100M project to upgrade a leading bank’s ATM network for Diebold Canada. Through three O Project Solutions, Dave has partnered with Infomaxium (http://www.infomaxium.com/) to offer classroom project management training. Dave has also helped prepare project managers to pass their PMP exam through the Lakeshore chapter of the PMI.
Related Articles
- Successfully Interviewing Your Project Customer and Gathering Project Requirements - Part I - Introduction
- Successfully Interviewing Your Project Customer and Gathering Project Requirements - Part VIII - Asking the Questions
- Successfully Interviewing Your Project Customer and Gathering Project Requirements - Part IX - Drill Down Questions
- Successfully Interviewing Your Project Customer and Gathering Project Requirements - Part V - Requirements Interview Process
- Successfully Interviewing Your Project Customer and Gathering Project Requirements - Part X - Model of Interview Questions
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.











1 person has left a comment
[...] other reason, it will cause all the dependent activities to slip. Once you’ve chosen your requirements gathering approach and the stakeholders you’ll meet with to gather the requirements, you can schedule [...]