Got Traceability? |
||||||||||||
|
|
Home > Articles > Got Traceability? by Andrew Makar September 19, 2007 How do you ensure the business requirements defined at the start of the project are successfully transformed into the IT solution?
As a project manager, we spend considerable effort tracking project issues, risks and project schedules. How often do we track business requirements to ensure the requirements are correctly developed? Without requirements traceability, projects run the risk of assuming business requirements will be translated into a solution once the initial business requirement specification or use case is defined.
According to Carnegie Melon’s Software Engineering Institute, requirements traceability is “the ability to describe and follow the life of a requirement, in both a forward and backward direction”. Traceability indicates the requirement can be tracked from its origins, specification, development, deployment and use as the project executes across the project lifecycle.
Please login/register to read the entire article.
sponsored announcements and special offers
Position yourself for success with Florida Tech's MBA in Project Management, accredited by PMI® GAC. There's no GMAT or GRE required, and you'll also qualify for 1,500 experience hours that can be used toward earning a prestigious PMP® credential.
The Enterprise PPM and PMO Blue Print. Learn strategies and best practices for taking a top-down, enterprise-wide approach to PPM processes and system deployment. To learn more and register now, click here!
|
| ||||||||||
|
| ||||||||||||