Off-Platform Project Production
Description / Purpose
The purpose of this process is to produce a single off-platform project that aligns with the Off-Platform Project Content Standards
Off-Platform Project Production Processes
Step 1: Ideation
Typically, off-platform projects are more involved or complex than on-platform projects. This makes the ideation phase of production particularly important. During this period the Curriculum Developer or Content Associate will create a "design document" that outlines what they want the project to be, what the outcomes for the learner are, and what learning standards the project is giving applied practice on.
This step can either be done by a Curriculum Developer, who then hands the design document over to a Content Associate for production, or it can be done by a Content Associate from start to finish with guidance and review from a Curriculum Developer.
During this stage it should be decided what kind of off-platform (or simply cumulative) project this will be. Will it use the project content item? Will it use an informational? What local environment setup instructions will be needed?
Needs Review: If this step was completed by a Content Associate, the design document needs review.
Step 2: Solution Code Draft
Once the project idea is approved, the first step is to create a draft of the expected solution code. The form this takes depends on the type of project. It may be a full Jupyter notebook (as is the case in many Data Science projects), or it may be a completed website/web app, as is the case in many Web Development projects.
Needs Review: Solution code draft.
Step 3 + 4: Final Solution Code and Starting Code
Changes to the first solution code draft are made and the final solution code for the off-platform project is completed. Additionally, the author puts together the starting code that is given to the learner at the beginning of the project. This includes any relevant assets or data sets that will be included in the project.
Step 4: Draft of Instructions
In google documents, the project author drafts a series of Task Groups and individual tasks (also know as project steps) that the learner will follow to turn the starting code into the solution code.
Needs Review: Draft of the instructions.
Step 6: Informational / Project in Author
Revisions to the instructions are incorporated and everything is moved into Author, into whatever the appropriate content item for this type of project is. A couple extra steps need to be done here as well:
- Starting Code + solution code + any assets the learner needs to download are compressed into a .zip and uploaded to S3.
- A project thumbnail is selected. Either request an design using the ART board, or select an appropriate image from Unsplash
Step 7: Final Review + Revisions
The final stage of review: a Curriculum Developer takes the project in full, as a learner would experience it. Any final revisions are then incorporated by the author of the project.
Step 8: Video Walkthrough is Requested
Once the project is completed an approved, the Curriculum Developer overseeing production should request a video walkthrough from the VIDEO board.
Milestones/Deliverables for Production
When producing an off-platform project with a Content Associate, the previous steps are consolidated into the following set of deliverables.
|Solution Code||The solution code and project summary. You will produce this deliverable in the most appropriate format that you and the Reviewer agree upon.||4 days production + 2 days review|
|Project Draft + Starting Code||A draft of the project task groups and steps in a google document along with the starting code/workspace||4 days production + 2 days review|
|Final Project||This deliverable includes the initial savepoint, final savepoint, and project checkpoints. You will produce this deliverable in Author.||2 days production|
The following diagram shows the deliverables to produce a an off-platform project in a day by day gantt-like chart. Light green days are dedicated to production, darker green days are when deliverables are due, and yellow days are when the content is being reviewed.