Course: Project Management Professional (PMP)
The Project Management Professional (PMP) chapter introduces core principles, methodologies, and best practices required for effective project delivery across industries. It frames project management as a disciplined practice of initiating, planning, executing, monitoring and controlling, and closing work to achieve defined objectives within time and budget constraints. The chapter highlights Agile and Scrum as flexible frameworks for iterative delivery, stakeholder collaboration, and rapid adaptation to changing requirements. It also integrates PMBOK guidance (PMBOK6 and PMBOK7), contrasting process-group and principle-based approaches to tailor practices to specific project contexts. Emphasis is placed on scope management techniques such as WBS, scope validation, and change control to prevent scope creep. Scheduling and resource planning chapters introduce tools like Gantt charts, CPM, and resource leveling to optimize timelines and allocations. Risk management sections demonstrate identification, qualitative and quantitative analysis, and response planning to protect project value. Quality planning, assurance, and control are presented with actionable metrics and feedback loops for continuous improvement. Procurement and stakeholder engagement chapters teach strategic sourcing, contract lifecycle, and communication planning to align expectations. The course advocates capturing lessons learned and institutionalizing them for organizational learning and improved outcomes. Practical exercises include WBS creation, schedule development, budget control, and retrospectives to reinforce applied skills. Overall, the chapter promotes adaptability, transparency, and stakeholder-centric value delivery as pillars of modern project management practice.Lesson
Subtitle: Project Management Professional (PMP)
Learning Outcomes
- Explain the five project process groups and their purpose.
- Compare Agile/Scrum with predictive (Waterfall) approaches and PMBOK6 vs PMBOK7 perspectives.
- Create a basic Work Breakdown Structure (WBS) and project schedule.
- Apply risk, quality, procurement, and stakeholder-management practices.
- Capture and use lessons learned to improve future projects.
Conceptual Explanation
This section condenses core concepts into an actionable summary and a compact reference table.
| Topic | Key Elements | Tools / Artifacts |
|---|---|---|
| Process Groups | Initiate • Plan • Execute • Monitor & Control • Close | Project Charter • PM Plan • Status Reports • Lessons Learned |
| Scope & WBS | Define objectives • Decompose into work packages | WBS, WBS Dictionary, Requirements Traceability Matrix |
| Schedule & Resources | Activities, dependencies, estimates, levelling | Gantt, CPM, Resource Histogram, Kanban |
| Risk & Quality | Identify, analyze, respond • Plan QA/QC | Risk Register, Mitigation Plans, Test Reports, PDCA |
| Agile / Scrum | Sprints, Product Backlog, Iterative delivery | User Stories, Sprint Backlog, Burndown Charts |
| Stakeholders & Communication | Identify, analyze, engage, report | Stakeholder Matrix, Communication Plan, Dashboards |
PMBOK6 provides process-oriented guidance while PMBOK7 emphasizes principles and performance domains; tailoring is required to choose processes, models, and artifacts that fit the project environment.
Bilingual (EN → বাংলা)
EN: Project management organizes work to deliver value on time and within budget through defined processes, stakeholder engagement, and continuous improvement.
বাংলা: প্রকল্প ব্যবস্থাপনা নির্দিষ্ট প্রক্রিয়া, স্টেকহোল্ডার অংশগ্রহণ এবং ধারাবাহিক উন্নতির মাধ্যমে সময়মতো এবং বাজেটের মধ্যে মূল্য প্রদান করার কাজগুলো সংগঠিত করে।
Answer
EN Key Terms → বাংলা
- Initiation — প্রারম্ভ
- Planning — পরিকল্পনা
- Execution — বাস্তবায়ন
- Monitoring & Controlling — পর্যবেক্ষণ ও নিয়ন্ত্রণ
- Closure — সমাপ্তি
- Risk — ঝুঁকি
- Stakeholder — স্টেকহোল্ডার / অংশগ্রহণকারী
Important Notes
- Always tailor frameworks—use PMBOK principles + Agile or predictive practices as appropriate.
- Document scope and change control rigorously to avoid scope creep.
- Engage stakeholders early and keep communication frequent and transparent.
- Use retrospectives and lessons learned to build organizational knowledge.
- Balance schedule, cost, and quality; monitor earned value and other KPIs to detect deviations early.
Exercises → True / False / Fill in the Blanks / MCQ / Matching / Descriptive / Creative
Activities
- Create a 6–8 item WBS for a simple software feature and map owners to work packages.
- Draft a two‑week sprint plan with backlog items, estimates, and a Definition of Done.
- Build a basic risk register with impact/probability and one mitigation per risk.
Answer
Sample WBS (high level): 1.0 Feature A • 1.1 Requirements • 1.2 UI Design • 1.3 Development • 1.4 Testing • 1.5 Deployment • 1.6 Documentation. Assign owners to 1.1–1.6 accordingly.
Sample Sprint Plan: Sprint Goal: Deliver login API + UI • Backlog Items: Login API (5 SP), UI Form (3 SP), Unit Tests (2 SP). DoD: Code reviewed, unit tested, integrated, deployed to staging.
Risk Register Example: R1 — Integration delay; Likelihood: Medium; Impact: High; Mitigation: Daily integration checks + CI pipeline alerts.
Vocabulary
- Work Breakdown Structure (WBS)
- Earned Value Management (EVM)
- Backlog, Sprint, User Story
- Change Control Board (CCB)
- Definition of Done (DoD)
Answer
WBS — hierarchical decomposition of scope. EVM — integrates scope, schedule, cost to assess performance. Backlog — ordered list of work; Sprint — time-boxed iteration; DoD — criteria for completeness.
Homework
- Read PMBOK7 principles and write a one-page reflection on how they change your approach to a current project.
- Interview a stakeholder and document their top three priorities and communication preferences.
Answer
Guidance: For the reflection, focus on tailoring, value delivery, and stakeholder engagement. For the interview, capture contact method, update frequency, and acceptance criteria.
Practice Task
Using a simple project (e.g., a one‑page website), produce: project charter, WBS, 4‑week schedule (Gantt/Kanban), risk register, and a stakeholder communication plan.
Answer
Provide a concise project charter: objective, scope, sponsor, high-level timeline, budget estimate, key stakeholders. Map WBS to schedule and risks; list weekly communications (status email + demo at week end).
True / False
- The Project Charter formally authorizes the project. (True/False)
- PMBOK7 removes the need for processes entirely. (True/False)
- Scope creep can be avoided by having no changes. (True/False)
Answer
- True — the charter authorizes the project.
- False — PMBOK7 emphasizes principles and tailoring but processes remain useful; it does not remove processes.
- False — changes are natural; proper change control and stakeholder engagement manage scope creep, not forbidding change.
Fill in the Blanks
- The five process groups are Initiating, ______, Executing, Monitoring & Controlling, and Closing.
- In Scrum, the time‑boxed iteration is called a ______.
- A WBS work package should follow the ______ Rule (captures 100% of the scope).
Answer
- Planning
- Sprint
- 100% Rule
MCQ (Multiple Choice)
- Which artifact prioritizes work in Scrum?
- Project Charter
- Product Backlog
- WBS
- Gantt Chart
- Which metric integrates scope, schedule, and cost?
- CPM
- EVM
- MoSCoW
- RACI
Answer
- b) Product Backlog
- b) Earned Value Management (EVM)
Matching
Match the item to its primary purpose:
| Item | Purpose |
|---|---|
| A. Stakeholder Matrix | 1. Visualize task dependencies |
| B. Gantt Chart | 2. Identify and prioritize stakeholders |
| C. WBS | 3. Decompose deliverables into work packages |
Answer
Matches: A → 2; B → 1; C → 3.
Descriptive
Describe how you would handle a mid‑project change request that impacts scope and schedule.
Answer
Steps: 1) Log the change request in change register; 2) Assess impact on scope, schedule, cost, quality, and risks; 3) Consult stakeholders and, if applicable, Change Control Board; 4) Approve/reject or negotiate scope/time/cost tradeoffs; 5) Update project plan, communicate changes, and monitor implementation; 6) Record lessons learned.
Creative
Design a one‑page poster that summarizes Agile values and PMBOK7 principles for team orientation.
Answer
Poster elements: Agile values on left (individuals, working product, collaboration, responding to change), PMBOK7 principles on right (stewardship, value delivery, stakeholder engagement, adaptability), center: “Tailor, Inspect, Adapt”. Use icons for sprints, stakeholders, checklist, and lightbulb for lessons learned.
Further reading: PMBOK Guide (6th & 7th editions) • Agile Manifesto • Scrum Guide • Relevant PMI resources.