{"id":7015,"date":"2018-02-06T09:00:18","date_gmt":"2018-02-06T14:00:18","guid":{"rendered":"http:\/\/mgrush.com\/blog\/?p=7015"},"modified":"2026-04-21T13:18:16","modified_gmt":"2026-04-21T17:18:16","slug":"scrum-facilitation","status":"publish","type":"post","link":"https:\/\/mgrush.com\/blog\/scrum-facilitation\/","title":{"rendered":"Don\u2019t Ruin Your Scrum Sprints \u2014 Facilitate Scrum Events Using These Agendas"},"content":{"rendered":"

The Agile mindset demands frequent, and continuing, interaction among its stakeholders. Perhaps more so with Scrum, than other frameworks.<\/strong> From Daily Scrum activities to Sprint Retrospective events held every one to four weeks, Scrum facilitation yields an unspeakable value for Sprints. First, an update from its creators.<\/span><\/h2>\n
\n

Scrum Guide Update, November 2020<\/strong><\/h3>\n

Definition Enhancements Including Reference to Lean Thinking<\/h4>\n
\n
\n
\n

Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.<\/span><\/p>\n

\n
\n
\n

The Scrum framework is purposefully incomplete, only defining the parts required to implement Scrum theory. Scrum is built upon the collective intelligence of the people using it. Rather than provide people with detailed instructions, the rules of Scrum guide their relationships and interactions…<\/span>Various processes, techniques, and methods can be employed within the framework.\u00a0<\/span><\/p>\n

\n
\n
\n

Scrum is founded on empiricism and lean thinking. Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Lean thinking reduces waste and focuses on the essentials.<\/span><\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

Changing “Roles” to “Accountabilities”<\/h4>\n
\n
\n
\n

The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint. Scrum defines three specific accountabilities within the Scrum Team: the Developers, the Product Owner, and the Scrum Master.<\/span><\/p>\n<\/div>\n<\/div>\n<\/div>\n

Changing “Development Team” to “Developers”<\/h4>\n
\n
\n
\n

The specific skills needed by the Developers are often broad and will vary with the domain of work.<\/span><\/p>\n<\/div>\n<\/div>\n<\/div>\n

Changing “self-organizing” to “self-managing”<\/h4>\n
\n
\n
\n
\n
\n
\n

Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value for each Sprint. They are also self-managing, meaning they internally decide who does what, when, and how.<\/span><\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

Additionally<\/span><\/h4>\n

WHY was added to Sprint Planning, the three questions have been removed from the Daily Scrum (and replaced with an “actionable plan”), and they changed the term “shippable” to “useable. Artifacts now stress commitments and the phrase “product goal” now equates to the product backlog.<\/span><\/p><\/blockquote>\n

Scrum Facilitation Framework<\/span><\/span><\/strong><\/span><\/h3>\n

Unlike waterfall mindsets, Scrum Development Teams stick together for a while. Theoretically, if forever, they may be called tribes who never disband. As teams transition from product to product, each containing multiple Sprints, new stakeholders may appear. While the Scrum Product Owner\u00ae (SPO) remains largely responsible for the relationship between the stakeholders and the Scrum Development Team, the SPO also encourages direct communications, rather than isolating or protecting either group. <\/span><\/p>\n

Interviewing and asking questions drive the ordering of product features. Therefore, the SPO remains vigilant about developing optimal questions, sequencing them, and listening to responses. Some of the product features contained within an Ordered Product Backlog[1]<\/span> derive from interviews, rather than formal Scrum facilitation events, meetings, or ceremonies.<\/span><\/p>\n

When You Facilitate Scrum Events — Here Are The <\/em><\/strong><\/span>Core Scrum Facilitation Skills <\/em><\/strong><\/span><\/h3>\n

Facilitative skills fortify the Scrum Master\u00ae and SPO including:<\/span><\/p>\n