The Purpose of life is to go toward the freedom and drop all the fears of life. - Upanishdas
About Me
44% of pm use no software, even though PWC found that the use of commercially available PM software increases performance and satisfaction. Follow Tweet

Metrics: Leading Causes of Failed Agile Project Follow Tweet
PMLOGY

Expert Judgement

expert-judgement

Expert Judgement

×

My Message!

Click “X” to close.

PMBOK is industry agnostic project management standard. It defines 47 processes to manage a project. Every process has defined input, output, tools & techniques. But we know that tools and techniques required to manage a project also depends upon the industry for which we are doing a project. To do the industry specific work PMI has come up with a beautiful concept called “Expert Judgement”. This term is heavily used in the PMBOK in fact 28 processes out of 47, i.e. 60% of the processes uses this term as tool and technique. But the meaning and purpose of this changes from process to process and industry to industry. Broadly expert judgement can be bucketed into following groups.

  • A department within the organization
  • Consultants
  • Industry Group
  • Engineering Associations
  • Subject Matter Expert

Keep in mind that it is different from Organizational Process Assets, which is related to the processes or artifacts and part of the organization and built earlier.

Manytimes PMP aspirants get confused that a PMBOK process lists many tools and techniques and then one more, Expert Judgement. They think that this is the overuse of the term, either expert judgement or give list of all those tools and techniques why both. But PMBOK is very cautious about when they are addressing to all the industries through this standard. Many a times meaning of this in a process is if you cannot complete the processes using the listed tools and techniques then use expert judgment :).

Expert Judgement is Tool and Techniques to following processes.

  1. Develop Project Charter
  2. Develop Project Management Plan
  3. Direct and Manage Project Work
  4. Monitor and Control Project Work
  5. Perform Integrated Change Control
  6. Close Project or Phase
  7. Plan Scope Management
  8. Define Scope
  9. Create WBS
  10. Plan Schedule Management
  11. Define Activities
  12. Estimate Activity Resources
  13. Estimate Activity Durations
  14. Plan Cost Management
  15. Estimate Cost
  16. Determine Budget
  17. Plan Human Resource Management
  18. Control Communications
  19. Plan Risk Management
  20. Identify Risks
  21. Perform Qualitative Risk Analysis
  22. Perform Quantitative Risk Analysis
  23. Plan Risk Response
  24. Plan Procurement Management
  25. Conduct Procurements
  26. Identify Stakeholders
  27. Plan Stakeholder Management
  28. Control Stakeholder Engagement

PMBOK Process Summary Table

Save

Want to add something?

Loading Facebook Comments ...

Leave a Reply

Your email address will not be published. Required fields are marked *

 

Loading Disqus Comments ...
9 Shares
Share4
Tweet
Share4
+11
Pin