PMBOK

A set of standard terminology and guidelines for project management.

Practices Employed

• Change Management: Integrated Change Control is used to manage changes to project deliverables and documents.
• Documentation: Project management plans and project documents ensure clarity and traceability.
• Estimating: PMBOK covers various estimation techniques like analogous, parametric, and three-point estimating.
• Issue Management: Monitoring and controlling project work includes managing issues as they arise.
• Measurement: Earned Value Management (EVM) is used to track project performance against the baseline.
• Requirements Capture: Defining scope and capturing requirements are fundamental process groups.
• Stakeholder Management: Identifying and managing stakeholder expectations is a core knowledge area.

Addresses / Mitigates

Risk	Practices
Agency Risk	Estimating: Helps in planning and managing staff usage effectively. Stakeholder Management: Aligns the goals and expectations of various stakeholders, reducing conflicts.
Communication Risk	Documentation: Provides clear guidelines and information, reducing misunderstandings. Issue Management: Facilitates communication about issues and their status among team members. Requirements Capture: Helps in explaining exactly what should be built. Stakeholder Management: Facilitates clear and consistent communication between stakeholders.
Coordination Risk	Change Management: Specifically addresses coordinating change in a structured way. Requirements Capture: Reduces coordination risks around deciding what should be built. Stakeholder Management: Allows stakeholders to coordinate on their demands.
Deadline Risk	Estimating: Provides realistic timelines helps hit important deadlines.
Feature Fit Risk	Measurement: Helps in understanding the use of the system. Requirements Capture: Ensures that features align with client needs and expectations.
Funding Risk	Estimating: Accurate estimation helps in securing and managing funding.
Implementation Risk	Change Management: Avoid bugs from creeping into the system. Issue Management: Tracks and manages defects and issues, ensuring they are resolved. Measurement: Identifies areas of improvement in the implementation process.
Internal Model Risk	Documentation: Detailed documentation helps manage and understand complex systems. Stakeholder Management: Talking to stakeholders helps to share and socialise Internal Models.
Operational Risk	Change Management: Ensures changes are implemented smoothly and systematically. Issue Management: Provides a systematic approach to managing and addressing operational issues. Measurement: Provides data to inform decision-making and improve operational efficiency.
Reputational Risk	Issue Management: Tracking and fixing bugs improves software reputation.
Security Risk	Issue Management: Track and Prioritise Security Issues and Incidents.

Attendant Risks

Attendant Risk	Practices
Agency Risk	Estimating: Can put unnecessary pressure on staff to hit deadlines.
Communication Risk	Stakeholder Management: Misaligned communication strategies can lead to misunderstandings and conflicts.
Complexity Risk	Documentation: Documentation is also a source of complexity on a project and can slow down change. Issue Management: Managing an excessive number of logged issues can add complexity. Measurement: Collecting and analyzing data can add to the complexity of the project.
Deadline Risk	Estimating: Can create dependencies on estimated timelines and resources.
Funding Risk	Measurement: Implementing measurement systems can be expensive.
Internal Model Risk	Measurement: Focusing on the wrong measures can blind you to what's important.
Process Risk	Change Management: Change control is a process, and therefore is a source of process risk. Issue Management: The issue lifecycle from creation to resolution is a process, therefore a source of process risk.
Reliability Risk	Measurement: Creates dependencies on measurement tools and their accuracy.
Schedule Risk	Change Management: Managing changes systematically can introduce delays. Documentation: Creating and maintaining documentation can be time-consuming. Estimating: Inaccurate estimates can lead to schedule overruns. Issue Management: Managing and resolving logged issues can impact project timelines. Requirements Capture: Thorough requirements capture can be time-consuming.

Description

"The Project Management Body of Knowledge (PMBOK) is a set of standard terminology and guidelines for project management. The body of knowledge evolves over time and is presented in A Guide to the Project Management Body of Knowledge (the Guide to the PMBOK or the Guide)." - Project Management Body of Knowledge, Wikipedia

PMBOK provides a comprehensive framework that categorizes project management into Process Groups and Knowledge Areas. It serves as a global standard for the profession, offering best practices that can be applied to a wide range of projects across various industries.

See Also