M2 Portfolio Requirements

Purpose

  • Acknowledging Progress: portfolios give students the opportunity to understand their own progress in pursuit of their career as a software developer.
  • Practicing Narrative: portfolio presentation pushes 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.

Structure

  • Student-directed presentation (5 minutes)
  • Instructor feedback (5 minutes)

Requirements

Each student will deliver a 5 minute slide presentation in front of your instructors.

  • A student who will repeat the current module uses their presentation time to explore why they struggled, discuss the lessons learned, and lay out a plan for what will be different next time.
  • A student who is repeating unsuccessfully and will leave the program is excused from the presentation and can use the entire portfolio time for feedback and discussion.
  • A student who passes the module will present the following:
    • What particular skills, talent, or perspectives do you bring to a team?
    • What have you learned about building software in pairs and teams?
    • What makes for a successful team? What derails a well-intentioned team?
    • What factors determined the success and quality of your pair and group projects?
    • How will your experience in team projects influence your professional work in the industry?
    • How will your Gear Up sessions impact you as a software developer?
    • What practical lessons are you taking away from Gear Up sessions that you will use on the job? (use your gists to help reflect on this question)

The presentation should not be a series of slides that directly answers each of these questions with bullet points, but instead should:

  • Follow a narrative format – this is an opportunity to fine tune your story and how you speak about your work. Slides should flow naturally from one to the next.
  • Include images and graphics to illustrate the concepts you plan to discuss. These may include screenshots/animated gifs of an application you created, snippets of code from your projects, diagrams of interesting concepts/structures that you used in your project(s).

Submittal

  • Students are not required to submit any documents but instead should be prepared to give their presentation to their instructors and engage in a follow up conversation.

Potential Outcomes

  • If everything goes to plan: good luck in next mod!
  • If a student fails to present a portfolio (due to illness, etc): need to present it in Week 1 of the next inning
  • If a student delivers an exceptionally poor portfolio: we’ll determine next steps, possible PIP, etc