T13: Methodology | Domain 2

📖 Choosing the Right Approach

🇺🇸 English

The correct methodology depends on:

Requirements clarity: Clear/stable → Predictive. Unclear/evolving → Agile.
Delivery frequency: One final delivery → Predictive. Frequent incremental delivery → Agile.
Risk tolerance: Low tolerance + regulatory → Predictive with gates. High tolerance + innovation → Agile.
Customer involvement: Low availability → Predictive. Active, engaged → Agile.
Team experience: Agile requires experienced, self-organized teams

Tailoring: Adapting the chosen methodology to project context. No methodology is applied 100% as-prescribed — always tailor.

Reference: PMI Disciplined Agile — Methodology Selection

🇻🇳 Tiếng Việt

Methodology đúng phụ thuộc vào:

Độ rõ ràng của requirements: Rõ/ổn định → Predictive. Không rõ/thay đổi → Agile.
Tần suất giao hàng: Giao một lần cuối → Predictive. Giao thường xuyên theo increments → Agile.
Mức độ tham gia của khách hàng: Ít tham gia → Predictive. Tích cực, engaged → Agile.

Tailoring: Thích nghi methodology đã chọn với ngữ cảnh dự án. Không methodology nào được áp dụng 100% như mô tả — luôn tailoring.

📊 Methodology Comparison

Factor	Predictive (Waterfall)	Agile (Scrum/Kanban)	Hybrid
Requirements	Fixed upfront, detailed	Evolving, prioritized backlog	Core fixed, features flexible
Delivery	Single delivery at end	Working increment every sprint	Phase deliveries + sprint releases
Planning	Comprehensive upfront	Sprint-by-sprint, rolling	High-level upfront + detailed per phase
Change	Formal CCB, change control	Welcome, through backlog	CCB for major; backlog for enhancements
Team structure	Functional, hierarchical	Cross-functional, self-organizing	Balanced, PM + Scrum Master
Best for	Construction, infrastructure, compliance-heavy	Software, innovative products, startup	Complex tech + regulatory, fintech
PM role	Command and control	Servant leader / coach	Adaptive facilitator

🔄 Agile Frameworks Comparison

Framework	Key Structure	Best For	Key Roles
Scrum	Time-boxed sprints (1-4 weeks), defined ceremonies	Feature development, product teams	PO, Scrum Master, Dev Team
Kanban	Continuous flow, WIP limits, pull system	Operations, support, maintenance	No prescribed roles; team-defined
XP (Extreme Programming)	Engineering practices: TDD, pair programming, CI	High-quality software development	Customer, Coach, Programmers
SAFe	Scaled agile: PI Planning, ARTs (Agile Release Trains)	Large enterprises, multiple teams	RTE (Release Train Engineer), PO, PM/PdM
LeSS	Multiple Scrum teams sharing single product backlog	Multi-team product development	Same as Scrum, scaled

Methodology Selection Decision Guide

QUESTION: Which approach for this project? Q1: Are requirements well-understood and stable? YES → Consider Predictive NO → Consider Agile Q2: Will customer/stakeholders be available for frequent feedback? YES → Agile favored NO → Predictive or Hybrid Q3: Is there regulatory/compliance requirement for full documentation? YES → Predictive or Hybrid (compliance phases predictive) NO → Agile ok Q4: Can value be delivered in increments? YES → Agile or Hybrid NO → Predictive (e.g., bridge — you can't use "half a bridge") Q5: Is the team experienced with agile practices? YES → Agile possible NO → Predictive or light Hybrid (Scrum but with PM oversight) FinTech Company X answer: HYBRID Core platform: Predictive (fixed contract, compliance requirements) Feature sprints: Agile (evolving partner needs, frequent delivery)

🎯

Exam Tips — Methodology Selection

PMP doesn't test Scrum/SAFe theory deeply — tests when to use which approach
50% of exam questions have agile/hybrid context — know Scrum ceremonies and roles well
Tailoring is always the correct approach — no methodology is one-size-fits-all
Agile works best when: innovative product, evolving requirements, engaged customer, experienced team
Predictive works best when: stable requirements, fixed contract, regulatory mandate, physical deliverables
The PM role in agile = servant leader, not command-and-control. Remove impediments, protect team.

💼 Thực chiến / Scenario

🏢

FinTech Company X — Hybrid Methodology Design

Challenge: Project Alpha phải satisfy hai masters: (1) Bank Partner A yêu cầu formal project governance, SLAs, và milestone-based reporting — predictive-friendly. (2) Internal product team muốn deliver features incrementally, gather market feedback, và adapt quickly — agile-friendly.

Hybrid design decision:

Phase 1 — Foundation (Predictive): Infrastructure, compliance features, partner integration. Fixed scope, milestone-based. Formal documentation. 3 months.
Phase 2 — Feature Sprints (Agile): 2-week sprints, prioritized backlog. Sprint reviews with internal stakeholders. Velocity-based forecasting. 6 months.
Governance layer (always-on): Weekly PM status report, monthly steering committee, change control board for major changes.

Team structure: PM (overall coordination, governance), Tech Lead (Phase 1 architecture), Scrum Master (Phase 2 sprint facilitation), Product Owner (backlog, priority). Not one person wearing all hats — clear separation of concerns.

Result: Partner gets predictability (Phase 1 milestone contracts), product team gets flexibility (Phase 2 backlog). Both objectives met through tailored hybrid.

✏️ Practice Questions

Question 1

A project involves building a financial compliance system with detailed regulatory requirements that must be met before launch. Requirements are fully defined and cannot change after approval. What is the BEST methodology?

A. Scrum with 2-week sprints
B. Kanban with WIP limits
C. Predictive (waterfall) with formal phase gates
D. SAFe with Program Increment planning

✅ Answer: C — Predictive with phase gates. Fixed, detailed regulatory requirements, no change allowed, formal compliance documentation — these characteristics favor predictive methodology. Phase gates ensure compliance checkpoints before proceeding. Agile approaches (A, B, D) are designed for evolving requirements and incremental delivery, which doesn't fit this context.

Question 2

A project team is using Scrum but the organization requires formal sign-off on deliverables before payment from a government client. What is the BEST approach?

A. Abandon Scrum entirely and use waterfall
B. Use a hybrid: Scrum for development execution, with formal phase gates and documentation for contractual sign-offs
C. Ask the government client to accept informal sprint reviews
D. Use Scrum without changes and manage the sign-off informally

✅ Answer: B — A hybrid approach tailors methodology to the project's context. Scrum provides iterative delivery and team efficiency; the predictive governance layer (phase gates, formal documentation) satisfies the contractual and regulatory requirements of the government client. Abandoning Scrum entirely (A) sacrifices flexibility unnecessarily. Asking the client to accept informal reviews (C) ignores a contractual reality. Running Scrum unchanged with informal sign-offs (D) creates legal and compliance exposure.

Question 3

According to PMI, tailoring a methodology means:

A. Using any approach the PM prefers regardless of project context
B. Selecting and adapting processes, methods, and tools to best fit the specific project environment, team, and organizational context
C. Reducing documentation to save time
D. Using the simplest possible approach on every project

✅ Answer: B — PMI's PMBOK 7th Edition emphasizes tailoring as an intentional, context-driven adaptation of processes, methods, and tools. It is not about preference (A), simplification (C), or defaulting to minimal approaches (D). Tailoring decisions consider project complexity, stakeholder needs, organizational culture, risk, and regulatory environment — then select the most appropriate combination of practices for that specific situation.

🤖 AI Tools for PMs

🤖

How AI Augments This Process

AI helps PMs evaluate methodology options, design hybrid frameworks, create tailoring decision matrices, and document methodology selection rationale for stakeholders.

Sample Claude Prompts

Methodology selection advisory Help me select the right project methodology for my project. Project characteristics: Deliverable type: [software / physical product / process change / organizational change] Requirements clarity: [fully defined / partially defined / highly volatile] Stakeholder availability for feedback: [weekly / monthly / limited access] Team experience with Agile: [high / medium / low] Regulatory/compliance requirements: [strict documentation required / flexible] Schedule flexibility: [fixed deadline / flexible / iterative releases okay] Risk tolerance: [low / medium / high] Org culture: [hierarchical / collaborative / startup-like] Evaluate these methodologies for this project: 1. Predictive (Waterfall): pros, cons, when it fits 2. Scrum: pros, cons, when it fits 3. Kanban: pros, cons, when it fits 4. Hybrid (Scrum for dev + predictive for governance): pros, cons 5. SAFe or LeSS (if >3 teams needed): brief note Recommend the best approach with: - Primary recommendation and rationale - 3 risks with the chosen approach and mitigations - How to present this decision to a skeptical sponsor

Agile tailoring for regulated environment I'm implementing Agile in a regulated / compliance-heavy environment. Help me tailor the approach. Industry: [fintech / healthcare / government / pharma] Regulatory requirements: [specific regulations — SOX, PCI-DSS, HIPAA, etc.] Documentation mandated: [what records must be kept] Approval gates required: [sign-offs at specific stages] Audit trail needed: [yes — what kind] Current org maturity with Agile: [beginner / intermediate / advanced] Design a "compliance-ready Agile" framework that: 1. Identifies which Agile ceremonies to keep, modify, or replace 2. Defines documentation generated at each sprint (to satisfy auditors) 3. Designs approval checkpoints that don't disrupt sprint cadence 4. Creates a traceability approach: requirement → story → test → release 5. Shows how to handle regulatory change requests within Agile 6. Gives me language to explain this hybrid to both the Agile team AND the compliance auditors

Methodology transition plan We are transitioning from [Waterfall / ad-hoc] to [Scrum / Kanban / SAFe]. Help me plan the transition. Current state: [methodology being used, team size, duration of current approach] Target state: [desired methodology] Transition trigger: [why we're changing — management decision / failed delivery / new leadership] Team readiness: [have they done Agile before? any Agile champions?] Stakeholder buy-in: [sponsor supportive / neutral / skeptical] Timeline available for transition: [months] Org change complexity: [just our team / whole department / enterprise] Create a methodology transition plan: 1. Transition phases (assess / prepare / pilot / scale) 2. Training needs by role 3. Tooling changes needed (Jira setup, Confluence templates) 4. First sprint design (what to do in the first 2 weeks to demonstrate value) 5. Success metrics for the transition 6. Rollback criteria (when to admit this isn't working and adjust) 7. How to handle in-flight projects during the transition

Jira / Confluence Template

Confluence — Methodology Decision Record

── CONFLUENCE: METHODOLOGY DECISION RECORD ────────────── Project: [Project Alpha] | PM: [name] | Date: [YYYY-MM-DD] Sponsor: [name] | Approved: [ ] Yes [ ] Pending ── PROJECT CHARACTERISTICS ─────────────────────────────── Requirements clarity: [High / Medium / Low] Change likelihood: [High / Medium / Low] Delivery cadence: [Single delivery / Incremental releases / Continuous] Team Agile maturity: [High / Medium / Low] Regulatory constraints: [Yes — specify / No] ── SELECTED METHODOLOGY ────────────────────────────────── Approach: [Scrum / Kanban / SAFe / Hybrid / Predictive] Rationale: [2 sentences — why this fits the project profile] Tailoring: Kept: [standard practices retained] Modified: [practices adapted — explain why] Dropped: [practices eliminated — explain why] Added: [custom practices added for this context] ── RISKS ───────────────────────────────────────────────── Risk 1: [methodology risk] → Mitigation: [action] Risk 2: [methodology risk] → Mitigation: [action]

Determine Appropriate Project Methodology / Methods and Practices