2015-07-15 : Sprint 6 retrospective

Warm-up: Happiness histogram

We used the Happiness histogram as a warm-up exercise to evaluate, what do the team members think about how successfully and efficiently our team is collaborating.

![](https://hackpad-attachments.s3.amazonaws.com/apinf.hackpad.com_zzZd7M0Revq_p.363414_1436965298132_happiness histogram2_version_small.jpg)

Coming up with working agreements

The warm-up exercise prepared us for the main theme of the meeting: coming up with working agreements. Working agreements are a set of rules or processes the team identifies and formulates together and agrees to follow to become more efficient as a team.

Firstly, we had individual brainstorming to gather insights on issues (both positive ad negative) related to past/current team cooperation. The insights were gathered on sticky notes. Each team member presented their post-it notes, which were then grouped to 6 groups. We started working on the most popular groups, used dot voting to identify the most important issues. Based on the findings, we formulated 5 working agreements.

Our set of working agreements

Emphasize teamwork by daily pair programming and task splitting.

Participate in sprint pre-planning at least once a month.

Keep meetings brief and relevant.

Communicate task progress on daily basis by updating time estimates and linking PR's and commits.

Always review others' work thoroughly.

List of sticky notes collected in the exercise

  • Collaboration
    • Pair programming
    • Working in pairs sharing tasks
    • Pre-planning needs more team involvement
    • standups
    • Laughs and jokes during the day > we have a good spritit
    • Handling conflicts
    • Long standups

    • Peer review
    • reviews

    • commits
    • updating task status on Waffle
    • Keeping tasks updated regularly
    • Commenting issues/progress in tasks (Waffle)

    • Working space
    • Tight working space. Do we need to be in the same room?

    • Not having couch in the office
    • focus and interruption

    • Preparation and study
    • Familiarizing yourselves w tasks before sprint planning

    • Confidence in coding and implementation
    • Meteor + JS

    • Timeliness
    • Being on time

    • Arriving at meetings in time / prepared

    • QA
    • code +=testing