<?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 Dan Gutman on Medium]]></title>
        <description><![CDATA[Stories by Dan Gutman on Medium]]></description>
        <link>https://medium.com/@dannygut?source=rss-2b91f82defda------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*C9_4_2vV6Gdn2v4lXhsKKg.jpeg</url>
            <title>Stories by Dan Gutman on Medium</title>
            <link>https://medium.com/@dannygut?source=rss-2b91f82defda------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 02:23:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dannygut/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[Does Working in Sprints Accelerate Delivery?]]></title>
            <link>https://blog.devgenius.io/does-working-in-sprints-accelerate-delivery-e78d4cf1394b?source=rss-2b91f82defda------2</link>
            <guid isPermaLink="false">https://medium.com/p/e78d4cf1394b</guid>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[sprint]]></category>
            <dc:creator><![CDATA[Dan Gutman]]></dc:creator>
            <pubDate>Sun, 12 Jul 2020 08:43:19 GMT</pubDate>
            <atom:updated>2020-07-13T10:59:37.038Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*npVV4ZlKLDT6wAGTJVvZmQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@laurinebailly?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Laurine Bailly</a> on <a href="https://unsplash.com/s/photos/running?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>One of the things most associated with Agile is working in sprints. But do sprints actually enable you to deliver faster?</p><p>Let’s say you’re a runner moving towards a destination which is 42k away. Does it make sense to break it down to 42 legs of 1k and run each at full speed? Or is it faster and more efficient to run it in a steady marathon pace?</p><p>Many people like ‘sprints’ because it captures two desirable traits: Speed and Focus. Speed appeals to those who want to accelerate delivery, usually management. “With Agile we will deliver twice as much in half of the time”. Whereas, focus appeals to developers, who during a sprint, can focus on getting their work done without changes in priorities.</p><p>But does running in sprints get us faster to our destination? Or does it make us exhausted?</p><p>If you’re running on a known and predictable path, sprints are not going to make a difference. The fastest and most efficient approach is to pace yourself at a steady speed.</p><p>But in real life, we live in a complex and constantly changing world. And for most teams, the path they’re walking on is not clear, nor is their exact destination.</p><p>So why does sprinting work well in this case?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kDkSUQmC2FUzWp8qoHYYVA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@theexplorerdad?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Joshua Ness</a> on <a href="https://unsplash.com/s/photos/reach-destination?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>The power of sprints comes less from what happens during the sprints, and more from what happens between them. These are the moments where you stop, reflect and decide to make adjustments or to change direction — the moments where you sense and adapt.</p><p>If you’re running sprints without stopping to regroup, If in each iteration you’re running with the same shoes, on the same surface and towards the same direction, then you’re not agile, you’re just making yourself exhausted.</p><p>Many teams that adopt Agile are quick to utilize working in sprints and executing the ceremonies associated with it. But they fail to understand that this is not enough.</p><p>Working in Agile requires a shift in mind. <br>When you understand that the power is in the breaks between the sprints, in the action of sensing and adapting, then you start running differently. It becomes less about being faster and stronger to cover more distance. And it becomes more about learning, and choosing a path that will generate more meaningful reflection and insights at its end.</p><p>“In this sprint, instead of keeping running straight, I would climb up this hill. I would try these new running shoes and would attempt the new stretching exercises that I have just learned.<br>This hill would be a perfect spot to get a better view of my surroundings and to reflect on my journey so far, and on my final destination. I will contemplate if my new shoes boosted my pace and if my new stretching exercises helped me to have a less painful and a more sustainable journey.<br>Based on what I’ll learn, I will plan my next sprint, the next leg of my journey.“</p><p>Working in this manner feels more like a journey of exploration, where learning becomes the most important thing. And the wisdom that you gain through this learning process is what guides you faster to achieve your goals.</p><p>If you work in sprints, ask yourself:</p><ul><li>Is your main focus is to build things, or is it to validate, learn and explore?</li><li>Is your next iteration a direct continuation of the previous one, or do you use what you’ve learned to adapt and enhance your plans?</li><li>Do you use the same tools and processes that you have used before, or do you try out new improvements every sprint?</li><li>Do you reach the exact destination that you set out in the beginning, or do you change course along the way to arrive in a better place?</li><li>Do you feel exhausted and out of breath, or do you feel motivated and intrigued?</li></ul><p>Working in sprints doesn’t necessarily mean that you accelerate your delivery. But it means that you accelerate your learning, and this accelerates the time that it takes you to find and reach your destination.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cLM2cTJ9FAdVJsRFqAUTng.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@missnjc?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Natalie Grainger</a> on <a href="https://unsplash.com/s/photos/reach-destination?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e78d4cf1394b" width="1" height="1" alt=""><hr><p><a href="https://blog.devgenius.io/does-working-in-sprints-accelerate-delivery-e78d4cf1394b">Does Working in Sprints Accelerate Delivery?</a> was originally published in <a href="https://blog.devgenius.io/">Dev Genius</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[PI Planning — How to align multiple Agile Teams]]></title>
            <link>https://medium.com/@dannygut/pi-planning-how-to-align-multiple-agile-teams-c6f320f3af65?source=rss-2b91f82defda------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6f320f3af65</guid>
            <category><![CDATA[scaled-agile-framework]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[planning]]></category>
            <dc:creator><![CDATA[Dan Gutman]]></dc:creator>
            <pubDate>Fri, 29 May 2020 06:28:38 GMT</pubDate>
            <atom:updated>2020-05-29T06:28:38.637Z</atom:updated>
            <content:encoded><![CDATA[<h3>PI Planning — How to align multiple Agile Teams</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CQy8pUqjIKLftbxA_RmjMA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@shwetha?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Shwetha Shankar</a> on <a href="https://unsplash.com/s/photos/birds-flying?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>How do you coordinate multiple Agile teams working on the same value stream? How do you align them to the same purpose? How do you plan their work for the next quarter or the next major release?</p><p>These are difficult questions faced by many organizations. In reality, teams often push in different directions. They have different understandings of the vision and purpose, which lead to different goals and priorities.</p><p>PI (Program Increment) Planning is a SAFe practice that aims to tackle these issues. It brings into one big room all the members of an Agile Release Train, face to face, for two days. During this event, the teams align on a shared mission and plan their objectives for the next quarter together. You don’t need to be a SAFe practitioner to benefit from this practice. You can borrow and adapt it to align, coordinate and plan the work of multiple teams practicing any form of Agile.</p><p>I won’t go into the details of how to run this event. You can get this information directly from the SAFe website: <a href="https://www.scaledagileframework.com/pi-planning/">https://www.scaledagileframework.com/pi-planning/</a></p><p>As an Agile coach or an RTE, it is quite a complicated event to organize and facilitate. In this post, I’d like to share my experience of what helped me to make this practice more impactful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pTfq_nxyrKs5zijF2VGKSg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@joshcala?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Josh Calabrese</a> on <a href="https://unsplash.com/s/photos/team?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>The main goal of the event is to create alignment. Alignment to a shared purpose, to shared objectives and shared priorities. What I got wrong in the beginning was that I focused too much on the planning aspect of the practice. And that came at the expense of reaching alignment.</p><p>How does a planning-focused PI planning look? <br>The main goal is to plan and commit to the work in the next three months. The room will be relatively quiet, as each team focuses most of its time in planning: breaking down their stories, estimating, and trying to fit work into sprints. The pressure is to get more detail, which presumably will lead to more confidence in the plan. In practice, the teams will often run out of time, they won’t get their desired level of detail, and as a result, they would feel less confident about the plan. There won’t be a lot of interaction between the teams. And issues and dependencies will surface relatively late on the day, with little time to resolve them.</p><p>The issue is that this kind of planning is wasteful. Once the teams start their work, they are bound to find new information that will alter their plans. And this raises the question of “why should we do PI planning in the first place?” These uneasy feelings came to me in the first couple of times that I ran this event. And then I realized that I was focusing on the wrong thing.</p><p>So how does an alignment-focused PI planning look? <br>The main goal is to reach alignment and to commit to shared objectives. There will be much more energy in the room and a lot of interactions between the teams. The teams will spend less time planning their work, and more time engaging with other teams and stakeholders, working to resolve their risks, issues and dependencies.</p><p>And the result? The teams will be more aligned. They might not have a detailed backlog at the end of the day, but they will have a good idea of their priorities, and how to approach their risks and dependencies. They will have a better understanding of the plans and priorities of the other teams and how their own plan fits into the greater plan of the Release Train.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sm3jl3qNCcu6z8yJ1NVKYg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@joshcala?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Josh Calabrese</a> on <a href="https://unsplash.com/s/photos/team?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>So how can you move from a planning-based to an alignment-based event?</p><p>1- Reiterate that the purpose of the meeting is alignment. <br>At the beginning of the event and during the day, I reiterate the emphasis on alignment. “The purpose of this event is to gain alignment to a common, committed set of achievable outcomes for the next quarter and identify the things that we need to learn”. “The reason that everyone is in the same room is that we can collaborate and resolve our risks, dependencies and issues together”.</p><p>2- Focus the planning on the things that you need to learn. <br>In my instructions to the teams, I ask them to plan at a relatively detailed manner, the things that they need to learn. It includes planning how to build a functional walking skeleton to validate their solution, planning how to tackle their dependencies on other teams, stakeholders or technologies, and planning how to address their risks, challenges, assumptions, and unknowns. Then the rest of the planning, which includes building the functionality should be done only in high-level.</p><p>3- Connect and bring people together<br>When I facilitate during the day, I worry less about the teams completing their plans and more about bringing people together. If a team identifies a dependency, I urge them to connect and discuss it with the other team. If they identify risks or issues, I ask who will be the best people to help resolve it, and I bring these people together. I try to identify and make these connections as early as possible on the day. The reason is that I prefer that the teams focus most of their time collaborating with each other to resolve their issues, rather than concentrating on perfecting their own plans.</p><p>When I first ran it this way, the positive effect was evident. There was so much more energy in the room, and people seemed to be much more engaged. People felt more confident in the plan, and they formed better connections with their peers in the other teams. And these relationships were valuable as they started working on their objectives. For me, it felt for the first time that I did it in a way that felt right and aligned with my principles.</p><p>So have you ever facilitated an event similar to PI planning? How did it feel? What are the things that work for you and help you make it meaningful and impactful?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bHX4tRmTs8K3Jphuh7ucIA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@sergiferrete?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Sergi Ferrete</a> on <a href="https://unsplash.com/s/photos/birds-flying?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c6f320f3af65" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Things I Learned About Agile Transformation While Cooking Risotto]]></title>
            <link>https://medium.com/@dannygut/things-i-learned-about-agile-transformation-while-cooking-risotto-df3c1048efc9?source=rss-2b91f82defda------2</link>
            <guid isPermaLink="false">https://medium.com/p/df3c1048efc9</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Dan Gutman]]></dc:creator>
            <pubDate>Sun, 16 Jun 2019 08:22:02 GMT</pubDate>
            <atom:updated>2019-06-16T10:32:08.613Z</atom:updated>
            <content:encoded><![CDATA[<h3>Things I Learned About Agile Transformations While Cooking Risotto</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dNCl3XWReKkmFoJAJpQM7A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@julienpian?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Julien Pianetti</a> on <a href="https://unsplash.com/search/photos/risotto?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Have you ever gone through an Agile transformation where the Development Teams were doing their part, but Product Management and the rest of the Business kept holding to their old ways? Many see Agile as just implementing and running Scrum ceremonies. Instead of the Business being part of the process, it stays outside as a separate entity.</p><p>The Business owns the <em>Why</em>, which it keeps mostly to itself. It also owns the <em>What</em>, which it hands over to the Dev. And the Dev owns the <em>How</em>, which it keeps mostly to itself. The interaction from the Business to the Dev is done through shopping lists full of feature requests.</p><p>What’s wrong with handing over shopping lists?</p><p>I’m one of those people walking down the supermarket aisle with a shopping list, and I get small moments of gratification each time that I tick an item off the list. I usually know where everything is, and things go quite smoothly but every now and then I get an unfamiliar item on the list. The other night I had “Arborio rice” which I couldn’t find, so I ended up getting another type of rice. I was pretty happy with myself until I got home.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ORYDb1leEB20BtuR-AA-Jg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@artbysanaei?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Mohammad Sanaei</a> on <a href="https://unsplash.com/search/photos/supermarket?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>“Why did you get a Basmati rice? I specifically asked for Arborio rice,” my partner exclaimed. <br>To which I replied, “What’s the matter? I couldn’t find that Berborio rice so I brought this one instead.” <br>“But I’m making a risotto tonight, and it’s called Arborio.”<br>“Can’t you make a risotto with Basmati rice? It is rice after all”.<br>I couldn’t be more wrong, and I got the “how can you be so dumb” look from my partner. <br>“No, Basmati has a strong taste, and it wouldn’t give the same creamy texture needed for risotto. If you want to eat risotto tonight, you better go back to the shops”.</p><p>Why are we happy to hand shopping lists to our development teams and then be surprised when we get a Biryani for dinner instead of a Risotto?</p><p>A shopping list simplifies the interaction and creates a clear gameplan. It lets you focus on the doing, your area of expertise which you were hired for without getting bogged down in unimportant details such as “What dish are we cooking tonight?”, “Who is going to eat it?” and “What would be their experience?”.</p><p>The thing is that in software development, not only do we give shopping lists to our development teams to fetch the ingredients, we also expect them to make the dish. This could work if we are producing something known and predictable, like a dish that has been done for years, such a … risotto. We can write down the required ingredients and the exact recipe, and with someone paying attention to details (unlike myself), and a skilled and experienced chef (again unlike myself), we should make a creamy and delicious risotto.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EfAO9TBge5XNIvRejPaQKw.jpeg" /></figure><p>The problem is that there is nothing predictable in developing software and delivering products. It’s like trying to invent a new dish that has never been done before, and halfway through cooking, we change the ingredients, and we also need to figure out how to operate a brand new stove.</p><p>And yet many organizations are still happy to give shopping lists to their development teams with minimal business context and minimal business say. To make sure that the teams will deliver the right thing, the Business accompanies the list with an elaborate requirements document: “The dish must be creamy but not too thick.” “The grains shall be adequately smooth. Not too rough, but not too soft either.” The team will be cooking the dish according to the requirements, but oblivious to the fact that they’re actually making risotto.</p><p>And how will the development teams assess that they’re making the right dish? They will do so by testing what is known to them, which is the requirements document. They will come up with elaborate tests to verify that the dish is creamy and that the grains are acceptably smooth.</p><p>The Business people will look at the dish, and they won’t be happy with what they’re seeing which looks nothing like the risotto they had in mind. They will give the “how can you be some dumb” look to their development teams. Next, a blame game will start: Has the Business written the requirements precisely? Have the development teams interpreted and implemented them correctly?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A6AbKpSNKYUsZvK1_RX7qQ.jpeg" /></figure><p>In all this process, the Dev and Business would fail to do one crucial test. Anybody cooking knows that the ultimate test of a dish is… tasting. “Does it taste any good?” “Did I put enough salt?” “ Is it too spicy?” <br>Yet many organizations do not “taste” their products until it is released to the market. Then there is a big surprise when people don’t like the product or simply ignore it.</p><p>So how can we avoid this spiral road downhill?<br> <br>Let’s break down the silos between Business and Development. For Agile to properly work, the Business and Dev need to work together as one cohesive team.</p><p>Development Teams can be very productive, but if they don’t work closely with the business, they’re not being effective. They just keep delivering features that nobody likes or wants.</p><p>In many Agile teams, I see what I call proxy Product Owners. They get shopping lists from the Business, and they need to constantly validate and ask for approval for any decision they make. Genuine Product Owners thoroughly understand the business, seek constant feedback from stakeholders and customers, and are empowered to make decisions.<br> <br>Great Product Owners do not keep all the business context and decisions to themselves, but they share it with the team constantly. Otherwise, we haven’t really broken the silos. We just moved them to within the Agile team. Every member of the team should have empathy towards their target customers. They should understand how their own work contributes to achieving the customers’ and their organization’s goals.</p><p>Great Agile teams do not only test their product against acceptance criteria or any other form of requirements but they also “taste” their products. And they do it early and often. They build prototypes and MVPs, give them to their customers, and watch them use it. Then they use what they learned to adjust their products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SvJwzM_o9Y2M3X7UCzn8gA.jpeg" /></figure><p>So, next time you’re making risotto, don’t just send your partner to the shops with a shopping list. Make a list together. Sit down with them, tell them who is coming for dinner, and what you’re planning to make. And most importantly, while cooking let them taste the risotto. I’m sure they’ll be very pleased with that.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df3c1048efc9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Things I Learned about Agile Planning while Hiking]]></title>
            <link>https://medium.com/@dannygut/things-i-learned-about-agile-planning-while-hiking-61dd9194599f?source=rss-2b91f82defda------2</link>
            <guid isPermaLink="false">https://medium.com/p/61dd9194599f</guid>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[planning]]></category>
            <dc:creator><![CDATA[Dan Gutman]]></dc:creator>
            <pubDate>Sun, 31 Mar 2019 01:30:34 GMT</pubDate>
            <atom:updated>2019-03-31T01:30:34.349Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-j9Vb7Z5SEaWjqFPdJrBLQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/NkTOpVl7jJE?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Hanna Viellehner</a> on <a href="https://unsplash.com/search/photos/hiking?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Agile frameworks such as Scrum are good at prescribing short term planning such as sprint planning, but they don’t say much about long term planning such as release or quarterly planning. As an Agile coach I sometimes get asked: “Why do we need to plan our next release coming in 4 months? Isn’t that waterfall? I thought we’re working in Agile.” I have also encountered managers reluctant to move to Agile saying: “We got customers, we got commitments, we can’t just move to Agile and change things every two weeks.”</p><p><strong>So does working in Agile really means no planning?</strong><br>It may seem so looking in the Agile manifesto, where it states: “Responding to change over following a plan.” But paying attention to the exact wording, it doesn’t say “over planning”, but “over <em>following</em> a plan.” So the underlying assumption is that a plan exists. We just place less value on following the original plan when things change.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AN4m533L4tgB04X4WRO_0g.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/TsMXK2W9hV0?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Dennis Ottink</a> on <a href="https://unsplash.com/search/photos/hike-mountain?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Imagine that you intend to climb a mountain<strong>, </strong>and you set a goal to reach its summit. Would you start going on your way without any planning, just responding to the environment and events as you go along?<br>On the other hand, let’s say you have made a great plan and while hiking up the mountain you’re realizing that a bridge on your planned track has collapsed, or you’re discovering a shortcut that can save you two hours, would you stick to your original plan or respond to change?</p><p>Some would challenge: <strong>“What is the point in coming up with a plan, if you don’t intend to follow it?”</strong> Well, if you don’t have a plan, you might have a very nice walk and you might get somewhere, but it probably won’t be the summit.</p><p>A more interesting question to pose is: <strong>“Assuming that we need a plan, AND assuming that the plan is bound to change once we discover new things along the way, what is the <em>most effective</em> (least wasteful) way to conduct the planning?”</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O3PrCG8rwbzz2zjCgZlzRw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/XIrQfDWyNdk?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Les Anderson</a> on <a href="https://unsplash.com/search/photos/planning-hike?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p><strong>The approach that many take to planning is analytic.</strong> Let’s break the complex problem into smaller, more manageable pieces, plan them really well and in advance and derive the overall plan from the small parts.</p><p>How would this might look like for someone planning to climb a mountain?</p><ol><li>Look at the whole path to the summit and break it down into high-level sections</li><li>Take each high-level section and break it down into smaller sections. Repeat the breakdown until you’re satisfied with the size of each section.</li><li>Now plan and estimate each section really well: The most “interesting” question to focus on is how long will it take to walk the section? Closely followed by what is the equipment and budget needed?</li><li>Summarize all your estimates to get the final duration and budget.</li><li>And lastly the most “fun” stage: <br>Add buffers and padding to your plan if you’re going to be held accountable to the plan to make sure you’re on the safe side. Or alternatively, if you’re really eager to go on the hike and want to make sure that the plan is approved, cut and adjust the plan to fit into the expected time and budget.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1sWNQMWIjH0sSwgb9xSPiA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/8TJbrQGKFyU?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">David Marcu</a> on <a href="https://unsplash.com/search/photos/hiking?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>How would an experienced hiker react if you ask her to plan in this way?</p><p>She might say: “This approach sounds quite interesting, but to be honest, to do this kind of breakdown and detailed planning right now will be a complete waste of time. There are many things that I don’t know at this stage to be able to do it properly.</p><p>“My goal is to reach the summit, but in order to do so, there are a few things that I need learn to ensure I’m successful. Here is a list I have made to identify those things using the following questions:</p><ul><li><strong>What are the challenging parts of the hike?</strong> Climbing very steep cliffs. Carrying a heavy weight for an extended period of time.</li><li><strong>What are the risky parts?</strong> There are a few sections that will require me to walk through ice.</li><li><strong>Any external dependencies?</strong> I might need to get a special permit from the authorities.</li><li><strong>Any unknowns?</strong> This is the first time for me to hike in high altitude. I’m not sure how my body would cope and what would be my pace.</li><li><strong>Any assumptions that we need to validate?</strong> I’m not sure if my new hiking shoes will be suitable for this hike.</li><li><strong>Anything else that I need to learn?</strong> It might be good to pick up a few phrases in the local language, in case I need to ask for directions or help.</li></ul><p>“Now look at the plan that I have made: It includes a full program to get in shape. Here I planned several hikes in increasing levels of difficulty and altitudes, some of them designed specifically to walk through ice. Here’s a longer hike where I can test my new shoes and see how I cope with the heavy weight. I also signed up for a course in the new language which I’m planning to start next week.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m-Wg0rsXfLKVIb4Y3ANQvw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/XIrQfDWyNdk?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Les Anderson</a> on <a href="https://unsplash.com/search/photos/summit?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Some would say “this is just a training plan, this is not THE plan.”</p><p>So which approach is the right one? the “analytic plan” or the “learning plan”? Do we really have to choose between the two?</p><p>We don’t. <strong>Both approaches serve important purposes and both should be done. The question is what is the most effective and least wasteful way to apply each one.</strong></p><p>The “analytic plan” is not very effective to be done fully upfront when the least amount of information is available. It is less wasteful to do it in an<em> iterative </em>manner. Do the minimum, just enough upfront to get ballpark understanding and figures, and refine it as you learn new things along the way.</p><p>The “learning plan” on the other hand, is effective when done <em>upfront</em>. It makes sure that we focus on the things that we need to learn to reach our goals and outcomes and that we schedule them early in our plans, giving us a chance to pivot when necessary earlier rather than later.</p><p>So, what is your experience with long term planning? What is your approach? Do you get push back? What things do you focus on?</p><p>I would love to hear your experience and thoughts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qrXsAcOBxFqVyyPWSWIN5Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/AJqeO_-ifx0?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Paula May</a> on <a href="https://unsplash.com/search/photos/summit?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61dd9194599f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>