Do you need customer support or technical assistance? Click here to submit a support ticket...

TOPIC: Process Plan Scope Management and its output

Process Plan Scope Management and its output 8 years 2 months ago #4811

  • Jessica Schiffmann
  • Jessica Schiffmann's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 1
  • Thank you received: 0

when studying the outputs of the 'Plan Scope Management' process, I do not understand the difference of Requirement Management Plan and Scope Management Plan, correctly. I would have assumed that the requirements are part of the scope.
Google suggested that requirments are for the whole project and scope for the phases, or requirements are somehow alls orts of requirments and scope is more functional.

Could someone help me understand the difference of requirements and scope?

Thanks a lot

Process Plan Scope Management and its output 8 years 2 months ago #4815

  • Steve Sandoval
  • Steve Sandoval's Avatar
  • Offline
  • Senior Boarder
  • Senior Boarder
  • Posts: 49
  • Thank you received: 10
Hello Jessica,

I can see how this could be confusing. Yes, I would say that requirements are part of the scope. Indeed, both the Scope Management Plan and the Requirements Management plan are outputs of the Plan Scope Management process! I suggest that reviewing the respective paragraphs in the PMBOK might be helpful here ( for Scope Management Plan, and for Requirements Mangement Plan -- PMBOK Guide 5th Edition).

The Scope Management plan covers things like how you are going to develop a project scope statement, developing and maintaining your WBS, how you will get your customer to formally approve deliverables, and how you will deal with change reqests to the scope statement.

The Requirements Management Plan deals more specifically with requirements -- how are you going to collect them, how you will prioritize them, how you will trace them, etc.

So while the two are intimately related, perhaps it is best just to think of it this way: the requirements are so important we dedicate an entire plan to covering them!

I hope this helps.
Steve Sandoval, PMP
Community Moderator
The following user(s) said Thank You: Sandeep Kulkarni

Process Plan Scope Management and its output 8 years 2 months ago #4819

  • Michael DeCicco
  • Michael DeCicco's Avatar
  • Offline
  • Expert Boarder
  • Expert Boarder
  • Posts: 130
  • Karma: 12
  • Thank you received: 43
Jessica, you may have already sorted it out already from Steve's reply. I'd like to add how you can think of Scope Management as the process you're in charge of as you go through the project, whereas the the Requirements are a customer driven process. You can control the rate of your work to complete the project by defining scope and managing changes to it. This becomes crucial, particularly as the voice of customer often asks for more things, which they are entitled to as the paying customer or boss, but as long as it fits into the agreed upon scope. If the requirements create variation for you from the scope, you will have to monitor and control. Any changes need to be adjudicated and compensated with money, time, or other material necessary to complete the project.
Yours Respectfully
Michael DeCicco, PMP
Community Moderator
Moderators: Yolanda MabutasMary Kathrine PaduaJohn Paul BugarinLisa Sweeney PMPHarry ElstonBrad Pennington, PMPKyle Kilbride, PMPJean Kwanda

Training for Project Management Professional (PMP)®, PMI Agile Certified Practitioner (PMI-ACP)®, and Certified Associate in Project Management (CAPM)®