<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ken Roberts on Medium]]></title>
        <description><![CDATA[Stories by Ken Roberts on Medium]]></description>
        <link>https://medium.com/@k3n.r0berts?source=rss-9407653edf52------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*2UV9ARjIVUyUGYEr8UhIBA.jpeg</url>
            <title>Stories by Ken Roberts on Medium</title>
            <link>https://medium.com/@k3n.r0berts?source=rss-9407653edf52------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 09:12:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@k3n.r0berts/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Discovering Value]]></title>
            <link>https://medium.com/serious-scrum/discovering-value-7ca281332500?source=rss-9407653edf52------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ca281332500</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[serious-scrum]]></category>
            <category><![CDATA[value-cycles]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Ken Roberts]]></dc:creator>
            <pubDate>Mon, 02 Nov 2020 08:02:30 GMT</pubDate>
            <atom:updated>2020-11-02T08:02:30.077Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*v7-xrdHfHXj4LdqMJiXThg.png" /></figure><h4>How Project-thinking can limit value delivery</h4><p>When working with a Scrum Team you will be aware that there is an emphasis on delivering value. This idea is a differentiator for Agile delivery. We deliver valuable outcomes. We deliver increments of valuable software. We deliver the most valuable thing first.</p><p>In my experience, conversations about value are harder for people in Project-orientated organisations. Product Owners working on <em>Projects </em>may end up prioritising a Project business case. That’s a different thing to ‘maximising the value of the product’.</p><blockquote>Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. — <a href="https://agilemanifesto.org/principles.html">The Principles Behind the Agile Manifesto</a></blockquote><p>Practitioners of Scrum will be aware that Scrum defines itself as:</p><blockquote>Scrum (n): A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. — <a href="https://www.scrum.org/resources/scrum-guide">The Scrum Guide 2017</a></blockquote><p>The Scrum Guide is clear that:</p><blockquote>The Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team. How this is done may vary widely across organizations, Scrum Teams, and individuals. — <a href="https://www.scrum.org/resources/scrum-guide">The Scrum Guide 2017</a></blockquote><p>Like Marc Loeffler, speaker, author and Agile coach says: ‘<em>Scrum is not magic</em>’. It will help make a software delivery process transparent but then it’s up to us to fix the problems.</p><p>I’d like to share a definition of value that helps us understand how Project-thinking can inhibit value discovery. This may help us expand how we consider value.</p><h3>A Definition of Value</h3><p>I like the <a href="https://iism.org/post/glossary-value-76">iiSM definition of value</a>:</p><p>‘<em>Value exists in four states: potential (needs deficits), discovered (new recipes, solutions, or other creative works), replicated (reproduced products, goods, shows, or services), and liquid (cash or cash equivalents). Examples of “things of value” by the value state include:</em></p><ol><li><em>Potential Value — unmet needs or desires, need deficits, unmet demand, or outstanding orders</em></li><li><a href="https://iism.org/post/glossary-discovered-value-73"><em>Discovered Value</em></a><em> — recipes, manuscripts, drawings, patents, formulas, code or other descriptions of a solution or creative work that is discovered to reliably meet a need</em></li><li><a href="https://iism.org/post/glossary-replicated-value-77"><em>Replicated Value</em></a><em> — finished goods, orders, plates of food, delivered products or other solutions, productions, or services that are reproduced through a known means</em></li><li><em>Liquid Value — cash or cash equivalents such as stocks, bonds, or checks, or other easily exchangeable things of worth that have a stable value</em></li></ol><p><em>Value in any of these four states can be recognized as being valuable due to its potential to fulfil an actual unmet need. In the presence of unmet need, outstanding orders are valuable, new recipes that meet a need are valuable, created goods using a known recipe are valuable, and cash or cash equivalents for the sales of replicated goods or services are valuable.</em>’ — <a href="https://iism.org/home">iiSM</a></p><p>I like this definition because it is accessible to people immediately. It does not need translation of technical jargon and is not limited to software. At the same time, it is not a simple dictionary definition and is helpful for considering software development.</p><h4>The Value Fulfilment Cycle</h4><p>The value fulfilment cycle can be thought of as the process by which <strong>potential </strong>value is <strong>discovered</strong>, <strong>replicated </strong>and then results in <strong>revenue</strong>.</p><p>In order for an organisation to realise or fulfil value, the parts of the <a href="https://iism.org/post/glossary-value-fulfillment-cycle-68">value fulfilment cycle</a> must work together.</p><p>In discussing value through software delivery with Scrum I’d introduce this as:</p><ol><li>Financial management — initial investment <em>and </em>return on investment.</li><li>Value discovery — understanding user needs and creatively producing increments of met needs.</li><li>Value replication — delivery and scaling of the working increment. This may be by delivery of smaller value increments which each satisfy customer needs.</li></ol><p>Financial management (liquidation management) is well understood in modern organisations. There will often be a separate Finance Department dedicated to this.</p><p>Value discovery is the process of identifying an unmet need (potential value) and then converting it into replicated value. This requires new learning and is also likely to involve failure (and more learning!). A learning environment that fosters creativity and diversity of thought is required for organisations to achieve this.</p><p>Value replication (business management) is also well established in most business contexts. Replicated value involves known solutions, known equipment and known work practices. Typically the people doing the work are familiar with it and have been trained in the work practices. This type of work lends itself well to long-term planning: Gannt charts and predictive plans.</p><p>For a deeper look at the origins of these elements of the value fulfilment cycle I’d recommend Gene Bond’s great article <a href="https://iism.org/article/why-are-ceos-failing-software-engineers-56">Why Are CEOs Failing Software Engineers?</a></p><p>Value discovery may be new territory for many traditional organisations. If we want to be able to maximise the value of our work we need to understand what it takes.</p><h3>Agile Project</h3><p>Projects work well for certain types of activities but can have limitations when applied to software development. In my opinion a typical Project is unlikely to consider value discovery.</p><p>In a Project-centric organisation business management is used to determine up-front which Projects align with the strategic aims and what each Project needs to do (for brevity lets include regulatory change and exposure/risk reduction with strategy). Projects are prioritised and funded based on strategic alignment (with funding based on high level estimates that may <em>not </em>have been provided by the team that will do the work). Projects are then allocated to temporary Project teams. These teams may then produce a more detailed business case to define the Project budget and deliverables. When completed they will hand-over to a separate support function.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*GXZyxivZLCiID_1KS63ABA.png" /><figcaption>Image used under licence from <a href="https://www.shutterstock.com/home">Shutterstock</a></figcaption></figure><p>Where does value discovery sit in a context where feature scope and total cost are defined up-front? If Project teams are held to up-front definitions of scope then there is no flexibility for discovering higher value outcomes or for adapting to feedback.</p><p>There are viable work-arounds for dealing with the problem of being unable to discover value during a Project.</p><p>Project-orientated organisations may fund a distinct ‘discovery’ phase that has the sole purpose of discovering or establishing a need. Once established further funding may then be released to deliver against that need.</p><p>Feedback may be sought per increment with funding re-evaluated at a distinct Project lifecycle stage. For example, the <a href="https://www.agilebusiness.org/page/whatisdsdm">DSDM </a>framework helps with this. Feedback is sought per increment and funding is re-evaluated at the Foundations stage.</p><p>Contrast Project-workarounds with the idea of funding stable Product teams. These teams use their budget, determined by strategic importance, to discover the value that will enable them to achieve their strategic aims (e.g. more customers, market entry, etc.). They can make decisions about benefits which make sense for the Product and can deliver value for current <em>and </em>future funding cycles. Acknowledging value discovery and seeking to benefit from it encourages feedback loops. These teams have the flexibility to address value discovered via these feedback channels. There is no hand-over or end point — these teams will make decisions that consider the Product lifecycle.</p><p>Whether you are in a context that is at one of these extremes, or somewhere in between, factoring in value discovery is essential to maximise value.</p><h3>Opportunities to Discover Value</h3><p>Articles about how to deliver value will often have a list of activities that one should consider to deliver value. I’ve created a diagram which shows opportunities for value discovery instead.</p><figure><img alt="Diagram showing routes for value discovery in software delivery." src="https://cdn-images-1.medium.com/max/1024/1*MgtB0_QR136GCTSBqAhpsw.png" /></figure><p>The yellow arrows show value discovery via feedback routes. This feedback can then influence the work.</p><p>Activities like technical debt resolution or technical automation, which many Project-orientated teams have to fight to prioritise, actually assist <em>value realisation</em> across the cycle. These activities will reduce time to develop software and will also make replication of value easier (by speeding up this process and/or improving operability). But if we stick to a Project plan based on feature delivery how do we discover and then realise this value?</p><p>Feature delivery will result in <em>something </em>that can be replicated but if user needs are not met and user outcomes not supported then a delivery is unlikely to result in ROI or actually achieve business goals.</p><p>By understanding value fulfilment as a cycle we can look for opportunities to put in place feedback loops and use the feedback to enhance the value we deliver.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*o7M4KaQel0a0Yuqltvfcbw.png" /><figcaption>Early feedback may have identified problems. (Image used under licence from <a href="https://www.shutterstock.com/home">Shutterstock</a>)</figcaption></figure><h3>Closing</h3><p>Failing to consider the value fulfilment cycle can lead to missing value discovery activities. It can also mean that feedback loops, that will enhance financial return or simplify value replication, are absent. Dogged insistence on traditional business management reduces the effectiveness, and the value, of software delivery outcomes.</p><p>By understanding value fulfilment as a cycle we can look for opportunities to put feedback loops in place. We can then use the feedback to enhance the value we deliver per increment.</p><p>As Scrum Masters we want to encourage an organisation toward empirical Product development. The benefits for inspection and adaptation that value discovery activities provide are too significant to be overlooked.</p><p>Product Owners may find themselves trying to maximise value for a Project that has a one dimensional view of value. Worse yet, they may be unable to capitalise on discovered value because it wasn’t on the Project plan.</p><p>An organisation that struggles with innovation is likely to have overlooked the importance of value discovery. Failure to consider the whole cycle of value fulfilment will limit our definition of value. This will limit the value of the work we deliver to end-users and customers.</p><h4>References</h4><p>Bond, Gene: <a href="https://iism.org/article/why-are-ceos-failing-software-engineers-56">Why Are CEOs Failing Software Engineers?</a></p><p>Loeffler, Marc: ‘Five Things Nobody Tells You About Scrum’ from ‘97 Things Every Scrum Practitioner Should Know: Collective Wisdom from the Experts’, 2020</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*N-w1ittwn9dyleIC.png" /><figcaption><a href="http://seriousscrum.com/invite">Do you want to write for Serious Scrum or seriously discuss Scrum?</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ca281332500" width="1" height="1" alt=""><hr><p><a href="https://medium.com/serious-scrum/discovering-value-7ca281332500">Discovering Value</a> was originally published in <a href="https://medium.com/serious-scrum">Serious Scrum</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Blocked or Impeded?]]></title>
            <link>https://medium.com/serious-scrum/impediments-c00642c22041?source=rss-9407653edf52------2</link>
            <guid isPermaLink="false">https://medium.com/p/c00642c22041</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[serious-scrum]]></category>
            <dc:creator><![CDATA[Ken Roberts]]></dc:creator>
            <pubDate>Mon, 13 Jul 2020 06:13:25 GMT</pubDate>
            <atom:updated>2020-10-17T16:15:25.906Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*nq-opLYr6s9iOU22TrVZnQ.png" /></figure><p>I’ve worked with Scrum Masters who describe the main part of their role as being about ‘removing blockers to the Development Team’. I’ve seen this description in job adverts and other online sources.</p><p>I was interested in why the word <em>impediment (</em>actually used in the Scrum Guide)<em> </em>would be commonly changed to <em>blocker, </em>how the words are used<em> </em>interchangeably<em>, </em>whether this mattered and what it can mean for Scrum Masters.</p><h3>Back to the Source</h3><p>The Scrum Guide lists the Scrum Master’s responsibility for impediment removal when it discusses Scrum Master services to the Development Team.</p><p>‘<em>The Scrum Master serves the Development Team in several ways, including:</em></p><ul><li><em>Coaching the Development Team in self-organization and cross-functionality;</em></li><li><em>Helping the Development Team to create high-value products;</em></li><li><strong><em>Removing impediments to the Development Team’s progress;</em></strong></li><li><em>Facilitating Scrum events as requested or needed; and,</em></li><li><em>Coaching the Development Team in organizational environments in which Scrum is not yet fully adopted and understood</em>.’ — The Scrum Guide 2017 (my emphasis added).</li></ul><p>Impediments are explicitly mentioned in the Scrum guide in only 3 places. The quotation above and then twice when the Daily Scrum is described. They are mentioned in the 3 questions provided as an example Daily Scrum format that might be used by a Development Team:</p><blockquote>The structure of the meeting is set by the Development Team and can be conducted in different ways if it focuses on progress toward the Sprint Goal. Some Development Teams will use questions, some will be more discussion based. Here is an example of what might be used:</blockquote><blockquote>• What did I do yesterday that helped the Development Team meet the Sprint Goal?</blockquote><blockquote>• What will I do today to help the Development Team meet the Sprint Goal?</blockquote><blockquote>• Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?</blockquote><blockquote>— The Scrum Guide 2017</blockquote><p>And also here:</p><blockquote>Daily Scrums improve communications, eliminate other meetings, identify impediments to development for removal, highlight and promote quick decision-making, and improve the Development Team’s level of knowledge. — The Scrum Guide 2017</blockquote><p>Blockers are not mentioned at all in the Scrum Guide 2017.</p><h3>The Problem</h3><p>Clearly, synonyms of <em>impediment </em><strong>would </strong>include <em>barrier, obstacle, blockage</em> in modern English usage. Perhaps it seems less pretentious to use <em>blocker </em>rather than <em>impediment </em>in conversation?</p><p>I think that the first problem with the more colloquial ‘a Scrum Master removers blockers’ may be the thinking:</p><ol><li>Blockers and impediments are the same thing.</li><li>Blockers will be raised at the Daily Scrum.</li><li>The Scrum Master need only be responsible for blockers raised at the Daily Scrum.</li></ol><p>The responsibility to ‘remove impediments to the Development Team’s progress’ should cover much more than just blockers raised at the Daily Scrum.</p><p>The second problem is that with people, teams or organisations that are new to Scrum this change of language may have unforeseen consequences.</p><p>If we interpret our role as Scrum Master to be just about <em>removing blockers</em> rather than (as the Scrum Guide says) to be about <em>removing impediments</em> then we may be missing opportunities to serve the team and coach them towards self-organisation.</p><p>We use Scrum to help us work in complex environments. Changing the language of Scrum seems like something that could add to the complexity and introduce confusion rather than help teams deal with it.</p><p>I think that this is more than semantics and is about how we interpret the Scrum Master role and how it is viewed by others.</p><h3>Differentiation</h3><blockquote>Equality without differentiation is bad equality. Differentiation without equality if bad differentiation. — Katsuki Sekida</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*jNHxRFDt0AHnkaYLgZ4iWQ.png" /><figcaption>Photo by <a href="https://unsplash.com/@markusspiske?utm_source=unsplash&amp;amp;utm_medium=referral&amp;amp;utm_content=creditCopyText">Markus Spiske</a> on <a href="https://unsplash.com/s/photos/different?utm_source=unsplash&amp;amp;utm_medium=referral&amp;amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>In ‘Scrum Shortcuts Without Cutting Corners: Agile Tactics, Tools, &amp; Tips’ IIan Goldstein makes the distinction that:</p><blockquote>Many teams use the terms <em>block</em> and <em>impediment </em>interchangeably, but I like to differentiate between the two. I do so to clearly identify an obstruction that has <em>stopped </em>progress on a particular task but hasn’t necessarily slowed down overall progress (a block) versus an obstruction that is <em>slowing down</em> the team’s sprint progress (an impediment).</blockquote><p>In ‘Scrum A Smart Travel Companion, A Pocket Guide’ Gunther Verheyen provides a glossary where he defines impediment as:</p><blockquote><strong>Impediment</strong>: any hindrance or obstacle that is blocking or slowing down the Development Team and cannot be solved through the self-organization of the Development Team itself. Raised no later than at the Daily Scrum, the Scrum Master is accountable for its removal.</blockquote><p>Combining these I’d say that the set of impediments <em>includes </em>the set of blockers but that it is helpful to differentiate because:</p><ul><li>A work-impacting blocker is more likely to be raised in the Daily Scrum.</li><li>A team may deal with individual blockers well, but repeat blockers may signify an impediment to progress that may not be raised at the Daily Scrum.</li><li>One team’s blocker (stops work on a task) may be another team’s impediment (slows down work) depending on the self-organising capability of the Development Team experiencing them.</li><li>Different organisational contexts or cultures may present <em>superficially similar </em>impediments to Scrum Teams but different approaches, appropriate to the context, may be required to address them.</li><li>‘Removing impediments to the Development Team’s progress’ does not necessarily mean that the Development Team have raised the impediment or necessarily visualise it as an impediment.</li><li>Impediments <em>should </em>be raised immediately (at the latest at the Daily Scrum) but a team may need help to visualise the impediments that are acting upon it.</li></ul><p>A Development Team <em>may </em>raise all of the impediments that impact them in the Daily Scrum but, in my experience, they are more likely to raise work impacting <em>blockers </em>to ask for help. As Scrum Masters, we cannot expect that all <em>impediments </em>will be surfaced in this way.</p><figure><img alt="4 people at a Daily Scrum meeting." src="https://cdn-images-1.medium.com/max/1024/1*PbPeI_AzLnXP16oJk1iiig.png" /><figcaption>What types of statements are more common at the Daily Scrum?</figcaption></figure><h3>Why Differentiate?</h3><p>I think that a Scrum Master should coach a team to remove blockers and help them to identify and visualise impediments. As the self-organising capability of a team improves they may self-organise to address impediments to progress (maybe outside of the Scrum Events). The Scrum Master remains responsible for this process and for removal of impediments that the team cannot address.</p><p>I think this distinction is useful for a number of reasons and can help us consider how to best help people and teams using Scrum:</p><ul><li>A new Development Team member that is used to hierarchical management styles (and escalating any problems to a ‘lead’ or manager) may initially lack the self-organisation to address a blocker. This may be by asking for help from the team or by pro-actively progressing this problem. Solving the blocker for a person rather than coaching them to address it can be less beneficial in the long run.</li><li>A Development Team of people that are pro-active individually may resolve their own blockers — but may not have the experience with self-organisation or the openness to look at the cumulative impact of blockers on the team. The wider impediment could be missed.</li><li>A team that does consider impact at the team level may limit themselves to tangible task-orientated impediments (i.e. groupings of blockers) but lack the trust or self-organisation to discuss people conflicts or training requirements openly and respectfully.</li><li>An inexperienced Scrum Master may limit themselves to picking up blocker-level impediments raised at the Daily Scrum and miss an opportunity to coach the team towards recognising and tackling impediments in a self-organising way.</li></ul><p>These are all opportunities for collaboration, coaching and progression that Scrum Masters can be alert to.</p><p>Not only is there a progression for the Development Team but also for the Scrum Master. To deal with impediments that are wider-ranging the Scrum Master can ask for help and support and will need skills and techniques to be able to do this effectively.</p><h3>Not Just the Daily Scrum</h3><p>Scrum provides us with the opportunity to inspect the performance of the last Sprint as a Scrum Team in the Sprint Retrospective.</p><p>In the interests of keeping this article focused I don’t want to get into the pros and cons of different Retrospective formats. Suffice it to say that as Scrum Masters facilitating a Retrospective we can choose a format that helps the team discuss topics that may not come up elsewhere in the Sprint.</p><p>There are well-known Retrospective formats that leverage visual metaphor to help Scrum Teams with this. Examples would include the <a href="https://www.funretrospectives.com/hot-air-balloon-bad-weather/">hot air balloon retrospective</a> and the <a href="https://retrospectivewiki.org/index.php?title=Sailboat">sailboat retrospective</a>.</p><h4>Explore</h4><p>In addition to a Retrospective format that helps identify blockers and impediments, root cause analysis of a given blocker can help us to look deeper.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*fIy1PsT1xbxL4wMBRmyE3Q.png" /><figcaption>Photo by <a href="https://unsplash.com/@outsighted?utm_source=unsplash&amp;amp;utm_medium=referral&amp;amp;utm_content=creditCopyText">Scott Walsh</a> on <a href="https://unsplash.com/s/photos/explore?utm_source=unsplash&amp;amp;utm_medium=referral&amp;amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Root cause analysis techniques such as an <a href="https://en.wikipedia.org/wiki/Ishikawa_diagram">Ishigawa Diagram</a> or a <a href="https://en.wikipedia.org/wiki/Five_whys">Five Whys</a> exercise are helpful techniques to work through with a team when discussing repeat blockers or blockers that collectively constitute an impediment.</p><p>The root cause, whilst not actively blocking the team at that moment in time, is nevertheless an impediment that we should take ownership of (or better yet, coach the team towards ownership of the problem).</p><p>In this way, the Scrum Master can help to address impediments that are impacting the Development Team’s progress and also coach the team towards being alert to the value of looking deeper.</p><p>From observation, I believe that a new Scrum Master or a Team new to Scrum are more likely to pick up on task-level blockers that impacted the previous Sprint rather than look for root cause impediments in a Retrospective.</p><p>Visualisation and quantification will be invaluable when trying to enlist support from managers or executives to tackle impediments that are likely to impact multiple teams and/or the success of Scrum in an organisation.</p><p>A Sprint Retrospective may not surface all impediment types. How the team visualise the Sprint, the extent to which work is transparent, the level of openness on the team and the format of the Retrospective itself may all impact whether impediments are raised.</p><h3>Impediments</h3><p>We use Scrum to help us with complex work and complex work will inherently have many opportunities to experience impediments.</p><p>The Scrum Master must serve the wider organisation in a number of ways including:</p><blockquote>Causing change that increases the productivity of the Scrum Team; — The Scrum Guide 2017</blockquote><p>If we look for implicit examples of impediments that a Scrum Master might need to be aware of from the <a href="https://www.scrumguides.org/scrum-guide.html#team-sm">Scrum Guide</a> then it is clear that the Scrum Master’s service to the Scrum Team and the wider organisation covers many areas that may need support. Any of these areas could impede the progress of the Development Team.</p><p>When the challenge of complex work is added to the challenges that come from working as a team, challenges that come from larger groups in scaled Scrum, or from working in large or complicated organisations we can end up with an almost endless variety of things that may impede a team.</p><h3>Conclusion</h3><p>I think that it does matter whether Scrum Masters describe their role as about being ‘blocker removal’ or ‘impediment removal’. It’s helpful to differentiate blockers and impediments because of how that helps us think about them. As Scrum Masters, our role is to remove impediments not just blockers.</p><p>Exactly how we proceed to deal with impediments that may be impacting a team will vary depending on the factors discussed above. I don’t think there are many hard and fast rules due to the different contexts that are possible but I would suggest:</p><ul><li>Empiricism asks us to be transparent, to inspect and then adapt. Improving transparency by differentiating blockers and impediments helps us inspect and work out how to adapt.</li><li>Discussing impediments as a team and collaborating on how to tackle them can mean working beyond the Scrum Team with wider communities of practice and leadership teams.</li><li>Scrum Masters do not have to solve all of the problems. <em>But </em>we can help by visualising the impediments that are slowing teams down, quantifying the impacts and being able to articulate this in a respectful, positive and constructive way.</li><li>If we stop looking for impediments at the Daily Scrum or only focus on blockers then we are limiting the ways we serve the Development Team and the wider organisation.</li><li>If we do not take a wider view of impediments then we would be missing out on a large part of our responsibility as Scrum Masters, opportunities to grow the capabilities of Scrum Teams and opportunities to develop as Scrum Masters.</li></ul><p>‘Impediment Remover’ is discussed as a Scrum Master stance in Barry Overeem’s whitepaper <a href="https://scrumorg-website-prod.s3.amazonaws.com/drupal/2017-05/The%208%20Stances%20of%20a%20Scrum%20Master%20Whitepaper%20v2_0.pdf">The 8 Stances of a Scrum Master</a>. I think that to be able to deal with all of the possible types of impediments we will need to master the 7 other stances exceptionally well.</p><h4>References</h4><p>Goldstein, Ilan: ‘Scrum Shortcuts Without Cutting Corners: Agile Tactics, Tools, &amp; Tips’</p><p>Loeffler, Marc: ‘Five Things Nobody Tells You About Scrum’, from ’97 Things Every Scrum Practitioner Should Know’ Edited by Gunther Verheyen</p><p>Overeem, Barry: ‘<a href="https://scrumorg-website-prod.s3.amazonaws.com/drupal/2017-05/The%208%20Stances%20of%20a%20Scrum%20Master%20Whitepaper%20v2_0.pdf">The 8 Stances of a Scrum Master</a>’</p><p>Verheyen, Gunther: ‘Scrum A Smart Travel Companion, A Pocket Guide 2nd Edition’</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*N-w1ittwn9dyleIC.png" /><figcaption><a href="http://seriousscrum.com/invite">Do you want to write for Serious Scrum or seriously discuss Scrum?</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c00642c22041" width="1" height="1" alt=""><hr><p><a href="https://medium.com/serious-scrum/impediments-c00642c22041">Blocked or Impeded?</a> was originally published in <a href="https://medium.com/serious-scrum">Serious Scrum</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Coaching Remote Scrum Teams]]></title>
            <link>https://medium.com/serious-scrum/coaching-remote-scrum-teams-90eedab93f5b?source=rss-9407653edf52------2</link>
            <guid isPermaLink="false">https://medium.com/p/90eedab93f5b</guid>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[serious-scrum]]></category>
            <category><![CDATA[remote-working]]></category>
            <dc:creator><![CDATA[Ken Roberts]]></dc:creator>
            <pubDate>Tue, 07 Apr 2020 08:17:06 GMT</pubDate>
            <atom:updated>2020-04-07T08:17:06.548Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*nBET_kjJgXIEpfdyP4NTAQ.png" /></figure><h4>Coaching related thoughts for remote-first Scrum Masters.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AQi4ny7sS8sGxmm8aBzTzw.jpeg" /></figure><h3>Scrum Master as Coach</h3><p>The Scrum Guide mentions coaching when it describes the Scrum Master’s service to the development team:</p><blockquote>‘The Scrum Master serves the Development Team in several ways, including:</blockquote><blockquote>⦁ Coaching the Development Team in self-organization and cross-functionality;</blockquote><blockquote>⦁ Helping the Development Team to create high-value products;</blockquote><blockquote>⦁ Removing impediments to the Development Team’s progress;</blockquote><blockquote>⦁ Facilitating Scrum events as requested or needed; and,</blockquote><blockquote>⦁ Coaching the Development Team in organizational environments in which Scrum is not yet fully adopted and understood.’ — The Scrum Guide</blockquote><p>We could be coaching individuals one-on-one or we could be coaching teams. The Scrum Guide also mentions the Scrum Master responsibility to coach and lead within the wider organisation. For this article I want to focus on the service to the team and look at practical approaches and considerations that may assist us.</p><p>No doubt many of us in the Serious Scrum community are used to working with multi-site teams and have experienced the necessity to coach remotely. In these cases any tooling and technical problems may have been solved long ago.</p><p>At the time of writing the covid-19 pandemic has impacted countries around the world and many organisations have rapidly switched to remote-first working.</p><p>Depending the specific context we find ourselves in, there may be very little change to us and our teams. But if we’ve been working with a co-located single-site team up until now there may have been significant upheaval.</p><p>This backdrop meant that I wanted to pull together some thoughts and sources so that I could share these with Scrum Masters within my own organisation. I thought it would be a small step to writing it up and sharing in case other Scrum Masters find this useful.</p><h3>Coaching</h3><p>I won’t repeat the many facets involved in how the Scrum Master acts as a coach. We have our own styles, influences and definitions. <a href="https://www.scrum.org/resources/blog/scrum-master-coach-0">Barry Overeem’s Scrum.org article</a> is a good place to refresh on this.</p><p>A personal definition that works well for me, when thinking about how I want to <em>coach </em>as a Scrum Master, was inspired by the International Coach Federation (ICF) definition <em>and </em>the Scrum Guide:</p><p><em>‘I engage with Scrum teams in a thought-provoking and creative process to inspire them to maximise their potential to self-organise, work cross-functionally and to understand and adopt Scrum.’</em></p><p>This definition is not impacted by whether a team is co-located, multi-site or remote first.</p><p>Perhaps considering your own definition of how you coach a team will help focus when it comes to how one might enable these outcomes remotely?</p><h3>Remote Coaching</h3><p>These 7 enablers from Jennifer Britton’s book Effective Virtual Conversations are great areas to consider when approaching the challenge of coaching remotely.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/909/1*gMTQOV8xjoxIycOjpYzpJw.png" /></figure><p>One may consider how an enabler may be impacted by the approach for a given coaching session. How the choices we make might impact them, what we can do to emphasise others and what we might need to be particularly aware off.</p><p>I’ve decided to group the thoughts and guidance I’ve found helpful on this topic into general areas.</p><h4>Organisation</h4><figure><img alt="A map with some highlighter pens on it, some candles and a compass." src="https://cdn-images-1.medium.com/max/1024/1*B643g8gq1B6QOBk_iQRd4A.jpeg" /><figcaption>Photo by Simon Migaj on Unsplash</figcaption></figure><p><strong>Manage time. </strong>This is a given but is further nuanced when working entirely remotely. For example, in face-to-face sessions we have nonverbal queues that we practice and are attuned to. Think of the person closing their laptop, clearly signalling that the session is ending without having to speak.</p><p>We may have become accustomed to a slight over-run or being able to easily pick up the conversation later or continue it as we walk back to our desks. There may be habits and assumptions that we’re unaware of because they work fine for face-to-face.</p><p>When working remotely we need to be more careful about running out of time and avoid trying to hastily wrap up a conversation. Otherwise we risk ending the session on the wrong note with a rushed re-cap and possibly even confusion or uncertainty about next steps.</p><p>It can also be helpful to leave some time between the end of a session and the next session in your schedule. Build in time for reflection and for any unexpected emotional element to have time to clear. Session lengths of 25 or 50 minutes may be more helpful in this respect rather than sticking with typical session lengths. This can be good practice whether we’re remote or not.</p><p><strong>Location (still) matters</strong>. Even though we may be remote working we still need to ensure a private comfortable space for participants and for ourselves. It should be free from interruption to help with the increased interpersonal challenge of remotely coaching.</p><p><strong>Focus</strong>. As Scrum practitioners we recognise the importance of this value and must continue to lead by example. Don’t try and multi-task. We’re all tempted by this when we’re on a call / video call but people can sense when our attention wanders and this will have an impact on the session.</p><p>I think these considerations can impact the consistency, communication, clarity, connection and collaboration of a remote conversation. We may in turn be impacted as coaches by the pervasive cultural attitude to timekeeping and multi-tasking.</p><p>If the work culture threatens to impose norms that reduce the value or effectiveness of coaching sessions then a great facilitation technique, detailed in Jean Tabaka’s Collaboration Explained, is to build specific organisation tools into your session. I’ve found that asking a group for permission to introduce and collaborate on some basic ground rules to be effective in the remote space. These can include <em>starting and ending on time</em> and <em>respecting the speaker with our attention </em>and can be expanded in collaboration to mitigate organisational habits that may work against the session.</p><h4>Facilitation tools</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t_QqL0HS8bv2Lqt3QmQavQ.jpeg" /></figure><p><strong>What’s the right medium?</strong> As far as possible I think that we should not dictate the medium. Options may be limited when coaching teams but for individuals there may be a strong preference. We should respect this and, as far as possible, collaboratively agree on the right medium for the situation.</p><p><strong>Have the right equipment</strong>. An external webcam or mic can make a big difference to the level of engagement participants have on a video call. Even a dedicated headset rather than mobile phone headphones will make a significant improvement to call audio quality. As coaches our presence is important.</p><p><strong>Build confidence with the tools.</strong> This means practice. If you’re introducing new tools to help with remote sessions then taking the time to learn your way around the tools ahead of a session is a good investment. There have been other articles dealing with specific tools and strategies for using them that cover:</p><p>⦁ Using polls</p><p>⦁ Virtual breakout rooms (great for peer coaching)</p><p>⦁ The importance of visualisations</p><p>⦁ Tools for collaborative annotation for team sessions</p><p>I’d recommend <a href="https://www.collaborationsuperpowers.com/tools/">Collaboration Superpowers</a> and the ThoughtWorks <a href="https://www.thoughtworks.com/remote-work-playbook?utm_campaign=remoteplaybook&amp;utm_medium=social&amp;utm_source=LinkedIn">Remote Work Playbook</a> as great resources for you to find out more about some of the available tools.</p><p>From a facilitation perspective I’m convinced that email is best used as follow-up (questions, links to reading etc.) rather than the primary means of coaching someone remotely.</p><p>I think consideration of the tools we use may show how they may enable the communication, clarity, connection, collaboration and culture of a remote conversation. Additionally the culture and the community may themselves guide us when considering the types of tool we use to facilitate these sessions.</p><h4>Interpersonal</h4><p>Coaching remotely means we’ll encounter differences if we’re used to primarily coaching face-to-face. It’s <a href="https://en.wikipedia.org/wiki/Nonverbal_communication">well documented</a> that we rely on non-verbal queues in conversation and as coaches we may have invested time and effort building an awareness of these.</p><p>Grainy or sluggish video connections will give you much less to go on and with purely audio sessions you won’t have these visuals queues at all.</p><p>The ICF provides members coaching guidance for the remote space and highlights differences to watch for. I’ve listed the considerations I find most helpful along with my thoughts about what to look and listen for. These apply to video calls but will help on purely audio calls too.</p><p><strong>Pace</strong>. Listen for and watch the energy. How fast is someone talking? What areas are they pausing on? In a team session is anyone left behind?</p><p><strong>Interactivity</strong>. How interactive is the session? If it’s a team session then how interactive is the session for the participants? Are there tools we could use to build in greater interactivity? Polls, lean coffee, annotation tools all provide opportunities to improve interactivity in our sessions.</p><p><strong>Connection and trust.</strong> We need to ensure that our verbal skills are sufficient to build connection and trust and pay special attention to the them when working remotely.</p><p>Using <a href="https://youtu.be/xJ-32O4_p14">clean language</a> to help the conversation and to encourage participation without steering the conversation.</p><p>Actively listening and practising <a href="https://en.wikipedia.org/wiki/Active_listening">active listening</a> skills <em>without </em>the richness of the non-verbal queues you may be used to. This may include summarising and paraphrasing so that participants have feedback that they have been heard and that we are paying attention.</p><p><strong>Diverse perspectives. </strong>When team coaching we need to pay special attention to the group and try to encourage participation to ensure that we capture diverse perspectives. Does someone dominate the session? What techniques can we use to build in collaboration across a group?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C8rordCuvEK799dMoDHcuA.jpeg" /><figcaption>Photo by Miguel Á. Padriñán from Pexels</figcaption></figure><p>I think that considering how interpersonal communication is impacted in remote sessions speaks directly to communication, clarity, connection and collaboration. This is an area where all 7 enablers can be considered.</p><h4>Sustainability</h4><blockquote>Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. — Principles Behind the Agile Manifesto</blockquote><p>That includes us as Scrum Masters. If we’re spending more time and energy on preparation, facilitation and moving from coaching co-located teams to remote teams this will be tiring. Serve the team but also look after yourself.</p><p>When we work on remote first teams that are that way by design it is different to working with teams that have suddenly found themselves working remotely. When fulfilling a coaching role for a team I think that sensitivity to this is important.</p><p>Supporting colleagues that are struggling with remote working is something that can be addressed by a self-organising team. It takes openness and trust but, in my experience, teams will rally around a colleague that is finding it difficult.</p><p>I think that an awareness that people who have suddenly switched to working from home are on a change curve is important. As coaches how can we help them? An awareness of models that may help us deal with change, or coach people through change, is such a beneficial area that I intend to pick this topic up in a future article. I’ve found <a href="https://www.mindtools.com/pages/article/bridges-transition-model.htm">William Bridge’s three processes of transition </a>a helpful model to keep in mind for this specific challenge perhaps because of the differentiation between <em>change </em>and <em>transition</em>. Taking time to deal with change and transition is normal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/969/0*N-w1ittwn9dyleIC.png" /><figcaption><a href="http://seriousscrum.com/invite">Do you want to write for Serious Scrum or seriously discuss Scrum?</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90eedab93f5b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/serious-scrum/coaching-remote-scrum-teams-90eedab93f5b">Coaching Remote Scrum Teams</a> was originally published in <a href="https://medium.com/serious-scrum">Serious Scrum</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Crafting Sprint Goals]]></title>
            <link>https://medium.com/serious-scrum/crafting-sprint-goals-86ed8070041b?source=rss-9407653edf52------2</link>
            <guid isPermaLink="false">https://medium.com/p/86ed8070041b</guid>
            <category><![CDATA[serious-scrum]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Ken Roberts]]></dc:creator>
            <pubDate>Sun, 23 Feb 2020 11:35:11 GMT</pubDate>
            <atom:updated>2020-02-23T13:27:03.047Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/988/1*nBET_kjJgXIEpfdyP4NTAQ.png" /></figure><p>This article emphasises the importance of the Sprint Goal in Scrum, identifies scenarios where goal setting may be difficult and offers pointers toward the crafting of Sprint Goals for teams that are finding the process difficult.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*06c8I-q52nnIYWoSpDqVAQ.png" /></figure><h3>The Goal</h3><p>As practitioners of Scrum we are familiar with the 3 pillars of empirical process control. There are many great articles and resources out there that help us to develop and nuance our understanding. Some of my favourites include Sjoerd Nijland’s excellent <a href="https://medium.com/serious-scrum/psmiii/home">Road to PSM III</a> articles on Inspection, Adaptation and Transparency.</p><p>It is while discussing Scrum theory and empiricism that the Scrum Guide first mentions goals:</p><blockquote>‘Scrum users must frequently inspect Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances.’ — The Scrum Guide</blockquote><p>The idea of the Sprint Goal is a key part of Scrum. We inspect our progress toward the goal each Sprint and need to watch out for ‘undesirable variances’.</p><p>The Scrum Guide also mentions goals when it discusses the Scrum Values, Scrum Roles and Scrum Events. The concept that we are Sprinting towards a goal is part of Scrum at a fundamental level.</p><p>For a deep dive of the Sprint Goal I’d recommend Sjoerd Nijland’s Medium article <a href="https://medium.com/serious-scrum/the-sprint-goal-c667762f8e81">The Sprint Goal</a>.</p><p>In <em>this</em> article I’d like to explore a techniques for creating goals, and some of the problems that may prevent goal formation.</p><h3>Why have a goal?</h3><p>The Scrum Guide goes on to say this about the Sprint Goal.</p><blockquote>‘The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Development Team on why it is building the Increment. It is created during the Sprint Planning meeting. The Sprint Goal gives the Development Team some flexibility regarding the functionality implemented within the Sprint. The selected Product Backlog items deliver one coherent function, which can be the Sprint Goal. The Sprint Goal can be any other coherence that causes the Development Team to work together rather than on separate initiatives.’ — The Scrum Guide</blockquote><p>The Sprint Goal is our compass and we’re heading into the high country where the peaks are movable and the terrain will change around us. We’re going to need it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*57aBo8JFtkZ7q-cYwdK6ug.png" /></figure><h3>Missing or basic goal</h3><p>In my experience, some Scrum Teams find it hard to formulate a Sprint Goal. Some teams do not set a Sprint Goal <em>at all. </em>In my experience this is more common with new teams or teams that are new to Scrum.</p><p>The most frequent explanation I’ve heard from teams that either do not have a goal or have a very literal goal is that the team has many different types of work brought into one Sprint. Perhaps there are Stories about Feature Epic 1 and Feature Epic 2 along with an operability Story. Perhaps there are a whole bunch of operability or technical debt-related Stories that, at first glance, may not seem to lend themselves towards a cohesive goal.</p><p>Even teams that set Sprint Goals may find it harder to craft one that can help them navigate this type of Sprint.</p><p>I’d like to look at how we might help teams that find themselves either unable to craft a goal or unable to create anything more than a basic goal like ‘complete Stories 12345, 64891 and 36912’.</p><blockquote>‘During Sprint Planning the Scrum Team also crafts a Sprint Goal. The Sprint Goal is an objective that will be met within the Sprint through the implementation of the Product Backlog, and it provides guidance to the Development Team on why it is building the Increment.’ — The Scrum Guide</blockquote><p>This is a very clear statement. It is typically laconic and does not go into factors that may prevent or hinder teams when they come to craft a goal. Here are some of the factors that I’ve seen.</p><h3>Too broad</h3><p>There may be a simple misunderstanding that the team thinks it’s goal needs to encompass <em>all</em> the work that could possibly be achieved in the Sprint. In the attempt to find an over-arching goal a more useful goal that helps focus the team on the highest value work is lost. In this scenario coaching the Product Owner to explain the highest value item in the Sprint and to provide a vision for the Sprint based on this may be helpful.</p><p>Broad, uninspiring goals may be an example of what Geoff Watts refers to as a ‘forced-fit’ Sprint Goal because the team are trying to force a goal to fit items that are selected based on priority only rather than value.</p><h3>Disparate Sprint Backlog</h3><p>The Product Backlog may be organised without grouping to assist focused Sprints. I’ve seen this contribute to the scenario where a team feels that it has many types of disparate work in the Sprint. This may represent the face value of the Product Backlog items while losing the value of a focused, goal driven Sprint. For example, some grouping to allow a clearer goal or theme for the Sprint may allow for greater focus and be more motivational resulting in more creative work and higher value outcomes.</p><p>Coaching the Product Owner to consider the benefit and the value of organising work in this way may help the team.</p><p>Coaching the team to help select the Product Backlog items based on the Product Owner’s vision for the end of the Sprint can also help here.</p><p>This avoids forcing a goal and helps us focus on value and outcomes rather than just priority. These are examples of how the goal could be driven ‘top down’ from the Product Owner or ‘bottom up’ from the team.</p><h3>Team Culture</h3><p>There may be a cultural element at play. To craft a Sprint Goal, and to explore many of the approaches we could try, may require going out of our comfort zone. This may be a factor for new teams or teams where trust has not developed. If you feel that you are in a team that doesn’t have the cohesion or trust to set a Sprint Goal then it may be a good idea to revisit some of the exercises that help the team learn about one another and how they will work together. Stephanie Ockerman and Simon Reindl’s ‘Mastering Professional Scrum’ provides very practical guidance about how this can be approached.</p><p>It might even be that a habit of not trying to set a Sprint Goal or of using flat, technical goals has formed.</p><blockquote>‘Chains of habit are too light to be felt until they are too heavy to break.’ — Warren Buffett</blockquote><h3>Disconnect</h3><p>In my experience problems with goal setting may be indicative of a disconnect between the vision for the Product and the work of the Scrum Team. The team just can’t see how the work of the Sprint relates to a meaningful outcome.</p><p>This is like knowing where we are going and having some idea about how we’re going to get there but not knowing <em>why</em> we are going or what the <em>point</em> of the expedition is. This is a factor when we need to adapt. If we don’t know the reason how will we creatively adapt to achieve the goal?</p><p>If the Product Owner genuinely cannot provide a goal for the Sprint then this may be because there is a disconnect between the Product Backlog and the Product Vision. Hopefully this is not underwear gnome territory. Since I’ve seen this video I now find it impossible to think about Roadmaps without also thinking about these guys:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F79954057%3Fapp_id%3D122963&amp;dntp=1&amp;display_name=Vimeo&amp;url=https%3A%2F%2Fvimeo.com%2F79954057&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F455759813_640.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="640" height="358" frameborder="0" scrolling="no"><a href="https://medium.com/media/b475252c0ad38aa1d9ab7b200534e09b/href">https://medium.com/media/b475252c0ad38aa1d9ab7b200534e09b/href</a></iframe><p>A Scrum Master can serve the team and the wider organisation by facilitating a session to capture the vision for the Product that can be used to derive a simple Roadmap.</p><p>This is a complimentary practice to Scrum and we have many different options to explore that may help the team.</p><p>If you’re in a context where you have Service Design experts then this is a great time to ask for their help. If you don’t have this option you can still help the team to move forward.</p><p>Roman Pichler provides some guidance about how we can seek to close this gap in his book Strategize. There is also a lot of great free advice on his website.</p><p>There are different ways to arrive at a link between a goal for the Product and the work we’re planning in a Sprint. In my opinion Roman Pichler’s ideas provide a practical and simple structure that can be used to great effect. It can be relatively straight forward to arrive at a single page showing how our work relates to business goals.</p><p>My simplified image below shows this flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wsaeKArZiOdm45s63MIbSQ.png" /></figure><p>With a simple Roadmap we have a way of showing the over-arching business goals for several Sprints worth of work. This gives us a vital link between Product vision and the work of an individual Sprint. If we’ve managed to facilitate the session successfully we also have a team that have been actively involved in the discussion about what we’re doing and why. This will be invaluable when the team are discussing the goal of a given Sprint when we come to Sprint Planning.</p><h3>Crafting a Goal</h3><p>Before we move into goal crafting we’ve differentiated whether the team are experiencing one or more of these situations:</p><p>· The goal is too broad and not value focused.</p><p>· The backlog is not organised into value focused Sprints. Resulting goals may be too literal or goal crafting is abandoned because an over-arching goal is too hard to craft (it feels forced).</p><p>· The team feel uncomfortable or out of the comfort zone with goal setting. There may be little interaction and a bad vibe when this is attempted.</p><p>· There is a disconnect between the product backlog and the product vision so the value of a Sprint is poorly understood.</p><p>We’ve helped the team to have a better chance of crafting a goal by identifying if these factors are at work and have coached accordingly.</p><p>We’ve checked the link between the Product vision and a Product Roadmap and used this to understand what is going to be in the Sprint and why.</p><p>Although the business goals are now clearer it may still be hard to move beyond flat, descriptive goals of the Sprint.</p><h3>Visual Thinking</h3><p>To move into more creative territory I’ve found that using metaphor is a good way to arrive at a motivational goal. Please do not be put off by this; as Scrum practitioners we need to show courage!</p><blockquote>‘When we see a picture in our mind’s eye, such as when we use a metaphor, we create a mental map quickly and with minimal effort.’ — David Rock</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*wB8IfdBTKOWQgOTEsZy8hA.jpeg" /></figure><p>It’s so much easier for us to understand the picture and grasp the meaning than if we tried to describe the situation literally. When dealing with the complexities of software development we frequently use visualisation to help us understand a situation. Why wouldn’t we try the same approach with our goals?</p><p>There are approaches that you can ask the team to try that may help generate some different ideas. This facilitation can be seen, in my opinion, as part of the Scrum Master role of helping the team to understand product goals and how these relate to Sprint Goals.</p><p>· If you had to describe the Sprint Goal as a piece of music, from any genre, what would it be? Why would it be that? Can you expand this?</p><p>· If the Feature is a fictional character who are they? This may be based on characteristics like: exciting, boring, conscientious, big, small etc.</p><p>· If this was a sporting event what type of event would it be?</p><p>· A famous person?</p><p>· A film?</p><p>With a conceptual metaphor you may find it helpful to focus on how the team, or a stakeholder, will feel when the work is accomplished. This can provide you with an image from which to build and map a metaphor.</p><p>Depending on your team culture you may already have rich sources of metaphor around you. Look at the Scrum Team names and the stickers people have. Listen to the sorts of conversation the teams have and whether themes come up. When you talk to the team are there cultural reference points that would make a good starting point?</p><p>You’ll soon build up your own list of sources of metaphor and I think you’ll have fun in the process.</p><h3>Closing</h3><p>We’ve looked at why the Sprint Goal is important and some practical tips for identifying why a team might be struggling with using them. In the process we’ve touched on areas that are significant and complicated in their own right and I’ve provided further links to the named references above.</p><p>Once we’re able to work with the team so that crafting a goal is more achievable we can then move on to visualisation to further help with more meaningful and fun Sprint Goals.</p><h3>References:</h3><p>‘The Sprint Goal’, Sjoerd Nijland, <a href="https://deref-gmx.co.uk/mail/client/KT3K8i_PBMI/dereferrer/?redirectUrl=https%3A%2F%2Fmedium.com%2Fserious-scrum%2Fthe-sprint-goal-c667762f8e81">https://medium.com/serious-scrum/the-sprint-goal-c667762f8e81</a></p><p>‘Mastering Professional Scrum, A Practitioner’s Guide to Overcoming Challenges and Maximizing the Benefits of Agility’, Stephanie Ockerman and Simon Reindl, Addison-Wesley 2020</p><p>‘Working with the GO Product Roadmap’ , Roman Pichler, <a href="https://deref-gmx.co.uk/mail/client/ygiDpUSajWQ/dereferrer/?redirectUrl=https%3A%2F%2Fwww.romanpichler.com%2Fblog%2Fworking-go-product-roadmap%2F">https://www.romanpichler.com/blog/working-go-product-roadmap/</a></p><p>‘Sprint Goal Template’, Roman Pichler, <a href="https://deref-gmx.co.uk/mail/client/H21x6ydVrQM/dereferrer/?redirectUrl=https%3A%2F%2Fwww.romanpichler.com%2Fblog%2Fsprint-goal-template%2F">https://www.romanpichler.com/blog/sprint-goal-template/</a></p><p>‘What does “Inspect and Adapt” really mean?’, Dan Ray, ’<a href="https://deref-gmx.co.uk/mail/client/I9CUxCXa8lA/dereferrer/?redirectUrl=https%3A%2F%2Fmedium.com%2Fserious-scrum%2Fwhat-does-inspect-and-adapt-really-mean-c9c61897027d">https://medium.com/serious-scrum/what-does-inspect-and-adapt-really-mean-c9c61897027d</a></p><p>‘Coaching with the Brain in Mind’, David Rock and Linda J. Page PhD, Wiley 2009</p><p><a href="https://deref-gmx.co.uk/mail/client/7sK7LyD-64I/dereferrer/?redirectUrl=https%3A%2F%2Fguntherverheyen.com%2F2011%2F10%2F22%2Fthe-house-of-scrum%2F">‘House of Scrum’,</a> Gunther Verheyen, <a href="https://deref-gmx.co.uk/mail/client/7sK7LyD-64I/dereferrer/?redirectUrl=https%3A%2F%2Fguntherverheyen.com%2F2011%2F10%2F22%2Fthe-house-of-scrum%2F">https://guntherverheyen.com/2011/10/22/the-house-of-scrum/</a></p><p>‘Myth: Having a Sprint Goals is Optional in Scrum’, Christiaan Verwijs &amp; Barry Overeem, <a href="https://deref-gmx.co.uk/mail/client/aRFV0ZCglow/dereferrer/?redirectUrl=https%3A%2F%2Fwww.scrum.org%2Fresources%2Fblog%2Fmyth-having-sprint-goal-optional-scrum">https://www.scrum.org/resources/blog/myth-having-sprint-goal-optional-scrum</a></p><p>‘Scrum Mastery: From Good to Great Servant Leadership’, Geoff Watts, Inspect &amp; Adapt Ltd 2010</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/969/1*rrpftt5r8sVctV24xkSLZg.png" /><figcaption><a href="http://seriousscrum.com/invite">Do you want to write for Serious Scrum or seriously discuss Scrum?</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=86ed8070041b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/serious-scrum/crafting-sprint-goals-86ed8070041b">Crafting Sprint Goals</a> was originally published in <a href="https://medium.com/serious-scrum">Serious Scrum</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>