STATIK (be)FOR(e) SCRUM: Start your Scrum Teams off with Kanban - It's not just a "blue pill or red pill" choice
STATIK (Systems Thinking Approach To Introducing Kanban) can be a great way to help Scrum teams get up and running quickly. “Heresy!” you say.
But it doesn’t have to be just one or the other, a blue pill or red pill decision.
This is not the same thing as “Scrum-ban”.
This is “Start with what you do now” in order to help avoid over-thinking how existing work, structures and/or roles “fit” into Scrum.
Specifically, applying this approach designed for Kanban can dramatically accelerate the forming and improvements of a Scrum team.
This session will provide an understanding of STATIK and how to apply it effectively as part of a new Team Chartering workshop for a new Scrum team. We have used this approach to help teams Form and establish Norms for them to work toward, including how they will norm around Scrum.
… and tomorrow "you will wake up in your bed and believe whatever you want to believe."
Outline/Structure of the Workshop
Quick Introduction of self and topic
Connection (C1) –
Ask audience to introduce themselves to their table mates, then pair up and share an experience or a challenge relating to a new Scrum team or maybe they have been on a team that has struggled with Scrum and wanted to transition to Kanban, because it's "easier".
Lecture / Concept (C2) portion –
<20-25 minutes – intertwined with Exercise>
Share some real-world examples of starting up new Scrum teams and/or how some groups/orgs struggle with changes that Scrum brings.
– i.e. Client 'X' who’s management spent several weeks thrashing over the Scrum Master and Product Owner Roles, among other things, causing anxiety and distractions with the teams, who simply wanted to get things done; Or Client ‘Y’, where there were a handful of teams that jumped into Scrum because their management mandated it, so the team never took ownership of their work or process.
Talk about resistance to change. – even though the level of change is relatively low (new roles, new ceremonies, etc.) with Scrum, it can still be overwhelming for some teams in certain environments.
Introduce STATIK model and walk through each element (high-level)
Share experiences I’ve had running multiple STATIK workshops for teams.
Talk about how to incorporate into team working agreements and norms.
Before going into Exercise, ask for a few people to share what they discussed in the opening connection exercise.
Concrete Practice (C3) Core Exercise –
<40-45 minutes – 5-7 minutes per step, plus review time>
The point of the exercise is to walk participants through the steps of STATIK and have them share examples from their teams relating to each step. Will tell them not to over-think these, just jot down the most obvious ideas based on their current or most recent team. May make judgement calls to entertain a deeper-dive on any given topic or step based on the questions and my reading of the room.
Provide STATIK handout.
Exercise best preformed on a flip chart, so all table participants can effectively interact and contribute.
Ask them to create a flipchart with the STATIK steps
I will explain each Step, then have the group brainstorm, write post-its and share with the table mates.
Give them 5-7 minutes per step
Wrap-up the exercise with table “Shout-Out” – Ask each table to pick 1 insight or open question and share it with the group. 5-7 minutes (maybe longer depending on number of tables/groups.
Close/Conclusion (C4) –
Encourage everyone to ID 1 key element of the STATIK model that they think may be missing with their Scrum team(s) that they could take back to the team and discuss and address. Have them share that with one of their table mates.
Allow for Q&A to close out the session.
Reconnecting with the fundamental concepts that connect Scrum, Agile and Lean, like continuous improvement, transparency, respect for people. etc.
Participants will learn about STATIK and how each element can be leveraged to help teams build their own understanding of their purpose and way of working, that can then help accelerate their application Scrum.
Learn how to facilitate a team workshop based on STATIK
Techniques for addressing common challenges with new Scrum teams
Team members, Scrum Masters, Project Managers, Managers
Prerequisites for Attendees
Some experience, as a team members, Scrum Master or Manager, starting a new Scrum team or transitioning a team to Scrum.
Past conference sessions include:
- Mile High Agile 2017, “Virtues of an Agile Coach”
- Agile Development Conference East 2015 "Smart Agile at Scale: ASK the Right Questions"
- Agile 2015 conference "Backlog Refinement – The Rodney Dangerfield of Scrum Ceremonies"
- Mile High Agile 2015, Denver "Backlog Refinement – The Rodney Dangerfield of Scrum Ceremonies".
- Agile 2014, Orlando "Smart Scaling"
- Scrum Gathering 2014, New Orleans "Smart Scaling"
- Mile High Agile 2014, Denver "Smart Scaling"
- VersionOne AgilePalooza, May 2013, Seattle “Focus on the Customer”
- PMI Chicagoland Professional Development Day 2013, Chicago “Focus on the Customer”
- Mile High Agile 2012, Denver "Agile for ERP/COTS"