Team Phoenix Working Agreement

Be Respectful:

1. Always be respectful and courteous.

2. Be mindful, that we are not ALL going to have good days.

3. Show Respect to your peers when working in pairs or collaborating.

4. Show-up to meetings on-time, with cameras “on”.

5. Be “present” at the meeting. We are only human. It has been proven that people are actually incapable of multi-tasking. Afford all meeting attendees with your undivided attention.

Be Available:

1. All team members will be available during the core working hours from 10 am - 3 pm.

Eat Lunch:

1. No meetings should ever be scheduled for the lunch hour. You are free to decline any such invitations from anyone!

Leave and Milestone Tracking:

1. Give advance notice (when possible) of leave. This is especially important before Sprint Planning so that we can properly do “capacity planning”.

2. Place any absences (including training and vacations) into the Team Calendar; Calendar - Boards (azure.com)

3. Set your “Out of Office” notification within Outlook.

4. Put key dates and milestones on team calendar: Calendar - Boards (azure.com)

Daily stand-up will be at 10:00 every morning. If you are unable to make it, notify the team in advance through the MS teams chat (with your updates for the day: see Number 6 below).

Wednesday is “Heads-down Hump-day”. Team members are enabled to focus with minimal formal distractions (meetings). Place your updates in the Teams chat (DMP+SFOC Team) with the format of:

1. Yesterday: <I did this>;

2. Today: <I will do that>;

3. Blocked: <I am experiencing a blocker on this thing and require some assistance>;

Ask For Help:

1. Ask for help when you need it… and offer help if you see someone struggling.

2. Raise your hand if you have nothing to do, or if you are blocked.

3. All important information should be documented in Confluence.

   1. e.g. reoccurring bug fixes, environment setup information,…

4. Once a week (on Friday at the end of Scrum), we will have a team activity (e.g. play a game, etc),

5. At the end of each Sprint, we will meet in-person for Team retrospective and Sprint planning.

Nightly Code Pushes:

1. Push your topic branch nightly. Stuff happens, people need to be absent. Making your work available for others to continue working-on in your absence, helps everyone!

Sprint Composition

1. We will aim to compose each Sprint of 70% Business related work items and 30% Technical Debt items.

2. The Technical Advisor will consult with the Developers each Sprint to solicit priority Technical Debt items for inclusion in upcoming Sprints as well as defining those items and tagging them as “Defined”.

3. We will aim to dedicate one Sprint each quarter to Technical Debt only if needed.