ProjectConnections Print View
888-722-5235
7am-5pm Pacific
Monday - Friday
We'd love to talk to you.
Learn more about ProjectConnections and who writes our content.
| Content Levels | |
 | Register for free access to papers, case studies, and almost 50 templates. |
 | Subscribe for complete access: $14.95 monthly or $149/year |
| Risk-free 15-day trial!
Compare levels View sample templates Corporate subscriptions | |
Requirements Change Management Guideline
Quick Summary
If you're not doing impact evaluation and communication, you're not doing change management. This guideline condenses 20 years of lessons learned to provide a complete overview of change management components, processes, and controls.
What this is
A guideline written by an experienced software development executive describing the importance of and the requirements for implementing comprehensive requirements change management. Building on 20 years of lessons learned, this guideline provides the suggested components, processes, and workflows for a robust change management system. It also argues convincingly the need to include evaluation and communication of the impacts of any change requests.
Why it's useful
Change is inevitable. Knowing how to handle changes and requests for changes is vital to delivering the right product on time. Properly estimating the impact of a requested change is one of the most important jobs of the engineering manager, and communicating that impact in a clear way is vital to the success of the project. It's almost embarrassing to ask for an additional 4 hours of budget for a change, and perhaps that's not always necessary. But the cumulative effect of 50 4-hour changes–that's easier to understand and shows why it's necessary to have a process that includes impact evaluation and documentation.The case illustrations and lessons learned will also be helpful for anyone trying to build a business case for implementing a requirements management system in their organization.
How to use it
To implement change management successfully, three elements must be defined, implemented, and adopted. This guideline provides an overview and practical examples for all three elements:
- A Requirements Management System, for creating and tracking requirement baselines. This can be created in a spreadsheet or in a dedicated requirements management tool.
- A Change Process, with no exceptions or circumvention allowed. A typical software change process is illustrated.
- A Change Tracking System to keep track of it all. Suggested elements and workflow are provided.
Software Requirements Capture Guideline
Detailed guidelines from an experienced software development executive.
Change Control Form
A form for requesting and documenting changes and their projected impact.
©Copyright 2000-2008 Emprend, Inc. All Rights Reserved.
About us Site Map View current sponsorship opportunities (PDF)
Contact us for more information or e-mail info@projectconnections.com
Terms of Service and Privacy Policy