Project Management

Please login or join to subscribe to this thread

Any Comments on PMBOK 6th Ed?

linkedin twitter facebook   Estimating   Governance   Work Breakdown Structures (WBS)  
avatar
MANSOUR THABET ALQUBATY System Controller| Teleyemen Sana'A, N/A, Yemen
Hello All,

Those who are a PMI member ship and down loaded the PMBOK 6th Ed,or getting by other method, ( How you see it , expectation, Prep. test and new things about this issue??)

Thanks and regards,
Mansour
Sort By:
< 1 2 >
avatar
Mirko Blüming Senior Project Manager| Statkraft Germany GmbH Düsseldorf, Nrw, Germany
I like how it integrats agile aproaches. I also think the processes are more consistent than in the 5th edition.
...
1 reply by Simon Harris
Sep 13, 2018 2:57 AM
Simon Harris
...
My take was it constantly says "we are agile" then says things like "vital to define scope clearly" & examines an expected flow that runs 52.-5.3-5.4 -7.2-7.3. yes it CAN be described as not stopping agile but its hardly agile guidance. The accompanying document starts well but is an joke/ embarresment before it ends
On processes the change to such generic statement of input descriptions to just say plan and docs as inputs everywhere obfuscates what matters in each processes - a reduction in the easy of understanding of integration.
Also WBS-Dictionary, Activity-Attributes, Basis of Estimate are equivalent concepts with different names - Its an opportunity for consistency that may be worthwhile
The processes names Manage, Control & Monitor are a mess.
Some like 10.3 have the same aim as those named Control. While some control have the same aims as those named manage. The clear distinction at work is "Do it" versus "Oversee, measure and direct those doing it" the book is less clear.
IMHO
6th did not take us where we could have gone
Simon
avatar
Simon Harris consultant| Logical Model Ltd Edinburgh, Midlothian, United Kingdom
Sep 12, 2018 7:28 PM
Replying to Mirko Blüming
...
I like how it integrats agile aproaches. I also think the processes are more consistent than in the 5th edition.
My take was it constantly says "we are agile" then says things like "vital to define scope clearly" & examines an expected flow that runs 52.-5.3-5.4 -7.2-7.3. yes it CAN be described as not stopping agile but its hardly agile guidance. The accompanying document starts well but is an joke/ embarresment before it ends
On processes the change to such generic statement of input descriptions to just say plan and docs as inputs everywhere obfuscates what matters in each processes - a reduction in the easy of understanding of integration.
Also WBS-Dictionary, Activity-Attributes, Basis of Estimate are equivalent concepts with different names - Its an opportunity for consistency that may be worthwhile
The processes names Manage, Control & Monitor are a mess.
Some like 10.3 have the same aim as those named Control. While some control have the same aims as those named manage. The clear distinction at work is "Do it" versus "Oversee, measure and direct those doing it" the book is less clear.
IMHO
6th did not take us where we could have gone
Simon
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Opera is where a guy gets stabbed in the back, and instead of dying, he sings."

- Robert Benchley

ADVERTISEMENT

Sponsors







Vendor Events

See all Vendor Events

Newsletters

Jun 3: The Career Problem Facing New PMs
May 20: Your PM Career as a Project Life Cycle
May 13: The Big Lie After Layoffs

See all newsletters