SE Portfolio Requirements
Purpose
We believe that portfolio sessions are important opportunities for three areas of growth:
- Confronting Progress: Portfolios give students the opportunity to understand their own progress in pursuit of their career as a software developer.
- Practicing Narrative: Portfolio presentations push students to articulate their narrative of their technical and professional journey.
- Direct Feedback: Portfolio feedback allows students to receive a summative perspective of their performance, including threads of successes and areas of growth.
Portfolio presentations are a requirement for all students, regardless of whether they are repeating a module or not.
Plan
Students will give a 10 minute presentation on the reflections prompts in the dropdowns below. Students will create a visual presentation with Google Slides, PowerPoint, Prezi, etc, your choice.
Your presentation should not be a series of slides that simply restate the prompt then directly answer it. Instead, it should follow a narrative format. This is an opportunity to fine tune your story and how you speak about your work. Slides/visuals should flow naturally from one to the next.
Your slides should not be full of text. You should have 2 - 4 bullet points max on each slide. The narrative you want to speak to for each slide needs to be saved in the notes for that slide. Instructors should be able to look at your presentation slide deck and know what you’ve said in the presentation.
Your presentation slides will be submitted as a deliverable at the beginning of the portfolio session. Then you will be sent to breakout rooms in pairs to present to each other.
M1 > M2
Focus: Your Background and Vision
- How does your past experience link to your work at Turing and in the eventual career?
- What strengths are you bringing with you to this new industry?
- Why are you motivated to become a software developer?
M2 > M3
Focus: Collaborative Learning & Building
- What particular skills, talent, or perspectives do you bring to a team?
- What makes for a successful team? What derails a well-intentioned team?
- What are some tools and systems that you’ve used this inning to help with collaborative technical work? (i.e. project boards, code reviews, etc)
- How will your experience in team projects influence your professional work in the industry?
- What were your key takeaways from your coffee chat this inning?
Repeating Students (any module)
Focus: Targeting Areas Of Opportunity
- What is something you are proud of from this inning?
- What would you say were your top two challenges this inning?
- What will you do next inning to combat those challenges?
- What is supports will you next inning?
- Next inning, what will you do when you get stuck on a technical problem? What resources will you utilize? (Be specific!)
- What is something you’re excited about for the upcoming inning?