# New Program Development Checklist - CodePath.org

This is a list of all the stuff that comes up every time we create a new course.

## Marketing/Applications

- [ ] Do we have the course title and short description?
- [ ] Do we have the course long description?
- [ ] Prepare the application for students to enroll
- [ ] Create the cohort on the back-end
- [ ] Application body and description text
- [ ] Review questions asked in application
- [ ] Prepare the landing page for [CodePath.org](http://codepath.org/) with appropriate copy
- [ ] Have we created the policy syllabus or overview snippet for the course to be shared with students and professors?
- [ ] Has the marketing and outreach to students started?

## Admissions

- [ ] Have we drafted and configured the automated emails during admissions
- [ ] Do we have the pre-work created?
- [ ] Has the pre-work been added as a snippet in the portal?
- [ ] Do we have the pre-work sent to students with automated emails?
- [ ] Do we have the pre-work reminder configured?
- [ ] Do we have clear rubric and instructions for grading and processing incoming pre-work?
- [ ] Is someone actively processing incoming pre-works and updating their status?

## Curriculum

- [ ] Have we decided how long the course is and how many sessions per week?
- [ ] Are there groups formed in the course? When are they formed?
- [ ] Have we setup regular meeting with the curriculum team?
- [ ] Have we outlined the contents of a given unit?
- [ ] Has the curriculum team been unblocked to begin development?
- [ ] Have we outlined the entire unit outline breakdown over the course?
- What topics are introduced each week?
- What assignments or submissions are assigned and what are they?
- Is there work before the session?
- [ ] Have we outlined the tabs that will show up for a given unit on the course system?
- [ ] Have we set a timeline for completing the first 3 weeks of the course in the portal?
- [ ] Have we identified the submissions and deadlines for the course?
- [ ] Have we created readme templates for every submission?
- [ ] Have we created clear submission instructions on the course system?

## Instruction

- [ ] Have the slide decks been created for all sessions?
- [ ] What is the session outline for a given session each week?
- [ ] Have the sessions been designed and clearly outlined in the course system?

## Staffing

- [ ] Have we discussed the overall budget for this course?
- [ ] Curriculum
- Who is the curriculum lead/leads? 
- Do we need curriculum supporting developers? How many?
- [ ] Instructors
- Can the curriculum leads also run the sessions as instructor?
- [ ] Beta Testers
- Do we need testers?
- Are we paying testers?
- How are we sourcing?
- [ ] TAs/Mentors
- Do we need industry TAs?
- Are we paying TAs?
- How are we sourcing?
- [ ] Technical Support
- Do we need technical support?
- Are we paying technical support?
- How are we sourcing?
- [ ] Do we need to confirm any panelists for panels during the class?
- Have we identified the topic of each panel?
- Have we communicated the panels to the rest of the team?

## Program / Operations

- [ ] Have we identified the operations member that will manage the sessions?
- [ ] Have we specified the tasks the operation member needs to perform during the session (attendance, breakout rooms, recording)
- [ ] How and when are breakout rooms being used in Zoom?
- Grading (Projects, labs and group milestones)
- [ ] Have we identified the submissions and deadlines for the course?
- [ ] Have we specified how the submissions will be scored?
- [ ] Have we added this information to the course system?
- Accountability
- [ ] Have we identified the session attendance requirements?
- [ ] Have we identified the excused absences allowed?
- [ ] Have we identified the missing assignment policy?
- [ ] What is the withdrawal policy?

## Admissions

- [ ] Have we processed pre-works and admitted students?
- [ ] Have we sent students calendar invites for all sessions?
- [ ] Have we added students into Slack channels?
- [ ] Have we sent out starting details reminder to students?

## Key Milestones

- [ ] Application and landing page are live
- [ ] Pre-work is ready and configured to be sent
- [ ] First pre-work has been submitted by applicant
- [ ] Unit sequence and outline is agreed upon
- [ ] First content unit on course portalis completed
- [ ] Get beta testers running through the first unit of content