Requirements management involves establishing and maintaining agreement between customer and developer on both technical and non-technical requirements. This agreement forms the basis for estimating, planning, performing, and tracking project activities throughout the project and for maintaining and enhancing developed software. Key activities include:

Some models, such as the Software Engineering Institute's CMMI, put some of these activities in other process areas such as requirements engineering, project management, or configuration management.

RM Plans

The RM plan is a component of the project management plan. Generally, the purpose of RM is to ensure customer and developer have a common understanding of what the requirements for an undertaking are. Several subordinate goals must be met for this to take place: in particular, requirements must be of good quality and change must be controlled. The plan documents how these goals will be achieved. Depending on your project standards, a variety of sections might be included in your RM plan. Some examples are:

I have The Project Manager's Desk Reference and Effective Requirements Practices in my library and recommend them both. Effective Requirements Practices contains templates and practical instructions for developing RM plans, policies, and processes. The author works for a CMM level 5 organization. Find them and more at Amazon.

Download an RM Plan template

Requirements Management Metrics

Vital information to help manage other work can come from the RM process. For example, associating costs with requirements and using the data to estimate similar work can help improve cost estimates. The development processes must be stable enough and similar to make cost data comparisons.

Some measures used for RM include:

Visit the Practical Software and Systems Measurement site.

Next page

Page updated 6/12/2013
Ludwig Consulting Services, LLC