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 team if you must step away/ turn camera off


We promise to show each other respect, at all times

  1. Assume Positive Intent when dealing with other team members
  2. Speak from feelings (“I feel/felt like”) to move toward agreement and understand perspectives to avoid accusatory language
  3. Wait for others to finish speaking before responding
  4. We take time to recognize/celebrate accomplishments as a team. (Potentially Move this item into another column) 


We value the time of all team members

...

  1. We understand that our work quality reflects on every member of the team (LACE).
  2. All LACE team members are working towards familiarizing themselves with trainings, playbook, and onboarding guide (Have strong knowledge with onboarding and training guide) 
  3. All work is peer reviewed by at least one other team member 
  4. All coaching recommendations are in alignment with the playbook and the training
  5. When there is no guidance in the playbook and training discuss with team before providing recommendations to the CCSQ Community


We will be a model for vulnerability and transparency in our organization (Revisit)

  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 Calendar
  3. Communicate Consider outages in during iteration planning
  4. Ask for help or peer reviews when needed
  5. We won't fear that judgment/negative response responses will keep us from being transparent 
  6. We welcome failure to encourage growth

...

  1. Examine problems blamelessly
  2. Adapt Processes(mange manage Jira board, write user stories, etc.) for transparency and efficiency
  3. Honor retrospective commitments
  4. Update team contracts regularly
  5. Mistakes are an opportunity for improvement​

...