Product Owner: Lilly Marletta.
Scrum Master: Tony Cocchiaro
Within your group, agree on a group contract that will govern your collaboration. The contract should spell out the behaviors you expect of all group members, as well as procedures for resolving impasses in the group.
Specific questions to think about include the following:
- What is our level of ambition for this project?
- The goal of the project is to implement a functional, easy-to-use webpage from both the professor and student end. We want to accomplish as much as we can during the remainder of the term. We understand that we have time constraints and will need to adapt to those.
- How will we communicate with each other?
- We will communicate with each other after classes and through texts.
- How often and where will we meet?
- We will meet when needed. Most likely once a week, for every milestone. We will meet in ISEC 070.
- How will we make sure that our meetings are productive?
- We will make sure our meetings are productive by setting specific goals to accomplish during our meeting. We will assign tasks for each team member to complete outside of our meetings.
- What behaviors do we expect from team members to ensure that the team is productive and reaches its goals and that every member can contribute to their fullest potential?
- We expect each team member to complete the tasks assigned to them. Communication is highly important. Each team member should communicate their progress on their tasks and indicate if they are needing help.
- What will we do if some team member violates any agreements in this contract?
- If a team member violates the agreement, we will communicate this with Kristina. Each team member should signal their agreement with this contract by adding their name at the bottom.
Abby Michalek, Lilly Marletta, Advitya Singh, Theo Scola, Tony Cocchiaro
- What went well?
- We got our work done on time. Everybody agrees. Our presentation of our users stories went well. We worked together as a team to implement our feedback.
- What didn’t go well?
- N/A
- What have I learned?
- It's nice to follow up about assignments in our team group chat. We have found to helpful to remind each other of our assignments.
- What still puzzles me?
- How will we split up the work when it comes time to implement coding?
- What do we commit to in the next sprint? What will you continue doing? What will you start doing?
- We will continue being on time to our group meeting and planning a good meeting time that works for everyone. We will meet more frequently when the assignments get to a larger scale. We will commit to coming to our meetings prepared, with the assignments read through beforehand.
- What went well?
- We met on time at the agreed upon date for our meeting. We all worked together to split up tasks and keep each other updated on our progress.
- What didn’t go well?
- Could have planned meeting time earlier.
- What have I learned?
- We should try to meet earlier to not be under a time crunch with our other commitments.
- What still puzzles me?
- The time frame of the project completion is worrying.
- What do we commit to in the next sprint? What will you continue doing? What will you start doing?
- We will commit to meeting earlier so we have more time to complete the milestone. We will continue to collaborate well as a group during meetings.