Please login or join to subscribe to this thread
Validating the scope happens both at the beginning and at the end of projects.
Validating the scope at the beginning of the project is ensuring that the defined scope completely, correctly, and clearly defines the boundaries of the project. This is validating that the problem statement is right.
Validating scope at the end of the project is to ensure the project delivered everything within the scope of the project (complete), the deliverables work as expected (correct), and that the customer understands how the solution works. (clear). This is validating that the provided solution adequately addresses the problem statement.
Remember that inside the PMBOK is not a project life cycle defined then is not right to say that something comes before the other. The project life cycle will determine that. PMI explicit said that the numbers assigned to process were giving just to facilitate the reading (in the understanding of the PMI) but they do not define precedence. So, the important thing, is to understand what it does mean each ones. Validate Scope is the formal acceptance. Is when you as project manager goes to the stakeholder that requested the solution you are creating and you say "ok, let us review that all you request is all you get". Control Scope are actions you take to avoid things like scope creep.
Monitoring & Controlling Processes can be executed at any time over the life of a project and there is generally not a linear flow to the PMBOK processes. Validate Scope does usually come after Control Quality for a given deliverable as we want to have our stakeholders accept verified deliverables, but Control Scope could happen at any time once we have defined the scope of the project.
Project Management processes aren't a rigid line that must be followed in a certain order. Processes are iterative and could be performed many times throughout the life cycle. Validate scope occurs when a deliverable is done and passes a validating and verifying process prior to enter to finish stage. Control scope can be executed at any time in the life cycle of the project to execute adjustments as required.
I'm of the same view as Kiron Bondale and Veronica Ruiz. Additionally, depending on the project type and industry, Validate and Control scope processes may be done concurrently and/or interchangeably. The PMBOK is a guide to ensure that the processes are followed and not necessarily that the processes are done in a specific flow.
Verification is the process of evaluating whether something meets individual requirements, such as through a test or analysis. Validation is the process of auditing the full set of requirements to ensure that it is the appropriate set to completely define the solution and that at the end, verification is complete for the entire set of requirements.
You can verify that your product meets a set of requirements such as performance, but if you did not capture all the right requirements to begin with such as you missed safety, you do not have a valid solution.
In the past I have reviewed everywhere the PMBOK uses these terms, and although they define them correctly, they use them somewhat interchangeably and sometimes incorrectly within the text.
Thank you all for your responses. I truly appreciate this discussion & you sharing the knowledge. I understand that each process has its own role to play and depending on life cycle, can be iterative in nature and can be performed as needed (not necessarily as defined in PMBOK). I have personally experienced that too. But keeping what happens in real world aside, and going by PMBOK way of things, there is a logic to why certain process come before or after another process, e.g. ideally you should not or cannot not
- Create WBS without Collecting Requirements,
- Plan Risk Response without correctly Identifying Risks
- Develop/ Manage Team without Acquiring Team.
In the same breath, ideally we cannot/should not present anything to customer (Validate scope) unless it has been through Control Scope. Again I fully understand the functionality of both processes but like other Process groups following an order, I personally feel it just makes more sense that Validate scope (final step before closure) should happen after Control Scope (managing changes to scope baseline).
Please login or join to reply