______     _   _           _      __
|  ___|   | | | |         | |  .'".'"'.
| |_ _   _| |_| |__   ___ | | :._.""._.:
|  _| | | | __| '_ \ / _ \| | :  \__/  :
| | | |_| | |_| |_) | (_) | |  './  \.'
\_|  \__,_|\__|_.__/ \___/|_|     ""

Brought to you by DefCom4

Table of Contents

• Check-in
• Organization
• Design-Approach
• DTR
• Contributors
• Retrospective

Check-in

• Daily morning stand ups in slack
• Group work time in study hall/collaborate when needed
• Created protocol for reaching out to team if unproductive struggle for >= 1hr

Return to Top

Organization

• DefCom4 Figma Board
• DefCom4 GitHub Project
• Adhere to a formula for writing commit messages to streamline readability

Return to Top

Design Approach

• Adherence to SRP
• Russian nesting doll approach
• Refactor after functionality is achieved

Return to Top

DTR

• Original DTR
• Second DTR

Return to Top

Contributors

• Angel Byun - LinkedIn - Github

• Andrew Bingham - LinkedIn - Github

• Thomas Hawley - LinkedIn - Github

• Crow Rising - LinkedIn - Github

Return to Top

Retrospective

Sailboat Method

• This is where we discovered this method for running a retrospective

Top things that went well during your project

• We had excellent communication
• We targeted our learning goals and gave each other opportunities to practice them
• Everyone’s great work ethic

Top things your team would do differently next time

• We should have planned everything more at the start (naming conventions, etc)
• Should have avoided working late into the night on some pieces

Return to Top