Skip to content

Instantly share code, notes, and snippets.

@neight-allen

neight-allen/1605-scale-up-retro.md

Created November 7, 2016 15:57
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save neight-allen/002182cf3e04552e37acf094fb9bde01 to your computer and use it in GitHub Desktop.
Save neight-allen/002182cf3e04552e37acf094fb9bde01 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
1605-scale-up-retro.md

9:00: Introduction

Setting the Context:

This is similar to a consulting situation where you basically run out of billable hours and need to wrap up and leave things in a good state for the client or the next consultant on the project. Since we had a pretty informal Scale Up, and since we didn't have a cohort retro on Friday - let's also take this opportunity to support one another with some technical reviews!

Prime Directive ‘Regardless of what we discover, we understand and truly believe that everyone did the best job he or she could, given what was known at the time, his or her skills and abilities, the resources available, and the situation at hand.’

9:05: Small Groups: Project Discussion

Small Groups:

  • Patrick Wentz & Matthew Packer & Karina Gonzalez & Deb Hamel
  • Yoseph Anderson & Trent Whitinger & Roberta Doyle & Lane Winham
  • Kerry Sheldon & Matthew Campbell & David Tinianow & Caleb Cowen
  • Ryan Flach & Kris Sparks & Tommasina Miller & Zachary Forbing
  • Garrett Smestad & Jason Hanna & Jennifer Soden & Christopher Concannon

Break into small groups per this document. Each person should talk about:

  • What they worked on for the two weeks
    • Give a small demo
  • What did you feel went well?
  • What did you feel went not well?
  • Assuming you can never work on this again after today - what do you need to make this project in your Github or resume something impressive and well wrapped up. Does what you have done now work?

9:30 - 🍅 BREAK

9:40 - Small Groups: Blog Post Sharing

Small Groups:

  • Patrick Wentz & Matthew Packer & Karina Gonzalez & Deb Hamel
  • Yoseph Anderson & Trent Whitinger & Roberta Doyle & Lane Winham
  • Kerry Sheldon & Matthew Campbell & David Tinianow & Caleb Cowen
  • Ryan Flach & Kris Sparks & Tommasina Miller & Zachary Forbing
  • Garrett Smestad & Jason Hanna & Jennifer Soden & Christopher Concannon

Send copies of your published blog posts to the members of your small groups

Individual Review

Read through each blog to give feedback (pro-tip: copying the content of the blog into a google drive document that you can share with the person is a great way to comment inline)

Think about and look to answer the following questions:

  • Does the blog post have any grammatical errors or spelling errors?
  • Does the blog post have enough context that someone outside of the Turing community can understand/learn from it?
  • Does the ending of the blog post summarize the article well?
  • Does the blog post include useful reference links and attribution for resources that helped the blog post writer?
  • What questions are outstanding in your mind after reading the post?
  • What did you like about the blog post?

10:00 - Feedback Review

Send feedback to each member of your group. Spend the next 10 minutes reviewing that feedback.

10:10 - Small Group Discussion

Discuss what you found while reviewing each others' posts. Especially those things you liked and appreciated.

10:20 - 🍅 BREAK

10:30 - Resume/Profile/Project Review: Hand Out

Small Groups:

  • Patrick Wentz & Matthew Packer & Karina Gonzalez & Deb Hamel
  • Yoseph Anderson & Trent Whitinger & Roberta Doyle & Lane Winham
  • Kerry Sheldon & Matthew Campbell & David Tinianow & Caleb Cowen
  • Ryan Flach & Kris Sparks & Tommasina Miller & Zachary Forbing
  • Garrett Smestad & Jason Hanna & Jennifer Soden & Christopher Concannon

In your small groups - share links to your resume and turing profile.

Individual Review

Read through this document on READMEs

Read through the resumes and Turing profiles that were shared with you. Write down your feedback so you can share it. Look to give feedback on the following things:

  • Do the linked projects in the resume have:

    • An easily found link to production
    • A description of the technical challenge
    • A description of skills learned or utilized
    • A description of technologies used
    • Enough context for someone outside of Turing to understand the project

  • Does the resume have any red flags

    • misspelled or incorrectly capitalized technical names: i.e. java script instead of JavaScript
    • grammatical errors
    • mismatched fonts
    • overly informal language
    • explanations of work or projects that would be hard to understand for someone not from Turing

  • What did you like/appreciate about the resume?

  • What did you like/appreciate about the repo READMEs?

10:50 - Feedback Review

Send Resume feedback to each member of your group. Spend the next 10 minutes reviewing that feedback.

11:00 - Small Group Discussion

Discuss what you found while reviewing each other's Resumes and projects. Especially those things you liked and appreciated.

11:10 - 🍅 BREAK

11:20 - Large Group Discussion

Meet as a group to discuss our experiences reviewing.

11:45: Hardening

  • Future work and stories for LookingFor - what's still in flight?

  • Anyone who is interested, stick around to clean up the LookingFor/MentorSHIP issues and codebase and merge any outstanding PRs

  • Individual projects: Use this time to go over your notes for what you want to wrap up on the project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment