Portfolios

In order to earn promotion to the next module or graduation you need to complete, submit, and defend your portfolio.

A submission summarizes your accomplishments in these key areas:

• Individual
• Team
• Community

Authoring Process

• Carefully read the submission_guidelines.markdown to understand how your portfolio should be written/submitted
• Read a sample portfolio in sample.markdown in this repo
• Copy the content of template.markdown as a starting point
• Fill in and submit your own content.

Per-Module Expectations

Module 1 (Back-end)

• Individual Assessment: Passing Score (All 3's) required
• Required Project: Final Project (Headcount / Black Thursday) -- Passing Score (All 3's) required
• Included Projects: All individual and paired projects
• Feedback: Self-Solicited and from Feedback App

** To Repeat the Module **

A passing Chisel project completed during the final 2 weeks of the module OR Satisfactory progress on the Headcount / Black Thursday final project.

Soft Skills / Protocol Requirements

1. 1 DTR memo from a project during the module
2. 1 example of a well-written project readme

Module 1 (Front-end)

• Individual Assessment: Passing Score (All 3's) required
• Required Project: Final Project (Game Time) -- Passing Score (All 3's) required
• Included Projects:
• Linked List
• Number Guesser
• Color Changer
• Feedback: Self-Solicited and from Feedback App

Soft Skills / Protocol Requirements

1. 1 DTR memo from a project during the module
2. 1 example of a well-written project readme

Module 2

• Evaluation notes - You need to take notes during assessments/evaluations

• Blog post (>=1)

• Self-solicited continual peer feedback

• If you're in a posse - please include:

  • a blurb about what you did with your posse over the module
  • your favorite thing about the posse experience
  • how has your posse experience helped you grow as a professional?

• Non evaluated projects: Sinatra CRUD, Tool Chest, Mix Master

• Include what you learned/took away fromt he project.

• Peer evaluated projects: Rails Mini Project

• Include what you implemented for the extension day. And include a short description of what you built and what you took away/learned from this project.

• Evaluated projects: Rush Hour, Little Shop

• Assessments: mid-module, final

Module 3

• Individual Assessment
• Included Projects: Self-Directed Project, Rales Engine, The Pivot
• Bonus Project (not required): APIcurious
• Feedback: Self-Solicited
• Something valuable you've taken away from your posse.

Module 4

• Individual Assessment (thoughtbox)
• Required Project: GameTime, ScaleUp
  • Should include points breakdown per project
• Bonus Project (not required): IdeaBox
• Feedback: Self-Solicited

Submission Guidelines

A pull request with your submission must be made at least 12 hours before your scheduled defense. Non-conforming formats, filenames, or directories will be rejected and your defense rescheduled.

Self-Evaluation

Your submitted portfolio should include self-assessment scores. Use the rubric to determine your proper scores.

Filename & Directory

The file should be saved in the format "date-name-completing.markdown" where:

• date is the last day of the module in compressed year/month/day, like 20150831
• name is your first and last name like jeff-casimir
• completing is the module that you're completing, like m4

So a complete filename might look like 20150831-jeff-casimir-m4.markdown. This file needs to be stored in a directory portfolios/students/your-cohort/your-name where your-name is like jeff-casimir and your-cohort is your cohort number.

If you were completing Module 4 in Cohort 1410 on August 31, 2015 and your name was Jeff Casimir, your portfolio submission would reside at the following location: portfolios/students/1410/jeff-casimir/20150831-jeff-casimir-m4.markdown.

Evaluation Process

Your portfolio will be evaluated in the last week of the module by a panel of at least two instructors. During this short session:

• You will start by showing the scores of your self assessment
• You will walk through the rubric and the content of your portfolio to explain your scoring
• The instructors will ask questions along the way and record notes
• As you finish the explanation the instructors will validate or correct your self-assessment scores
• The instructors will use those scores to render a promotion/graduation decision
• Everything from the instructors will be committed back to your portfolio

Outcomes

Portfolio evaluations have four possible outcomes:

• PROMOTED - your portfolio demonstrates a successful fulfillment of expectations and you may move on to the next module or graduate
• RETAINED - your portfolio is lacking in one or more areas and you may either repeat the current module or leave the program
• EXCUSED - your portfolio is lacking in one or more areas and either (a) you've now failed to pass the module in two attempts or (b) the reviewers have determined that you will not be successful at Turing
• PENDING - your portfolio is incomplete or non-conforming and will be re-evaluated as soon as possible. If it is incomplete after 24 hours it will be moved to RETAINED or EXCUSED