We are committed to being there for our teammates
- Core Working Hours: 10am-3pm
- When asked for help, immediately acknowledge the request and schedule time to assist
- We will work in our collaboration space when not in meetings or in need of “Focus Time”
- We will have the courage to step out of our comfort zone to help with each others duties and responsibilities
- We will share our knowledge and pair work within the team to encourage growth/support
We promise to show each other respect, at all times
- Assume Positive Intent when dealing with other team members
- Speak from feelings (“I feel/felt like”) to move toward agreement and understand perspectives to avoid accusatory language
- Wait for others to finish speaking before responding
- 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
- Be on time to all meetings or provide notice and expected deliverables if you will be absent
- Be fully engaged in meetings (no work or cell phones, cameras on in all meetings)
We hold ourselves to the highest standard of work
- We understand that our work quality reflects on every member of the team (LACE)
- All LACE members are working towards familiarizing themselves with trainings, playbook, and onboarding guide (Have strong knowledge with onboarding and training guide)
- All work is peer reviewed by at least one other team member
- All coaching recommendations are in alignment with the playbook and the training
- When there is no guidance in the playbook and training discuss with team before providing recommendations.
We will be a model for vulnerability and transparency in our organization (Revisit)
- Update your work on the board before daily stand-up
- Notify a week in advance of Planned outages other than emergencies on Agile Calendar
- Communicate outages in iteration planning
- Ask for help or peer reviews when needed
- We won't fear judgment/negative response keep us from being transparent
- We welcome failure to encourage growth
We will prioritize continuous improvement above all other work
- Examine problems blamelessly
- Adapt Processes(mange Jira board, write user stories, etc.) for transparency and efficiency
- Honor retrospective commitments
- Update team contracts regularly
- 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)
We will prioritize continuous improvement above all other work
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)
Previous 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.