Team Agreement - VMBailey/qumolo GitHub Wiki

Cooperation prep

Vincent:

Strengths? Adaptability Handling Ambiguity Openness

With a sense of adaptability

Areas of Growth? Curiosity Innovation Networking

Day to day Communication is crucial in order for us to stay on schedule.

Bill Strengths? Constant Improvement - truly invested in performing his best. Adaptability Customer orientation Innovation - Likes to give the customer options. Does his best to understand the customer’s needs to best deliver a polished product for them. Listening Collaboration - team player Problem solving - truly shines in team settings. Creative

With boundless energy and a big heart, Bill will be an integral part of the team.

Areas of growth

Analytical thinking Prioritization Planning and estimating Incremental delivery Project execution Judgement Craft

Day to Day? Create a roadmap; a checklist of things to accomplish every day. Help each other finish tasks

Daniel

Strengths? Curiosity - asks questions Integrity Ambition and initiative Inclusivity Organized Analytical mind

Daniel is the calm before the storm. With a laid back aura, he will play an integral role not just for project management, but also for team vigor.

Areas of Growth? Confidence - feels a lack of confidence in areas that he isn’t educated in. Technical

Day to Day work? Checking in is crucial. Making sure everyone is on the same page before moving on to the next step.

Conflict Plan Conflict when it arises? Mediation acts as the relieving agent for conflict. Communication and transparency are crucial. If you have a problem, talk it out.

Skill Levels? We’re all learning. No one is perfect. We’ll approach this entire project with full transparency.

Escalation? Reach out to TA for unresolved conflicts

Communication Plan Bill: 8am - 8pm Pacific Daniel: 8am - 6pm Pacific Vincent: 10am - 10pm Central

Platforms: Slack, Discord, Google

Breaks Every 45 to 50 minutes, 10 minute break Hour for lunch

After Hours? We’re always available after hours

Voice is heard? Communication is crucial

Inclusivity? Check-ins and empathy.

Work Plan Explain your work plan to track whether everyone is contributing equally to all parts of the project, and that each person is working on “meaty” problems. This should prevent “lone wolf” efforts and “siloed” efforts.

Project management with Google Spreadsheets. Checklists and check ins. Morning check ins will shape the day and evening check ins will shape what needs to be worked on the next day.

Git Process Share repository We’ve created an organization repository for the project.

Scripts pertaining to PowerShell and Group Policy

What is your Git flow? We will work on scripts together, but we will communicate with each other before scripts are pushed out.

Will you be using a PR review workflow? Given our modes of communication that are in place, we do not require the use of the PR review workflow