Planning Process: SCOPE Baseline vs SCOPE Statement
I understand "SCOPE Baseline" is created in "Create WBS" process, where "Project Scope Statement" is input from "Define Process". And I also understand that "Scope Statement" (Assumptions, Constraints, Stakeholder Analysis etc) is included in "Scope Baseline".
In Project Time Management, "Define Activities" process, i will use "Scope Baseline" as Input but will have "Project Scope statement" as output.
In Project Risk Management process: "Plan Risk Management" I will use "Project Scope Statement" as Input but in "Identify Risks" I will use "Scope Baseline" and finally in "Perform Qualitative Risk Analysis" I will use "Project Scope Statement" again.
Please help me understand, when do I use "Scope Baseline" as INPUT and when do I use "Project Scope Statement" as INPUT, or do I really need to memorize all this? I would rather try to understand, how it works. :(
Thank you
D
sspawar
Wed, 02/13/2013 - 16:51
Permalink
Read first -- Head First OR
Read first -- Head First OR ANDY, then RITA/ PMBOK
Read chapter wise -and solve quetions chapter wise . Dont make - the BHEL-PURI, an Indian Gujarati light food - means mixing all.
Do research in last after completing all chapters / after a couple of months.
JanaDee
Wed, 02/13/2013 - 17:02
Permalink
that was not an answer to my
that was not an answer to my question
sspawar
Thu, 02/14/2013 - 01:33
Permalink
I mean better understand
I mean better understand those areas, it is the first way and 80% problem will be solved in this way.
There many things to read apart from this.
Perhaps you then will get grip on subject, and will not worry this much on these approx 600 parodies. It is not like sequential flow chart.
After that still you find its necessity - you may select what parts are important. It varies with person to person and individual's style of learning/grasping the subject.
There are many posts and discussions on ITTOS, you may refer them too.
--------------------------------------------
PSS and SBL
PSS - Mostly qualitative and thick information and data
SBL - Descriptive, quantitative and detailed information and data
----------------------
Define activity depends on WBS elements, with their characteristics, needs SBL.
Planning risk management - vital theme any planning is - HOW to deal with , -- so it needs - qualitative characteristics of project -ie in PSS.
Identify risks - require descriptive and quantifiable data hence needed - SBL/WBS work packages, with their characteristics.
Perform Qual Ana -- does not need quantity but only characters.
like this way ----you may distinguish
bcrawl
Wed, 08/12/2015 - 20:25
Permalink
I know I am digging up an old
I know I am digging up an old thread but can some one comment on this question?
as the original poster asked:
I work to create Project Scope, then Scope Baseline and then incorporate this into the Scope Management Plan and finally include that information in Project Management Plan.
ok. This sounds like a normal progression.
Now, I have a change in scope which is from a change request which was approved, so now, does PMBOK say that:
I should go back and update Project Scope Statement , Scope Baseline document, Scope Management Plan and Project Management Plan...all the while updating the other list of documents such as requirements, cost, risk, schedule "documents"..
In real world, do you guys use a software which I am not aware of? This just sounds ridiculous. In my work, I create and manage 4 version controlled documents. Thats it. Plan, 2 types of Requirements, Quality. Thats it.
We dont call sections of these documents as deliverables and make a big scene out of it.
Documenting how to will gather requirements is not a "document". Its an agreement which can at best be summarized in 3 lines in either stakeholder section or requirements section of the project plan. But no. This is a whole section of deliverable which needs other documents as inputs and acts as...."zzzzzsleep"
This is why no one outside of PMI values PMP. Its like going back to high school days when we are expected to take calculus classes and the teachers just give out formulas to solve and students blindly memorize them to clear the test. Thats it. No one ever stops and gives an explanation of why one should learn it.
Same bullshit here. Do I want to clear this test? Yes. But its just like my calculus course. Clear. No point in trying to apply this in real world. I want to clear this test so I will go ahead and rote this stupid rule by PMI.
Anyways, past my rant, my original question.
Scope Statement -> Scope Base Line -> Scope Management Plan -> Project Plan
And if scope changes, rinse and repeat this step. Is this correct?
Thanks.
admin
Thu, 08/13/2015 - 05:51
Permalink
Well in practical scenarios
Well in practical scenarios where you need to follow the process, its done with help of software. The recommended process will apply in most scenarios.
What is meant by scope change - say you are building a bridge and decide that instead of suspension bridge it will be a normal bridge. Everything else remains the same, but this small change in scope statement will completely change the project plan, vendors you deal with, your cost, schedule etc.
On the surface it may seem ridiculous , generally when PMs do lot more than mangagement then work involved in managing project seems overhead.
I disagree with fact that outside PMI there is no value of PMP. There is value for PMP in industry.