Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

...

Green = Most voted for

Orange = Second most voted for

No Colour = less votes, however they can potentially still be included if we wish

...

Core hours – times during the day that all Team members agree to be present and available for collaboration

...

Daily Standup – the time that it happens and what to do if you realize that you can’t make it that day

...

Cell phones – if or when it is appropriate to use them during Team events

...

Headphones – when it is fine to use headphones, versus when Team members will not use them so they’re available to communicate and collaborate with others

...

Product Owner – availability and contact information

...

Definition of ‘Done’

...

How the Team limits Work In Progress (i.e. the Kanban Concept)

...

How the Team ensures everyone has an equal voice and feels respected

...

If you miss a meeting or event then you agree to support decisions made in your absence.

...

If you can’t attend a Team event you will let the Team know in advance.

...

During each Sprint, at least one Team Member will work on growing a skill outside of their core strengths.

...

In the case of software development, every Sprint the Team will make an effort to improve some part of their code base.

...

Don’t be afraid to ask for help

...

Product Owner is available during core hours

...

Be on time for meetings

...

Tell the truth

...

Communicate individual schedule

...

ALL changes to the Sprint / Backlog must be approved by the Product Owner

...

Use the Impediment Backlog (or swimlane) for blocked issues

...

Define and adhere to ‘DONE’ criteria for stories

...

Define and adhere to Version Control rules

...

Adhere to code documentation standards

...

Update Backlog before Standup daily

...

Respect your team member’s time

...

Scrum Value

Working Agreement

Commitment

People personally commit to achieving the goals of the Scrum Team

  • We will be accountable as a team. Members work together to complete team goals and objectives; and do an equitable number of PBI’s / tasks.

  • We will Finish in progress PBIs rather than starting a new PBI. STOP STARTING; START FINISHING;

  • We will work collaboratively when possible and use a consensus approach when making team decisions.

Courage

Scrum Team members have courage to do the right thing and work on tough problems

  • We will solve impediments as a team that can be solved by the team. Otherwise we will give to SM to address.

Focus

Everyone focuses on the work of the Sprint and the goals of the Scrum Team

  • Have an agenda for meetings and keep each other accountable. e.g.: daily = collaboration; planning = disciplined intake of work; demo = show value delivered; retro = reflect and adapt.

  • We will update our tasks on the board each day before Daily Scrum (Daily Stand-up).

  • Before signing off each day, we will write a status update in our In-Progress tasks.

Respect

Scrum Team members respect each other to be capable, independent people

  • All team members will treat each other with respect at all times.

  • Everyone has equal voice and valuable contribution.

  • We will recognize and celebrate all individual and team accomplishments.

  • Since we are participating remotely, put yourself on Mute when not talking.

  • Avoid unnecessary meetings if issue can be discussed over MS Teams.

  • Meetings: Be on time, end on time.

  • Meetings: 5 minute grace at start of meeting and end 5 minutes early.

  • Encourage “2 ft rule”: if a team member is not directly benefiting or contributing to the discussion, they can drop off

  • Team members are encouraged to turn on camera for key meetings for better collaboration.

Openness

The Scrum Team and its stakeholders agree to be open about all the work and the challenges with performing the work

  • Encourage participation in a way that allows everyone to contribute in their own way.

  • We will give feedback. Receive feedback. Act on feedback.

  • When applicable, we will communicate openly in PBI/Bug discussions and in Teams Channels, as opposed to private chats.

  • Use the PBI/Bug discussion to notify the PO when there is work that is ready for feedback.

  • Ensure all work is known to the PO and entered into a PBI for visibility, tracking/understanding of work in progress (WIP).

Other

Working Agreement

 

 

 

Team Collaboration and Empowerment

  • Knowledge sharing within team.

    • Training sharing sessions

    • Confluence

    • Describe solutions within PBIs/Bugs/Tasks.

  • If there is an issue, any team member shall be able to help and support.

  • If member is not available, other team member should be able to pick-up his/her work from the board.

  • Distribute work so everyone is challenged equally - take on varied and more complex tasks (not always the same / similar ones).

  • Encouraged to become T-shaped team vs I-shaped team.

Downtime (No meeting day)

 

Signed by:

Additional Information and direction that applies
Values and Ethics (for casuals, students, employees)
• Performance Management Agreement (for casuals, students, employees)
• Contract (for contractors)
• The expectation is that this will be part of our team culture and we will all actively work towards making this a success.
• If you find that one of us is working against this agreement, is it our responsibility to flag to the rest of the team soonest so we can address.