A complete Agile/Scrum program artifact set for a fictional SaaS telehealth mobile platform migration at ACME Health — migrating patients and providers off a legacy vendor platform onto a new native mobile app and provider web console. This suite demonstrates the PM-owned side of iterative delivery: not just a Jira board, but the vision-setting, team charter, ceremony facilitation, cross-team coordination, metrics reporting, and stakeholder governance that a Program/Delivery Manager actually owns in an Agile environment.
Suite complete: Program Setup, Backlog & Board, Ceremonies, Metrics & Reporting, Governance & Stakeholder Management, Vendor Management, Agile-Only Practices, and Reference are all live — 49 artifacts total. All 49 artifacts now include native Word/Excel/PowerPoint downloads, matching the PM Suite convention.
Program Setup
Established before Sprint 1 begins — the foundation every ceremony, board, and report in this suite is built on.
Program Charter
The formal authorization document — business case, high-level scope, risks, summary milestones/budget, Product Owner authority, and Sponsor sign-off.
Program Management Plan
The integrated plan tying Agile delivery approach, scope, release/sprint planning, cost, quality, resources, risk, vendor, and metrics together across the whole suite.
Vision & Roadmap
Program vision, business drivers, success metrics/OKRs, and a Now/Next/Later release roadmap mapped to sprints.
Agile Team Charter & Working Agreement
Ceremony cadence, team norms, WIP limits, Scrum-of-Scrums structure, and escalation path for two coordinating teams.
Definition of Ready & Definition of Done
The quality gates every story must clear entering and exiting a sprint — includes the clinical/compliance-specific checks unique to telehealth.
Test & Quality Strategy
How quality is built in-sprint rather than inspected at the end — the test pyramid and CI gating, mobile device matrix and degraded-network testing, telehealth video and PulseConnect SDK coverage, HIPAA/PHI and clinical safety validation, accessibility, data-migration reconciliation, and release gating across both releases.
Agile RACI
Who owns backlog prioritization, ceremony facilitation, Definition of Done sign-off, and release approval — mapped across both teams and stakeholders.
Organizational Chart
Program reporting structure — direct line from Sponsor through the Agile Delivery Lead, two Scrum teams, and matrixed advisory relationships to Clinical and Compliance.
Cost-Benefit Analysis
7-year cash flow and NPV — quantified provider-capacity, retention, and support-cost benefits against the program investment, with an honest note on the vendor-EOL-driven non-discretionary side of this decision.
Benefits Realization Plan
161 days of live operating data against the $1,130,000 benefit case — what the CBA's own before/after measures actually show, and why a program that shipped every two weeks measured its benefits exactly never.
Total Cost of Ownership
7-year TCO vs. the legacy status quo — raw cost comparison that, read alongside the CBA, shows why cost-alone doesn't justify modernization but the full benefit case does.
Work Breakdown Structure (WBS) Console
Interactive Gantt-style schedule — 102 line items across 6 phases and 8 sprints, with live % complete and a "Today" marker. Sprint Backlogs stay the source of truth for day-to-day work; this is the task-level governance/dependency view.
Backlog & Faux Jira Board
Product Backlog
6 Epics — Patient Identity, Scheduling, Video Visits, Provider Console, Data Migration/Decommission, Messaging/Refills — 34 prioritized, story-pointed stories.
Requirements Traceability (Agile)
The Agile-native traceability view: Vision → Epic → User Story → Definition of Done → Sprint/Release across all 6 epics and 33 stories. Explains why the living backlog plus a shared Definition of Done is the traceability vehicle in Scrum — not a waterfall matrix.
Sprint Backlogs
Committed stories, sprint goal, and capacity-vs-delivered for Sprint 2 (early), Sprint 5 (Release 1/MVP), and Sprint 8 (cutover).
Ceremonies
Program Kickoff Deck
The actual kickoff presentation — welcome, why the program matters, OKRs, scope, teams (all 13, not just leads), sprint timeline, budget, working agreement, risks, and next steps in one deck.
Program Kickoff Meeting Notes
One-time program-level kickoff — agenda, attendees, key discussion points, and decisions that shaped the Definition of Done and Scrum-of-Scrums cadence. See the Kickoff Deck for the actual presentation.
Sprint Planning Notes
Sprint 3 example — capacity planning by team, stories pulled in, and discussion of a high-risk cross-team dependency identified at planning.
Daily Standup Log
One fully-detailed sample day (Sprint 2, Day 6) — full team transcript, a real blocker raised and escalated, tied directly to that day's board snapshot.
Backlog Refinement Notes
A story split (large EHR-integration story broken into two), a re-estimation after new information, and a live Definition of Ready check.
Sprint Review / Demo Notes
Sprint 5 — the Release 1 (MVP) launch sprint. Stakeholder feedback, a new backlog candidate raised live, and the formal Go/No-Go release decision.
Metrics & Reporting
Sprint Burndown Chart
Sprint 5 (Release 1/MVP) actual vs. ideal burndown — with the flat stretches (release hardening, no closures) left visible rather than smoothed out.
Velocity Chart
Committed vs. delivered points across all 8 sprints — ramp-up in Sprint 1, ~94% predictability from Sprint 2 onward, used for release forecasting.
Release Burnup
Cumulative scope delivered vs. total program scope across all 8 sprints, with Release 1 and Release 2 milestones marked and a documented scope re-estimation.
Sprint Status Report
Sprint 6 stakeholder-facing report — RAG status, accomplished/planned, risks, budget health, and upcoming milestones, in the same format the Steering Committee sees.
Governance & Stakeholder Management
Agile RAIDD Log
Risks, Assumptions, Issues, Dependencies, Decisions — every entry traceable back to the specific ceremony or sprint where it originated.
Stakeholder Communication Plan
Who needs what, how often, in what format — Sponsor, Clinical, Compliance, pilot providers, IT Operations, and both delivery teams.
Change Handling in Agile
Where backlog reprioritization ends and formal change control begins — with the program's actual 3-CR change log referenced.
Roles & Responsibilities
Who owns what across two Scrum teams and 28 people — including why the Product Owner sits on the business side and the Delivery Lead does not hold that role, and what each function explicitly does not own.
Steering Committee Deck
7-slide monthly update — RAG status, delivery progress, timeline, risks, budget, team health, and decisions requested.
Release & Milestone Schedule
The Agile equivalent of a project-plan Gantt chart — an Epic-level rolling schedule, honest about how far ahead any of it was actually known.
Program Closeout & Lessons Learned
Final performance summary, deliverable acceptance, and outstanding items — summarizing the 8 lessons learned, each traced back to the artifact where it originated.
Lessons Learned Register
The standalone register — 8 entries (2 improvement lessons, 6 positive practices), each separating what happened, root cause, impact, and recommendation, traced to the sprint or decision where it originated.
Program Budget
Cost by category, full named-roster rate card, and baseline sign-off — scaled to this program's size, with both approved CRs traced through.
Team Resource Plan
Named 28-person roster across both teams with FTE%, location, and blended rate — reconciled line-for-line to the Program Budget's delivery labor lines.
Change Control Log
10 formal Change Requests with full impact analysis (cost/schedule/scope) and "outcome if not approved" for each — the concrete companion to Change Handling.
Change Control Detail
The ten change requests behind the log, each worked in full — business justification, impact across scope, sprint capacity, cost and risk, options considered, recommendation, and the approval record.
Vendor Management
Vendor Management Plan
The two vendors on this program — PulseConnect (incoming, active) and Vantix Health Systems (outgoing, legacy) — and why each needs a different kind of artifact.
Vendor SOW & Scorecard — PulseConnect
Contract summary, SLA terms, and a performance scorecard tracking actual vendor delivery against those SLAs across the program.
SOW-001 · Vantix Transition & Offboarding
The contract binding Vantix to the cooperation this program needs in its own replacement — export access and schema documentation, support to each migration validation, and the written deletion certification due within thirty days of the formal request. Four deliverables anchored to sprints, $45,000 fixed, with the final twenty percent held against certification rather than decommission.
Agile-Only Practices
Practices you genuinely wouldn't find in a waterfall PM Suite — included to show the parts of Agile/SAFe that are substantively different, not just relabeled.
PI Objectives (Light SAFe)
Release 1 and Release 2 treated as informal Program Increments — team-level objectives with business-value scoring and SAFe-standard ROAM risk tracking.
Reference
Glossary & Acronyms — Agile / Scrum / SAFe
Every term and acronym used across this suite, defined in plain language — core Scrum, estimation, metrics, SAFe scaling terms, and program-specific/compliance terms.
Common Agile/Scrum Questions
What are the core Scrum ceremonies?
Sprint Planning, Daily Standup, Sprint Review, and Sprint Retrospective, repeating every sprint, plus ongoing Backlog Refinement between sprints.
How does Agile handle a change in scope without formal change control?
Ordinary reprioritization is free — the Product Owner just reorders the Product Backlog. Formal Change Requests are only raised when a change affects a baselined budget or schedule commitment.
What is velocity in Scrum?
The amount of story-point work a team reliably delivers per sprint, based on recent sprint history, used to forecast future sprints and releases.
What's the difference between Definition of Ready and Definition of Done?
Ready gates entry into a sprint; Done gates exit — work isn't complete until it clears Done.
What is a Sprint Retrospective?
A team-only ceremony at the end of every sprint to reflect on what to keep, stop, and start — Agile's continuous version of a Lessons Learned register.