Scrum Master Skills: Visualizing the Tuckman Model
“A picture is worth a thousand words.” Probably, we have all heard that piece of wisdom before. In my experience, having some — even rudimentary — sketching or drawing capabilities is an essential Scrum Master skill. Visualizing a tricky issue while explaining the background to a stakeholder, someone from the management or a teammate helps to pave the way to have a meaningful discussion.
Let me introduce you to an example sketch based on the Tuckman model of group dynamics I use in my Professional Scrum Master training classes to make the effort and cost of creating a Scrum Team easier understandable.
🗞 Shall I notify you about articles like this one? Awesome! You can sign up here for the ‘Food for Agile Thought’ newsletter and join 31,000-plus other subscribers.
🎓 Join Stefan in one of his upcoming Professional Scrum training classes, for example, the guaranteed Professional Scrum Master class (EN) from July 13-16, 2021.
📅 Join us on Agust 10, 2021: Hands-on Agile #33: Adapt How You Lead for Agile Success—Johanna Rothman.
Scrum Master Skills: Visualizing the Tuckman Model
In 1965, Bruce Tuckman introduced a model describing team building dynamics. While all models are wrong, some are useful, and Tuckman’s model certainly falls into the latter category. The original model comprises four stages forming, storming, norming, and performing that a group of individuals probably goes through on their path to becoming a Scrum Team pursuing a common purpose.
The purpose of the following sketching exercise is to point at the likely costs of changing the composition of the Scrum Team rapidly or regularly, probably initiated by the management or driven by a lack of team success, resulting in low team morale.
Sketching the Tuckman Model
Forming
Let us assume for the visualization that the future Scrum team self-selected at t=0. The vertical axis represents all team members’ combined productivity or effectiveness, and the horizontal axis covers time. The sum of all contributions of those individuals to an imaginary outcome of the group at the beginning is set to 0.
Storming/Norming: Investing in Scrum Team Building
According to Tuckman, we now enter the storming/norming phases, and we will first see a drop in contributions of all individuals as they are preoccupied with figuring out their new internal team structure. That is followed by an increase in effectiveness as individuals merge into a team during the norming phase. Nevertheless, the two phases represent an investment by the organization, represented by the red area below the time axis. (Loss of effectiveness over time.)
Performing: Reaping the Rewards of Team Building
Once we get to the performing phase, the Scrum team will now be more effective than the previous group of distinct individuals. The resulting return on the (team building) investment is represented by the green areas. Depending on how well the team building went, die “amortization period” will be different, depending on usual factors like organizational culture, industry, individuals involved, level of support from the organization, etc.
In the example above at t=tx, scenario S1 hasn’t yet delivered a return on the (team building) investment. Scenario S2 (comprised of the light green and the middle green area) is probably breaking even. (At least I try to show that while sketching.) However, scenario S3 (comprised of the light green area, the middle green area, and the dark green area) has a positive ROI.
The Scrum Master Skill of Opening Discussions
Now, suppose you add the resulting dynamics of changing teams by adding or removing team members frequently to the narrative. In that case, even the most hardened number-driven managers understand that this management reflex requires more thought: Reinitiating the Tuckman cycle regularly is not a sound business decision.
Also, the Tuckman Model sketch helps to explain why dynamic re-teaming works when the participants know each other well: the red area will be significantly smaller than the resulting green area. Consequently, the team building will be a (very) short process that probably even fits into a Sprint of one or two weeks.
Conclusion
Sketching this “Scrum team building by Tuckman” graph takes five minutes and is, in my experience, an excellent opener for meaningful discussion. You can have this conversation anywhere: in a café using a napkin, on a whiteboard, or virtually. (In my training classes, I use an iPad and an app called Paper to make these sketches.) Just give it a try!
How are you communicating the challenges of Scrum team building to stakeholders and the management? Please share them with us in the comments.
✋ Do Not Miss Out and Hone your Scrum Master Skills: Join the 10,000-plus Strong ‘Hands-on Agile’ Slack Team
I invite you to join the “Hands-on Agile” Slack team and enjoy the benefits of a fast-growing, vibrant community of agile practitioners from around the world.
If you like to join now all you have to do now is provide your credentials via this Google form, and I will sign you up. By the way, it’s free.
📖 Visualizing the Tuckman Model for Scrum Teams — Related Posts
Agile Audit: How Is Your Agile Transition Progressing?
Three Wide-Spread Stakeholder Failures in 6:05 Minutes—Making Your Scrum Work #8
Download the Scrum Anti-Patterns Guide for free.
