Jamals Musings – Requirements Engineering compared with Project Scope Management

It is worthwhile to compare the requirements engineering process with the project scope management flow (see Figure 1).

Figure 1

As can be seen the “Collect Requirements” process corresponds perfectly to the “Elicitation” phase in the requirements engineering domain. The “Define Scope” process includes all of “Analysis’ and the beginning of the “Specifications” stage. Work breakdown structures are finalized once the “Specifications” phase is complete. “Verify Scope" and “Validation” correspond one to another perfectly, while “Control Scope” includes both “Requirements Tracking” and “Requirements Maintenance”.


This is an excerpt from my new book “Project Scope Management: A Practical Guide to Requirements for Engineering, Product, Construction, IT and Enterprise Projects” that is being published by CRC Press The book should soon be available on Amazon.

Please leave your feedback in the “Add New Comment” section below. Also, feel free to share this article via Facebook, Twitter, LinkedIn or Google Plus by clicking the buttons at the top of the page.

About the Author

Jamal Moustafaev, MBA, PMP – president and founder of Thinktank Consulting is an internationally acclaimed expert and speaker in the areas of project/portfolio management, scope definition, process improvement and corporate training. Jamal Moustafaev has done work for private-sector companies and government organizations in Canada, US, Asia, Europe and Middle East.  Read Jamal’s Blog @ www.thinktankconsulting.ca

Jamal is an author of two very popular books: Delivering Exceptional Project Results: A Practical Guide to Project Selection, Scoping, Estimation and Management and Project Scope Management: A Practical Guide to Requirements for Engineering, Product, Construction, IT and Enterprise Projects.