Create WBS - Outputs: Change request?
Submitted by Antoine D on Tue, 09/18/2012 - 23:07
One of the output is project document updates, PMBOK says:
"if approved change requests result from the Create WBS process, then the requirements documentation may need to be updated to include approved changes".
Why don't we have change request as an output of the create WBS process?
Forums:
aliweb
Wed, 09/19/2012 - 07:27
Permalink
I think because the focus
I think because the focus here is on "Project document updates" and not the change request itself. In all the processes mentioned in PMBOK, almost all of them can have many more outputs then mentioned but they can't write each and every one of them so only important ones are mentioned.
For e.g. in some cases they have mentioned "Change request" as output but not "Project document updates" because the focus is more on change request in that particular process.
projmanpro
Wed, 09/19/2012 - 09:24
Permalink
Understand the Create WBS process
To understand the Create WBS process, could you see any chance that a change request will be an output-meaning the intent and purpose of the process? I believe NO. Create WBS process is mainly to structure and breakdown works into workable and measurable work packages. If in case along the process, issues were identified that need to be changed, where as per the PM process has to comply with the Change request and approval requirement, then Change request there i would say is not actually the intent of the Create WBS process but rather associated or subsequent process.
I agree that the requirements documentation must be updated to include the approved changes that would estbalish the consistency between the WBS and the requirements documentation. To figure it out, your WBS structurize and decompose/interpret your requirements into a workable and measurable work packages.
====
You may follow my other PMP posts and explanations at www.pmptrend.com
sspawar
Wed, 09/19/2012 - 11:56
Permalink
In Creat WBS process output
In Creat WBS process output will be WBS, and further WBS Dictionary possesses all information regarding particular WBS / work packages /WBS Components.
like
Other things I think not asked ,it is sufficient.
sspawar
Wed, 09/19/2012 - 15:35
Permalink
Dear Antoeni D Are you
Dear Antoeni D
Are you getting my point or any thing else has remained there.
WBS dictionary will suffice all regarding WBS of approved change requests.
Hope it is very clear.
Regards
projmanpro
Wed, 09/19/2012 - 15:59
Permalink
I think pawar you did not get
I think pawar you did not get his (Antoeni D) point. This man was wondering why, change request is not considered as OUTPUT of the Create WBS process while it is then written in PMBOK that according to Antoeni, "if approved change request ..... blah blah blah..."
sspawar
Thu, 09/20/2012 - 02:16
Permalink
Dear ProjmanproI understood
Dear Projmanpro
I understood it well
what he actually wants to explore out.
His comprehension is that after requirements documentation- Appd change request goes to create WBS, but why its existance is not further shown in Create WBS process as Output.
His query is indicating that how Change request can further be tracked for implimentation , if create WBS is silent as in its output.
His quesion is genuine and appropriatly answered by me.
In some extend Mr. Ali told correctly that each and every thing could not mentioned in so detail, but how it can be tracked i answered here.
My explanation
is very clear in that regard - App change request as output will be there (in create wbs process) and in the form of WBS(as output of create WBS)
And it would be recognised and tracked by detailes attributed in WBS Dictionary.
My advise is dont make him understand that what is create WBS process, He understands it well,
His main intent is what will be the flow diagram of change request till its implementation, and in create wbs process, if it is not clearly shown as output then how it will tracked and recognized here.
Hope you now have been got the point .
projmanpro
Thu, 09/20/2012 - 05:11
Permalink
very lenghty post, the
very lenghty post, the question is very short...
anand_kl
Fri, 09/21/2012 - 06:57
Permalink
Change request
Dear Antoine,
Your question is legitimate. I agree with aliweb and to add further, we need to understand the term Change request (CR) in this context.
From PMBOK itself, CR is mostly NOT Output of Planning process (Except in procurement planning, since it might affefct the other baselines).
CR are mostly outputs of executing and/or Montioring and controlling process, since executing and M&C process gives the feedback on your planning. As we know CR can be in form of Preventive action, Corrective action or Defect repair.
As aliweb has pointed out, during planning process "Project document updates" are in focus since you might uncover certain requirements during create WBS process which you might have missed during your collect requirement process OR there may be some duplicated or redundant requirements as well. So in such cases you need to go back to update your Requirement document.
And to track such changes you might chose to go through a Change control process.
Hope this helps.
Regards
Anand KL, PMP
Antoine D
Sun, 09/23/2012 - 17:42
Permalink
Thanks everyone for your
Thanks everyone for your contributions to clarify this point.
I noticed a similar issue on the process "estimate activity duration". One of this TnT is reserve analysis that implies the analysis of the contingency reserve but there is no input with that information (i.e. risk register).
On the other hand, "estimate cost" has the same TnT "reserve analysis" and has the risk register has an input.
The PMBOK only lists the main inputs but secondary one may also be used.
If a question asks "Is the risk register an input of the estimate activity duration?". What would be the correct answer: yes or no?
sspawar
Fri, 09/21/2012 - 12:48
Permalink
Flow Diagram of Change Requests till impimentation
/CHANGE LOG
/CHANGE LOG
/CHANGE LOG