Skip to content

Project Prep One

Jump to bottom
Stephen Clemmer edited this page Oct 15, 2022 · 1 revision

Final Project for Code Fellows 401

Authors:

Xavier Hillman: Stephen: WA (PST): Brandon Pitts: Jack Subblefield: KC Hofstetter:

Resources

Group Project: Team Agreement

What are the key strengths of each person on the team?

KC Hofstetter: React, data structures and algorithms, socket.io, organization, front end beautifying

Stephen: Good with HTML; feeling comfortable with backend, still getting comfortable with React, feeling comfortable with AWS SNS and SQS, event driven programming.

Xavier: Competent with event driven application design and API connections

Jack: Good with most backend stuff, learning new stuff fast, and working with data. debugging

Brandon: Competent with back end, API, Crud applications, Sockets without queues

Identify team leads through all stages of the project (Subject Matter Expert)

KC Hofstetter: project organization, debugging

Stephen: Pair programming, project management, Trello

Jack: debugging, data flow / modularizing

Xavier: Event driven program design, API interactions

Brandon: Project planning, Team Scheduling

In which professional competencies do you each want to develop greater strength? KC Hofstetter: communication, leadership Stephen: Craft Competency, Results Competency Xavier: Planning and Estimating Jack: Working with a team, project planning, setting good project goals/expectations Brandon: Craft

Knowing that every person in your team needs to understand all aspects of the project, how do you plan to approach the day-to-day work?

  • Morning Stand Up:
  • Are there any merges outstanding
  • Git pull origin main to make sure we’re in the same place
  • Plan the timeline based on the structure of the project
  • Check in before and after lunch to make sure the team is aligned
  • Check if there are any merges
  • Merge branches often so we are coordinated and nothing changes too drastically.
  • Git pull origin main at the end of the working day
  • 9am - 6 pm PST working day
  • Take breaks when needed

Conflict Plan

What will be your group’s process to resolve conflict, when it arises?

  • Open communication: Honest, clear, feeling comfortable taking risks to clear the air, no grudges
  • Timeouts - Walk away when things get heated so they don’t escalate
  • Grab another member to mediate in the group
  • Team vote on major decisions
  • What will your team do if one person is taking over the project and not letting the other members contribute?
  • Respectfully draw their attention to the behavior and give them an opportunity to wrap up their thoughts.
  • Hand off the conversation to another person.

How will you approach each other and the challenges of the project knowing that it is impossible for all members to be at the exact same place in understanding and skill level?

  • Ask questions
  • Preschool mindset - continuous learning
  • Be cool

How will you raise concerns to members who are not adequately contributing?

  • Open communication
  • Be direct with that person
  • How and when will you escalate the conflict if your resolution attempts are unsuccessful?

If / when conflict starts to affect the project timeline:

  • Tribal Council
  • Consult Ryan

Communication Plan

** What hours will you be available to communicate?**

KC Hofstetter: (start 10/16) sun-sat 8AM-11PM Stephen: Sun-Sat 8:00 a.m. PST - 11:00 pm PST Xavier: Sat & Sun: 9am - 2pm PST —-- Mon - Fri: 9am - 9pm PST Jack: Sat/Sun: 6:00am - 8:00pm PST | M-F 6:00am - 8:00pm PST Brandon: Mon-Fri: 9am-9pm PST Sat-Sun 9am-12pm PST

What platforms will you use to communicate (ie. Slack, phone …)?

KC Hofstetter: slack, remo, text , or email Xavier: Slack, Remo, Text Brandon: Slack, Remo, Phone, Email Stephen: Slack (for group chat), Phone: (immediate chat) Text (Respond within 2 hours), (email: for larger docs, collateral materials, and items that are larger than a chat/text. Responds within 24 hours) Jack: Slack, Remo, Text, Email.

How often will you take breaks?

  • As needed

What is your plan if you start to fall behind?

  • Communication
  • Utilize TA support
  • Reach out to Ryan
  • Focus on the MVP - SIMPLIFY FROM THE START

How will you communicate after hours and on the weekend?

  • Slack for things that can be handled by anyone in the group when we return to work, or asap
  • Text: For things that can be responded to within an hour
  • Call: For immediate emergency communication

What is your strategy for ensuring everyone’s voice is heard?

  • Preschool mindset
  • How will you ensure that you are creating a safe environment where everyone feels comfortable speaking up?
  • Genuine/natural conversation
  • Work Plan

How will you identify tasks, assign tasks, know when they are complete, and manage work in general?

  • Project manager: Stephen will submit to Ryan for the group. Jack will submit for Delta-V

  • Morning standup:

  • Daily standup: 10-15 minutes

    • What did you do yesterday? (60 seconds)
    • What are you working on today? (60 seconds)
    • Any blockers? (60 seconds)

  • End of day huddle

    • Daily standup: 10-15 minutes
    • What did you do today? (60 seconds)
    • What are you working on tomorrow? (60 seconds)
    • Any blockers? (60 seconds)

What project management tool will be used?

  • Slack: for team communication

  • Google Docs: for planning and file management (like this doc), pres deck

  • Project Management Tool: Trello or Git hub - TBD

  • Whiteboard tool: Figma

  • Github: for collateral materials, Google docs folder for 401 Midterm (i.e., pics, etc.)

  • Presentation Deck

  • Make a single copy of the Presentation Deck Template. Share your copy with all team members, so everyone is working from the same file. Link to the shared doc in your project plan. Google Doc Slide

  • Schedule your practice session - Stephen will talk to Ryan to schedule this - TBD

Git Process

What components of your project will live on GitHub?

  • Organization/Repositories/Assets(except for the assets that live in the team’s Google Folder)

How will you share the repository with your teammates?

  • Merge early and often and on schedule
  • Anytime we have a working piece of the project, we should seek to merge.

What is your Git flow?

  • Branch on individual branch (‘name-feature’)
  • Git Pull Origin Main to sync branches
  • Merge and Pull request when we have working code
  • Git pull origin main to sync branches

How many people must review a PR?

  • 2

Who merges PRs?

  • Subject matter expert & person who wrote the code (alt. PM)

How often will you merge?

  • Anytime we have working code for a piece of the project

How will you communicate that it’s time to merge?

  • Video chat in Remo.
Clone this wiki locally