Dear all,
I would like to have your point of view as I don't succeed to have a clear for the process dedicated to "Change request".
How is it manage in the whole process ?
I propose the below sequence :
Need for change -- Issue log -- Control Scope -- Change log -- Change Request -- Perform Integrated Control Change -- Approved Change Request -- Change log update -- Baseline update (scope, schedule, cost, risk register…)
Can you confirm / modify / update my point of view ?
Thank you Saving Changes...
Multiple PMBOK processes (usually the Monitor/Control ones) will produce Change Requests as an output.
Those will be inputs into the Perform Integrated Change Control process and (if accepted) will become Accepted Change Requests which are an input into the Direct and Manage Project Work process.
Kiron Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Olivier,
I worked with this process, aligned to PMBoK but adding emphasis on change analysis (which might be a project on its own).
ok thanks,
So, just to complete and clarify :
- "issue log" is dedicated to state on change how managing the project with stakeholder
- "change log" is dedicated to identify modification on requirements
Is it right ?
...
1 reply by Kiron Bondale
Mar 05, 2020 5:07 PM
Kiron Bondale
...
Olivier -
An issue log is a general repository of ANY project issue which is material enough to be captured and shared. The issues might be stakeholder-related or could be related to something entirely different (e.g. solution/technical challenges).
A change log captures any request (approved or rejected) which would result in a baseline change whether that is scope/requirements-related or not. For example, extending the timeline or increasing the budget beyond approved baselines would necessitate a change request. Baselines could be schedule, cost, scope, quality and other dimensions...
ok thanks,
So, just to complete and clarify :
- "issue log" is dedicated to state on change how managing the project with stakeholder
- "change log" is dedicated to identify modification on requirements
Is it right ?
Olivier -
An issue log is a general repository of ANY project issue which is material enough to be captured and shared. The issues might be stakeholder-related or could be related to something entirely different (e.g. solution/technical challenges).
A change log captures any request (approved or rejected) which would result in a baseline change whether that is scope/requirements-related or not. For example, extending the timeline or increasing the budget beyond approved baselines would necessitate a change request. Baselines could be schedule, cost, scope, quality and other dimensions...
Kiron
...
1 reply by Stéphane Parent
Mar 09, 2020 8:54 AM
Stéphane Parent
...
I've had to do a change request for changing milestones, even though the underlying activities did not change. The project sponsor insisted that's how the "change" should be recorded.
Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
Mar 05, 2020 5:07 PM
Replying to Kiron Bondale
...
Olivier -
An issue log is a general repository of ANY project issue which is material enough to be captured and shared. The issues might be stakeholder-related or could be related to something entirely different (e.g. solution/technical challenges).
A change log captures any request (approved or rejected) which would result in a baseline change whether that is scope/requirements-related or not. For example, extending the timeline or increasing the budget beyond approved baselines would necessitate a change request. Baselines could be schedule, cost, scope, quality and other dimensions...
Kiron
I've had to do a change request for changing milestones, even though the underlying activities did not change. The project sponsor insisted that's how the "change" should be recorded. Saving Changes...
