Senior Scrum Master
CurrentAs their first full-time Scrum Master I helped the organisation, and teams, start to realise the benefit of following Scrum in it's entirety. I formulated several initiatives after speaking with everyone at the company and followed through with the support of the leadership team. These included:Improving work visibility by making sure everything each team worked on was in sprint;Making sure separate wiki's scattered around were visible to all developers;Making some official "professional development time" available to developers;Slowing down some meetings so the team had time to properly understand and discuss what they are being asked to do in the following sprint;There was some confusion around when each team's sprint started, so making this clearly visible to everyone;Making team's aware of their own velocity and how this is calculated;Getting the whole team involved in all refinement/sizing sessions. Discouraging any sessions about work that didn't involve the entire team;Following up on actions from retrospectives.. were they achieved or deemed no longer important?;Push back on external pressures to allow the team's to produce great quality product increments;Remove "noise" from Product backlogs so that the entire team understands what's in it as well as their relative priorities;Make the teams feel comfortable in their retro's. Its essential this is a safe place for them to discuss their problems, so removed all management from these meetings;Coaching the teams on how to get more value from their meetings;Refocusing Lead Developers on what they are really good at.. developing;Getting everyone engaged in Epics, by having Epic Introduction sessions;Allowing the Product owners to plan longer term by getting teams to early size large pieces or work and teaching the product owners how to run these sessions themselves;Stabilise the teams by discouraging shuffling team membership without reason;Show leadership the value of quarterly planning.