====== PMP Overview ====== ===== Introduction ===== Many people hear the word: > PMP and immediately think: * difficult certification * exam questions * project manager role But PMP is much broader than an exam. PMP represents a professional framework for managing projects effectively. Understanding PMP helps professionals: * deliver work more predictably * communicate better * manage uncertainty * lead teams * align technical and business goals For software engineers and technical leaders, PMP provides structured management thinking that complements technical skills. ----- ===== What is PMP? ===== PMP stands for: > Project Management Professional It is a globally recognized certification and professional standard created by PMI. PMP validates knowledge and experience in project management. However, PMP is not merely a certificate. It represents: * project management principles * best practices * professional mindset * structured decision-making Think of PMP as: > A framework for professional project delivery. The certification is one part. The mindset and practices matter more in daily work. ----- ===== Who Created PMP? ===== PMP is maintained by: [[pmp:foundation:pmi_and_pmbok|PMI (Project Management Institute)]] PMI develops: * standards * methodologies * research * professional certifications PMP is their flagship credential. PMI continuously updates PMP to reflect modern project work. This includes: * predictive projects * Agile methods * hybrid delivery * leadership skills * business alignment Modern PMP is broader than traditional waterfall management. ----- ===== Why PMP Exists ===== Projects have existed for thousands of years. Examples: * pyramids * bridges * railways * software systems * digital transformation Historically, projects often suffered from: * delays * poor coordination * budget problems * communication failures Organizations needed a structured way to manage complexity. PMP emerged to standardize: * terminology * methods * processes * leadership practices Goal: Improve project success rates. PMP creates shared language and proven practices. ----- ===== PMP Is Not Only for Project Managers ===== A common misunderstanding: > PMP is only for PM job titles. This is false. Many professionals use PMP thinking: * team leads * engineering managers * architects * delivery managers * consultants * senior engineers * startup founders Anyone coordinating work and stakeholders can benefit. Modern technical work often requires PM capability. Technical expertise alone may not be sufficient. ----- ===== What PMP Teaches ===== PMP covers multiple dimensions of project delivery. Broad areas include: ===== Planning ===== Projects need direction. PMP teaches: * scope definition * scheduling * estimation * resource planning Planning reduces uncertainty. ----- ===== Risk Management ===== Projects contain uncertainty. PMP teaches: * identify risks * assess probability * estimate impact * prepare responses Good PMs think proactively. ----- ===== Stakeholder Management ===== Projects involve people. PMP teaches: * identify stakeholders * understand expectations * manage communication * resolve conflict People problems often matter more than technical problems. ----- ===== Execution and Delivery ===== PMP covers: * coordination * leadership * monitoring * quality control * change management Delivery requires continuous adjustment. ----- ===== Business Alignment ===== Projects exist for business value. PMP teaches: > Delivery is not enough. Projects should support: * strategy * customer needs * organizational goals Successful projects solve real problems. ----- ===== PMP Knowledge Areas ===== Traditional PMP organizes knowledge into multiple domains. Examples: * Integration Management * Scope Management * Schedule Management * Cost Management * Quality Management * Resource Management * Communication Management * Risk Management * Procurement Management * Stakeholder Management Each area addresses specific project challenges. You will study these individually later. Together they form a complete management system. ----- ===== PMP Process Groups ===== PMP also uses: > Process Groups These describe project flow. Five classic groups: ```text Initiating ↓ Planning ↓ Executing ↓ Monitoring & Controlling ↓ Closing ``` These align with: [[pmp:foundation:project_lifecycle|Project Lifecycle]] Process groups organize delivery work. They are not rigid phases— but management activities. ----- ===== Predictive, Agile, and Hybrid ===== Older PMP versions focused heavily on: Predictive (Waterfall) projects. Modern PMP evolved. Today it includes: ===== Predictive ===== Detailed upfront planning. Example: Construction. ----- ===== Agile ===== Iterative delivery. Example: Software development. ----- ===== Hybrid ===== Combination of both. Example: Cloud migration with Agile development and fixed compliance milestones. Modern PMP recognizes: No single method fits all projects. Flexibility matters. ----- ===== PMP Triangle of Talent ===== PMI emphasizes: > PMI Talent Triangle Professional capability includes: ===== Ways of Working ===== How projects are delivered. Examples: * predictive * Agile * hybrid ----- ===== Power Skills ===== Human leadership skills. Examples: * communication * negotiation * conflict management * influence * emotional intelligence ----- ===== Business Acumen ===== Understanding business context. Examples: * strategy * value * market needs * financial impact Modern PM requires balance. Not just process knowledge. ----- ===== PMP Certification Overview ===== PMP certification demonstrates professional competence. Typical requirements include: * project experience * project education * passing PMP exam Exam evaluates: * scenario thinking * judgment * leadership * project decision-making Memorization alone is insufficient. PMP increasingly focuses on: Real-world application. ----- ===== Why PMP Is Valuable ===== PMP provides several benefits. ===== Structured Thinking ===== PMP gives mental models. Instead of reacting randomly: Professionals think systematically. ----- ===== Better Communication ===== PMP provides shared language. Example: Terms like: * scope * risk * stakeholder * milestone Communication becomes clearer. ----- ===== Improved Leadership ===== PMP teaches: * influence * coordination * prioritization * decision-making Leadership improves. ----- ===== Career Growth ===== Many organizations value PMP. Benefits may include: * leadership opportunities * consulting work * international roles * management pathways PMP can support career progression. ----- ===== Real-World Software Example ===== Consider: EKS deployment project. Technical work: * Docker * Kubernetes * Terraform * AWS Technical skill alone does not guarantee success. Project also needs: Scope: What will be delivered? Schedule: When? Risk: What could fail? Stakeholders: Who approves? Communication: How is status reported? This is PMP thinking. Technology + management. Together. ----- ===== Common Misunderstandings ===== ===== Mistake 1 — PMP Is Bureaucracy ===== Some believe: PMP means paperwork. Not true. PMP promotes: Appropriate management. Goal: Reduce chaos. Not create unnecessary process. ----- ===== Mistake 2 — PMP Replaces Technical Skill ===== False. PMP complements technical expertise. Projects need both. Technical depth and delivery capability. ----- ===== Mistake 3 — PMP Is Only Waterfall ===== Outdated belief. Modern PMP includes: * Agile * hybrid * adaptive delivery Flexibility is central. ----- ===== PMP and Software Engineering ===== Software engineers increasingly perform project responsibilities. Examples: Estimating: Schedule management. Prioritizing: Scope management. Leading deployment: Execution management. Handling blockers: Risk management. Coordinating teams: Stakeholder management. PMP provides formal structure to strengthen these skills. This supports: * senior engineering * technical leadership * delivery ownership * consulting capability ----- ===== Why Learn PMP Before Certification ===== Many people rush toward exam preparation. But understanding comes first. Recommended path: Step 1: Learn concepts. Step 2: Apply to real work. Step 3: Develop PM mindset. Step 4: Consider certification. Certification without understanding has limited value. Practice matters. ----- ===== Key Takeaways ===== * PMP means Project Management Professional. * PMP is both certification and professional framework. * PMP teaches structured project delivery. * Modern PMP includes predictive, Agile, and hybrid approaches. * PMP emphasizes planning, leadership, communication, and business value. * PMP is useful beyond formal PM roles. * Technical professionals benefit from PMP thinking. ----- ===== Reflection Questions ===== * Which PM activities do I already perform? * Do I rely mostly on technical skill or also delivery skill? * Which PMP area seems most relevant to my work? * Would PMP thinking improve how I lead projects?