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.

• 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).

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)

• See Sprint Calendar

• Avoid meetings outside core working hours.

Tibo (Unlicensed)

25 Jun 2021

Kalvin Alexander (Unlicensed)

25 Jun 2021

Karan Dhillon (Unlicensed)

25 Jun 2021

zhiyong zhang

Jun 19, 2021