lindsaywparker / portfolios

Turing School promotion portfolios

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
• Professional Development
• Community

Authoring Process

• Carefully read this document - README.markdown - to understand how your portfolio should be written/submitted
• Read thru a portfolio from a student in upper mod for reference
• Fork this repo and edit the template.markdown file in portfolios/students/your-cohort/your-name. IF the file or folder in question is missing, then copy the content of template.markdown as a starting point.
• Fill in and submit your own content. Submission guidelines are located at the bottom of this document

Per-Module Expectations

Module 1 (Back-end)

1. Fork and clone this repo.
2. Follow instructions in portfolio expectations to create your folder and file for your M1 portfolio.
3. Copy the template code from the M1 template markdown to your new file.
4. Update placeholder text in template.
5. Commit your changes, push to your remote repo, then create a PR to the turing/portfolios repo.

Module 1 (Front-end)

Your promotion to the next module is based upon a summative assessment coined the Pentathlon. The Pentathlon includes:

1. Individual Coding Challenge-A: Passing Score (Proficient in all areas) required
2. Individual Coding Challenge-B: Passing Score (Proficient in all areas) required
3. Final Project (Static Comp Challenge #3) -- Passing Score (Proficient in all areas) required
4. Comprehensive Quizlette: Passing Score (80% correct answers) required
5. Completed Portfolio

Your completed portfolio is also comprised of the following required material:

• Course Projects:
  • Number Guesser
  • Linked List or Foto Finder
  • Idea Box
  • 2DoBox Pivot
• Community:
  • A recap of reflections from Gear Up

You may optionally elect to include a status of "pass", "fail", "pending" for each of the individual Pentathlon challenges in your portfolio, but it is not required. Your instructors will send your Pentathlon challenge scores to you upon completion of those evaluations and in advance of portfolio reviews.

Module 2 (Back-end)

• Evaluation notes - You need to take notes during assessments/evaluations
• Blog post (>=1)
• If you're in a posse - please include (in the Being a Community Member section):
  • 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: Rails Mini Project, Mix Master
  • Include what you learned/took away from the project.
• Evaluated projects: Little Shop, Bike Share
• Assessments: Final
• Community:
  • A recap of reflections from Gear Up

Module 2 (Front-end)

• Individual Assessment: Passing Score (All 3's) required
• Required Project: ToDo Box Pivot, Shoot the Breeze, FireBae (Tier Two) -- scores should all be passing (All 3's) or show gradual improvement
• Included Projects:
• Weatherly
• Community:
  • A recap of reflections from Gear Up
  • Summary of how you've contributed to the community

Module 3 (Back-end)

• See template here
• Individual Assessment
• Included Projects: Self-Directed Project, Rales Engine, Cloney Island
• Bonus Project (not required): APIcurious
• Something valuable you've taken away from your posse.
• Community:
  • A recap of reflections from Gear Up

Professional Development does not need to be included in the portfolio. Submit your deliverables here

Module 3 (Front-end)

• Individual Assessment
• Included Projects: Self-Directed Project, Remember (Number of Completed User Stories), Weather Forecast
• Bonus Project (not required): None
• Community:
  • A recap of reflections from Gear Up

Module 4 (Back-end)

• Individual Assessment
• Required Project: Capstone Project
  • Should include points breakdown per project
• Link to your PR for opensource contributions
• Community:
  • A recap of reflections from Gear Up

Complete and document 2 of the following:

• Lead or co-lead a Friday Spike
• Deliver any session at a meetup or conference
• Pair three or more times with students in lower modules
• Contribute in a meaningful way to project of a student/team not in your module

Professional Development does not need to be included in the portfolio. Deliverables and submission guidelines are here

Module 4 (Front-end)

• Individual Assessment

• Required Projects (4 out of 5): Capstone Project, Imposter Syndrome, Jet Fuel, BYOB

  • Should include points breakdown per project

• Community:

  • Summary of how you've contributed to the community
  • A recap of reflections from Gear Up

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