Working Agreement :
- Be on time to team meetings.
- End meetings on time.
- Check teams status before calling on Teams or otherwise.
- Cameras on in Team Meetings.
- Team members will accept or decline meeting invitations from other team members.
- Team Meetings take priority (Exception: Program Support)
- Communicate if you cannot make a team meeting.
- Provide update if you cannot make a team meeting.
- Follow-up with team for what was missed.
- Intent and purpose of meetings
- For any meeting scheduled by any member of the team.
- Will be communicated in advance of the meeting.
- Will be expressed clearly and include only the appropriate team members.
- Use communications best practices for team meetings
- Do not multi-task in team meetings (give your full attention and respect).
- Don't speak over each other.
- Use the team channel rather than meeting chats.
- Respond to team members in clear affirmatives/negatives.
- Announce when you are adding someone to a chat or call.
- Be aware of audience if non-team members are present at meetings.
- Assume positive intent.
- Express yourself thoughtfully when interacting with other team members.
- Provide constructive feedback thoughtfully (Carefrontations).
- Work towards the shared purpose and vision for the LACE.
- Team members will be prepared with user stories for backlog refinement.
- Recognize each other for good work and help (ex. Praise in team channel, Wall of Fame post, etc.).
- This agreement will be reviewed at the Retrospective as needed.
- Retrospective Items will be added to team board and discussed at the weekly meetings and discuss at the beginning of Planning and retro.
- All vacations, training events, and program PI events will be added to the team calendar.
- 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.
- Every meeting has a facilitator, timebox, and agenda. All who are contributing are prepared.
- Use the Kanban board during the stand up.
- When in Training mute notifications.