Sample phase 1 team checklist

This is meant as an example of the kind of thing each team can prepare at the start of each phase then check off as the key deliverables/deadlines are met.

Deadlines

Each team member reports to the team manager/organizer/lead when they have successfully completed the given step.

The team manager/organizer/lead distributes the final team versions of proposal.md and charter.md and keeps track of what team members have reported (and nudges/reminds team members who have not yet reported completion of necessary steps).

Team member	Has successfully forked/cloned project repo	Has final copy of team proposal.md	Has final copy of team charter.md	Has successfully submitted project repo (working tree clean)	Has successfully forked/cloned contributions repo	Has successfully submitted their contributions repo (working tree clean)
name of team member a
name of team member b
name of team member c
name of team member d
name of team member e
name of team member f

Deliverable contents

Team members will have their portions of proposal.md and charter.md completed and submitted to the document lead at least 48 hours prior to the document submission deadline, and the document lead will distribute the final document versions to all team members at least 24 hours prior to the document submission deadline.

Confirmed/correct deliverable contents (checked by the document lead when the final versions of the documents have been prepared)

proposal.md contents	Completed
Team and project name
Contact person for document
Product overview and introduction
Target audience and motivation
Product features and behaviour
Preliminary sketches/mockup
Scaling plans
Technical risks
charter.md contents	Completed
Team and project name
Contact person for document
Name and viu email for each team member
Brief product outline
Team philosophies, goals, priorities
Handling of roles, responsibilities, workloads
Meeting and communication plans
Plans for handling deadlines
Plans for addressing feedback
Plans for conflict resolution
Policies and procedures for AI use
Collective team strengths and weaknesses