Project Kickoff and Intake

Use this page to lock in scope, stakeholders, timeline, module list, development path, and initial simulation scope so Planning can start.

What you need before starting

Development request (or clear ask)
Access to stakeholders for intake
UCI rules (new vs existing course)

What you need to produce

Intake notes (e.g. Google Doc from meeting)
Project charter (or equivalent): scope, objectives, timeline, stakeholders
Module list with numbering
SME team roster (roles and contacts)
Initial simulation scope (target role, context, key scenarios)

What to do

Analyze the request and clarify deliverables.
Assign roles (Development SME, Product Manager, etc.) and document in charter/notes.
Confirm whether new modules or reuse; get UCI assigned or confirmed.
Conduct intake call; cover the items in Cover in intake (below) and document in meeting notes.
Draft project charter (summary, goals, constraints, approval path).
Finalize module list with numbering and draft initial simulation scope (role, scenarios).
Confirm development path (custom / vendor / hybrid) and timeline with stakeholders.
Submit any infrastructure requests.

Exit criteria

Kickoff is complete when:

Intake notes are documented
UCI is assigned or confirmed
Module list is finalized
Development path is chosen (custom / vendor / hybrid)
Simulation scope is drafted
Stakeholders and timeline are confirmed

Common mistakes

Skipping or skimming intake notes so Planning lacks context.
Leaving UCI or module list vague so naming and tracking break later.
Not choosing custom vs vendor vs hybrid up front so the team builds the wrong way.
Simulation scope left blank or generic so Planning has to invent the frame from scratch.
Stakeholders or timeline not confirmed, leading to rework or missed handoffs.

What must be completed before you leave kickoff?

Just the module list
Intake notes, UCI, module list, dev path, simulation scope, and stakeholder confirmation
Only stakeholder approval
A full planning doc
Select an answer to view feedback.

Cover in intake (document in meeting notes)

Cover in intake / meeting notes

Module repo
Development SME
Product Manager
Target curriculum for piloting
Objectives
Outcome measurement
Modality
Module length
Class time
Development timeline
Q&A timeline
Canvas readiness timeline
Target cohort for piloting

UCI (Unique Course Identifier)

UCI rules (expand for detail)

Four-digit UCI; revisions use decimals (1001.1, 1001.2). Series: Market 1000, Customized 2000, Alumni 3000, Internal 4000. When a new UCI is needed depends on requester and type of change. See full UCI guide.

Developer Quick Start — full sequence and checkpoints
UCI guide — course numbering rules
Planning — next phase after kickoff

Next step

Planning — Define objectives, choose evidence types, and plan learning sequences.