TC_ECH: Scrum Master Transition Plan

Standard Assignment:

Standard Assignment:
Daily	Weekly	Bi-Weekly
Keep the delivery team focused on team goals Ensure the Sprint taskboard reflects the team’s actual work Identify impediments or opportunities to assist the team’s delivery goals ensure action and awareness based on Agile practices Celebrate team successes!	Prep Sprint Retrospective event Consider a mid-Sprint checkup to reassess the Sprint Plan Check-in with POs that PBIs are ready for refinement ( attend PO-only refinement session when possible (friday mornings)	Conduct Sprint Retrospective Facilitate Team Building Event make sure entire team understands and agrees to Sprint Goal

Planned Actions

Responsibility	Task	Team	Timing	Notes/Links

Responsibility	Task	Team	Timing
Working session with PO	Work with PO to clean up Backlog and realign with current roadmap. Ensure PBIs meet DOR Create a system for PBI verification for stories that are cross team focused	SM and PO	Weekly (coordinate with PO schedule)
Work with Devs to improve PBI task workflow	-monitor the amount of task in progress by each Dev, and reasons why PBIs are skipped by some Devs -look at potential capacity building opportunities	Devs
Weekly refinement with delivery team ( and PO where necessary)	Ensure that all Devs have an understanding of PBI linkage to EPICs/Features	Devs, SM UX PO ( if needed)	Weekly (this is a set meeting on Team calendar)
Develop Agile/Scrum Content for future Sharepoint site	Work with Manager for direction	SM Manager
Facilitate improved team dynamics To maintain Retrospective cadence during SM transition	-find ways to highlight Dev skill development -facilitate events to encourage further engagement from more junior Devs --Connect Teambuilding activity to Retrospective meeting	Devs SM	a targeted Retro event
Deepen shared ownership of Delivery Team	-work on increasing Dev engagement during refinement event. -work on shared leadership	Devs SM	a targeted Retro event
Develop the Team’s state of flow	-work with team to develop an efficient feedback process	Devs UX PO	a targeted retro? and/or Daily Stand up
Overall Retrospective	-create a special event to discuss/resolve cross-team issues impacted co-related projects	Devs POs Manager UX

Facilitation Tools

Miro - used for discussion and team input and engagement ( during Retro or other relevant Team planning sessions)

Easy Retro - used for Lean and some focused Retrospective Events

Core Working / Meetings Hours

All team meetings and ceremonies will be scheduled during core working hours 9:00 am - 3:30 pm EST. (*Exceptions will be there when meeting may be scheduled outside core hours.)

No meeting days: Thurs and Fri except planned sprint events. This means that no major team meetings will be scheduled to allow team members to dedicate more focus on work items.

Scrum Events

Date	Attendees	Agenda	Notes, decisions and action items

Date	Attendees	Agenda	Notes, decisions and action items
Mon-Fri ( 9-9:15)	Entire team	Daily Scrum
Wed Morning - Bi-weekly	Entire Team	Sprint Planning
Tues Afternoon - Bi-weekly	Entire Team and stakeholders	Sprint Review
Wed Afternoon - Bi-weekly	Entire Team	Sprint Retrospective	Entire Team involved in Sprint
Tues Afternoon - Bi-weekly	Entire Team	Backlog refinement	Alternate week from the Sprint Review. Team adjust as needed.