Session 0 — Kickoff & Pilot Product Selection

Phase: 1 — Assessment & Strategy Target Week: Week 1 (precedes Session 1) Duration: 1 hour Format: Remote working session Audience: Engagement sponsor (Donnell Jenkins), dev team leads, architect(s), anyone with broad knowledge of Turner's internal product portfolio

Note. The pilot is a project that hasn't started yet — selection criteria emphasize readiness of vision, named participants, and timeline alignment over access to existing repos and pipelines.

Objective

Kick off the engagement, walk the team through what they're about to receive over the next ten weeks, and — most importantly — select the pilot product: a single internal Turner product that will be the running case study across every subsequent session. By the time the engagement ends, that product will be fully wrapped in AI-assisted development practices, and Turner's team will have the pattern they need to replicate that wrapping across the rest of their portfolio.

Why a pilot product

A single focal product turns abstract training into concrete craft. Instead of demonstrating techniques on disconnected examples, every session in Phases 1 and 2 advances the same artifact: discovery on the product, governance shaped around the product, CLAUDE.md and skills authored for the product, the product's Azure DevOps pipeline gaining AI-augmented steps, and a real backlog item from the product taken end-to-end in the capstone.

The team owns the work of wrapping the rest of their portfolio after the engagement; this engagement equips them with a complete, working example to copy from.

Key Topics

Engagement overview: the three phases, the four SOW focus areas, what Turner gets and what's expected of them
Inventory of Turner's internal products that the team currently maintains
Discussion of pain points and AI ambitions for each candidate product
Selection criteria for the pilot product (see below)
Selection of the pilot product and confirmation of access/availability
Logistics: cadence, scheduling, communication channel, who attends which sessions

Pilot Product Selection Criteria

The selected product should be:

Representative of how Turner builds and maintains software internally — picking the weirdest outlier teaches less
Vision is concrete — there's enough requirements/architecture clarity that Session 1 can produce a substantive intent map, not a one-paragraph sketch
Staffed — at least one developer and one domain expert who will be present across the engagement
Has a sister product to mirror — an existing Turner product whose conventions, stack, and patterns the new pilot will inherit
Right-sized — substantive enough to exercise the full toolchain, but not so ambitious that no real work can happen in five weeks
Timeline-aligned — development is actually scheduled to start during or shortly after the engagement, not deferred to next year

Outcomes

Shared understanding of the engagement shape and expectations
Selected pilot product with sign-off from the sponsor
Named developer and domain expert who will attend the engagement consistently
Confirmed access path (repos, Azure DevOps, pipelines) for the pilot product
Anchor for everything Nubitz prepares before Session 1

Inputs Required from Turner

Sponsor (Donnell) present
Someone who can speak to the product portfolio at a high level
Decision authority to commit a product as the pilot product by end of session

Deliverable Contribution

Sets the scope for the AI Development Strategy Document and the AI Configuration Assets deliverables — both will be tailored to the selected pilot product as the primary worked example.