AI Enablement Engagement

Session 0 — Kickoff & Learning Bed Selection (Detailed Agenda)

Total Duration: 1.5 hours (90 minutes) Phase / Week: Phase 1, Week 1 (precedes Session 1 by a few days) Format: Remote working session Required attendees: Engagement sponsor (Donnell Jenkins), dev team lead(s), architect, anyone with broad knowledge of the internal product portfolio

Pre-session prep (Turner)

  • Have a working list of internal products the team currently maintains, with one or two sentences each on what they do and who uses them
  • Sponsor and at least one technical leader available with decision authority to commit a learning bed product
  • Light read of the SOW so the engagement overview can move quickly

Agenda

0:00 – 0:10 (10 min) — Welcome and introductions

  • Lead: Nubitz
  • Format: Briefing
  • Who's in the room, what they care about, what success looks like for each person.

0:10 – 0:30 (20 min) — Engagement overview

  • Lead: Nubitz
  • Format: Walkthrough
  • The three phases, the four SOW focus areas (context/governance, tooling, speed-vs-risk, DevOps integration), the deliverables, and the cadence. Set expectations for what Nubitz brings and what Turner brings. Introduce the learning bed concept and why it shapes the engagement.

0:30 – 1:00 (30 min) — Internal product portfolio tour

  • Lead: Turner — dev team leads / architect, Nubitz facilitating
  • Format: Discussion
  • Walk the candidate products: what each does, complexity, current pain points, where AI would most help, any blockers to participation (access, staffing, sensitivity). Nubitz asks targeted questions to surface fit against the selection criteria.

1:00 – 1:20 (20 min) — Learning bed selection

  • Lead: Joint — sponsor decides, Nubitz facilitates
  • Format: Decision
  • Review the selection criteria. Score the leading candidates against them. Make the call. Name the developer and domain expert who will attend the engagement consistently. Confirm access path for repos, pipelines, and environments.

1:20 – 1:30 (10 min) — Logistics and next steps

  • Lead: Nubitz
  • Format: Synthesis
  • Confirm Session 1 date, attendees, and prep. Pin down communication channel and shared note-doc location. Hand off the access-request checklist so blockers surface immediately, not the morning of Session 1.

Selection Criteria Reference

For the live selection block, evaluate each candidate product against:

  • Representative of how Turner builds software internally
  • Accessible repos, pipelines, and environments
  • Has a committed developer and domain expert
  • Has an active backlog the capstone can pull from
  • Right-sized — complex enough to exercise the toolchain, not so sprawling we lose the thread
  • Low-blast-radius for pilot pipeline changes

What Nubitz produces after this session

  • One-pager: selected learning bed product, named participants, access path, agreed cadence
  • Updated draft agendas for Sessions 1-6 customized to the selected product
  • Access-request checklist for Turner

Risks to manage

  • Selection deferred: if the room can't commit by end of session, name the decision-maker and a hard date (within 48 hours) — Session 1 prep depends on this.
  • Over-broad candidate: a product nobody can demo end-to-end in 30 minutes is probably too sprawling for the learning bed.
  • No named participants: without committed developer + domain expert the learning bed never moves between sessions.