Page History

We are committed to being there for our teammates ​

1. Core Working  Working Hours: 10am-3pm4pm​
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 others 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. Be available on Slack AND Teams during working hours
8. We will commit to a team-building activity once every 2 months virtual/ in-person

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.

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 absent​ or late
   
2. When sending out OOO set invite to 'Free' then update your status on your local calendar
3. Be fully engaged in meetings (no work or cell phones, cameras on in all meetings)
4. Use the "raise hand" icon on zoom so everyone knows you would like to speak
5. Leave a note in chat when you have to step away so the group is aware
6. Leave your camera on when you step away so team knows you are unavailable 

We hold ourselves to the highest standard of work and alignment​

1. We understand that our work quality reflects on every member of the team (LACE)​All LACE members are familiar with trainings, playbook, and onboarding guide ​
2. We will identify when pair work is needed in iteration planning
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. All team members are working towards a strong knowledge of training, playbook, and onboarding guide
6. When there is no guidance in the playbook and training, discuss with the team before providing recommendations . to the CCSQ Community
7. Primary coach should OWN the engagement and consult with other coaches when needed

We will be a model for vulnerability and transparency in our organization ​

1. Update your work on the board before daily stand-up​
2. Add outages to the team calendar​
3. Notify a week in advance of Planned outages on the Agile Calendar (other than emergencies)
4. Consider outages during Communicate outages in iteration planning​
5. Ask for help or , peer reviews when needed; Let the team know if you are overloaded
6. We won't fear that judgment/negative response responses will keep us from being transparent 
7. 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. Constantly evaluate and decide which continuous improvement items are most important, and honor them​ in each iterationHonor retrospective commitments​
   
4. Update team contracts regularlyduring I&P
5. Mistakes are an opportunity for improvement​

Working Agreement(previous Work) :

We value team collaboration over working individually

We value diversity and experience over traditional ways of working

We value high quality work over quantity/speed work

1.We will hold all incoming work to the standard of DoR

2.Peer Review

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

1.Update Jira board daily(live time)

...

Notes:

1.Inform prior commitments to customer?

2.Add to backlog items that come in from customer? 

4.Use raise hand button on zoom (easier to see)

1. Be on time to team meetings.
2. End meetings on time.
3. Check teams status before calling on Teams or otherwise.
4. Cameras on in Team Meetings.
5. Team members will accept or decline meeting invitations from other team members.
Team Meetings take priority (Exception: Program Support)
6. Communicate if you cannot make a team meeting.
Provide update if you cannot make a team meeting.
7. Follow-up with team for what was missed.
8. Intent and purpose of meetings 
   1. For any meeting scheduled by any member of the team.
   2. Will be communicated in advance of the meeting.
   3. Will be expressed clearly and include only the appropriate team members. 
9. Use communications best practices for team meetings
   1. Do not multi-task in team meetings (give your full attention and respect).
   2. Don't speak over each other.
   3. Use the team channel rather than meeting chats.
   4. Respond to team members in clear affirmatives/negatives.
   5. Announce when you are adding someone to a chat or call.
   6. Be aware of audience if non-team members are present at meetings.
10. Assume positive intent.
11. Express yourself thoughtfully when interacting with other team members.
12. Provide constructive feedback thoughtfully (Carefrontations).
13. Work towards the shared purpose and vision for the LACE.
14. Team members will be prepared with user stories for backlog refinement.
15. Recognize each other for good work and help (ex. Praise in team channel, Wall of Fame post, etc.).
16. This agreement will be reviewed at the Retrospective as needed.
17. Retrospective Items will be added to team board and discussed at the weekly meetings and discuss at the beginning of Planning and retro.
18. All vacations, training events, and program PI events will be added to the team calendar.
19. Team members should have a summary in the title and Value statement and AC in the description in Jira tickets (All team members).
When all user stories are complete, demonstrated, and accepted by PdM feature should be closed by the person completing Feature.
20. Every meeting has a facilitator, timebox, and agenda. All who are contributing are prepared.
21. Use the Kanban board during the stand up. 
22. When in Training mute notifications.