-
Notifications
You must be signed in to change notification settings - Fork 0
TeamAgreement
Like all dynamic systems, teams have life-cycles. It is important to consider the strategies and tools leaders use to support effective functioning at a team's various stages. When launching a team, we often spend time planning what to do and forget to establish how we want to work together to support our collective objectives.
Collaborative planning is a framework designed to initiate a conversation that helps transition a team from individual orientations to that of a collective. It helps develop a shared understanding and accountability for how you want to work together to best leverage your individual preferences, strengths, and goals towards an innovative joint outcome. Your collaborative plan is a dynamic repository of your shared agreements that you can refer to and update as you learn more about each other and the project.
Note this repository is public. If there is information you prefer not to write here, you can write it on Slack instead. In particular, don't put phone numbers in this document!
City Tigers
A collaborative climate engenders balanced communication within the team, thorough exploration and discussion of ideas, active reflection on team dynamics, proactive management of interpersonal conflict, and a safe environment for taking risks.
Discuss a previous team experience you've had in which the team cultivated a strong collaborative climate. What behaviors contributed to creating this type of team climate? What behaviors are important to your capstone team for building a collaborative climate?
Show up at Meetings, Be respectful/ communicative about other peoples code, Readable and clear code, Look at bigger picture.
Discuss your prior experiences as relevant to the CS capstone in general and your project in particular. Capture your understandings here:
- Team Member 1: ... SEAN
- Likes programming
- Modular code (Loves Object Oriented Code)
- Small classes
- Needs help with developer tools
- Python
- AI
- C++
- Java Script
- Whiteboard work before code
- Detail Oriented
- Team Member 2: ... SAGE LEVIN
- JAVA
- PYTHON
- C++
- C#
- Organizing
- Team Member 3: ... Mikaela Slade
- Python
- C++
- GIS
- Big Picture / Idea Person
- Strategic Planning
- Good with people
- Geology
- Economics
- Team Leader
- Team Member 4: ... Kai Mcconnell
- C++
- Java
- Javascript
- VUE
- Python
- Data Mining stuff
- C#
- SML
- Github
- Terminal
- Team Leadership
- Over thinking stuff
- Pyplot
- Computer Graphics (A smidge)
- Unity
- Communication
- Loves programming
- Netbeans
- Spyder
- Web Scraping
- Team Member 5: ...
What do you each hope to learn or gain from the CS capstone? What would make you proud of your individual contributions? Capture your understandings here:
- Team Member 1: ... SEAN
- Big project
- Learning GIS
- Team Programming
- Team Member 2: ... Mikaela
- Real world Impact
- Team Member 3: ... SAGE
- Learning GIS
- Experience real world projects
- Team stuff
- Team Member 4: ... Kai
- Learn GIS
- Improve team skills in real world enviroment
- Create cool product that can be shown to the world
- Help Walla Walla in some way.
- Team Member 5: ...
Discuss your collective learning goals for the capstone project. What do you want to gain from the experience? What would make you proud of your work as a team?
Learning GIS Data, Real world Project, Team programming, Working with a Client, creating a useful and impactful project.
Discuss any preferences for when you like to work, the technologies you might use to coordinate between meetings, your expectations for responsiveness, and any constraints that might limit when you are available. Consider potential roles you might need to coordinate your work during meetings or between meetings (scribe, contrarian, discussion facilitator, project coordinator, client contact, version control expert, etc.)
Pair Programming, Agile, Source Tree, One IDE for all, Trello, GitHub, Slack.
Have each team member finish the following prompts:
- I find it annoying when other people...
- I know something about me that can annoy others is...
Sean
- Not readable code
- Don't prematurely optimize
- Can be distracting Kai
- Respect other peoples code
- Talk to much and overthink things Mikaela
- Respect other people's code
- Doesn't like rescheduling alot Sage