Page tree

Versions Compared

Key

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

...

  1. Core Working Hours: 10am-3pm
  2. When asked for help, immediately acknowledge the request and schedule time to assist
  3. We will work in our collaboration space when not in meetings or in need of “Focus Time”
  4. We will have the courage to step out of our comfort zone to help with each other's duties and responsibilities
  5. We will share our knowledge and pair work within the team to encourage growth/support
  6. We will keep the cameras on and inform the team if you must step away/ turn camera off
  7. We will commit to a team-building activity once every 2 months virtual/ in-person

...

We value the time of all team members

  1. Be on time to for all meetings or provide notice and expected deliverables if you will be absentor late
  2. Be fully engaged in meetings (no work or cell phones, cameras on in all meetings)
  3. Use the "raise hand" icon on zoom so everyone knows you would like to speak
  4. Leave a note in chat when you have to step away so the group is aware

...

  1. We understand that our work quality reflects on every member of the team
  2. All team members are working towards a strong knowledge of trainingstraining, playbook, and onboarding guide
  3. We will identify when pair work is needed in iteration planning
  4. All work is peer-reviewed by at least one other team member 
  5. All coaching recommendations are in alignment with the playbook and the training
  6. When there is no guidance in the playbook and training, discuss with the team before providing recommendations to the CCSQ Community

...

  1. Update your work on the board before daily stand-up
  2. Notify a week in advance of Planned outages other than emergencies on the Agile Calendar (other than emergencies)
  3. Consider outages during iteration planning
  4. Ask for help or peer reviews when needed
  5. We won't fear that judgment/negative responses will keep us from being transparent 
  6. We welcome failure to encourage growth

...

  1. Examine problems blamelessly
  2. Adapt Processes (manage Jira board, write user stories, etc.) for transparency and efficiency
  3. Constantly evaluate and decide which continuous improvement items are most important, and honor them​ in each iterationHonor retrospective commitments
  4. Update team contracts regularly
  5. Mistakes are an opportunity for improvement​

...