<?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 Agile Alex on Medium]]></title>
        <description><![CDATA[Stories by Agile Alex on Medium]]></description>
        <link>https://medium.com/@agilealex?source=rss-272ebf135ae8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*fJHq1feaByiUlZczJFbT_w.jpeg</url>
            <title>Stories by Agile Alex on Medium</title>
            <link>https://medium.com/@agilealex?source=rss-272ebf135ae8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 14:53:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@agilealex/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[Real-Time Roadmaps: from the illusion of control to risk-based reality]]></title>
            <link>https://agilealex.medium.com/real-time-roadmaps-from-the-illusion-of-control-to-risk-based-reality-3902343ae475?source=rss-272ebf135ae8------2</link>
            <guid isPermaLink="false">https://medium.com/p/3902343ae475</guid>
            <dc:creator><![CDATA[Agile Alex]]></dc:creator>
            <pubDate>Tue, 23 Jun 2026 21:44:04 GMT</pubDate>
            <atom:updated>2026-07-05T20:01:41.814Z</atom:updated>
            <content:encoded><![CDATA[<p><em>An introduction to a different kind of roadmap — one built on probability rather than false certainty, and drawn from the work you are already doing.</em></p><p>Every organisation has a version of the same meeting. Once a quarter, a roomful of capable people spends a day or two producing a roadmap: a tidy grid with time along the top, initiatives down the side and a confident bar for each one. It looks authoritative; it was made with a specialist tool or presented as a PowerPoint slide. Someone presents it to leadership, who all nod.</p><p>And almost everyone in that room (when asked privately, and promised discretion) would admit they do not quite believe it. They have seen this before. Within a few weeks, reality will have drifted from the grid; within a few months, the two will have almost nothing to do with one another. The roadmap will not be corrected. It will simply stop being mentioned until the next planning cycle produces a fresh one: equally detailed, equally authoritative, equally doomed.</p><p>This article is about what you give people instead. Not a better planned roadmap, a different instrument altogether. I call it the <strong>Real-Time Roadmap. I</strong>ts most surprising feature is that you are probably most of the way to having one already.</p><h3>Why the familiar roadmap lies</h3><p>The timeline roadmap descends from the Gantt chart. That was a tool for a different era; built for work that is repeatable, predictable and fixed in sequence. For manufacturing, construction or work done so often before, the duration of each step is known from records. For that work, a bar chart is not a lie; it is a faithful picture of a future you can foresee, because you have lived it many times.</p><p>Product development fails all three tests. It is not repeatable — if a feature had been built before in exactly this form, you would copy it, not build it. It is not predictable — you cannot have reliable records for something never done. And it is not fixed in sequence — you often learn the right order only once you are moving, when the work, or a customer, tells you the thing scheduled for Q3 should not be built at all.</p><p>While the traditional roadmap is a good tool, it’s been forced into service in a world it was never designed for.</p><p>The damage shows up in two ways. The grid is organised around features and dates rather than problems and outcomes. It commits to building particular things long before anyone knows they are the right ones. It also asserts certainty: a bar in a quarter is a promise about a future that a product manager confidently says will happen.</p><p>Think of a printed itinerary versus a live navigation app. The timeline roadmap is the printed itinerary that says you will arrive at 5:12 p.m. It’s reassuring, precise and useful right until the first traffic jam, after which it is worse than useless. Not because having a plan wasn’t good, but because it keeps announcing a time that will not happen and offers no way to adjust. What you want, once you are on the road, is the thing that watches the traffic, reroutes around the jam and revises its estimate as it learns.</p><h3>Probabilistic, not deterministic</h3><p>Underneath the grid sits a belief worth naming, because everything that follows argues against it. Call it the<strong> deterministic mindset: the as</strong>sumption that the future of a piece of work has a single, knowable outcome, and that planning means writing that one path down accurately.</p><p>It assumes the work will be the size you thought, that nothing more urgent will arrive, that the team’s pace will hold and that today’s priorities will still be right in three months. None of those assumptions is bad. Each is simply, reliably, false.</p><p>The honest picture is different. The future of a feature is not one outcome; it is a <em>range</em>, some outcomes likelier than others. It might land on the 4th, the 11th, or — if three things go wrong — the 25th. A single date picks one point out of that range and presents it as though the others did not exist. It is a forecast with its uncertainty deleted.</p><p>So the honest answer to “when will it be done?” is never a single date. It is a date with a probability: “we are about 85% likely to be done by the 18th, almost certain by the 25th.” We accept this everywhere else. No serious weather forecaster says “it will rain tomorrow”; they say “70% chance,” and you decide whether to carry an umbrella. We read probability without panic in almost every domain — except, oddly, in our roadmaps, where we still demand one confident number and then act wounded when reality declines to comply.</p><p>That shift, from a deterministic mindset to a probabilistic one that acknowledges variability and states it honestly, is the foundation on which the Real-Time Roadmap is built.</p><h3>A short tour of flow</h3><p>To build a roadmap on probability, you need a few instruments that many product organisations do not yet use. They come from a body of practice called flow. If the vocabulary is new, here is the minimum you need to know. If you want more, read the <a href="https://prokanban.org/the-kanban-guide">Kanban Guide</a> or the <a href="https://prokanban.org/kpg">Kanban Pocket Guide</a>.</p><p>Flow is the steady, even movement of work through a system to a customer. The word people hear is “fast”; the word that matters is “even.” A motorway can have a high average speed and still be miserable, because it surges and stalls — and it can move at a steady, unspectacular pace and get everyone home on time. Good flow is the second kind. It is not haste but steadiness, and steadiness is what lets you make promises you can keep.</p><p>Now look at your board — the items started and not yet finished. Not a to-do list: each item costs something to start, and costs more for every day it sits there unfinished. It is a portfolio of live bets, each running up a bill while you wait to see how it turns out. A handful of plain measurements make it legible. We call these flow metrics, and there are four of them:</p><ol><li><strong>Work in progress (WIP)</strong> is the number of items started but not finished — a powerful measure, because it is the one you can change directly. A general insight from Little’s Law says that the more you have on the go at once, the longer each takes: attention is finite, and split across twenty items, each crawls. Therefore, the most counter-intuitive instruction in flow, and the most reliable, when you are in trouble, is to <em>stop starting and start finishing</em>.</li><li><strong>Throughput</strong> is how many items you finish per unit of time. Throughput is the exact count of work items. This is the flow metric you need to forecast multiple items using a Monte Carlo Simulation (see below)</li><li><strong>Cycle Time </strong>is the elapsed time between when a work item started and when a work item finished. This is the flow metric you need to forecast single items using an SLE (see below). Both Throughput and Cycle Time are facts about your own past, which makes them precious: they describe how your system genuinely behaves, not how you hope it will.</li><li><strong>Work Item Age</strong> is the elapsed time between when a work item started and the current date. This is the quiet hero. Cycle Time is known only once something is finished — a postmortem on money already spent. Age ticks upward in real time on the work in front of you now. It’s the one signal you can act on while there is still something to do. An item aged far past where your work usually finishes is not just old; it is almost certainly in trouble, and the age is the alarm.</li></ol><p>A few more useful definitions: A <strong>Service Level Expectation (SLE)</strong> derived from Cycle Times turns that history into an honest forecast for a single item: “85% of our work finishes within 20 days or less.” Note the probability and the range — a confidence level <em>and</em> a span of time. A time without a confidence level is just a wish.</p><p><strong>Monte Carlo simulation </strong>is a mathematical technique used to model the probability of different outcomes in a process with inherent uncertainty. Instead of guessing a single fixed value, it uses computational algorithms to run thousands of random trials, generating a full spectrum of possible results and their likelihoods. Past data and performance are used to model possible future outcomes.</p><p>That is the toolkit. Hold it loosely, because the roadmap is about to be built from it.</p><h3>How the roadmap evolved</h3><p>The Real-Time Roadmap is an evolution of things you are probably already doing.</p><p>The Gantt chart or grid we have already condemned: features as bars, each pinned to a quarter, asserting certainty about the unknown. Its two fatal properties — organised around features and dates, and certain about a future that is not — are exactly what the later steps exist to fix.</p><p>The evolution was the Now / Next / Later roadmap. The first real improvement was to throw the dates away. In 2012, Janna Bastow and Simon Cast, the British founders of the product tool ProdPad, replaced the grid of quarters with three horizons: what we are working on now, what is likely next, and what may come later. Its genius is in admitting that certainty decreases with distance. “Now” can be specific; “later” is deliberately vague, because you know little about the distant future and should stop pretending otherwise. And the columns are framed around problems and outcomes, not features with dates. It is a genuine leap, and for many teams it is enough. A big gap remains: it still does not answer “when?” with any rigour.</p><h3>Your Kanban board is your roadmap</h3><p>This next step is the move that changes everything. It is so simple it is easy to miss: your Kanban board is a roadmap already. It is a form of the Now / Next / Later roadmap. The items in progress are your “now.” The items ready to be pulled next are your “next.” The backlog behind them is your “later.”</p><p>The board is organised by exactly those horizons — but with a decisive advantage. It is not a separate artefact that drifts from reality, because it is reality. Nobody maintains it by hand; it updates itself as the work moves. Why keep a map alongside the territory when the territory can be read as the map?</p><p>Stakeholders will probably object immediately: a board is too granular — leadership does not want forty tickets, they want the shape of the year. Fair enough. But the answer is not to retreat to the Gantt chart. Rather, the board-as-roadmap is read at different altitudes by different people. A team reads individual items. A product leader reads a higher level — features, epics and outcomes, fed by the same flow data underneath. An executive reads a handful of big bets (you may call these initiatives or themes) with live forecasts and risk colours. Same roadmap all the way up, zoomed to the right resolution for the audience. The grid tried to serve everyone with one watered-down artefact and served no one; this serves each audience the same truth at the detail they need.</p><p>The evolution is to build your Real-Time Roadmap by layering on the tools defined earlier. If you run a flow system, you have already built every one. Add the workflow stages, and the roadmap shows not just what is in flight but how far along each thing is. Add WIP control, and it becomes honest about capacity: it can only show as much “now” as you can actually do at once, forcing the prioritisation a grid lets you dodge. Add your SLEs and continuous Monte Carlo forecasts, and it answers “when?”. Not with a fixed date but with a live probability for every item and feature, updating itself as the work moves.</p><p>Where genuine fixed dates exist — a regulatory deadline, a launch, a contractual commitment — lay the forecast against them for a live, traffic-light view: green where the forecast comfortably beats the date, amber where it is tight, red where the data says you will miss. In real-time, you are giving people insight into risk and the ability, with time, to act.</p><figure><img alt="A high-level Real-Time Roadmap communicating risk to a series of fixed date commitments." src="https://cdn-images-1.medium.com/max/1024/1*0jaGOjlO-lgjL-ZhbYvhUQ.png" /><figcaption>A high-level Real-Time Roadmap communicating risk to a series of fixed date commitments. Note the confidence level attached.</figcaption></figure><p>That is the Real-Time Roadmap: your board. Add in stages, WIP control, SLEs and forecasts if that helps you. It’s more insight as a single living object showing what you are doing, how far along it is, when it is likely to be done and where the risks are. All from real data, all updating itself. It is everything the timeline grid pretended to be and never was. And because it is the work, not a picture of the work, it cannot drift out of date.</p><p>Make it concrete. Picture a team building single sign-on for enterprise customers — letting people log in through their own company’s identity provider.</p><p>On the old roadmap, “enterprise SSO” was one bar in Q3, asserting a date nobody believed. On the Real-Time Roadmap, it is a small cluster of thin slices: a couple already shipped and live; one in progress, showing amber against the date sales have been quietly promising, because it has stalled on a security review that never appeared on anyone’s board. Two more in “next”; and the ambitious admin console is still in “later,” deliberately vague. A stakeholder sees at a glance what has shipped, what is moving now, what the live forecast says about the part with a real deadline, and what is uncommitted because it is too far off to pin down. No bar, no false date — just the actual work, its actual state, and an honest “when” for the parts that have one.</p><h3>The roadmap that tells the truth about your priorities</h3><p>The deepest payoff is not about dates at all. It is political, and it is where the Real-Time Roadmap really shines.</p><p>A traditional roadmap shows stated priorities — the order that leadership agreed on in the planning room. The Real-Time Roadmap reveals priorities — what the organisation is actually spending its capacity on right now. The two are often startlingly different.</p><p>Everyone has lived it: the roadmap says the top priority is the big strategic initiative, while the board shows most of the team’s capacity going to interruptions, urgent fixes and pushed-in work that appears on no roadmap anywhere. The plan and the real work have diverged, and only the board knows. This is uncomfortable — and the discomfort is the entire value, because you cannot manage a misallocation you cannot see. The Real-Time Roadmap drags the true allocation of your most precious resource, your people’s attention, into the light, where it can be discussed honestly.</p><p>While a traditional roadmap lets everyone keep believing the plan, the Real-Time Roadmap makes everyone confront reality. The second conversation is harder, though infinitely more useful.</p><h3>Deciding at the last responsible moment</h3><p>Because the roadmap is live and the forecasts are continuous, you no longer need to fix the whole order of work months ahead. You decide what to pull next at the moment you have the capacity to start it , which is the moment you know the most, having learned everything the work has taught you so far. Deciding later is not indecision; it is deciding with more information. The traditional roadmap forced you to commit to the distant future when you knew least. The Real-Time Roadmap lets you commit each thing at the last responsible moment, when you know most.</p><p>A discipline goes with this. Most teams let the small-and-urgent consume the day — the way unguarded meetings expand to fill a calendar — and then find no room left for the handful of bets that actually move the business. Reserve capacity for the important few first and let the small work settle around them. The Real-Time Roadmap is the first instrument that lets you see, in live data, whether the important things are getting the room they need or being quietly buried.</p><h3>Reforecasting is not a failure</h3><p>One last point, because it is the one most likely to trouble stakeholders. A probabilistic forecast changes as new data arrives. The forecast you give today will not be the one you give in two weeks. Mainly because at that time, two weeks of finished items will have flowed through. Your Throughput data will have new and potentially different data to model from. To a mind raised on fixed plans, this looks like failure: “you said the 18th, now you say the 25th — you got it wrong.”</p><p>It is not a failure. It is the forecast working as it should. Your navigation app revises its arrival time as the traffic changes, and you do not accuse it of lying — you are grateful it is keeping up. A forecast that never moved would be the suspicious one: it would mean you were ignoring everything you had learned. So reforecast often, and frame the changes for what they are — not broken promises. It is the honest narrowing of uncertainty as the work reveals itself. A forecast is a living estimate, not a promise carved in stone.</p><h3>You are probably already most of the way there</h3><p>The Real-Time Roadmap does not abolish the roadmap. It evolves it — through evolving a Now / Next / Later, through reading the board as the map, and finally by using the instruments of flow. It aims to tell the truth: what you are doing, how far along it is, when it is likely to land and crucially, where the risk sits.</p><p>It answers the question every stakeholder has always asked — <em>when will it be done?</em> — but honestly, as a probability. In doing so, it escapes the trap the traditional roadmap never could: it stops spending the organisation’s trust faster than it builds it.</p><p>And the best part is the one we began with: you are probably most of the way there already. You have a board. You almost certainly have a history of finished work, whether or not you have looked at it as data. Reading the one through the other is the whole move. You do not need a beautiful lie about the future. You can have a useful truth about it instead.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3902343ae475" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How much data do I need to start forecasting?]]></title>
            <link>https://agilealex.medium.com/how-much-data-do-i-need-to-start-forecasting-63a59e16ecf5?source=rss-272ebf135ae8------2</link>
            <guid isPermaLink="false">https://medium.com/p/63a59e16ecf5</guid>
            <category><![CDATA[time-series-forecasting]]></category>
            <category><![CDATA[forecasting]]></category>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[flow]]></category>
            <category><![CDATA[metrics]]></category>
            <dc:creator><![CDATA[Agile Alex]]></dc:creator>
            <pubDate>Thu, 04 Sep 2025 10:11:39 GMT</pubDate>
            <atom:updated>2026-06-26T11:50:49.157Z</atom:updated>
            <content:encoded><![CDATA[<p>As Daniel Vacanti puts it: <em>“They are the five words that product development teams hate to hear most: ‘When will it be done?’”</em> This blog is inspired by his work — and the thinking of others — on how to approach forecasting in a more practical, evidence-based way.</p><p>In ProKanban’s <em>Applying Metrics for Predictability</em> and <em>Applying Flow Metrics for Scrum</em> classes, we explore this question in depth. Students learn techniques to answer the hated question with confidence, using flow-based forecasting rather than estimation, endless planning and guesswork. This article is written mainly for my students: it’s a continuation of the conversation we begin in the classroom and a reference they can return to when putting these ideas into practice.</p><h3>The question everyone asks</h3><p>When people first consider forecasting, one question almost always comes up: <em>“How much data do I need before I can begin?”</em></p><p>It’s an understandable concern. Forecasting often conjures images of massive spreadsheets, years of historical records and, frankly, a lot of faff before anything useful emerges. Many leaders assume that without a mountain of numbers, forecasts aren’t worth the paper (or pixels) they’re written on.</p><p>Here’s the good news: you don’t need to wait until you’ve stockpiled hundreds of observations. You can learn a surprising amount from far fewer data points than most people expect. The key is to know what’s “enough” to make a confident start — and to avoid delaying action while you chase diminishing returns.</p><h3>Small data samples can give big insights</h3><p>A helpful starting point is Douglas Hubbard’s “Rule of Five”, taken from his epic book <em>How to Measure Anything: Finding the Value of Intangibles in Business</em>. In simple terms, there is power in using small samples. In using an example of a population of employees, if you take a random sample of five items, there’s a 93.75% chance that the median of the whole population sits between the smallest and largest of those five. With only five observations you can already place the middle of your process with reasonable confidence.</p><p>Imagine a support desk measuring ticket resolution times. After just five completed tickets you won’t yet know everything about variability or extremes, but you’ll have a credible estimate of the 50th percentile — a surprisingly useful anchor for expectations and planning. Here’s what that looks like in practice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j7dZ6JpmE03I0jcben1S0Q.png" /></figure><h3>Thinking in ranges</h3><p>You can push the idea of “small data” further with a simple thought experiment: a fair six-sided die. Because each outcome is equally likely, the distribution of the results is uniform. After only 11 rolls, there’s already a strong chance the next roll will land between the minimum and maximum you’ve seen so far.</p><p>This is just a teaching device — or a conceptual model — because real processes are rarely so uniform. Even so, the message is clear: you don’t need a huge sample before useful boundaries start to appear. In fact, a small, up-to-date dataset often paints a more accurate picture of what’s happening right now than a large collection of stale, historical data.</p><p>To make this tangible, here’s a quick visual from a simulated set of eleven rolls. Notice how the min–max range firms up quickly. Again, this is a teaching device as we know the lower range of this data will be 1 and the upper range of this data will be 6 — and always a whole number in between. We know this before the simulation has even begun.</p><p>In product development, things are rarely that clear. Though the teaching point serves a purpose: a small sample gives us an astonishingly accurate distribution of the data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YhMZgOK8YIKj1Yc8URjE8A.png" /></figure><p>So how many points should you gather before you draw proper limits around your process? A practical rule of thumb is to use a baseline of around 10 to 20 data points to calculate limits with confidence. Why that range? Because the real aim isn’t to hoard data; it’s to minimise two classic errors: mistaking noise for signal (seeing a pattern that isn’t there) and mistaking signal for noise (ignoring a real change). Ten to twenty recent observations usually strike the right balance — enough to separate pattern from randomness, but not so many that you anchor on outdated behaviour.</p><p>There are times when you can include more than 20 points, particularly if observations arrive quickly and you’re confident the process hasn’t changed materially. But beyond that, it’s sensible to treat your baseline as rolling. Newer points push out older ones so your forecast reflects current reality. This “rolling baseline” approach keeps your model alive to shifts in the system rather than embalmed in past performance.</p><h3>Why more isn’t usually better</h3><p>Why not simply collect more data forever? Three reasons. First, diminishing returns: the jump in understanding from 0 to 10 points is huge; from 100 to 110, usually tiny. Secondly, staleness: processes evolve — teams adopt new tools, policies change, markets move. Old data can become a poor guide to what comes next. Thirdly, practicality: the longer you wait to “have enough”, the longer you put off improving. Forecasting is a learning loop — and loops work best when they’re short.</p><h3>A few exceptions and things to note</h3><p>The key message so far is simple: you don’t need as much data as you think — so start with what you’ve got and get going!</p><p>That said, more data can be valuable. If someone gives me more data, I will always take it. My hope would be that it will give a richer picture of the process and make forecasts more robust; whether we’re looking at individual or multiple item forecasts. Just remember that at some point you’ll hit diminishing returns.</p><p>There are two important caveats here. First, <strong>recency matters more than volume</strong>. I’d take 15 fresh data points over 150 old ones in most contexts. Teams, portfolios, even whole organisations can change significantly over months, quarters and years. Old data may describe a world that no longer exists.</p><p>Second, make sure the data you use reflects the world you’re forecasting into. In the UK, for example, late December and early January are unusual times of the year: many people take time off for Christmas and New Year, which slows down work and skews flow metrics. Using that data to predict February performance would probably be misleading. Always choose samples from a period that looks like now. The simple rule might be: forecast the future world based on a fair representation of the past world. For how people take holidays, December and April are very different months.</p><h3>In summary</h3><p>What does this look like for a typical team or organisation? Suppose you’re forecasting cycle time for software work. After five completed items you can already anchor expectations around the median (50th percentile). After 10–15 items you can begin to sketch meaningful bounds for “most of our work”. Around 20 items you can turn those bounds into a rolling baseline and use them to spot potential signals — for instance, when a new item looks likely to exceed your upper band, or when a recent run of faster-than-usual completions hints at a real improvement. At each step, you’re making better decisions than if you’d waited for a perfect dataset.</p><p>There’s a softer, cultural benefit to starting small as well. Teams can be wary of data efforts if they sound like an enormous up-front investment. This is useful if you’re trying to convince your leadership to try flow metrics for the first time. Demonstrating value with just a handful of observations lowers the barrier to entry. People see early wins, develop trust in the measures and buy into the habit of continuously collecting and using data. Momentum beats perfection.</p><p>Here’s the crib sheet I often use as a concise set of takeaways to share:</p><ul><li>First: five data points are enough to estimate a median credibly, which is a surprisingly strong start for planning.</li><li>Second: in simple cases, eleven observations already tell you a lot about range.</li><li>Third: a rolling baseline of around 20 recent points is typically sufficient to establish useful limits and to separate signal from noise without drifting into historical trivia. If you need more precision later, you can always extend the window — but treat “more” as an option, not a default.</li></ul><h3>In summary</h3><p>You probably need less data than you think to begin forecasting. Start with what you have, aim for a rolling window of 10–20 points, and keep the dataset fresh. Don’t discard old data: it can be useful to see trends, progression and other useful things. Just don’t be upset when you use it to forecast a world that no longer exists.</p><p>Then, use those early insights to set expectations, manage risk and spot change. Forecasting isn’t about waiting for perfect certainty; it’s about reducing uncertainty enough to act — and doing so sooner rather than later.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=63a59e16ecf5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meet the Flow Canvas: a simple way to make work… flow]]></title>
            <link>https://agilealex.medium.com/meet-the-flow-canvas-a-simple-way-to-make-work-flow-ee6d192fc764?source=rss-272ebf135ae8------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee6d192fc764</guid>
            <category><![CDATA[canvas]]></category>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[flow]]></category>
            <category><![CDATA[workflow]]></category>
            <category><![CDATA[kanban-board]]></category>
            <dc:creator><![CDATA[Agile Alex]]></dc:creator>
            <pubDate>Wed, 03 Sep 2025 09:50:05 GMT</pubDate>
            <atom:updated>2025-09-03T09:59:41.930Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*faenJ31VxR-w7EPxT8cB-g.png" /><figcaption>A quick link: <a href="https://miro.com/miroverse/flow-canvas/">Flow Canvas on Miroverse</a>.</figcaption></figure><p>We’ve all been there. A project drags on longer than expected. A team going round in circles with endless carry-over work. Lots of things starting, with very little getting done. Endless conversations about estimates and delivery dates, always wrong.</p><p>Yet, no one’s quite sure where things are stuck. If you ask three different people how the work gets done, you’ll likely hear three different answers. It’s messy, confusing and it slows everyone down.</p><p>That’s exactly why I created the <strong>Flow Canvas</strong> — a straightforward, visual way to bring clarity to the chaos and help teams, portfolios, organisations (any ‘system’) actually see how their work flows from start to finish.</p><h3>Why I built it</h3><p>The Flow Canvas is based on <a href="https://www.prokanban.org/the-kanban-guide">the Kanban Guide</a> and my experience of teaching <a href="https://www.prokanban.org/events-category/apk">ProKanban’s Applying Professional Kanban</a> class. Time and again, I noticed that when people were asked to describe their workflow, or even start conversations about how to describe it, they found it difficult. They knew it in their heads, but when it came to putting it down on paper — or explaining it to someone else — the differences in perception quickly emerged.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*faenJ31VxR-w7EPxT8cB-g.png" /></figure><p>I wanted to create something that made those hidden assumptions visible. Something practical enough to use in a workshop, yet valuable enough for teams to continue using afterwards. The Flow Canvas became that tool. It acts as both a mirror, showing you how things really are, and a map, helping you chart where improvements could be made.</p><h3>How it works</h3><p>At its heart, the Flow Canvas is simply a shared space where people can lay out the stages of their workflow and begin a conversation about how work moves — or doesn’t move — through it. You don’t need to be a process expert to use it. In fact, some of the most valuable sessions I’ve seen are the simplest ones.</p><p>Once you copy the <a href="https://miro.com/miroverse/flow-canvas/">template into Miro</a>, start at the beginning and sketch out the key stages, using the questions as prompts. As people add their insights to the canvas, a clearer picture starts to emerge. Bottlenecks stand out. Hand-offs that were never questioned before suddenly appear clunky. Sometimes the biggest surprise is realising that half the team thought the work happened in a completely different order.</p><p>Once those insights are visible, the conversation naturally turns to what could be improved. That might mean adjusting responsibilities, smoothing hand-offs, or experimenting with new ways of working. The point isn’t to create the “perfect” process on day one — it’s to give the team a shared foundation for ongoing improvement.</p><p>Because the canvas lives in Miro, it doesn’t have to be a one-off exercise. It can become part of retrospectives, planning sessions, or team workshops. Over time, it evolves with the team, reflecting changes and keeping the flow of work transparent.</p><h3>Where you can find it</h3><p>The <a href="https://miro.com/miroverse/flow-canvas/">Flow Canvas is available in the <strong>Miroverse</strong></a>, Miro’s community library of templates. It sits alongside other resources for agile workflows, product management and team collaboration, which means it’s easy to find whether you’re a coach, a team lead, or simply someone who wants to make sense of a complicated process.</p><p>Once you open the template, simply click “Use template” and it will appear in your own Miro workspace. From there, you can invite colleagues in, adapt it to your context, and start mapping your flow. There’s no complicated set-up or rules — it’s deliberately lightweight so you can focus on the conversations that matter.</p><h3>Looking back</h3><p>When I first shared the Flow Canvas on LinkedIn, I wasn’t sure what the response would be. I’d used it successfully in training sessions, but releasing it publicly was a step into the unknown. The reaction was encouraging: people were genuinely excited to have a simple, accessible way to visualise their workflows. It confirmed what I’d believed all along — that teams don’t need heavy frameworks as much as they need approachable tools that spark the right conversations.</p><h3>Final thoughts</h3><p>In a nutshell, the Flow Canvas is a visual way to map your workflow. It started life as a training aid, but it has grown into something broader: a tool to help people cut through complexity, find alignment, and continue improving together.</p><p>If you’ve ever thought, <em>“There must be a clearer way to show how we work,”</em> this is it. Head over to Miro, give the template a try and see what conversations it sparks. Often, simply making the flow of work visible is the first step towards making it better.</p><p>Feedback and thoughts are always very welcome.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee6d192fc764" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What do we mean by ‘system stability’?]]></title>
            <link>https://agilealex.medium.com/what-do-we-mean-by-system-stability-4ec9974461ab?source=rss-272ebf135ae8------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ec9974461ab</guid>
            <dc:creator><![CDATA[Agile Alex]]></dc:creator>
            <pubDate>Thu, 22 May 2025 18:23:56 GMT</pubDate>
            <atom:updated>2025-05-22T18:31:26.617Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’ve ever felt like your team is constantly busy but nothing ever really gets done, chances are your system is unstable. If it feels like you’re using up more of your resources but getting less, that could be a signal that you have an unstable system. If you’re not able to give a trustworthy forecast of when something will be done, there’s a reasonable chance your system is unstable.</p><p>What do we mean when we talk about system stability<em> </em>and why does it matter so much in Kanban? Let’s break it down in simple, practical terms.</p><h4><strong>Stable, systems</strong></h4><p>Starting with a ‘system’. Kanban is all about managing flow. Flow refers to the movement of potential value through a process that is visually represented. We often refer to that visual process as a system. It’s how work begins, is worked on, and ultimately becomes something valuable for someone.</p><p>A ‘stable system’ means that work moves through a process consistently and predictably. One common way we create stable systems is to control the amount of work in a system at any one time. This is often referred to as limiting work in progress (WIP). In effect, we only pull work into our system when there is the capacity to work on it. Limit WIP and you’ll start to get better outcomes from your system. It’s all linked.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5jJSs2o8_eIXjOqic-2L6g.png" /></figure><p>This is the opposite of a push system, where work is pushed in regardless of whether there is capacity to work on it at that time. Push systems are unstable and focus on keeping people busy, rather than on flow. As Henrik Kniberg says in his <a href="https://www.youtube.com/watch?v=CostXs2p6r0">excellent video describing the resource utilisation trap</a>, ‘if all you do is focus on keeping people busy, all you get is busy people’.</p><p>Think about it like this. In an unstable system, we’re likely working on too many items, with things feeling chaotic. Some tasks fly through our process in a short amount of time, while many others drag on for much longer. Priorities shift constantly and planning becomes a guessing game, based more on opinion than data.</p><p>Stability is like the foundation of a house. Without it, everything else starts to wobble.</p><h3><strong>Signs and benefits of a stable system</strong></h3><p>If you’re running a stable system, it will provide you with signals that everything is running smoothly.</p><p>You’re likely not seeing that work is piling up. Your WIP control is working and work is flowing through at a good pace. Your customers are getting what they want, when they want it.</p><p>Generally, items are completed within an acceptable timeframe, with few exceptions. If you have a clear statement of how long you expect items to take, such as a Service Level Expectation (SLE), you’ll regularly adhere to it. That’s because you’re delivering at a steady pace.</p><p>You can then make better forecasts. Using past data, you can generate metrics for your system, which will help you forecast the future with a high level of confidence. Your SLE will be based on real data, providing a forecast with an acceptable degree of uncertainty. Statements like ‘we deliver a work item in 8 days or less, 85% of the time’ will be something your stakeholders or customers can trust.</p><h3><strong>Flow Metrics are your friend!</strong></h3><p>Stability does not mean the absence of variability in your data. Some level of variation is expected, particularly in product management, where less is known upfront. Instead, a stable system means that the variation is manageable and understood. Stability enables teams to utilise data for actionable insights, whereas instability obscures signals and increases risk.</p><p>Use four simple metrics to monitor flow and assess your stability:</p><ol><li><strong>Cycle Time</strong>: The elapsed time between when a work item started and when a work item finished. Stable systems have relatively consistent cycle times. You can base your SLE on your Cycle Time data, just pick the level of risk you’re comfortable with.</li><li><strong>Throughput: </strong>The number of work items finished per unit of time. Stability is reflected in steady throughput over time. You can forecast multiple items using your Throughput metric — a Monte Carlo Simulation is a great tool for that.</li><li><strong>Work in Progress (WIP): </strong>The number of work items started but not finished. High and variable WIP often signals instability. Try to keep your WIP as steady and as controlled as possible.</li><li><strong>Work Item Age: </strong>The elapsed time between when a work item started and the current date. Stable systems tend to have lower and more predictable work item ages. Along with controlling WIP, controlling the age of your items is one of the most effective ways to maintain system stability.</li></ol><p>In summary, system stability is what makes a Kanban system effective, efficient and predictable. It helps you to stop firefighting and start delivering with confidence.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ec9974461ab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to spot and fix issues with a cumulative flow diagram]]></title>
            <link>https://agilealex.medium.com/how-to-spot-and-fix-issues-with-a-cumulative-flow-diagram-4d2a7e98b400?source=rss-272ebf135ae8------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d2a7e98b400</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[lean]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Agile Alex]]></dc:creator>
            <pubDate>Sat, 03 Jul 2021 11:07:04 GMT</pubDate>
            <atom:updated>2023-08-18T19:39:56.082Z</atom:updated>
            <content:encoded><![CDATA[<p>A cumulative flow diagram (CFD) is a visual representation of how your system is performing. A CFD is a powerful tool, and it can tell you much about the health of your system. You’ll see patterns around the flow of work and issues — if you know what to look for.</p><p>In <a href="https://medium.com/@agilealex/how-to-read-a-cumulative-flow-diagram-2900bd7f2b85">the first blog article</a>, I outline some caveats and words of warning. As I help and not confuse, here is one important point on the next chart: I’ve not wanted to make the chart below too wordy. Technically, wherever you see the word ‘average’ you should read ‘approximate average’. I’m not going to go into why here, though chapters 4 and 5 in Daniel Vacanti’s excellent <a href="https://actionableagile.com/resources/publications/aamfp/">Actionable Agile Metrics for Predictability</a> explains it better than I ever could.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_cWAK1CrmMl_tUKp.png" /></figure><p>In this second blog, I’ve outlined some of the most common problems and warning signs. I’ve also included some questions a team could use with to discuss problems with their flow. I’ve used many of these as retrospective conversations. Given a CFD only looks backwards, it’s best used in that Scrum event, rather than planning.</p><p>An important reminder is that a CFD will show you variability in your flow. Variability is natural — you should always expect it in your system. Therefore a CFD to an extent will reflect that variability back to you. The charts below are occurrences observed with teams I’ve worked with and some of the questions we discussed together. Using a CFD as a conversation tool helped us to expose areas of improvements, all with the aim of achieving better flow.</p><h3>Widening bands</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1xDaTgJOHlaemTlC.png" /></figure><p>You want your arrival and departure rates to run in parallel with each other for a healthy flow. If you start noticing some of the bands in the graph widening, it means your work in progress (WIP) is increasing. The likely cause is a WIP limit being broken somewhere, causing too much work to come into the system.</p><p>Setting and keeping WIP limits is essential to help the team focus on a few items at a time. Little’s Law tells us that if you increase your WIP without finding a way of increasing your delivery rate, you will see your cycle time increase. Decrease your total WIP by setting limits and you’ll likely reduce your cycle time. WIP limits are an effective way of regulating flow.</p><p>If you’re not familiar with Little’s Law, Daniel Vacanti sums it up quite nicely:</p><blockquote><em>Three of these metrics (Work in Progress (WIP), Cycle Time, and Throughput) are intrinsically linked by a very straightforward and very powerful relationship known as Little’s Law:</em></blockquote><blockquote><strong><em>Average Cycle Time = Average WIP / Average Throughput</em></strong></blockquote><p>Even if you’re not good with numbers, this makes sense if you think about it. If you have more work in progress in your system, this will cause a team to context switch and multitask. Productivity will drop as the team will juggle multiple items simultaneously, meaning everything takes longer.</p><p>Instead, set WIP limits to focus on one or two items at a time. By setting and keeping to WIP limits, you will stabilise your flow, hopefully causing your cycle time to drop.</p><p>If you’re seeing widening bands, take action before your cycle start to seriously increase. Some of the questions to ask:</p><ul><li>Do the team have WIP limits and are they sticking to them? What are your policies for temporarily breaking WIP limits? Do you need to adjust (ideally lower) your limits?</li><li>Are there external pressures? Are tasks being pushed on the team by management instead of pulled by the team?</li><li>Are there issues with your system at specific points? Are you experiencing issues with your flow?</li></ul><h3>Narrowing bands</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SUDNgfMoYkkAjRhz.png" /></figure><p>Narrowing bands will probably be showing you the opposite of widening bands. Too little work is flowing in or to specific states within your system. It is possible items are jumping a state in the system, Or there could be a blockage that is starving another part of your system.</p><p>If you’re seeing narrowing bands, look out for the following:</p><ul><li>Have you set up your system in the best way? Are items able to flow through with clear policies in place? Is every state needed?</li><li>Do you need to set up queuing states within each state, for example, ‘doing’ and ‘done’? By setting up done stages for each state, you can more easily identify blockages and other issues with your flow.</li><li>Are your WIP limits right?</li></ul><h3>Flat lines</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/977/0*nLy2u0YEtNzTrkxC.png" /></figure><p>If you spot flat lines on your CFD, it means there have been times of no activity for that state in your system. The longer the flat lines are, the longer the period of inactivity. Flat lines :</p><ul><li>Is there a reason why there would be a period of inactivity? Is there a public holiday or series of absences in the team?</li><li>Is there a blockage somewhere in the system which is affecting flow?</li><li>Do you have items aging above of your service level estimation (SLE). Your SLE will tell you on average how long it takes items to flow through your system.</li><li>Could you improve one part of the system to improve your overall flow? For example, if testing slows things down, could you put in new testing systems to speed things up?</li></ul><h3>A staircase</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/941/0*tGnkrctNOEi40Aw0.png" /></figure><p>If your CFD looks like a staircase, it probably means you’re delivering your work in specific batches or cycles. While this isn’t necessarily a problem in the short term, it could be holding things up downstream in your system. It can also create dependencies within your system, as people wait for a batch to become available before they start work.</p><p>Longer term, this is problematic as it can become harder to predict flow and estimate how long work takes to complete. From a product point of view, you want to get your increment out and in front of customers as early as possible. That way, you can start to get feedback and validate your assumptions around value.</p><p>Some questions you can ask:</p><ul><li>What can we control as a team to even our flow and release more quickly? What conversations do we need to have with other teams if this is out of our control?</li><li>Can we move to better and faster ways of testing and releasing?</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d2a7e98b400" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to read a cumulative flow diagram]]></title>
            <link>https://agilealex.medium.com/how-to-read-a-cumulative-flow-diagram-2900bd7f2b85?source=rss-272ebf135ae8------2</link>
            <guid isPermaLink="false">https://medium.com/p/2900bd7f2b85</guid>
            <category><![CDATA[flow]]></category>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[kanban-board]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[metrics]]></category>
            <dc:creator><![CDATA[Agile Alex]]></dc:creator>
            <pubDate>Sun, 27 Jun 2021 20:50:57 GMT</pubDate>
            <atom:updated>2023-08-15T09:09:30.160Z</atom:updated>
            <content:encoded><![CDATA[<p>Adopting Kanban ways of working can help to enhance your Scrum. If you want to learn more about Scrum with Kanban, a great place to start is by reading <a href="https://www.scrum.org/resources/suggested-reading-professional-scrum-kanban">Scrum.org’s recommended reading list</a> for their <a href="https://www.scrum.org/professional-scrum-with-kanban-certification">Professional Scrum with Kanban</a> training.</p><p>One of the benefits of flow-based systems is the real-time data and metrics on performance. Moving away from burndown charts towards flow metrics gives a team more transparency about what is going on. It will also help you to forecast more effectively — by moving from deterministic to probabalistic mindset and ways of working.</p><p>One of my favourite tools is <a href="https://actionableagile.com/">ActionableAgile</a>, which I use as a <a href="https://azure.microsoft.com/en-us/services/devops/">Microsoft Azure DevOps</a> plugin. This plugin gives rich data insights on a range of flow metrics. For our purposes here, I’ll show you some of the metrics we get straight out of DevOps without ActionableAgile.</p><p>A cumulative flow diagram (CFD) is a visual representation of how healthy your flow is. It can tell you much about how a team is performing — if you know what to look for. It can be a powerful topic for a team retrospective. A CFD also brings together all the essential flow metrics into one place: cycle time, throughput, work in progress and work item age.</p><p>When a team is performing well, the ideal CFD shows you a steady growth of completed work. A CFD will give you good retrospective insights for the team to discuss flow. When problems start to arise, you can begin to spot them. A team can then start to have the right conversations and work to resolve them in a retrospective. For Scrum teams, a CFD only really works for a retrospective as it only looks back. Therefore it’s not a useful tool for sprint planning.</p><p>This graph is a CFD from my current team. The x-axis is time, and the y-axis is each product backlog item (PBI). I’ve annotated the metrics to look out for, which I have explained in a bit more detail below. There are a few important things to understand here, particularly how ActionableAgile works.</p><ul><li>A CFD shows when a PBI enters a state in your workflow. It counts as an arrival, rather than a departure into that point in your process. This makes most sense if you think about the end of your workflow or the done state. As a PBI will never leave done, we’re counting the arrival into that point.</li><li>I’ve not wanted to make the chart below too wordy. Technically, wherever you see the word ‘average’ you should read ‘approximate average’. I’m not going to go into why here, though chapters 4 and 5 in Daniel Vacanti’s excellent <a href="https://actionableagile.com/resources/publications/aamfp/">Actionable Agile Metrics for Predictability</a> explains it better than I ever could.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sykWWcesSaBHBaBD.png" /></figure><p>The top band in the graph shows new work coming into the system. The bottom band shows closed work leaving the system. Each band in between shows the different states or columns on the Kanban board. When someone pulls a PBI into a column from the queue, it enters an active state, and it remains active until it is done or closed.</p><p>With all these metrics, the overall goal is to limit your WIP, which should then help to reduce cycle times. In Scrum terms, this will help you achieve your sprint backlog, or throughput.</p><p>Kanban is counterintuitive that way — limiting your WIP and working in smaller batches will mean your team can do more while delivering results faster. <a href="https://www.tastycupcakes.org/2015/07/penny-flow/">The pennies game</a> shows this concept well and is an good aid as a game to play with your team if they are sceptical about WIP limits.</p><p>There are three key metrics we can understand from this chart. For our purposes, I’m not going to explain how to work these out manually. If you use DevOps or a similar system, the tool will work this out for you. However, a word of caution here. Inbuilt reports are either poorly setup or communicate entirely wrong thing. Jira is notorious for this. For all my metrics, I exclusively use ActionableAgile and would highly recommend you do the same.</p><p>A few reflections on flow metrics and CFDs.</p><h3>Throughput</h3><p>Throughput is the number of PBIs delivered over a set period. As a Scrum team working on sprints, we use a throughput metric to review how much work we delivered in a sprint. This helps us have some of the right expectations on committing to work in the future. I wouldn’t use a CFD to try to calculate throughput in the future — I’m not actually sure you could do that. Remember a CFD is used to look backwards, not forwards. You could use a CFD to try to see why your throughput has fallen. If you’re looking forward, aMonte Carlo Simulation is a useful tool to help answer the question around how many items can be done in a given time period, like a sprint.</p><h3>Work in progress (WIP)</h3><p>WIP shows the number of PBIs active in your system. To help maintain a healthy flow, Kanban uses WIP limits as a cap for the number of PBIs in your system. WIP limits help regulate the flow, by forcing the team focus on a few items at a time. If you use separate WIP limits for different stages in your flow, the total WIP should be the same as all your individual WIP limits combined.</p><p>When looking at a CFD, you want your arrival rate to run parallel with your departure rate. This will show you that work is entering your system at roughly the same rate as it is leaving. In our case, this is the number of items actively being worked on vs actively leaving. We don’t have a WIP limit for our backlog. This is because our backlog is the step before we have committed to any work, before our start point.</p><p>If the lines widen over time, it could indicate too much work is entering the system and breaking your WIP limits. There is a risk of your throughput will drop as the flow starts to become less controlled, making your system less stable.</p><h3>When to use your CFD</h3><p>As a ‘live’ chart, a Scrum team can use a CFD as a mirror to check team performance at any point. As a tool to diagnose operational problems, it can be invaluable.</p><p>These metrics the most useful (maybe really only useful) in a sprint retrospective. It can be a great starting point to discuss performance over the sprint and what the team can do to improve the performance. Reviewing a CFD together in a retrospective and pinpointing issues can be a good tool as a conversation starter.</p><p>Overall, a CFD will show the how healthy your flow is and therefore, the overall stability of the system. We want stable systems as we want to use metrics to forecast. A predictable system means better quality data and therefore gives you the ability to forecast within an agreed framework of risk.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2900bd7f2b85" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I passed Scrum.org’s Professional Agile Leadership I Certification]]></title>
            <link>https://agilealex.medium.com/how-i-passed-scrum-orgs-professional-agile-leadership-i-certification-c6769412f169?source=rss-272ebf135ae8------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6769412f169</guid>
            <category><![CDATA[scrumorg]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Agile Alex]]></dc:creator>
            <pubDate>Sun, 27 Jun 2021 20:48:42 GMT</pubDate>
            <atom:updated>2021-06-27T20:48:42.518Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*niboHQzI4fHuLMWM1EBZUA.jpeg" /></figure><p>The Professional Agile Leadership I (PAL I) from Scrum.org is one of two certifications in their agile leadership stream. Scrum.org describes this for ‘anyone who wishes to validate that you are a leader who understands that being Agile adds value to your business, and why leadership understanding, sponsorship, and support of Agile practices are essential to an organization becoming more agile.’</p><p>The other certification in the leadership stream is the <a href="https://www.scrum.org/assessments/professional-agile-leadershiptm-evidence-based-management-certification">Professional Agile Leadership — Evidence-Based Management (PAL-EBM)</a>. I was one of the first to take and pass the PAL-EBM certification and have <a href="https://www.agilealex.com/how-i-passed-the-pal-ebm-certification/">blogged about my experience</a>. Like the PAL-EBM, in my view, this is not an easy exam to pass. You are required to understand several important principles then apply them to different situations.</p><h3>The training course</h3><p>I am a product owner and was aware of some of the concepts already. For this certification, I took a class hosted by the course stewards, Ryan Ripley and Todd Miller, who run <a href="https://agileforhumans.com/">Agile for Humans</a>. It was a great class, and I recommend their course. I love these guys and all the great content they put out there, including their <a href="https://www.youtube.com/agileforhumans">YouTube channel</a>.</p><p>The Professional Agile Leadership Essentials (PAL-E) course sets you up well to pass the PAL I. Like the Professional Scrum Master II course, it is primarily scenario based, with a good amount of discussion time around how to deal with different situations. This is all from being a leader in an organisation and creating a culture that fosters agility.</p><p>The training course and certification frames nearly all the content around a number of key principles. If you use these points as a north star, it will help to answer the questions in the exam correctly:</p><p>1. Understand the role of management in Scrum. There’s no ‘us and them’­ in an agile organisation. Everyone is responsible for the outcomes and the quest for customer value. The role of management is to set clear goals and promote good behaviours to let agility flourish.</p><p>2. Always favour self-management. <a href="https://scrumguides.org/">The Scrum Guide</a> talks about this in more detail, though in every situation, do anything you can to encourage Scrum teams and members to self-manage. This doesn’t mean a team operates in a vacuum, divorced from a company strategy or vision. Instead, it is about living <a href="https://www.scrum.org/resources/scrum-values-poster">the Scrum values</a> and pushing a team to work to ensure they manage their work to deliver on a sprint goal, for example, rather than having management dictate to them.</p><p>3. Empower the team. Linked to the above, the Scrum Guide does not say there is no role for management or that Scrum teams are lone wolves, picking and choosing their work. The Scrum Guide instead sets a framework for how the Scrum Team should work. Depending on the context, managers outside the Scrum team might develop a culture and framework to help them in their work. In another context, it might mean management steps in to help remove impediments. Either way, the role of a leader is to empower the protect the agency of the team.</p><p>4. Foster an experimentation mindset. The EBM guide is focused on this concept. Empiricism is all about gaining knowledge from experience and making the right decisions based on what you see. It helps you to take meaningful steps to deal with complex problems. Those problems can be anything we encounter — different types of risk, new technologies, changing markets and more. Remember what you need to apply an empirical approach: it’s about forming a hypothesis, running an experiment, validating that hypothesis and then repeating. You don’t know whether something is true until it is released and validated by your customer. Running experiments will help you gather insights and plan your next step.</p><h3>How I prepared</h3><p>The first and the best thing you can do is read and re-read both the Scrum Guide and <a href="https://www.scrum.org/resources/evidence-based-management-guide">The Evidence-Based Management Guide</a>. It is foundational to everything covered in the course. You should be able to recite both of them. Make sure you understand the EBM principles: the types of goals, key value areas and when they are used, along with the different metrics and when you should use them.</p><p>When you set up a Scrum.org account, <a href="https://www.scrum.org/pathway/agile-leader-learning-path">the agile leader learning path</a> contains a number of useful resources, which you can track as you complete each item. <a href="https://www.scrum.org/open-assessments/agile-leadership-open">The agile leadership open assessment</a> is also relatively useful, though the pool of questions is quite basic and limited. You should keep taking this over and over again until you score 100% consistently.</p><p>I would also recommend taking a class. The opportunity to hear from other people in different contexts is something you can’t replicate from self-studying for this. This course is useful for anyone in a Scrum team, particularly for anyone outside, particularly trying to work out the best way to lead for agility.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c6769412f169" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why a Definition of Ready?]]></title>
            <link>https://agilealex.medium.com/why-a-definition-of-ready-800300edd36?source=rss-272ebf135ae8------2</link>
            <guid isPermaLink="false">https://medium.com/p/800300edd36</guid>
            <category><![CDATA[definition-of-ready]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Agile Alex]]></dc:creator>
            <pubDate>Tue, 08 Jun 2021 18:39:25 GMT</pubDate>
            <atom:updated>2023-06-09T08:43:38.697Z</atom:updated>
            <content:encoded><![CDATA[<p>A Definition of Done (DoD) is an essential requirement for a Scrum team. The Scrum Guide says that a product backlog item (PBI) becomes an increment once it has met the DoD. Put simply:</p><p>PBI + DoD = increment</p><p>After spending time as a team working to define our DoD, another question came up. Should we have a Definition of Ready (DoR) and if so, when and why? We went back to the Scrum Guide for guidance, though we didn’t find a clear answer.</p><blockquote>Product Backlog items that can be Done by the Scrum Team within one Sprint are deemed ready for selection in a Sprint Planning event. They usually acquire this degree of transparency after refining activities. Product Backlog refinement is the act of breaking down and further defining Product Backlog items into smaller more precise items. This is an ongoing activity to add details, such as a description, order, and size. Attributes often vary with the domain of work.</blockquote><p>The Scrum Guide raised more questions for our team than answers. How should we refine items to make sure they can be ready for selection? How can we be sure that something is refined enough? How can we refine PBIs well with both the development team and product owner (PO)?</p><p>Scrum is based on empiricism: knowledge comes from experience and making decisions now on what is known. In a complex environment, we won’t always have all the answers straight away. The three pillars of transparency, inspection and adaptation hold Scrum together and underpin empiricism. To help get us to a point where the team can accept a PBI into a sprint, we need three things:</p><ol><li>As the Scrum Guide above says, it needs to be small enough to be done in one sprint.</li><li>It must be sized by the development team so the overall product backlog can be understood as a whole.</li><li>It needs enough detail in the description so the development team can understand what is needed. The development team needs the detail to make a good forecast (meeting point 2).</li></ol><p>Other than these three points, the Scrum Guide doesn’t say very much. It also doesn’t mandate any form of a DoR or even the idea of one. That’s up to the team to decide.</p><p>Our development team needed more. They wanted to have a codified DoR to ensure the PO was giving them enough ahead of any commitment. We created a DoR using a variation of William Wake’s INVEST checklist, which came out of his excellent <a href="https://www.goodreads.com/en/book/show/67841.Extreme_Programming_Explored">book on Extreme Programming</a>. While originally created to help validate user stories, we used an adapted version for our PBIs. We often use user stories in our PBIs, though not always. It helped keep me as a PO focused on creating good PBIs.</p><p>INVEST stands for:</p><p>Independent: of all other stories. Can this PBI be delivered independently?</p><p>Negotiable: does the PBI give the development team the creativity to come to a solution by themselves? Does the PBI include the essence of the requirement, empowering the development team to define the details?</p><p>Valuable: this is essential for any PO. Will this deliver value to our customers. Do they want this?</p><p>Estimable: does the development team have enough information to estimate the amount of work needed?</p><p>Small: is the PBI small enough for the development team to deliver in one sprint or does it need to be broken down further?</p><p>Testable: can the team test this? This might either be with an existing test or one which could be created in the future.</p><p>Our new DoR based on INVEST became the standard in our refinement sessions. Having this DoR also prompted some excellent conversations. For example, if the team didn’t have enough information to estimate, I would make sure they had enough. If a PBI’s value couldn’t be defined, the team would discuss its value or I, as a PO, would have to explain it.</p><p>Having this DoR also improved the quality of our sprint backlog, our sprint reviews and ultimately, our increments. It gave the team more confidence in committing to PBIs and meant we took more work into the sprint, which was then delivered, giving us a good increment to inspect.</p><p><strong>A DoR and Kanban</strong></p><p>In our Scrum evolution towards including more Lean principles in the way we work, a DoR served another purpose. Like the Scrum Guide, the Kanban Guide doesn’t have any reference to a DoR (nor would you expect it to). In Kanban terms, we see the DoR as an entry policy of our workflow. Moving something to ‘ready’ means it enters our system and the cycle time clock starts ticking. Like having a DoD, I don’t believe there is any incompatibility here between Scrum and Kanban. Our DoR is final check before something enters the system, through a clear policy in our Kanban Definition of Workflow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=800300edd36" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why a Definition of Done?]]></title>
            <link>https://agilealex.medium.com/why-a-definition-of-done-f7b60866878b?source=rss-272ebf135ae8------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7b60866878b</guid>
            <category><![CDATA[definition-of-done]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Agile Alex]]></dc:creator>
            <pubDate>Tue, 08 Jun 2021 17:16:14 GMT</pubDate>
            <atom:updated>2023-06-09T08:42:42.509Z</atom:updated>
            <content:encoded><![CDATA[<p>Our team recently moved over to a new way of working, bringing <a href="https://www.agilealex.com/how-we-transformed-our-scrum-with-kanban-part-1/">Kanban into our Scrum</a>. As we reviewed our entire working processes, one question came up quite early on in our discussion: why and when should we create our Definition of Done (DoD)?</p><p>Some of the team wanted to wait for a sprint or two. The thinking was to go through a cycle, understand how the team will work internally and interact with our systems and stakeholders. Once we had that understanding, they then wanted to start to define some essential standards and aspects to make up a DoD.</p><p>Being a Scrum team, we went to the Scrum Guide to find the answer. We quickly concluded we needed something as soon as possible. On the DoD, the Scrum Guide says:</p><blockquote><em>The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.</em></blockquote><blockquote><em>The moment a Product Backlog item meets the Definition of Done, an Increment is born.</em></blockquote><blockquote><em>The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment. If a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at the Sprint Review. Instead, it returns to the Product Backlog for future consideration.</em></blockquote><blockquote><em>If the Definition of Done for an increment is part of the standards of the organization, all Scrum Teams must follow it as a minimum. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product.</em></blockquote><blockquote><em>The Developers are required to conform to the Definition of Done. If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done.</em></blockquote><p>As we started to understand the purpose of a DoD, we standard to discuss and answer the following questions.</p><p><strong>Who creates the DoD?</strong></p><p>Interestingly the guide doesn’t say who must create that DoD; only you need one. From experience, I’ve seen instances where the organisation has a DoD, which all teams must use. In other cases, I’ve seen teams empowered to define their own locally. In general, I have found it to be more mixed. Often the organisation will set its own DoD, with the team adding their requirements as needed to fit their context.</p><p><strong>Why do you need a DoD?</strong></p><p>Having a DoD means everyone in the team knows what is expected from them and what standard to deliver work. Having a clear DoD fosters transparency and means the team works to fit the broader organisation while maintaining quality.</p><p>Therefore, if an increment doesn’t meet the DoD, it’s not done and shouldn’t be presented in a Sprint Review. It would go back into the product backlog for further work or refinement, to be worked on in the next or a future sprint.</p><p>The overall purpose of a Scrum team is to deliver the Product Goal. ‘An increment is a concrete stepping stone toward the Product Goal’. Having and following a DoD will give you foundational solid blocks as you deliver each increment and work to achieve your Product Goal.</p><p>As a product owner (PO), a DoD is essential for many reasons. First, it will clarify quality and what could be accepted at a Sprint Review by you. Having these common standards will aid the development team, ensuring any code which doesn’t follow the DoD is rejected. This will help ensure the team focuses on delivering quality, keeping technical debt to a minimum. If you rack up technical debt, it will cost you more in the future to maintain your product. Even worse, you may not be aware you’re building technical debt up until problems start to emerge.</p><p><strong>When should you create your DoD?</strong></p><p>As early as possible, ideally in your first sprint. Remember, the moment a product backlog item meets the DoD, an increment is born. If you’re following Scrum, you need that DoD if you want to have an increment. It will also give everyone a shared understanding along with a meaningful Sprint Review.</p><p><strong>What should your DoD include?</strong></p><p>That will depend on your team and context. It will also depend on how your PO works and how their product backlog is defined.</p><p>If you are a feature team, you will likely focus on what you need to do to get your increment into the next release. Your DoD could then include a range of testing processes, the creation of documentation, integration requirements, compliance requirements and more.</p><p>If you use user stories, you might include acceptance criteria, code reviews, testing or even the PO themselves finally accepting the user story.</p><p>I’ve also seen teams have a DoD at an epic level, which helps focus on quality and standards at that higher level. Teams here might include standards around end-to-end integration, testing (often regression testing), entry into a production environment and more.</p><p>While all of the above are just examples, with teams including much more in their DoDs, one important thing to remember is to inspect and adapt your DoD often. Your DoD in sprint 1 probably shouldn’t look the same as your DoD in sprint 10 or 20. As the team becomes more comfortable working together, and as the product starts to emerge and then evolve, your standards will probably increase. You might choose to make your DoD stricter to raise quality and reduce technical debt.</p><p>In true Scrum spirit, nothing is perfect the first time, if ever. We continually inspect and adapt, working as a team to evolve and iteratively improve what we have. The same is true for the DoD. It’s an ongoing conversation for the whole team. It’s a great way of building transparency too.</p><p><strong>A DoD and Kanban</strong></p><p>We’re increasingly moving over to Lean principles in the way we work. The Kanban Guide doesn’t have any reference to a DoD, in the way the Scrum Guide does. However, in Kanban terms, we see the DoD as an exit policy of our workflow. Moving something to ‘done’ means it exits our system and the cycle time clock stops ticking. There is no incompatibility here between Scrum and Kanban: our DoD is our handoff or exit policy to the ‘done’ column.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7b60866878b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I passed Scrum.org’s PSPO III certification]]></title>
            <link>https://agilealex.medium.com/how-i-passed-scrum-orgs-pspo-iii-certification-3f0c44576b8a?source=rss-272ebf135ae8------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f0c44576b8a</guid>
            <category><![CDATA[scrum-product-owner]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[pspo-iii]]></category>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[scrumorg]]></category>
            <dc:creator><![CDATA[Agile Alex]]></dc:creator>
            <pubDate>Wed, 28 Apr 2021 11:30:48 GMT</pubDate>
            <atom:updated>2021-05-05T10:40:48.485Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3V97_o299Bfs823SOcICQA.png" /></figure><p>The <a href="https://www.scrum.org/professional-scrum-certifications/professional-scrum-product-owner-iii-assessment">Professional Scrum Product Owner III (PSPO III)</a> certification is Scrum.org’s top certification for Product Ownership. It’s both hard to pass and quite different in style from the others in its family. I found this a very tough exam. At the time of writing, there are only 365 holders of the PSPO III. Out of over 529,000 scrum certificates, just 0.07% of all certificates are PSPO III. Worthier people have no doubt tried and failed to accomplish this. I thought I had failed the exam after the time ran out, though I found out three weeks later I had passed.</p><p>The exam consists of both multiple choice and essay questions. Other people who have sat the exam before have said the exam is primarily multiple choice. I can confirm other reports from people from the start of this year. When the updated Scrum Guide 2020 arrived, the exam changed to reflect the update and make this exam much harder. For my exam, I had 20 multiple choice and 15 essay questions. The number of essay questions has gone up.</p><p>The multiple choice questions themselves are broadly similar to those found in the PSPO II exam. You need to understand the Product Owner (PO) role, how to maximise the value of a product and apply everything you’ve learnt to real world situations. I had some questions about how the PO interacts with a scrum master and development team, along with questions you should be able to answer from the Scrum Guide.</p><p>The essay questions are where things got more interesting. I’ve not sat the Professional Scrum Master III exam (yet), and this style of exam was new to me. These questions spanned quite a wide field of subjects. The skill here was being able to context switch very quickly to answer the questions. There is an expectation for different questions, you will be to:</p><ol><li>Answer the theory</li><li>Apply that theory to specific case studies given in the question</li><li>Sometimes, add specific examples from your own experience.</li></ol><p>Hearing other people’s experiences passing the PSPO III this year, my pool of essay questions seemed different. There doesn’t seem to be a consistent pattern of how these questions are chosen. While I’m not going to share the questions themselves, my essay questions broadly fell into the following categories:</p><ul><li>Understanding and defining value</li><li>Product backlog management and making decisions on how to maximise a product’s value</li><li>Key Value Areas from the <a href="https://www.scrum.org/resources/evidence-based-management">Evidence-Based Management Guide (EBM)</a></li><li>Scrum artefacts and how a PO and scrum team should use them</li><li>The PO and the relationship with other members of the scrum team, along with stakeholders outside the team</li><li>Technical debt and how that can impact a PO and your product.</li></ul><h3>How I prepared</h3><ul><li>Read the <a href="https://scrumguides.org/scrum-guide.html">Scrum Guide</a>. It goes without saying you should be able to recite this in your sleep. The EBM is another essential guide to know very well. I would then strongly suggest being very familiar with the <a href="https://www.google.com/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=&amp;cad=rja&amp;uact=8&amp;ved=2ahUKEwizmvqR5aDwAhWcXRUIHZTrBjQQFjAAegQIBBAD&amp;url=https%3A%2F%2Fwww.scrum.org%2Fresources%2Fkanban-guide-scrum-teams&amp;usg=AOvVaw0ggdJmvLo8osl_6v_9OTrO">Kanban Guide for Scrum Teams</a> and the <a href="https://www.google.com/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=&amp;cad=rja&amp;uact=8&amp;ved=2ahUKEwjUjKae5aDwAhVWaRUIHU_rAKAQFjACegQIBhAD&amp;url=https%3A%2F%2Fwww.scrum.org%2Fresources%2Fnexus-guide&amp;usg=AOvVaw0v5zXXAJU88VLGYJoZjEiV">Nexus Guide</a>.</li><li>I took both the PSPO I and PSPO Advanced training courses in the past. These were excellent. Though, as I took both classes a few years ago, I started by brushing up on the content we covered.</li><li>Completing and knowing every part of the Product Owner Learning Path in your Scrum.org profile.</li><li>My core reading list included (there were many more books):</li><li><a href="https://www.scrum.org/resources/professional-scrum-product-owner-book">The Professional Product Owner: Leveraging Scrum as a Competitive Advantage</a> by Don McGreal and Ralph Jocham</li><li><a href="https://www.scrum.org/resources/zombie-scrum-survival-guide-0">Zombie Scrum Survival Guide</a> by Johannes Schartau,Christiaan Verwijs and Barry Overeem. This is a great book, even if you think you are a high performing team.</li><li><a href="https://books.google.co.uk/books/about/Scrum_Insights_for_Practitioners.html?id=c6ghMQAACAAJ&amp;redir_esc=y">Scrum Insights for Practitioners: The Scrum Guide Companion</a> by Hiren Doshi</li><li><a href="https://www.goodreads.com/book/show/13589272-software-in-30-days">Software in 30 Days</a> by Ken Schwaber and Jeff Sutherland</li><li><a href="https://www.mountaingoatsoftware.com/books/user-stories-applied">User Stories Applied: For Agile Software Development</a> by Mike Cohn</li><li><a href="https://anthonyulwick.com/publications/">What Customers Want</a> by Anthony Ulwick</li><li><a href="https://simonsinek.com/product/start-with-why/">Start with Why</a> by Simon Sinek</li><li><a href="http://theleanstartup.com/">The Lean Startup</a> by Eric Reis</li><li><a href="http://leanuxbook.com/">Lean UX</a> by Jeff Gothelf and Josh Seden</li></ul><p>There are many other books on product management which I have found very useful. <a href="https://productcollective.com/best-books-for-product-managers/">This recent article</a> from the Product Collective lists many of them. I also love both of Marty Cagan’s books <a href="https://svpg.com/inspired-how-to-create-products-customers-love/">Inspired</a> and <a href="https://svpg.com/empowered-ordinary-people-extraordinary-products/">Empowered</a> on product management. While they may not directly help you in answering an exam question on Scrum, every product manager should read them. They deserve a special mention as they are excellent.</p><h3>Some tips as you sit the exam</h3><ul><li>I followed the advice many people have given in the past on passing either of the essay exams. Answer all the multiple choice questions first and skip the essay questions. I was hoping for only a handful of essay questions, and I was very disappointed! It took me around 40 minutes to answer all the essay questions, leaving me around 1 hour 20 minutes to answer the essay questions. That was then a little over five 5 minutes per essay question. This is not much time at all, and you’ll be stunned just how quickly 2 hours flies past.</li><li>Have a timer and give yourself 3–4 minutes per question. You’ll need a minute to think and review your answer afterwards.</li><li>Don’t overthink the question, and make sure you answer every part. Answer the theory and then if they ask about your own experience, make sure you include it.</li><li>Practice and get used to typing for 2 hours.</li><li>Practice typing out short, sharp answers to questions. They’re looking for concise rather than wordy answers. Less is more.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f0c44576b8a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>