Facilitator runbook

Deliver it five ways.

The same challenges/ content flexes to the customer's appetite and seniority — from a 90-minute executive walk-through to a multi-week engagement in a real tenant. Only scope and timing change. The default is the two-day RVAS (Real Value Acceleration Solutions).

Delivery formats— pick the one that matches the room
90 min
Express demo
Express demo
Execs · architects
Live narration of an already-provisioned 00 + 01 — an existing PR and its run. No hands-on; pure "see it work".
1 day
6–7 hrs
1-day immersion
Platform + data engineers
00 → 01, then pick two of 02–08. Skip the Capstone; finish with a guided demo.
2 days
Default
2-day RVAS
Mixed teams of 3–5 · 12–14 hrs
00 → 01 → four-to-five of 02–08 → Capstone. Judging and prizes optional.
4–8 wks
Engagement
Multi-week engagement
Customer platform team
All 10 challenges in the real tenant on real workloads. Weekly coaching; ends with a customer-owned fork.
∞ rolling
Self-paced
Self-paced enablement
Individuals
Any subset, on your own clock. Read-only solutions and async coach Q&A.
Full delivery guide →
Pre-flight checklists, coaching cards, judging logistics, and the evolve model — everything around the challenges.
Two-day agenda— assumes Challenge 00 is done before day 1
Day 1 · Build the control plane
09:00
Kickoff, team formation, blueprint overview
09:30
Challenge 01 — Workspace as codeAll teams
11:45
Challenge 02 · 03 · or 04Team choice
14:00
Challenge 05 or 06Heavier hands-on
16:15
Stretch sprint or Capstone planning
17:00
Day 1 retro
Day 2 · Prove it end-to-end
09:00
Standup — what's blocking each team
09:30
Challenge 07 or 08Team choice
13:00
Capstone buildOne PR exercises every challenge completed
16:00
Demos10 min per team, against the rubric
17:00
Judging, awards, retro, feedback form
Why the governance frame holds— the load-bearing design decisions
01

Federated identity, zero secrets

Identity is OIDC-federated — no client secrets anywhere in CI/CD, from Challenge 00 onward.

02

One validator, two places

The same validate code path runs on a laptop and in CI — no surprises between local and pipeline.

03

Drift runs nightly

Out-of-band portal changes surface automatically as GitHub issues — provable "no ClickOps".

04

Skills do the heavy lifting

Skills for Fabric ship medallion, Eventhouse, Power BI, and Activator work — wrapped in the PR loop so the frame still holds.

05

Agents accelerate, never bypass

GitHub Copilot and Fabric MCP speed authoring and review. Every change is still a reviewed PR applied by a service principal.

06

Each delivery feeds the next

Customer feedback becomes PRs that add or adapt challenges, so the blueprint compounds value over time.

Evolve the blueprint— feedback maps to one of four PR types
fix:

Bug or doc rot in an existing challenge — a broken link in 03, an outdated screenshot in 07.

enhance:

Sharpen an existing challenge — a new policy rule in 01, clearer success criteria in 04.

adapt:

A customer-specific variant kept alongside the original — a regulated-insurance take on 06.

feat:

A brand-new challenge — e.g. data-mesh federated governance for multi-domain tenants.

Every PR that adds or changes challenge content keeps the contract: each challenge demonstrates ≥ 1 MCP server and ≥ 1 Skill, and policy / schema changes need CODEOWNERS review.

The one-pager— hand this to a sponsor before the room
One-slide overview of the Agentic Governance Blueprint for Fabric: business and technical scenario, desired outcomes, materials, delivery formats, and the five-stage RVAS journey.
  • →Empty tenant → fully governed, PR-driven control plane in under two days.
  • →Auditable, replayable artifacts — no ClickOps, no long-lived secrets.
  • →Customer-owned repo and repeatable templates to continue immediately.
↓ Download the 1-slider (PPTX) Compose a custom delivery → 10-challenge visual tour