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
- 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.
- Individual Assessment: Passing Score (All 3's) required
- Individual Projects: All individual projects. A passing final project is required.
- Group Projects: All paired projects
- Professional Development:
- DTR Memo from 1 paired project
- Feedback: Paragraph; Self-solicited from project pairs
- Resume with a summary statement and placeholder for projects and skills to be obtained during Turing
- LinkedIn profile with a summary, descriptions under experience, and Turing under education
- Community:
- A recap of reflections from Gear Up
- Summary of how you've contributed to the community
** 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.
- Pentathlon
- Individual Coding Challenge-A: Passing Score (All 3's) required
- Individual Coding Challenge-B: Passing Score (All 3's) required
- Comprehensive Quizlette
- Final Project (Game Time) -- Passing Score (All 3's) required
- Completed Portfolio
- Included Projects:
- Linked List
- Number Guesser
- Idea Box
- Professional Development:
- DTR Memo from 1 paired project
- Resume with a summary statement and placeholder for projects and skills to be obtained during Turing
- LinkedIn profile with a summary, descriptions under experience, and Turing under education
- Feedback: Paragraph; Self-solicited from your peers (from project pairs and anyone else you've consistently worked with)
- Community:
- A recap of reflections from Gear Up
- 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: Bike Share, Little Shop, Job Tracker
- Assessments: Final
- Professional Development:
- Copy for a personal website
- Company tracker with ten companies of interest identified, including one point of contact for each company with contact information (email, blog, website, twitter, github)
- Seven cold emails sent to seven different contacts from the company tracker
- Attend two networking events
- Paragraph reflection on project management strategies you used in your projects (Bike Share and/or Little Shop); What went well? What didn’t go well?
- Paragraph reflection on how you incorporated feedback from your team members and what you learned about yourself in the process
- Community:
- A recap of reflections from Gear Up
- Feedback: Self-solicited and project pairs feedback, plus a summary of how you've contributed to the community
- 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
- Professional Development:
- Copy for a personal website
- Company tracker with ten companies of interest identified, including one point of contact for each company with contact information (email, blog, website, twitter, github)
- Seven cold emails sent to seven different contacts from the company tracker
- Attend two networking events
- Paragraph reflection on project management strategies you used in your projects (Bike Share and/or Little Shop); What went well? What didn’t go well?
- Paragraph reflection on how you incorporated feedback from your team members and what you learned about yourself in the process
- Community:
- A recap of reflections from Gear Up
- Feedback: Self-solicited and project pairs feedback, plus a summary of how you've contributed to the community
- Required feedback from at least one student outside of your cohort who you have paired with (Mod 1 student, back end student) AND/OR a mentor.
- Individual Assessment
- Included Projects: Self-Directed Project, Rales Engine, Cloney Island
- Bonus Project (not required): APIcurious
- Feedback: Self-Solicited and collected from Cloney Island
- Something valuable you've taken away from your posse.
- Professional Development:
- Turing alumni portfolio
- Pitch for personal project/Documentation showing your thought process
- Completed Flower Exercise -- Students can either upload a PDF of their completed flower graphic organizer OR they can create a gist with summarized points listed for each petal:
- Transferable Skills
- Favorite/Most Valued Knowledge
- Favorite working conditions
- Favorite people to work with/serve
- Values/Goals/Mission in life
- Preferred places to live
- Preferred salary and level of responsibility
- Three mock interviews
- Community:
- A recap of reflections from Gear Up
- Individual Assessment
- Included Projects: Self-Directed Project, Remember (Number of Completed User Stories), Weather Forecast
- Bonus Project (not required): None
- Feedback: Self-Solicited and collected from Weather Forecast and Remember
- Professional Development:
- Turing alumni portfolio
- Pitch for personal project/Documentation showing your thought process
- Completed Flower Exercise -- Students can either upload a PDF of their completed flower graphic organizer OR they can create a gist with summarized points listed for each petal:
- Transferable Skills
- Favorite/Most Valued Knowledge
- Favorite working conditions
- Favorite people to work with/serve
- Values/Goals/Mission in life
- Preferred places to live
- Preferred salary and level of responsibility
- Three mock interviews
- Community:
- A recap of reflections from Gear Up
- Individual Assessment
- Required Project: Capstone Project
- Should include points breakdown per project
- Link to your PR for opensource contributions
- Professional Development:
- Paragraph description of top three priorities in the job search and why
- 1-2 paragraph action plan for how to overcome perceived barriers to the job search
- Six cold outreach emails sent
- At least one Blog Post with at least a paragraph of peer review - Open-Source or Technical
- The Plan
- Community:
- A recap of reflections from Gear Up
- Feedback: Self-solicited and project pairs feedback, plus a summary of how you've contributed to the community
- Professional Development:
- Paragraph description of top three priorities in the job search and why
- 1-2 paragraph action plan for how to overcome perceived barriers to the job search
- Six cold outreach emails sent
- Community:
- A recap of reflections from Gear Up
- Feedback: Self-solicited and project pairs feedback, plus a summary of how you've contributed to the community
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.
Your submitted portfolio should include self-assessment scores. Use the rubric to determine your proper scores.
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, like20150831
name
is your first and last name likejeff-casimir
completing
is the module that you're completing, likem4
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
.
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
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