Dear all
In the Define activities process, we have a change request CR as an output because of the progressive elaboration of the deliverables.
Despite we are in the planning stage, this CR is processed for review and disposition through Perform integrated change control process.
Any clarifications are welcomed
Best regards
Abdelkader Saving Changes...
Dear Abdelkader,
In a cascade approach, change requests can be submitted when Baseline is completely defined, not during planning stages. If your project needs to introduce change requests during planning, you must consider an agile method, to plan each progressive and variable iterations, allowing adaptation of each of them according to the product backlog priorities which can be reorganized in an agile manner. Saving Changes...
Anton OosthuizenSenior Business Analyst / Project Manager| Self EmployedPretoria, Gauteng, South Africa
I like Verónica's suggestion but I do believe that it is possible to generate change requests during planning. It will, however, raise some red flags for me. Raising changes so early in the life cycle could be an indication that requirements are not understood very well. But there might be external factors that could necessitate a change. Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
There is no such thing as a planning stage or phase in PMBoK, planning takes place during the planning process group. Process groups are repeated during the project, iteratively.
Since a CR can only be issued when there is a baseline, this means a CR can only be issued from iteration 2 of the planning process group. This is also called progressive elaboration.
If you find new activities needed or refine activities defined in a previous iteration, then you might be required to issue a CR. Except you might have chosen (tailored your project) to not include activities at all in the baseline (but only work packages).
Phases or stages are part of the project life cycle, which is defined from the product created with the project, or it's industry. So it differs from project to project and can not be part of PMBoK which tries to guide to principles that are good practice in most projects, most of the time. Project cycles themselves can be predictive, iterative or adaptive.
Process groups are agile from the beginning.
This is one of the most overlooked principles of PMBoK. I do not blame agilistas not to know it, but I wonder how many PMPs did not get it. Saving Changes...
Asif GulConsultant Project Manager| Energoprojekt EntelMuscat, Oman
First thing is the all process group defined in the PMBOK are iterative hence even planning can also be progressively elaborated in each of its iteration.It can surely happens that once you start to define the activities, you need to bring some change in scope of project or any other key project document or deliverable which was defined and established earlier. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
The key is to decide when a CR deserves to be raised or not. That´s part of your governance and control process. In the case you describe, taking the information you wrote, you do not need to rise a CR saying that with the process I worked from more than 30 years. But just my case. Saving Changes...
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Dear Abdelkader
Interesting your question
Thanks for sharing it.
I completely agree with Veronica.
If the baselines are not yet fully defined we cannot consider any change request as a CR Saving Changes...
For example, with my last client which had a progressive funding model based on rolling wave planning, teams secured funding for an initial phase which was focused on getting them a high confidence plan for their next phase of work.
If a team needed more funding and/or time for that initial phase, a CR would be utilized even though they had not established baselines for delivering any customer value. They did have baselines, but those were just for the preliminary planning tranche of funding.
Kiron
...
1 reply by Thomas Walenta
Dec 12, 2019 10:02 AM
Thomas Walenta
...
Kiron
in your example it seems to me that the budget/timeframe given for the initial phase would on fact be the baseline against which the change request is issued.
Any CR needs a baseline which is supposed to change.
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Dec 12, 2019 7:16 AM
Replying to Kiron Bondale
...
This can be organization specific.
For example, with my last client which had a progressive funding model based on rolling wave planning, teams secured funding for an initial phase which was focused on getting them a high confidence plan for their next phase of work.
If a team needed more funding and/or time for that initial phase, a CR would be utilized even though they had not established baselines for delivering any customer value. They did have baselines, but those were just for the preliminary planning tranche of funding.
Kiron
Kiron
in your example it seems to me that the budget/timeframe given for the initial phase would on fact be the baseline against which the change request is issued.
Any CR needs a baseline which is supposed to change.
...
1 reply by Kiron Bondale
Dec 12, 2019 11:44 AM
Kiron Bondale
...
Absolutely correct, Thomas - it is a phase-based baseline vs. an overall baseline.
in your example it seems to me that the budget/timeframe given for the initial phase would on fact be the baseline against which the change request is issued.
Any CR needs a baseline which is supposed to change.
Absolutely correct, Thomas - it is a phase-based baseline vs. an overall baseline.
