T01: Business Value | Domain 2

📖 Lý thuyết / Theory

🇺🇸 English

Business value is the ultimate purpose of any project. It includes tangible benefits (revenue, cost savings, market share) and intangible benefits (brand, goodwill, employee satisfaction, capability).

Value delivery urgency means not waiting until the end of the project to deliver value. In Agile, this is fundamental — deliver working software in every iteration. In predictive, it means identifying and prioritizing high-value deliverables early.

PM's role: Continuously align project work with business objectives. Challenge scope items that don't contribute to business value. Facilitate rapid value delivery.

Reference: PMI — Value Delivery Principles

🇻🇳 Tiếng Việt

Giá trị kinh doanh là mục đích cuối cùng của bất kỳ dự án nào. Bao gồm lợi ích hữu hình (doanh thu, tiết kiệm chi phí, thị phần) và vô hình (thương hiệu, thiện chí, sự hài lòng nhân viên, năng lực).

Sự khẩn cấp trong value delivery nghĩa là không đợi đến cuối dự án mới deliver value. Trong Agile, điều này là cơ bản — deliver working software trong mỗi iteration.

Vai trò PM: Liên tục align công việc dự án với mục tiêu kinh doanh. Challenge scope items không đóng góp vào business value.

🎯 Business Value Framework

Value Type	Description	Examples (Fintech)	How PM Enables
Revenue	Direct income generation	Loan volume increase; conversion rate; new partner fee	Prioritize features that drive revenue metrics
Cost Reduction	Savings vs current state	Reduced manual processing; fewer errors; automated decisioning	Track automation ROI; quantify efficiency gains
Risk Reduction	Reducing exposure	Better fraud detection; compliance coverage; SLA penalties avoided	Prioritize compliance and security features
Customer Experience	User satisfaction, retention	Faster onboarding (from 20min to 5min); mobile UX improvement	Include user research in requirements; measure NPS
Strategic Capability	Building for future	Multi-tenant platform enables new markets; API-first enables integrations	Balance short-term features with platform investments

🔧 MVP & Incremental Value Delivery

🇺🇸 English

MVP (Minimum Viable Product) — the smallest version of a product that delivers value and can be released to get real feedback. Not the smallest possible version, but the smallest viable one.

MBI (Minimum Business Increment) — the smallest change that delivers meaningful business value. Used in SAFe and enterprise agile frameworks.

In iteration/sprint planning, always ask: "What is the minimum we need to deliver to create real value for this sprint?"

🇻🇳 Tiếng Việt

MVP (Minimum Viable Product) — phiên bản nhỏ nhất của sản phẩm deliver value và có thể release để nhận feedback thực tế. Không phải nhỏ nhất có thể, mà là nhỏ nhất viable.

MBI (Minimum Business Increment) — thay đổi nhỏ nhất deliver business value có ý nghĩa. Dùng trong SAFe và enterprise agile.

🎯

Exam Tips — Business Value

PM phải continually evaluate project alignment với business objectives, không chỉ ở đầu dự án
Agile: value delivered every sprint — không phải chỉ cuối project
Nếu project không còn aligned với business goals → PM nên raise to sponsor về continuing vs. closing
"Urgency" không nghĩa là vội vàng — nghĩa là ưu tiên high-value items và không delay unnecessarily
Business case → project charter → project: value chain phải maintained throughout

🔧 Business Value Scorecard

Business Value Scorecard — Project Alpha

── REVENUE IMPACT ─────────────────────────────────── Metric: Loan disbursement volume (VND billion/month) Baseline: 50B/month (manual process) Target: 200B/month post-launch (4x via automation) Current: 80B/month (Sprint 3 partial automation live) ── COST REDUCTION ─────────────────────────────────── Metric: Manual underwriting hours per 1,000 applications Baseline: 400 hrs/1K applications Target: 50 hrs/1K applications (87.5% reduction) Current: 180 hrs/1K (55% reduction achieved so far) ── RISK REDUCTION ─────────────────────────────────── Metric: Compliance audit findings (critical/major) Baseline: 12 findings in last audit Target: 0 critical, <3 major Current: Audit logging module deployed; re-audit scheduled Sprint 6 ── CUSTOMER EXPERIENCE ────────────────────────────── NPS: Baseline 32 → Target 50 Approval time: Baseline 3 days → Target 15 minutes Error rate: Baseline 8% → Target <1%

💼 Thực chiến / Scenario

🏢

FinTech Company X — Prioritizing for Business Value

Tình huống: Sprint planning cho sprint 5 của Project Alpha. Backlog có 40 story points. Team velocity = 25 SP/sprint. Cần prioritize.

Stories available: A) Partner API integration (15 SP) — blocks go-live. B) Admin dashboard UI polish (10 SP) — nice to have. C) Credit decision engine v2 (20 SP) — key differentiator. D) Compliance audit logging (8 SP) — regulatory requirement.

Business value analysis: D (Compliance) là không tùy chọn — regulatory = highest business risk. A (Partner API) là P0 — without it, no go-live. C (Credit decision) là high value but too large for this sprint. B (UI polish) = lowest business impact.

Decision: Sprint 5 = D + A + partial C (decompose into smaller slices). B pushed to later sprint. This is value-driven prioritization.

✏️ Practice Questions

Question 1

Midway through a project, the business case assumptions change significantly due to market conditions. The project's planned deliverables may no longer provide the expected ROI. What should the PM do FIRST?

A. Continue with the original plan since it was approved by the sponsor
B. Re-evaluate the project business case with the sponsor and present options: continue, modify, or terminate
C. Immediately stop the project to avoid wasting resources
D. Reduce project scope to bring costs down and maintain ROI

✅ Answer: B — PM continuously evaluates business value alignment. When the business case changes, PM must bring this to the sponsor with options and transparent information. Option A ignores reality. Option C (immediate stop) is too drastic without consulting sponsor. Option D assumes scope reduction is the solution without analyzing whether the project should continue at all.

Question 2

A PM is planning sprint 3. The backlog has: Feature A (8 SP, revenue-generating), Feature B (5 SP, compliance requirement), Feature C (13 SP, nice-to-have UI improvement). Team velocity is 20 SP. What should the PM prioritize?

A. Feature A + C (both fit in velocity)
B. Feature B + Feature A (compliance first, then revenue)
C. Feature C first since it's the largest
D. Feature A only, use remaining capacity for documentation

✅ Answer: B — Compliance is non-negotiable business value — regulatory risk trumps feature preferences. Feature B (5 SP) must be done. Feature A (8 SP, revenue) is the next highest value. Together they use 13 SP, leaving 7 SP for partial work on Feature C or other high-priority items. Feature C (nice-to-have UI) has the lowest business value and should be deprioritized. Choosing A + C (option A) ignores the compliance requirement entirely, which is a risk management failure.

Question 3

A project has been running for 4 months and delivered all planned features. However, 6 months post-launch, users are not adopting the system and no business benefits are materializing. This represents a failure of:

A. Scope management — wrong features were built
B. Value realization management — delivering outputs without ensuring outcomes and benefits
C. Quality management — the system must have bugs
D. Communication — users weren't informed

✅ Answer: B — Outputs ≠ outcomes ≠ benefits. The project delivered its outputs (planned features) but failed to realize business value. This is a value realization management failure — the PM and organization did not track or ensure that deliverables translated into actual benefits (adoption, usage, business results). A well-run project includes a benefits realization plan and post-launch monitoring. Scope (A) may be correct but is secondary — the real gap is benefits tracking. Quality (C) is speculation. Communication (D) may be a contributing factor but not the root cause.

🤖 AI Tools for PMs

🤖

How AI Augments This Process

AI helps PMs draft status reports, generate executive summaries, analyze project health signals, and synthesize team updates into clear leadership communications.

Sample Claude Prompts

Weekly status report generation Generate a project status report for my stakeholders. Project: [project name] | Week: [week number / date range] Overall status: [ ] Green [ ] Amber [ ] Red Reason for status: [1-sentence explanation if Amber/Red] Accomplishments this week: - [bullet 1] - [bullet 2] - [bullet 3] Next week plan: - [bullet 1] - [bullet 2] Risks/Issues: - [Risk/Issue + mitigation/action] Metrics: Schedule: [SPI value or % complete] | Budget: [CPI or % spent] | Quality: [defect count / test pass rate] Write a status report in two formats: 1. Executive summary (4 sentences, for sponsor/C-suite) 2. Full report (1 page, for steering committee) Tone: professional, transparent, solution-oriented.

Sprint/phase execution health check I want a quick health check of my project execution. Here's the data: Planned vs. actual velocity (last 3 sprints): [e.g., 40/42, 40/35, 40/28] Scope creep instances last month: [count] Open blockers: [count and average age in days] Team satisfaction (1-5): [score from last retro] Stakeholder satisfaction (1-5): [score from last review] Budget burn rate: [on track / ahead / behind] Quality metrics: [defect rate, test coverage %] Analyze this data and: 1. Identify the 2 biggest execution risks right now 2. Diagnose if the velocity trend indicates a systemic problem 3. Give me 3 specific corrective actions to implement this sprint 4. Tell me what leading indicator to watch most closely next week

Executive briefing preparation I'm presenting to [C-level executive / board / sponsor] who has [5 / 10 / 15] minutes. They care most about: [business outcome / risk / budget / timeline] My project status: [overall health + key numbers] The one decision I need from them: [what I need them to decide or approve] Potential concerns they'll raise: [anticipate their questions] Structure my briefing as: 1. Headline (1 slide): where we are in 3 numbers or less 2. Progress (1 slide): what's done, what's next 3. Risk (1 slide): top risk + mitigation status 4. Ask (1 slide): the specific decision needed Also draft the 90-second verbal opening that gets their attention.

Jira / Confluence Template

Confluence — Weekly Status Report

── CONFLUENCE: WEEKLY STATUS REPORT ───────────────────── Project: [Project Alpha] | Week: [YYYY-WNN] | PM: [name] Status: 🟢 Green / 🟡 Amber / 🔴 Red Summary: [1 sentence — what the PM most wants leadership to know] ── THIS WEEK ───────────────────────────────────────────── Completed: ✓ [Deliverable / milestone — link to Jira epic or Confluence page] ✓ [...] In Progress: → [Work in progress — % complete, due date] ── NEXT WEEK ───────────────────────────────────────────── • [Planned activity — owner] • [Planned milestone — target date] ── RISKS & ISSUES ──────────────────────────────────────── Risk: [Description] | Prob: H/M/L | Impact: H/M/L | Mitigation: [action] Issue: [Description] | Owner: [name] | Due: [date] | Status: [open/resolving] ── METRICS ─────────────────────────────────────────────── SPI: [value] | CPI: [value] | Velocity: [SP] | Open blockers: [count]

Execute Project with Urgency to Deliver Business Value