STATIK (be)FOR(e) Scrum
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 choice.
This is not the same thing as “Scrum-ban”.
This is “Start with what you do, or know, now” in order to help avoid over-thinking how existing work, structures and/or roles “fit” within 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 Team Chartering workshop for new or existing Scrum teams. We have used this approach to help teams Form and establish Norms for them to work toward, including how they will norm around Scrum. Participants will learn how to apply this approach to help remove some of the frustration and confusion often experienced by teams as they learn to apply Scrum consistently.
… 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. (Introduce self to your table mates)
Lecture / Concept (C2) portion –
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. company '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 company ‘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 –
Provide STATIK handout.
Exercise best preformed on a flip chart, so all table participants can effectively interact and contribute.
Ask each table to create a flip chart with the STATIK steps . (depending on size of the group, this may be a whole-table or pair/triad exercise)
The point of the exercise is to have them share examples from their teams relating to each Step. Tell them not to over-think these, just jot down the most obvious ideas based on their current or most recent team.
I will explain each Step, then have the group brainstorm, write post-its and share with the table mates.
Close/Conclusion (C4) –
Wrap-up the exercise with table “Shout-Out” – Ask each table to pick 1 insight or open question and share it with the group.
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 and share that with one of their table mates as we 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 of Scrum.
Learn how to facilitate a team workshop based on STATIK
Techniques for addressing common challenges with new Scrum teams
Learn to avoid the "Scrum VERSUS Kanban" conversation
Agile Practitioners, Managers, Team members, Scrum Masters, Coaches... anyone interested in learning a
Prerequisites for Attendees
Some basic knowledge of Scrum and Kanban is helpful but not required.