Session 6 — Speed vs. Risk: Capstone & Best Practices (Detailed Agenda)
Total Duration: 2.5 hours (150 minutes) Phase / Week: Phase 2, Week 5 Format: Capstone exercise plus closing best-practices discussion Required attendees: Turner developers; technical leadership present for the closing block
Pre-session prep (Turner)
- Select a real backlog item from the learning bed, sized for a working-session pace, that exercises the full toolchain (CLAUDE.md, custom skill, pipeline integration from Session 5)
- Confirm technical leadership availability for the closing retrospective
Agenda
0:00 – 0:10 (10 min) — Frame the capstone
- Lead: Nubitz
- Format: Briefing
- Restate the engagement arc. Set up the capstone: take a real backlog item from the learning bed product from refinement through PR using everything built in Sessions 3-5. Note that by end of session, the learning bed is fully wrapped — and the team's job in Phase 3 and beyond is to replicate the pattern across the rest of the portfolio.
0:10 – 0:35 (25 min) — Capstone phase 1: refinement and planning
- Lead: Developers; Nubitz observing and coaching
- Format: Hands-on
- Use AI to refine the story, write acceptance criteria, and outline an approach. Confirm the approach with peers before coding.
0:35 – 1:20 (45 min) — Capstone phase 2: implementation
- Lead: Developers; Nubitz observing and coaching
- Format: Hands-on
- Implement against the plan using AI assistance. Apply the CLAUDE.md/skills from Session 4. Lean on the patterns from Session 3. When friction appears, surface it for the retrospective.
1:20 – 1:30 (10 min) — Break
1:30 – 1:55 (25 min) — Capstone phase 3: PR, automated checks, and review
- Lead: Developers; Nubitz observing
- Format: Hands-on
- Open the PR. Watch the AI-augmented pipeline steps from Session 5 run. Compare AI's review with developer judgment. Iterate as needed.
1:55 – 2:15 (20 min) — Velocity-vs-quality patterns and security guardrails
- Lead: Nubitz
- Format: Briefing + discussion
- Synthesize the speed-vs-risk patterns observed across the capstone. Discuss secret hygiene, dependency vetting, supply-chain awareness, and code-review etiquette with AI in the loop.
2:15 – 2:30 (15 min) — Retrospective, hand-off, and Phase 3 setup
- Lead: Nubitz with Turner leadership
- Format: Synthesis
- What worked. What was friction. Where should Phase 3 support focus. Hand off the finalized Developer Reference Guide. Confirm Phase 3 logistics (booking the 10 hours of white-glove time).
Materials
- Finalized Developer Reference Guide (delivered at this session)
- Phase 3 booking template / shared scheduling link
- One-page portfolio-rollout plan (which Turner products to wrap next, using the learning bed pattern)
What Nubitz produces after this session
- Final Developer Reference Guide hand-off
- A real learning bed backlog item shipped (or PR-ready) during the session
- Phase 3 support topic backlog
- Phase 2 invoice trigger
- Final engagement summary one-pager
Risks to manage
- Wrong-sized backlog item: scope it carefully in advance. Too big and the capstone stalls; too small and the toolchain isn'