How to Manage Changing Business Requirements

Managing requirements change has been a major challenge even for the best-run projects. Keeping track of how the changing business environment impacts ongoing projects and production applications can be a nightmare without proper tools and techniques. The concept of requirements management is not new but with an increase in the use of off-shore developers and off-the-shelf solutions, it has become much more significant for information technology projects.

Requirements management starts with a well-developed Requirements Document (RD) which expresses a business need without regard for the underlying technology. A System Requirements Specifications (SRS) represents the details of the technical solution that will, upon implementation, meet the business needs. Application components from code, data, procedures, to test data and help facilities are all created based on the business requirements and technical specifications. Any and all of these are subject to change whenever the business needs changes. A well-defined requirements management methodology is your best protection against the changing world.

Defend the case for requirements management
Select the requirements management components most critical to you
Explain how requirements management facilitates impact analysis
Adapt requirements management philosophy to fit your organization
Develop a minimalist set of requirements management standards and guidelines
Use a change control log and a change request document

ILT: .5 - 1 day
Virtual: 0 Mods

Business Analysts
Business Managers
End-users
Project Leaders
Systems Analysts
Anyone else who is interested in using information technology
to create a competitive advantage
and is willing to expand their knowledge base to achieve that goal.