I'm just studyng the ITTOS for the Control scope process.
This is the process of monitoring the status of the project and product scope and managing changes to the scope baseline.
In the output i find: scope, schedule and cost baseline updates.
But in the input i don't have approved changes so i don't understand why also the updates of the performance baseline are in the outputs. If you kindly explain it to me.
thanks in advance Saving Changes...
Scope baseline is actually a part of PMB. Simply, when scope baseline is changed it automatically refers to PMB. Remember, even corrective action or preventative action comes as part of change.
I don't see a valid reason to put approved change as part of input here.
It does include change management plan and configuration management plan, which include the approval of changes.
...
1 reply by Stéphane Parent
Apr 29, 2019 9:51 PM
Stéphane Parent
...
How so, Kevin? Management plans are about how you will do the work. These will tell you how to approve the changes but won't, in themselves, be the source of the approved changes.
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
Apr 29, 2019 4:10 PM
Replying to Keith Novak
...
It does include change management plan and configuration management plan, which include the approval of changes.
How so, Kevin? Management plans are about how you will do the work. These will tell you how to approve the changes but won't, in themselves, be the source of the approved changes. Saving Changes...
The way these kinds of documents are written, it can be difficult to follow. I was an author and SME on similar types of documents, so I have a lot of practice. The whole section on change management, configuration management, and integrated change control is a stretch for anyone. The biggest problem of the section is that under Tools and Techniques, it only included Data Analysis. Analysis does not change plans which control scope clearly does.
Here's how they did include it, and I am not claiming it is well written.
From section 5.6.3.3 (I hate how I can't cut and paste the PMBOK now.)
"Scope baseline. Described in Section 5.4.3.1. Changes to the scope baseline are incorporated in response to approved changes in scope..."
Change and configuration management plans define how changes are processed. Perform integrated change control is the action of executing the plan. Approved changes are the output.
In section 2.3: OPAs include *any artifact*...from any or all of the performing organizations in the project that can be used to execute or govern the project. A record of an change approval is an OPA.
Since OPAs, and the processes to manage changes are inputs, that includes approved changes. It is a really hard way to get there, but I could pass a process audit with that.
...
1 reply by Stéphane Parent
Apr 30, 2019 10:26 AM
Stéphane Parent
...
Glad you’re able to make it work , Kevin
Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
Apr 29, 2019 10:34 PM
Replying to Keith Novak
...
Stéphane
The way these kinds of documents are written, it can be difficult to follow. I was an author and SME on similar types of documents, so I have a lot of practice. The whole section on change management, configuration management, and integrated change control is a stretch for anyone. The biggest problem of the section is that under Tools and Techniques, it only included Data Analysis. Analysis does not change plans which control scope clearly does.
Here's how they did include it, and I am not claiming it is well written.
From section 5.6.3.3 (I hate how I can't cut and paste the PMBOK now.)
"Scope baseline. Described in Section 5.4.3.1. Changes to the scope baseline are incorporated in response to approved changes in scope..."
Change and configuration management plans define how changes are processed. Perform integrated change control is the action of executing the plan. Approved changes are the output.
In section 2.3: OPAs include *any artifact*...from any or all of the performing organizations in the project that can be used to execute or govern the project. A record of an change approval is an OPA.
Since OPAs, and the processes to manage changes are inputs, that includes approved changes. It is a really hard way to get there, but I could pass a process audit with that.
Glad you’re able to make it work , Kevin Saving Changes...
To the credit of the authors, trying to document such a large field of knowledge is a daunting task, and the PMBoK is an admirable effort. When I see questions regarding whether something is missing, I can often reason out how it can actually be embedded somewhere else, but I won't claim that it is at all clear or obvious.
Unfortunately, I do find the PMBoK lacks consistency in a lot of ways in how they try to logically document various knowledge areas. If authors are not extremely careful with language and graphics standards, the intended meanings become unclear. I often find myself questioning why they would chose a specific term such as monitor over control, and I notice execution is out-of-scope for most knowledge areas. Also, as a document like this evolves over time, entropy is inevitable.
I found studying these ITTO diagrams the worst part of studying for the PMP exam, despite much professional experience creating them myself. I think they serve as a valuable took for learning the concepts, but as a PM practitioner, I find they have limited practical use and are certainly not a comprehensive road map, or instruction guide. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Frabrizio, changes to the baseline are the common changes (because the need to update documentation) you will do when performing Controlsomething. For example, in scope, if you have completed some deliverables then you will mark then into the scope list as "completed". On the other side, you have other type of changes that need to be put on change control. For example, if a new deliverable must be created into the project. This type of changes are processed inside other process. You have to take into account that there is not work flow defined into the PMBOK because it will be when you define your own project life cycle. The important thing, if you are studying for the PPM, is to understand each situation because questions are situational questions. So, you need to undestand the instant of time inside a project the question is locating you. Saving Changes...
"Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining."
