Promise-Driven Development: Foundations
From Shipping Features to Keeping Promises
Master Course Document v1.0
Offered by: Canadian Institute of Software Product Management (CISPM)
Audience: Software Engineers
Duration: 6 units × 3 hours (18 contact hours)
Format: 45-45-45 (Lecture – Exercise – Synthesis)
Version: 1.0
Last Updated: January 2026
Course Overview
Catalog Description (75 words)
This course introduces Promise-Driven Development (PDD), a methodology for organizing software product development around explicit value commitments to users. Software engineers master the five-level Promise Model Stack, learn to distinguish between feature delivery and value delivery, and develop competency in promise discovery, mapping, and product coherence evaluation. Through evidence-based instruction and applied exercises, engineers gain frameworks for principled product decisions—skills that differentiate them throughout their careers.
Positioning
For software engineers transitioning from project-based thinking to product-based thinking. This course addresses the gap between shipping features and delivering value—skills that differentiate engineers in their careers.
Core Message
Software teams ship features. Successful products keep promises.
You've spent years building projects. Now it's time to build products. The difference isn't just scope—it's mindset. Projects end; products evolve. Projects have requirements; products make promises. This course bridges that gap.
Course Learning Outcomes (CLOs)
Upon successful completion of this course, software engineers will be able to:
| CLO | Outcome | Bloom's Level |
|---|---|---|
| CLO 1 | Explain the Promise-Driven Development paradigm and describe how it addresses limitations of feature-driven approaches to software product development | Understand |
| CLO 2 | Apply the Promise Model Stack architecture to analyze and structure software products across five levels (Promise → Epic → Journey → Flow → Moment) | Apply |
| CLO 3 | Analyze the progression from user input to validated promise and distinguish between promise hypotheses and commitments | Analyze |
| CLO 4 | Evaluate proposed features and scope decisions using promise-driven criteria, demonstrating rationale for inclusion, modification, or rejection | Evaluate |
| CLO 5 | Construct initial Promise Maps for novel software product contexts | Create |
CLO ↔ ULO Mapping Matrix
| ULO | CLO 1 | CLO 2 | CLO 3 | CLO 4 | CLO 5 |
|---|---|---|---|---|---|
| 1.1 | P | ||||
| 1.2 | P | ||||
| 1.3 | P | ||||
| 1.4 | P | ||||
| 2.1 | S | P | |||
| 2.2 | S | P | |||
| 2.3 | P | ||||
| 2.4 | P | ||||
| 3.1 | P | ||||
| 3.2 | P | S | |||
| 3.3 | P | S | |||
| 3.4 | P | ||||
| 4.1 | P | ||||
| 4.2 | P | ||||
| 4.3 | P | ||||
| 4.4 | S | P | |||
| 5.1 | P | ||||
| 5.2 | P | S | |||
| 5.3 | P | ||||
| 5.4 | P | ||||
| 6.1 | S | S | S | P | |
| 6.2 | S | P | S | P | |
| 6.3 | S | S | P | S | |
| 6.4 | S | S | P | S |
P = Primary alignment | S = Supporting alignment
Note: Unit 6 (Applying PDD) serves as the synthesis unit, integrating all five CLOs.
Bloom's Progression Summary
| Unit | Title | Bloom's Range | Key Verbs |
|---|---|---|---|
| 1 | Software as Promise | Understand | Distinguish, Explain, Identify, Recognize |
| 2 | The Promise Model Stack | Understand → Apply | Define, Explain, Apply, Analyze |
| 3 | Software Moments | Understand → Analyze | Define, Classify, Analyze, Predict |
| 4 | Promise Discovery | Understand → Evaluate | Define, Explain, Distinguish, Evaluate |
| 5 | Product Coherence | Apply → Evaluate | Apply, Trace, Identify, Demonstrate |
| 6 | Applying PDD | Analyze → Create | Identify, Construct, Evaluate, Demonstrate |
Delivery Context
Session Structure (per unit)
Each 3-hour session follows a 45-45-45 format with breaks:
| Block | Duration | Focus | Description |
|---|---|---|---|
| Block 1: Lecture | 45 min | Exposition + Activation | Core concepts with prereading activation woven throughout |
| Break | 10 min | ||
| Block 2: Exercise | 45 min | Applied Practice | Jam session: teams create artifacts, pitch to peers |
| Break | 10 min | ||
| Block 3: Synthesis | 45 min | Discussion + Integration | Debrief exercises, sharpen concepts, connect to work |
Total structured time: ~2.5 hours
Total session time: ~3 hours (including breaks)
Exercise Format: Jam Sessions
Block 2 exercises use a consistent structure:
| Phase | Time | Description |
|---|---|---|
| Intro | 5 min | Explain activity, form teams, distribute materials |
| Create | 15-20 min | Teams produce artifact |
| Pitch | 5 min × rotations | One team presents; another listens and challenges |
| Rotate | 10-15 min | Repeat with new pairings |
| Wrap | 5 min | Refine artifact, prep for debrief |
Class Context
| Parameter | Typical Range |
|---|---|
| Class size | 20-30 engineers per section |
| Team size | 3-6 engineers per team |
| Teams per section | 5-6 teams |
Prereading by Unit
| Unit | Prereading | Time |
|---|---|---|
| 1 | Chapter 1 + Intro Narrative | ~35 min |
| 2 | None | — |
| 3 | None | — |
| 4 | Promise Discovery Overview | ~20 min |
| 5 | None | — |
| 6 | None | — |
Total prereading: ~55 minutes across 6 weeks
Slide Pacing Guidelines
| Context | Time/Slide | Notes |
|---|---|---|
| Unit 1 Lecture | ~2.8 min/slide | Discussion-heavy, foundational |
| Units 2-5 Lecture | ~2.2-2.5 min/slide | Teaching pace |
| Unit 6 Lecture | ~2.2-2.5 min/slide | Integration focus |
| Synthesis blocks | ~3-3.5 min/slide | Discussion-heavy |
| Exercise blocks | N/A | On-screen support, not presentation |
Unit Outlines
Unit 1: Software as Promise
Theme: From Project to Product
Prereading: Chapter 1 + Intro Narrative (~35 min)
Primary CLO: CLO 1
Unit Learning Outcomes
| ULO | Outcome | Bloom's |
|---|---|---|
| 1.1 | Distinguish between project-based and product-based thinking in software development | Understand |
| 1.2 | Explain why organizing software product development around explicit promises produces more coherent outcomes than organizing around features | Understand |
| 1.3 | Identify symptoms of promise-incoherent product development (scope creep, feature orphans, "agile theater") | Understand |
| 1.4 | Recognize implicit and explicit promises in familiar software products | Understand |
Mastery Indicators
- Accurately distinguishes feature-driven from promise-driven framing in case examples
- Articulates the organizational alignment benefits of explicit promises
- Recognizes promise-incoherence patterns without prompting
- Explains why product thinking matters for engineering careers
Block 1: Lecture (45 min)
| # | Topic | ULO | Time | Slides |
|---|---|---|---|---|
| 1.1 | Welcome & Course Framing | — | 5 min | • Unit 1 Title • Why You're Here • The 6-Unit Journey |
| 1.2 | From Project to Product | 1.1 | 10 min | • Projects vs. Products • Projects End, Products Evolve • Requirements vs. Promises |
| 1.3 | The Promise Paradigm | 1.2 | 10 min | • What Is a Promise? • Features Ship, Promises Keep • Promise Examples: Netflix, Uber, LinkedIn |
| 1.4 | What Breaks Without Promises | 1.3 | 10 min | • Symptoms of Incoherence • Scope Creep • Feature Orphans • Agile Theater |
| 1.5 | Seeing Promises in the Wild | 1.4 | 10 min | • Implicit vs. Explicit Promises • Reverse-Engineering Promises • Exercise Setup |
Slide count: ~16 | Pace: ~2.8 min/slide
Block 2: Exercise (45 min)
Activity: Promise Safari
| Phase | Activity | Time | Slides |
|---|---|---|---|
| Intro | Explain activity, form teams, select product | 5 min | • Promise Safari: What You'll Do • Instructions & Artifact Template • Pick Your Product |
| Create | Identify 2-3 promises. Complete worksheet. | 15 min | • On-Screen: Worksheet Template • On-Screen: Timer • On-Screen: Prompt "What value does this promise?" |
| Pitch | Team presents. Other team reflects back. | 5 min × rotations | • Jam Session Rules • Pitch (3 min) + Reflect (2 min) • On-Screen: Timer |
| Rotate | Switch partners, repeat 2-3 times | 15-20 min | • Rotate Now • On-Screen: Timer |
| Wrap | Refine promises, prep for debrief | 5 min | • Capture Your Refinements • What Changed? |
Slide count: ~10-12
Artifact: Promise Identification Worksheet
Block 3: Synthesis (45 min)
| # | Topic | Time | Slides |
|---|---|---|---|
| 3.1 | Debrief: What Did You Notice? | 15 min | • Debrief Questions • What Was Hard? • Where Did You Disagree? |
| 3.2 | Implicit vs. Explicit: The Netflix Example | 10 min | • "Love Is Sharing a Password" • The Emotional Contract • When Promises Break |
| 3.3 | Connecting to Your Work | 10 min | • Your Product's Promises • Discussion Prompt |
| 3.4 | Preview: The Promise Model Stack | 5 min | • Next Week: Structure • The 5-Level Stack (Teaser) |
| 3.5 | Close | 5 min | • Key Takeaway • Questions? |
Slide count: ~10-12
Unit 1 Summary
| Block | Time | Slides | Pace |
|---|---|---|---|
| Lecture | 45 min | ~16 | ~2.8 min/slide |
| Exercise | 45 min | ~10-12 | N/A |
| Synthesis | 45 min | ~10-12 | ~3.5 min/slide |
| Total | 135 min | ~36-40 |
Unit 1 Materials
| Material | Description |
|---|---|
| Slides | Unit 1 deck |
| Exercise Guide | Promise Safari instructions |
| Artifact Template | Promise Identification Worksheet |
| Exemplar | Completed worksheet (Uber or Netflix) |
| Quiz Bank | 5-7 prereading activation questions |
Unit 2: The Promise Model Stack
Theme: Architecture of Value
Prereading: None
Primary CLO: CLO 2
Unit Learning Outcomes
| ULO | Outcome | Bloom's |
|---|---|---|
| 2.1 | Define each level of the Promise Model Stack: Promise, Epic, Journey, Flow, Moment | Understand |
| 2.2 | Explain the purpose of Promise 0 (Universal Definition of Done) and how it keeps Moments DRY | Understand |
| 2.3 | Apply the 3-5 constraint system to evaluate product structure | Apply |
| 2.4 | Analyze the structure of a familiar product using the Promise Model Stack | Apply |
Mastery Indicators
- Accurately diagrams the five-level stack from memory
- Correctly categorizes product elements by stack level
- Detects constraint violations in case examples with 80%+ accuracy
- Explains how Promise 0 eliminates repetition across Moments
Block 1: Lecture (45 min)
| # | Topic | ULO | Time | Slides |
|---|---|---|---|---|
| 2.1 | Recap & Bridge | — | 5 min | • Unit 2 Title • Last Week: Promises • This Week: Structure |
| 2.2 | The Five Levels | 2.1 | 15 min | • The Promise Model Stack • Promise: Why We Exist • Epic: Major Capabilities • Journey: User Experiences • Flow: Process Sequences • Moment: Implementation Units |
| 2.3 | Promise 0: The Universal DoD | 2.2 | 8 min | • What Is Promise 0? • Keeping Moments DRY • Promise 0 Examples |
| 2.4 | The 3-5 Constraint | 2.3 | 10 min | • Why 3-5? • Too Few = Incomplete • Too Many = Incoherent • Constraint in Practice |
| 2.5 | Stack in the Wild | 2.4 | 7 min | • Uber's Stack (Walkthrough) • Exercise Setup |
Slide count: ~18-20 | Pace: ~2.2-2.5 min/slide
Block 2: Exercise (45 min)
Activity: Stack Mapping
| Phase | Activity | Time | Slides |
|---|---|---|---|
| Intro | Explain activity, form teams, select product | 5 min | • Stack Mapping: What You'll Do • Instructions & Artifact Template • Pick Your Product |
| Create | Map product to stack: 1 Promise → 2 Epics → 2 Journeys each | 20 min | • On-Screen: Stack Template Reference • On-Screen: Timer • On-Screen: Prompt "Find a Constraint Violation" |
| Pitch | Team presents stack. Other team challenges. | 5 min × rotations | • Jam Session Rules • Pitch (3 min) + Challenge (2 min) • On-Screen: Timer |
| Rotate | Switch partners, repeat 2 times | 10 min | • Rotate Now • On-Screen: Timer |
| Wrap | Refine stack, prep for debrief | 5 min | • Capture Your Refinements • What Changed? |
Slide count: ~10-12
Artifact: Stack Diagram Worksheet
Block 3: Synthesis (45 min)
| # | Topic | Time | Slides |
|---|---|---|---|
| 3.1 | Debrief: Stacks Compared | 12 min | • Debrief Questions • Same Product, Different Stacks? • Where Did Constraints Help? |
| 3.2 | Common Stack Mistakes | 10 min | • Epics That Are Really Journeys • Missing Levels • Constraint Violations |
| 3.3 | The Stack as Communication Tool | 8 min | • Engineers ↔ Product ↔ Design • One Stack, Many Conversations |
| 3.4 | Connecting to Your Work | 8 min | • Your Project's Stack • Discussion Prompt |
| 3.5 | Preview: Software Moments | 5 min | • Next Week: Stories vs. Jobs • Where Work Actually Happens |
| 3.6 | Close | 2 min | • Key Takeaway • Questions? |
Slide count: ~12-14
Unit 2 Summary
| Block | Time | Slides | Pace |
|---|---|---|---|
| Lecture | 45 min | ~18-20 | ~2.2-2.5 min/slide |
| Exercise | 45 min | ~10-12 | N/A |
| Synthesis | 45 min | ~12-14 | ~3.2-3.7 min/slide |
| Total | 135 min | ~40-46 |
Unit 2 Materials
| Material | Description |
|---|---|
| Slides | Unit 2 deck |
| Exercise Guide | Stack Mapping instructions |
| Artifact Template | Stack Diagram Worksheet |
| Exemplar | Completed stack for Uber or Spotify |
| Reference | Promise Model Stack quick reference card |
Unit 3: Software Moments
Theme: Where Work Happens
Prereading: None
Primary CLO: CLO 2, CLO 4
Unit Learning Outcomes
| ULO | Outcome | Bloom's |
|---|---|---|
| 3.1 | Define Stories as single-persona interactions and Jobs as multi-persona coordination tasks | Understand |
| 3.2 | Classify given Moments as Stories or Jobs with clear rationale | Apply |
| 3.3 | Analyze a Flow to identify its Story/Job composition | Analyze |
| 3.4 | Predict coordination requirements based on Job identification | Analyze |
Mastery Indicators
- Correctly classifies Moments with 85%+ accuracy and clear rationale
- Identifies the typical 3-4 Stories + 1 Job pattern in well-structured Flows
- Anticipates coordination challenges from Job density
Block 1: Lecture (45 min)
| # | Topic | ULO | Time | Slides |
|---|---|---|---|---|
| 3.1 | Recap & Bridge | — | 5 min | • Unit 3 Title • Last Week: The Stack • This Week: The Bottom Level |
| 3.2 | What Is a Moment? | 3.1 | 8 min | • Moments: Where Work Lives • The Implementation Unit • Moments Complete Flows |
| 3.3 | Stories vs. Jobs | 3.1 | 12 min | • Two Types of Moments • Story: Single-Persona Interaction • Job: Multi-Persona Coordination • The Hidden Complexity |
| 3.4 | The 3-4 + 1 Pattern | 3.3 | 10 min | • What We've Observed • 3-4 Stories + 1 Job per Flow • Why This Ratio Matters • Pattern Examples |
| 3.5 | Jobs Reveal Coordination Cost | 3.4 | 7 min | • Why Jobs Are Expensive • Estimation Implications • Spotting Hidden Jobs |
| 3.6 | Exercise Setup | — | 3 min | • Moment Classification: What You'll Do |
Slide count: ~18-20 | Pace: ~2.2-2.5 min/slide
Block 2: Exercise (45 min)
Activity: Moment Classification
| Phase | Activity | Time | Slides |
|---|---|---|---|
| Intro | Explain activity, form teams, receive Flow scenario | 5 min | • Moment Classification: What You'll Do • Instructions & Artifact Template • Your Flow Scenario |
| Create | Break Flow into Moments. Classify each as Story or Job. Identify the pattern. | 20 min | • On-Screen: Story vs. Job Reference • On-Screen: Timer • On-Screen: Prompt "Where's the hidden Job?" |
| Pitch | Team presents classification. Other team challenges: "Is that really a Job?" | 5 min × rotations | • Jam Session Rules • Pitch (3 min) + Challenge (2 min) • On-Screen: Timer |
| Rotate | Switch partners, repeat 2 times | 10 min | • Rotate Now • On-Screen: Timer |
| Wrap | Refine classifications, note disagreements | 5 min | • Capture Your Refinements • Where Did You Disagree? |
Slide count: ~10-12
Artifact: Moment Classification Worksheet
Block 3: Synthesis (45 min)
| # | Topic | Time | Slides |
|---|---|---|---|
| 3.1 | Debrief: Classification Challenges | 12 min | • Debrief Questions • Which Classifications Were Contested? • Stories That Were Really Jobs |
| 3.2 | The Coordination Tax | 10 min | • Jobs Require Handoffs • What This Means for Estimation • Job Density as Risk Signal |
| 3.3 | Common Classification Mistakes | 8 min | • Confusing Complexity with Coordination • The "Solo Job" Trap • When One Story Is Actually Three |
| 3.4 | Connecting to Your Work | 8 min | • Your Project's Moments • Where Are Your Jobs Hiding? • Discussion Prompt |
| 3.5 | Preview: Promise Discovery | 5 min | • Next Week: Where Promises Come From • VOC → HVP → CVP |
| 3.6 | Close | 2 min | • Key Takeaway • Questions? |
Slide count: ~12-14
Unit 3 Summary
| Block | Time | Slides | Pace |
|---|---|---|---|
| Lecture | 45 min | ~18-20 | ~2.2-2.5 min/slide |
| Exercise | 45 min | ~10-12 | N/A |
| Synthesis | 45 min | ~12-14 | ~3.2-3.7 min/slide |
| Total | 135 min | ~40-46 |
Unit 3 Materials
| Material | Description |
|---|---|
| Slides | Unit 3 deck |
| Exercise Guide | Moment Classification instructions |
| Artifact Template | Moment Classification Worksheet |
| Flow Scenarios | 3-4 pre-built Flows for teams to analyze |
| Exemplar | Completed classification for sample Flow |
| Reference | Story vs. Job quick reference card |
Unit 4: Promise Discovery
Theme: From Voice to Commitment
Prereading: Promise Discovery Overview (~20 min)
Primary CLO: CLO 3
Unit Learning Outcomes
| ULO | Outcome | Bloom's |
|---|---|---|
| 4.1 | Define the three stages of promise discovery: Voice of Customer (VOC), Hypothesized Value Promise (HVP), and Core Value Promise (CVP) | Understand |
| 4.2 | Explain why promises require validation before commitment | Understand |
| 4.3 | Distinguish between what users say they want and what will actually deliver value | Analyze |
| 4.4 | Evaluate the validation strength of a proposed promise | Evaluate |
Mastery Indicators
- Accurately sequences discovery stages without conflation
- Identifies validation gaps in promise proposals
- Distinguishes hypothesis from commitment in real-world examples
Block 1: Lecture (45 min)
| # | Topic | ULO | Time | Slides |
|---|---|---|---|---|
| 4.1 | Recap & Bridge | — | 5 min | • Unit 4 Title • So Far: Structure • This Week: Origin |
| 4.2 | Where Do Promises Come From? | 4.1 | 8 min | • The Discovery Problem • Promise Maps ≠ Discovery Tools • You Can't Map What You Haven't Found |
| 4.3 | The Three Stages | 4.1 | 12 min | • VOC: Voice of Customer • HVP: Hypothesized Value Promise • CVP: Core Value Promise • The Progression |
| 4.4 | Why Validation Matters | 4.2 | 8 min | • Hypothesis ≠ Commitment • The Cost of Wrong Promises • When to Commit |
| 4.5 | Users Say vs. Users Need | 4.3 | 7 min | • The Say/Need Gap • Faster Horses, Better Questions • Listening Through the Request |
| 4.6 | Evaluating Validation Strength | 4.4 | 5 min | • Strong vs. Weak Validation • Evidence Types • Exercise Setup |
Slide count: ~18-20 | Pace: ~2.2-2.5 min/slide
Block 2: Exercise (45 min)
Activity: Promise Validation Audit
| Phase | Activity | Time | Slides |
|---|---|---|---|
| Intro | Explain activity, form teams, receive promise scenario | 5 min | • Promise Validation Audit: What You'll Do • Instructions & Artifact Template • Your Promise Scenario |
| Create | Identify stage (VOC/HVP/CVP). Assess validation strength. Flag gaps. | 20 min | • On-Screen: VOC → HVP → CVP Reference • On-Screen: Timer • On-Screen: Prompt "What evidence is missing?" |
| Pitch | Team presents assessment. Other team challenges: "Is that really validated?" | 5 min × rotations | • Jam Session Rules • Pitch (3 min) + Challenge (2 min) • On-Screen: Timer |
| Rotate | Switch partners, repeat 2 times | 10 min | • Rotate Now • On-Screen: Timer |
| Wrap | Refine assessment, note validation gaps | 5 min | • Capture Your Refinements • What Evidence Would You Need? |
Slide count: ~10-12
Artifact: Promise Validation Worksheet
Block 3: Synthesis (45 min)
| # | Topic | Time | Slides |
|---|---|---|---|
| 4.1 | Debrief: Validation Gaps | 12 min | • Debrief Questions • What Evidence Was Missing? • VOC Disguised as CVP |
| 4.2 | The Premature Commitment Trap | 10 min | • Committing Too Early • The Sunk Cost Spiral • How to Stay in Hypothesis Mode |
| 4.3 | Real-World Discovery Examples | 8 min | • Slack: From Game Company to CVP • Instagram: Pivot to Promise • Discovery Is Messy |
| 4.4 | Connecting to Your Work | 8 min | • Your Project's Promises: What Stage? • What Validation Do You Have? • Discussion Prompt |
| 4.5 | Preview: Product Coherence | 5 min | • Next Week: Does This Feature Belong? • The Promise Fit Test |
| 4.6 | Close | 2 min | • Key Takeaway • Questions? |
Slide count: ~12-14
Unit 4 Summary
| Block | Time | Slides | Pace |
|---|---|---|---|
| Lecture | 45 min | ~18-20 | ~2.2-2.5 min/slide |
| Exercise | 45 min | ~10-12 | N/A |
| Synthesis | 45 min | ~12-14 | ~3.2-3.7 min/slide |
| Total | 135 min | ~40-46 |
Unit 4 Materials
| Material | Description |
|---|---|
| Slides | Unit 4 deck |
| Exercise Guide | Promise Validation Audit instructions |
| Artifact Template | Promise Validation Worksheet |
| Promise Scenarios | 3-4 promises at different stages with varying evidence |
| Exemplar | Completed validation audit |
| Reference | VOC → HVP → CVP quick reference card |
| Quiz Bank | 5-7 prereading activation questions |
Unit 5: Product Coherence
Theme: Does This Belong?
Prereading: None
Primary CLO: CLO 4
Unit Learning Outcomes
| ULO | Outcome | Bloom's |
|---|---|---|
| 5.1 | Apply the Promise Fit Test to evaluate a proposed feature | Apply |
| 5.2 | Trace a Moment through Flow, Journey, Epic to its parent Promise | Apply |
| 5.3 | Identify feature orphans—work that serves no existing promise | Analyze |
| 5.4 | Demonstrate reasoning for inclusion, modification, or rejection of proposed features | Evaluate |
Mastery Indicators
- Completes Promise Fit Test accurately with clear rationale
- Detects orphan features in product backlogs
- Produces well-reasoned recommendations with clear reasoning chain
Block 1: Lecture (45 min)
| # | Topic | ULO | Time | Slides |
|---|---|---|---|---|
| 5.1 | Recap & Bridge | — | 5 min | • Unit 5 Title • So Far: Stack + Discovery • This Week: Evaluation |
| 5.2 | The Coherence Problem | — | 8 min | • Features Multiply • The Backlog Grows • How Do You Decide? |
| 5.3 | The Promise Fit Test | 5.1 | 12 min | • What Is the Promise Fit Test? • The Three Questions • Fit Test Walkthrough • Decision Outcomes: Include, Modify, Reject |
| 5.4 | Tracing the Stack | 5.2 | 8 min | • Moment → Flow → Journey → Epic → Promise • The Traceability Requirement • When the Chain Breaks |
| 5.5 | Feature Orphans | 5.3 | 7 min | • What Is a Feature Orphan? • How Orphans Happen • Orphan or New Promise? |
| 5.6 | Building the Case | 5.4 | 5 min | • Reasoning for Inclusion • Reasoning for Rejection • Exercise Setup |
Slide count: ~18-20 | Pace: ~2.2-2.5 min/slide
Block 2: Exercise (45 min)
Activity: Feature Court
| Phase | Activity | Time | Slides |
|---|---|---|---|
| Intro | Explain activity, form teams, receive feature proposals | 5 min | • Feature Court: What You'll Do • Instructions & Artifact Template • Your Feature Proposals |
| Create | Run Promise Fit Test on 2-3 features. Trace each. Identify orphans. Build case for each. | 20 min | • On-Screen: Promise Fit Test Reference • On-Screen: Timer • On-Screen: Prompt "Include, Modify, or Reject?" |
| Pitch | Team presents verdict + reasoning. Other team cross-examines. | 5 min × rotations | • Jam Session Rules • Present Verdict (3 min) + Cross-Examine (2 min) • On-Screen: Timer |
| Rotate | Switch partners, repeat 2 times | 10 min | • Rotate Now • On-Screen: Timer |
| Wrap | Finalize verdicts, note contested decisions | 5 min | • Capture Your Verdicts • Which Decisions Were Contested? |
Slide count: ~10-12
Artifact: Promise Fit Test Worksheet
Block 3: Synthesis (45 min)
| # | Topic | Time | Slides |
|---|---|---|---|
| 5.1 | Debrief: Verdicts Compared | 12 min | • Debrief Questions • Same Feature, Different Verdicts? • What Made Decisions Hard? |
| 5.2 | The Modify Option | 10 min | • When Features Almost Fit • Reshaping to Align • Modify vs. Force-Fit |
| 5.3 | Orphans That Become Promises | 8 min | • When Rejection Is Wrong • The New Promise Case • Strategic Feature Expansion |
| 5.4 | Connecting to Your Work | 8 min | • Your Project's Backlog • Run the Fit Test • Discussion Prompt |
| 5.5 | Preview: Applying PDD | 5 min | • Next Week: Putting It All Together • Building Your Promise Map |
| 5.6 | Close | 2 min | • Key Takeaway • Questions? |
Slide count: ~12-14
Unit 5 Summary
| Block | Time | Slides | Pace |
|---|---|---|---|
| Lecture | 45 min | ~18-20 | ~2.2-2.5 min/slide |
| Exercise | 45 min | ~10-12 | N/A |
| Synthesis | 45 min | ~12-14 | ~3.2-3.7 min/slide |
| Total | 135 min | ~40-46 |
Unit 5 Materials
| Material | Description |
|---|---|
| Slides | Unit 5 deck |
| Exercise Guide | Feature Court instructions |
| Artifact Template | Promise Fit Test Worksheet |
| Feature Proposals | 6-8 feature proposals (mix of fits, orphans, edge cases) |
| Exemplar | Completed Promise Fit Test with reasoning |
| Reference | Promise Fit Test quick reference card |
Unit 6: Applying PDD
Theme: From Framework to Practice
Prereading: None
Primary CLO: CLO 4, CLO 5
Unit Learning Outcomes
| ULO | Outcome | Bloom's |
|---|---|---|
| 6.1 | Identify candidate promises for a given product context | Analyze |
| 6.2 | Construct a partial Promise Map (Promise → Epic → Journey) satisfying structural constraints | Create |
| 6.3 | Evaluate scope proposals using promise-driven criteria | Evaluate |
| 6.4 | Demonstrate how architectural decisions align with promise commitments | Evaluate |
Mastery Indicators
- Produces Promise Maps that satisfy structural constraints
- Demonstrates scope decisions with coherent promise-based reasoning
- Recognizes when a context is/isn't suitable for promise-driven approach
Block 1: Lecture (45 min)
| # | Topic | ULO | Time | Slides |
|---|---|---|---|---|
| 6.1 | Recap & Bridge | — | 5 min | • Unit 6 Title • The Journey So Far • This Week: Integration |
| 6.2 | The Five CLOs | — | 5 min | • What You've Learned • CLO 1-5 Recap • Today: All Together |
| 6.3 | From Analysis to Construction | 6.1, 6.2 | 10 min | • Analyzing vs. Building • Starting From Zero • Identifying Candidate Promises |
| 6.4 | Building the Promise Map | 6.2 | 10 min | • Promise Map Anatomy • Working Top-Down • Applying the 3-5 Constraint • When to Stop |
| 6.5 | Scope Decisions in Practice | 6.3 | 8 min | • The Scope Conversation • Promise-Driven Criteria • Saying No With Clarity |
| 6.6 | Architecture Meets Promise | 6.4 | 5 min | • Technical Decisions as Promise Decisions • Alignment Examples • Exercise Setup |
| 6.7 | Exercise Setup | — | 2 min | • Promise Map Build: What You'll Do |
Slide count: ~18-20 | Pace: ~2.2-2.5 min/slide
Block 2: Exercise (45 min)
Activity: Promise Map Build
| Phase | Activity | Time | Slides |
|---|---|---|---|
| Intro | Explain activity, form teams, receive product brief | 5 min | • Promise Map Build: What You'll Do • Instructions & Artifact Template • Your Product Brief |
| Create | Identify 2-3 promises. Build out Promise → Epic → Journey for one. Apply constraints. | 20 min | • On-Screen: Promise Map Template • On-Screen: Timer • On-Screen: Prompt "Does every Journey trace to a Promise?" |
| Pitch | Team presents map. Other team challenges: scope, constraints, traceability. | 5 min × rotations | • Jam Session Rules • Present Map (3 min) + Challenge (2 min) • On-Screen: Timer |
| Rotate | Switch partners, repeat 2 times | 10 min | • Rotate Now • On-Screen: Timer |
| Wrap | Refine map, note scope decisions made | 5 min | • Capture Your Refinements • What Scope Decisions Did You Make? |
Slide count: ~10-12
Artifact: Promise Map (partial)
Block 3: Synthesis (45 min)
| # | Topic | Time | Slides |
|---|---|---|---|
| 6.1 | Debrief: Maps Compared | 12 min | • Debrief Questions • Same Brief, Different Maps? • Where Did Constraints Bite? |
| 6.2 | Scope Decisions Exposed | 8 min | • What Got Cut? • How Did You Decide? • Promise-Driven Rationale |
| 6.3 | When PDD Fits (and When It Doesn't) | 8 min | • Good Contexts for PDD • Challenging Contexts • Adaptation, Not Dogma |
| 6.4 | Your Project: Next Steps | 8 min | • Applying PDD to Your Work • Starting Points • Discussion Prompt |
| 6.5 | Course Wrap-Up | 7 min | • The 6-Unit Journey • From Shipping Features to Keeping Promises • What Differentiates You Now |
| 6.6 | Close | 2 min | • Final Takeaway • Thank You • Questions? |
Slide count: ~14-16
Unit 6 Summary
| Block | Time | Slides | Pace |
|---|---|---|---|
| Lecture | 45 min | ~18-20 | ~2.2-2.5 min/slide |
| Exercise | 45 min | ~10-12 | N/A |
| Synthesis | 45 min | ~14-16 | ~2.8-3.2 min/slide |
| Total | 135 min | ~42-48 |
Unit 6 Materials
| Material | Description |
|---|---|
| Slides | Unit 6 deck |
| Exercise Guide | Promise Map Build instructions |
| Artifact Template | Promise Map Worksheet |
| Product Briefs | 3-4 novel product contexts (not previously used) |
| Exemplar | Completed Promise Map for sample product |
| Reference | Promise Model Stack + Promise Fit Test quick reference cards |
CLO Integration Check
| CLO | How It Appears in Unit 6 |
|---|---|
| CLO 1 | Implicit in all reasoning; explicit in course wrap-up |
| CLO 2 | Building the Promise Map (6.2), traceability challenges |
| CLO 3 | Identifying candidate promises (6.1), validation discussion |
| CLO 4 | Scope decisions (6.3), challenge rounds in exercise |
| CLO 5 | Constructing the Promise Map (6.2), primary deliverable |
Course Summary
Slide Count by Unit
| Unit | Title | Lecture | Exercise | Synthesis | Total |
|---|---|---|---|---|---|
| 1 | Software as Promise | ~16 | ~10-12 | ~10-12 | ~36-40 |
| 2 | The Promise Model Stack | ~18-20 | ~10-12 | ~12-14 | ~40-46 |
| 3 | Software Moments | ~18-20 | ~10-12 | ~12-14 | ~40-46 |
| 4 | Promise Discovery | ~18-20 | ~10-12 | ~12-14 | ~40-46 |
| 5 | Product Coherence | ~18-20 | ~10-12 | ~12-14 | ~40-46 |
| 6 | Applying PDD | ~18-20 | ~10-12 | ~14-16 | ~42-48 |
| Total | ~106-116 | ~60-72 | ~72-84 | ~238-272 |
Exercise Activities by Unit
| Unit | Activity | Artifact |
|---|---|---|
| 1 | Promise Safari | Promise Identification Worksheet |
| 2 | Stack Mapping | Stack Diagram Worksheet |
| 3 | Moment Classification | Moment Classification Worksheet |
| 4 | Promise Validation Audit | Promise Validation Worksheet |
| 5 | Feature Court | Promise Fit Test Worksheet |
| 6 | Promise Map Build | Promise Map (partial) |
Materials Inventory
| Material Type | Count | Notes |
|---|---|---|
| Unit Slide Decks | 6 | ~40-48 slides each |
| Exercise Guides | 6 | One per unit |
| Artifact Templates | 6 | One per unit |
| Exemplars | 6 | One per unit |
| Quick Reference Cards | 5 | Stack, Story/Job, VOC→CVP, Promise Fit Test, Promise Map |
| Quiz Banks | 2 | Units 1 and 4 (prereading units) |
| Flow Scenarios | 3-4 | For Unit 3 |
| Promise Scenarios | 3-4 | For Unit 4 |
| Feature Proposals | 6-8 | For Unit 5 |
| Product Briefs | 3-4 | For Unit 6 |
Intellectual Property
All course materials are the intellectual property of Sean Yo, licensed to and published by the Canadian Institute of Software Product Management (CISPM).
- Materials are provided for educational use under CISPM licensing
- CISPM branding must be retained on all materials
- Instructors may add supplementary materials but may not remove attribution
- Derivative works require approval
Master Course Document v1.0 — January 2026