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
For the module cycle ending the week of 8/14 we're still in the process of implementing a robust feedback system. For the feedback prompts you should do the best you can to characterize feedback you've received and given. It'd be ideal to gather your own quotes from teammates/classmates either via submitted anonymous feedback you've received or directly asking them for feedback.
Here are some notes about expectations for this cycle:
- Individual Assessment: Yes
- Required Project: Final Project (Headcount / Black Thursday)
- Included Projects: All individual and paired projects
- Instructor Pairing Feedback: At least 1 session from during the module
- Posse challenges (4/5)
- Feedback: Self-Solicited and from Feedback App
Soft Skills / Protocol Requirements
- 1 DTR memo from a project during the module
- 1 Blog post
- 2 examples of well-written pull requests
- 1 example of a well-written project readme
- Evaluation notes
- Mentor sessions (>=3)
- Blog post (>=1)
- Self-solicited continual peer feedback
- Posse challenges (4/5)
- Non evaluated projects: Sinatra CRUD, Tool Chest, Mix Master, Rails Mini Project
- Evaluated projects: Traffic Spy, Little Shop
- Assessments: mid-module, final
- Individual Assessment
- Included Projects: Self-Directed Project, Rales Engine, The Pivot
- Bonus Project (not required): APIcurious
- Feedback: Self-Solicited
- Posse challenges (4/5)
- Individual Assessment: Only if needed
- Required Project: GameTime
- Included Projects: RealTime, ScaleUp
- Feedback: Self-Solicited
- Posse challenges (4/5)
- Carefully read the
submission_guidelines.markdownto understand how your portfolio should be written/submitted - Read a sample portfolio in
sample.markdownin this repo - Copy the content of template.markdown as a starting point
- Fill in and submit your own content.
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.
The file should be
saved in the format "date-name-completing.markdown" where:
dateis the last day of the module in compressed year/month/day, like20150831nameis your first and last name likejeff-casimircompletingis 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 15-minute session the reviewers will:
- Read your portfolio
- Ask questions
- Use the rubric (
rubric.markdown) to assess the quality of your work - Render a promotion decision
- Record notes and the decision in 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