pmbok-project-management

149
29
Source

Comprehensive PMP/PMBOK project management methodologies and best practices. Use this skill when users need guidance on project management processes, templates, knowledge areas, process groups, tools, techniques, or certification preparation. Covers all 10 PMBOK Knowledge Areas and 5 Process Groups with practical templates, frameworks, and industry-standard approaches. Includes risk management, stakeholder engagement, schedule management, cost control, quality assurance, and resource planning.

Install

mkdir -p .claude/skills/pmbok-project-management && curl -L -o skill.zip "https://mcp.directory/api/skills/download/328" && unzip -o skill.zip -d .claude/skills/pmbok-project-management && rm skill.zip

Installs to .claude/skills/pmbok-project-management

About this skill

PMP/PMBOK Project Management Methodology Skill

This skill provides comprehensive guidance on Project Management Professional (PMP) and Project Management Body of Knowledge (PMBOK) methodologies, frameworks, tools, and best practices as defined by the Project Management Institute (PMI).

When to Use This Skill

Use this skill when the user requests:

  • Project management best practices and methodologies
  • PMBOK Knowledge Areas guidance
  • Process Groups implementation
  • Project management templates and frameworks
  • Risk management strategies
  • Stakeholder engagement plans
  • Schedule and cost management techniques
  • Quality assurance processes
  • Resource planning and allocation
  • Communications planning
  • Procurement management
  • Integration management across project phases
  • PMP certification exam preparation
  • Project management documentation standards

PMBOK Framework Overview

Latest Version: PMBOK Guide 7th Edition (2021)

  • 49 Processes across 10 Knowledge Areas and 5 Process Groups (PMBOK 6)
  • 12 Principles and 8 Project Performance Domains (PMBOK 7)
  • Integrates Agile, Hybrid, and Predictive approaches
  • Emphasizes value delivery and outcomes

PMBOK 6th Edition Structure (Still Widely Used)

  • 10 Knowledge Areas
  • 5 Process Groups
  • 49 Total Processes
  • Matrix structure: Each process belongs to one Knowledge Area and one Process Group

The 5 Project Management Process Groups (IPECC)

These represent the project lifecycle phases:

1. Initiating Process Group

Purpose: Authorize the project or phase and define objectives Color Code: Green (#d5e8d4)

Key Processes:

  • Develop Project Charter
  • Identify Stakeholders

Key Outputs:

  • Project Charter (formal authorization)
  • Stakeholder Register
  • Assumptions Log

Best Practices:

  • Align project with strategic objectives
  • Identify key stakeholders early
  • Define high-level requirements
  • Establish success criteria
  • Secure executive sponsorship

2. Planning Process Group

Purpose: Define course of action and refine objectives Color Code: Blue (#dae8fc)

Key Processes (24 total planning processes):

  • Develop Project Management Plan
  • Plan Scope Management
  • Collect Requirements
  • Define Scope
  • Create WBS
  • Plan Schedule Management
  • Define Activities
  • Sequence Activities
  • Estimate Activity Durations
  • Develop Schedule
  • Plan Cost Management
  • Estimate Costs
  • Determine Budget
  • Plan Quality Management
  • Plan Resource Management
  • Estimate Activity Resources
  • Plan Communications Management
  • Plan Risk Management
  • Identify Risks
  • Perform Qualitative Risk Analysis
  • Perform Quantitative Risk Analysis
  • Plan Risk Responses
  • Plan Procurement Management
  • Plan Stakeholder Engagement

Key Outputs:

  • Project Management Plan (comprehensive)
  • Work Breakdown Structure (WBS)
  • Project Schedule
  • Cost Baseline
  • Risk Register
  • Stakeholder Engagement Plan
  • Communications Management Plan

Best Practices:

  • Progressive elaboration - refine plans as information becomes available
  • Involve team in planning for buy-in
  • Document assumptions and constraints
  • Establish baselines for scope, schedule, and cost
  • Plan for all 10 Knowledge Areas
  • Use historical data and lessons learned

3. Executing Process Group

Purpose: Complete work defined in project management plan Color Code: Orange (#ffe6cc)

Key Processes (10 total):

  • Direct and Manage Project Work
  • Manage Project Knowledge
  • Manage Quality
  • Acquire Resources
  • Develop Team
  • Manage Team
  • Manage Communications
  • Implement Risk Responses
  • Conduct Procurements
  • Manage Stakeholder Engagement

Key Activities:

  • Coordinate people and resources
  • Execute project activities
  • Deliver project outputs
  • Manage team performance
  • Conduct quality assurance
  • Build and maintain relationships
  • Implement approved changes

Best Practices:

  • Focus on deliverables and value
  • Foster team collaboration
  • Maintain stakeholder engagement
  • Document lessons learned continuously
  • Manage changes through formal process
  • Conduct regular team meetings

4. Monitoring & Controlling Process Group

Purpose: Track, review, and regulate project progress Color Code: Yellow (#fff2cc)

Key Processes (12 total):

  • Monitor and Control Project Work
  • Perform Integrated Change Control
  • Validate Scope
  • Control Scope
  • Control Schedule
  • Control Costs
  • Control Quality
  • Control Resources
  • Monitor Communications
  • Monitor Risks
  • Control Procurements
  • Monitor Stakeholder Engagement

Key Techniques:

  • Earned Value Management (EVM)
  • Variance analysis
  • Trend analysis
  • Performance reviews
  • Change control procedures
  • Quality audits

Best Practices:

  • Measure against baselines
  • Identify variances early
  • Take corrective action promptly
  • Use formal change control
  • Track key performance indicators (KPIs)
  • Regular status reporting

5. Closing Process Group

Purpose: Finalize all activities and formally close project Color Code: Purple (#e1d5e7)

Key Processes:

  • Close Project or Phase

Key Activities:

  • Obtain final acceptance
  • Transfer deliverables
  • Release resources
  • Close contracts
  • Archive project documents
  • Capture lessons learned
  • Celebrate success

Best Practices:

  • Formal sign-off from stakeholders
  • Complete lessons learned session
  • Archive all documentation
  • Conduct team retrospective
  • Recognize team contributions
  • Update organizational process assets

The 10 Knowledge Areas

1. Project Integration Management

Purpose: Unify and coordinate all project processes Color Code: Gray (#f5f5f5)

Processes:

  • Develop Project Charter (Initiating)
  • Develop Project Management Plan (Planning)
  • Direct and Manage Project Work (Executing)
  • Manage Project Knowledge (Executing)
  • Monitor and Control Project Work (M&C)
  • Perform Integrated Change Control (M&C)
  • Close Project or Phase (Closing)

Key Concepts:

  • Project charter authorizes project
  • Project management plan integrates all subsidiary plans
  • Change control board (CCB) reviews changes
  • Integrated change control manages competing constraints
  • Knowledge management preserves organizational learning

Tools & Techniques:

  • Expert judgment
  • Meetings
  • Project management information systems (PMIS)
  • Change control tools
  • Configuration management

2. Project Scope Management

Purpose: Ensure all required work (and only required work) is included Color Code: Blue (#dae8fc)

Processes:

  • Plan Scope Management (Planning)
  • Collect Requirements (Planning)
  • Define Scope (Planning)
  • Create WBS (Planning)
  • Validate Scope (M&C)
  • Control Scope (M&C)

Key Deliverables:

  • Scope Management Plan
  • Requirements Documentation
  • Requirements Traceability Matrix
  • Project Scope Statement
  • Work Breakdown Structure (WBS)
  • WBS Dictionary
  • Scope Baseline

Key Concepts:

  • Product scope vs. project scope
  • Requirements gathering (interviews, surveys, workshops, observation)
  • Scope creep prevention
  • Gold plating avoidance
  • Progressive elaboration

Best Practices:

  • Clear scope statement
  • Decompose work to appropriate level (80-hour rule)
  • Use WBS for all project work
  • Formal scope validation
  • Strict change control
  • Requirements traceability

3. Project Schedule Management

Purpose: Ensure timely project completion Color Code: Green (#d5e8d4)

Processes:

  • Plan Schedule Management (Planning)
  • Define Activities (Planning)
  • Sequence Activities (Planning)
  • Estimate Activity Durations (Planning)
  • Develop Schedule (Planning)
  • Control Schedule (M&C)

Key Deliverables:

  • Schedule Management Plan
  • Activity List
  • Project Schedule Network Diagrams
  • Duration Estimates
  • Project Schedule (Gantt Chart)
  • Schedule Baseline

Key Techniques:

  • Critical Path Method (CPM)
  • Critical Chain Method
  • Program Evaluation and Review Technique (PERT)
  • Schedule compression:
    • Fast tracking (parallel activities)
    • Crashing (add resources)
  • Three-point estimating (Optimistic, Most Likely, Pessimistic)
  • Resource leveling and smoothing

Best Practices:

  • Bottom-up estimating for accuracy
  • Identify critical path
  • Build in contingency reserves
  • Monitor schedule variance (SV)
  • Update schedule regularly
  • Use schedule performance index (SPI)

4. Project Cost Management

Purpose: Ensure project is completed within approved budget Color Code: Orange (#ffe6cc)

Processes:

  • Plan Cost Management (Planning)
  • Estimate Costs (Planning)
  • Determine Budget (Planning)
  • Control Costs (M&C)

Key Deliverables:

  • Cost Management Plan
  • Cost Estimates
  • Cost Baseline
  • Project Budget
  • Funding Requirements

Key Techniques:

  • Analogous estimating (top-down)
  • Parametric estimating
  • Bottom-up estimating
  • Three-point estimating
  • Earned Value Management (EVM):
    • Planned Value (PV)
    • Earned Value (EV)
    • Actual Cost (AC)
    • Cost Variance (CV = EV - AC)
    • Schedule Variance (SV = EV - PV)
    • Cost Performance Index (CPI = EV / AC)
    • Schedule Performance Index (SPI = EV / PV)
    • Estimate at Completion (EAC)
    • Estimate to Complete (ETC)
    • To-Complete Performance Index (TCPI)

Best Practices:

  • Include all costs (direct, indirect, fixed, variable)
  • Establish cost baseline
  • Track actual vs. planned costs
  • Use EVM for performance measurement
  • Manage cost reserves (contingency and management)
  • Regular cost reviews and forecasting

5. Project Quality Management

Purpose: Satisfy quality requirements and standards Color Code: Red (#f8cecc)

Processes:

  • Plan Quality Management (Planning)
  • Manage Quality (Executing)
  • Control Quality (M&C)

Key Deliverables:

  • Quality Management Plan
  • Quality Metrics
  • Quality Control Measurements
  • Verified Deliverables

Key Concepts:

  • Quality vs. Grade (different concepts)
  • Prevention over inspection
  • Customer satisfaction
  • Continuous improvement
  • Management responsibility

Quality Gurus:


Content truncated.

You might also like

flutter-development

aj-geddes

Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.

1,5761,371

ui-ux-pro-max

nextlevelbuilder

"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."

1,1191,193

drawio-diagrams-enhanced

jgtolentino

Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.

1,4191,110

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

1,200751

nano-banana-pro

garg-aayush

Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.

1,159685

pdf-to-markdown

aliceisjustplaying

Convert entire PDF documents to clean, structured Markdown for full context loading. Use this skill when the user wants to extract ALL text from a PDF into context (not grep/search), when discussing or analyzing PDF content in full, when the user mentions "load the whole PDF", "bring the PDF into context", "read the entire PDF", or when partial extraction/grepping would miss important context. This is the preferred method for PDF text extraction over page-by-page or grep approaches.

1,331621

Stay ahead of the MCP ecosystem

Get weekly updates on new skills and servers.