<?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 Nicola Dourambeis on Medium]]></title>
        <description><![CDATA[Stories by Nicola Dourambeis on Medium]]></description>
        <link>https://medium.com/@ndoura?source=rss-c511c8c5442a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ya7sRftyd7lVj5Qg2oHzSQ.jpeg</url>
            <title>Stories by Nicola Dourambeis on Medium</title>
            <link>https://medium.com/@ndoura?source=rss-c511c8c5442a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 21:13:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ndoura/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[Practical Tips for Speaking to Executives]]></title>
            <link>https://medium.com/@ndoura/practical-tips-for-speaking-to-executives-801d49727a7c?source=rss-c511c8c5442a------2</link>
            <guid isPermaLink="false">https://medium.com/p/801d49727a7c</guid>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[presenting-skills]]></category>
            <dc:creator><![CDATA[Nicola Dourambeis]]></dc:creator>
            <pubDate>Thu, 22 Feb 2024 21:54:11 GMT</pubDate>
            <atom:updated>2024-02-22T21:54:11.713Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C_1FsczTiaJmgxSllFU05g.jpeg" /></figure><p>Here’s a scenario: Jenny (not her real name) has spent weeks working on a big presentation to pitch a brand new initiative to her senior executive team. She’s nervous because she doesn’t often get invited to meetings with senior people and believes that this is a chance to create a career making opportunity. Best case — she’ll get noticed and her great ideas will get approved. She will have her dream assignment. In order to prepare, Jenny has done a lot of research and created 30 slides which carefully build her data driven argument to reach her recommendations. To show that she’s considered everything, in addition to her recommendations, she gives four other options (two of which are not desired but she wants to demonstrate that she has thought of everything).</p><p>The meeting begins and before she gets to her third slide, one of the executives starts asking her rapid fire questions about a different topic. Others jump in and soon the discussion goes off in another direction entirely. Luckily her sponsor, the person who invited her to the meeting, sees this happening and intervenes to help. The meeting closes without any genuine discussion on the initiative proposal. Despite all of the hard work, Jenny only shows the three slides. Her best points never get seen and she wonders if she missed her chance to get noticed.</p><p>Does this sound familiar? If so, here are some tips:</p><ol><li><strong>Lead with the End</strong>: Executives are decisive, smart and busy. Rather than telling a story to build to a big finish, start your presentation with key recommendations or outcomes. Sometimes starting at the end is all that is needed. Execs often can fill in the blanks and move forward. If not, their questions will guide the discussion to the areas that are most interesting or open for debate. Your preparation will support your answers. That’s the discussion that is worth spending time.</li><li><strong>Embrace Idea Evolution</strong>: Recognize the value of executive insight and experience. Be open to refining your ideas. Collaboration often leads to a better path forward. Caution — this doesn’t mean that their ideas are always better, especially if you have been invited in as an expert. It’s ok to stand behind your ideas and lean on your preparation. No matter how much I prepare, internally I always think of my ideas as 80% formed and invite refinement on the last 20%. Moreover, if someone invests in shaping ideas, they are often more likely to support them.</li><li><strong>Quality Over Quantity</strong>: Avoid overwhelming executives with a plethora of options, especially if some are ones that you’d hate to see implemented. While I appreciate the exercise of thinking through every possible version, I only share ones that I would be comfortable endorsing. Most decisions are tradeoffs, so put forward the reasonable ones and be clear around your recommendations.</li></ol><p>Remember, effective communication with executives requires a strategic and adaptable approach. By using these tips, you can lower the stress and hopefully have a more productive discussion. Executives are busy. Most appreciate succinct and direct communication, so tailor your approach to align with their needs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=801d49727a7c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile Planning & Delivery: Five Common Mistakes and How to Fix Them]]></title>
            <link>https://medium.com/swlh/agile-planning-delivery-five-common-mistakes-and-how-to-fix-them-400d1f040a45?source=rss-c511c8c5442a------2</link>
            <guid isPermaLink="false">https://medium.com/p/400d1f040a45</guid>
            <category><![CDATA[delivery]]></category>
            <category><![CDATA[planning]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Nicola Dourambeis]]></dc:creator>
            <pubDate>Thu, 27 Jun 2019 17:44:31 GMT</pubDate>
            <atom:updated>2019-08-08T13:31:25.482Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Agile Planning &amp; Delivery: Five Common Mistakes and How to Fix Them</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*1TvYxTJZkjrCbWoDaPSKJg.jpeg" /></figure><p>Let me start with a story about a company I’ll call Acme (not its real name). Acme is a large public company that has been around for more than 20 years. They have a commanding presence in a unique product space, complex codebase, successful history of revenues and lots of customers. But, in recent years they have tried to execute very large technical deliveries and found themselves blocked for a variety of reasons. What started as a frustration turned into a crisis. Customers were getting cranky, shareholders were growing impatient and leaders could feel the pressure of disruptive competitors. They knew they needed a change and decided to “go agile”.</p><p>If you think you know this company, you might be surprised. Because this describes almost all of my large clients over the past five years. Unfortunately, it’s a pattern. It’s usually not unique or a by-product of incompetence or irresponsibility. It could be because of scale, speed, or a thousand little choices made in isolation that ultimately clash when put together.</p><p>To help, we embarked on an agile transformation using my playbook. First, we rearranged everyone into small, persistent, cross functional scrum teams. Then everyone was trained in scrum, with a narrative created to focus on solving recognizable issues. Team members seemed bought in and eager to try something new. All projects were converted into prioritized product backlogs. Teams did bottom up planning for the quarter allowing them to understand what was expected, to align and to create their own estimates. With new hope and excitement, these teams started to execute on the plans. All should have been good in agile-land….but it wasn’t.</p><p>Once we got into the execution, we realized that their plans were off. In some cases, by a lot. Many of the teams were not going to deliver as planned even though they, <em>the teams, </em>built the plans and felt good about them at the time.</p><p>What else was going on?</p><p>One of the most difficult parts of practicing scrum is uncovering hidden dysfunctions. Acme had many of them and we had to deal with them in order to create better, more predictable execution.</p><p>Here are some of the issues and some practical ways to handle them.</p><p><strong>1. Problem — Teams don’t understand their product backlogs</strong></p><p>It never fails to surprise me how many product backlogs are a list of single-line phrases in a tool. I get it. Writing requirements is time consuming. Long ago, people wrote very comprehensive documents to describe every requirement, how to build the requirement, every edge case to test and a bunch of things that they thought they may want someday. These documents were intended to cover everything thereby eliminating the need for conversation or negotiation. Fortunately, we now know that these documents create a ton of waste — either we build things that no one wants, build things incorrectly or take too long to get feedback from our customers.</p><p>I don’t see these type of documents anymore, which is progress. But it’s not uncommon to see backlogs in a tool (let’s call it JIRA) which list “requirements” that look like this:</p><p><em>Build authorization capability</em></p><p><em>Allow user to edit and save information</em></p><p><em>Fix performance issues</em> …and that’s it.</p><p>If this all sounds familiar, then we’re going to have to first admit this isn’t a product backlog which supports planning. It’s not easy to estimate, prioritize or execute independently. In some cases, it’s so ambiguous that every team member may assume something completely different.</p><p>Also let’s be fair to our teams — this is not engaging or interesting. How are they going to get inspired by who they are helping and why? Do they all have the same understanding of the customer (or user)? What does our customer need? How will we know we’re satisfying that need? Or better yet, what business problem are we trying to address? Why? How do we know we are done?</p><p><strong>The Fix </strong>— <strong>Build a better product backlog</strong></p><p>Simple and obvious, build a better product backlog (there are lots of great resources out there — after fifteen years, I still like Mike Cohn’s User Stories Applied). The act of building a product backlog doesn’t need to be arduous or intimidating. It also doesn’t need to be solely built by the product owner. If a team does not have a mature backlog, it’s worth taking the time to build one together. It also doesn’t happen in one sitting. We expect requirements to evolve as we learn more so we start with a higher level backlog that gets decomposed “just-in-time”.</p><p>For anyone who is about to say “<em>but that’s a huge waste of team time, it’s the product owner’s job to build the backlog!”</em>, my counter is <em>“how much waste is created by folks who are building the wrong things because they only have a vague idea of what they are supposed to build?”</em> or “<em>how many innovative ideas are missed when the whole team doesn’t understand or empathize with customer problems?”</em>.</p><p>When I first learned agile, it was made clear that the backlog was the product owner’s responsibility. While I want them to build and embrace their backlog, as well as ruthlessly prioritize it, a common complaint I hear is that the PO is too busy to spend a ton of time on writing requirements, so they remain ill-defined. Most engaged team members have many great ideas that can be unlocked by collaboration. Since the responsibility of every team member is to help each other, why wouldn’t we leverage their collective minds to help create and groom the backlog?</p><p><strong>2. Problem — Teams cannot create longer term estimates</strong></p><p>Agile teams have many techniques to estimate. My personal favorite for longer term planning is to use story points with a Fibonacci scale, but I’ve seen teams use different techniques and still be fine. However, there are times when any of the tried and true techniques fail to work…because the team <em>cannot </em>reliably estimate.</p><p>Here are some reasons why this may be the case:</p><p>- the code or the problem/domain is completely new. Without experience or a point of reference, any estimate is a massive guess.</p><p>- the team members are completely new and have no common frame of reference.</p><p>- there is too much technical debt or too many hidden surprises.</p><p>Remember the company that I introduced at the beginning, Acme? Their code had serious performance and scalability problems (so serious in fact that, painfully, they ultimately chose to rewrite everything rather than fix it). Any estimate would be inaccurate for Acme’s teams. Either they would miss issues that they would later encounter when building new scalable code in a debt ridden codebase or they would include such an extreme buffer on their estimates that they were essentially useless. Yet these teams continued to be asked for estimates (when will this be done? can it be done sooner?) and time after time, miss all commitments. It wasn’t their fault. Estimation was nearly impossible. Leaders asking the question over and over again didn’t make the answers any more reliable.</p><p><strong>The fix:</strong> <strong>Pay down technical debt and spike when needed</strong></p><p>If teams do not have enough knowledge to create informed estimates, there are ways to get help. They could choose to spike to learn more. Spikes are a short time box dedicated to gaining the knowledge needed to create an estimate or approach (through research, pseudo code or experimentation).</p><p>In the case of significant technical debt, I encourage teams to build a prioritized technical debt backlog (usually priority = severity or exposure to risk) and budget paying it down. If even building the backlog feels impossible for the team to do, then they can start with building test automation to expose issues. Or they can ask a senior technologist do an analysis of the code, looking to identify areas that are most often used and perform poorly as first priorities for refactor.</p><p>Most importantly, if a team is facing severe technical debt, they need to be honest about the condition of the code.</p><p>In the case of Acme, rather than building a strategy to remediate and prevent future debt, they continued to commit to dates which were made up. Further, since they were a publicly-traded company, they chose to share the dates with Wall Street. Any guesses how this impacted their stock?</p><p><strong>3. Problem — Team membership changes too frequently</strong></p><p>Remember Tuckman’s stages of group development — forming, storming, norming, performing? Time together and experience as a team makes a big difference in a team’s ability to predict what they can deliver in the future. Over time, if we maintain the team membership and composition, they get better at planning and execution. This is true even when they are faced with new problems and challenges. There is a lot of value in allowing a team to stabilize and not disrupt the membership. I realize with hiring and attrition, nothing is ever perfect. But I’ve seen the productivity difference in companies that value maintaining persistent cross functional teams as opposed to those that constantly tweak and/or launch new project/tiger/swat teams as short term accelerators. They may gain some short term lift but over the long term, most large organizations need to know how to deliver against a portfolio of work that comprises the majority of their teams.</p><p>Moreover, once I have a team that is working well together, they usually don’t want to change.</p><p><strong>The fix: Stabilize teams</strong></p><p>Scrum works well because it allows us to optimize a team rather than an individual. In order to reap the rewards of that optimization, keep the teams persistent. This doesn’t mean that people have to stay on a team for life, but it’s generally prudent to allow teams to work together for at least a quarter, preferably much more. Even if they don’t have every perfect skill, over this time they generally can get creative on how to overcome issues. If they are truly blocked, then this amount of time will allow you to better understand what gaps need to be filled (architecture? a junior doer? someone who knows how to test really well?).</p><p>If persisting teams seems impossible because of constant org changes, then be careful to separate management structure from scrum team formation. And stop having org changes. No one likes having six managers in a year.</p><p><strong>4. Problem — Priorities shift often</strong></p><p>While it may seem obvious that in order to deliver on plans, we expect them to largely stay unchanged, working in agile should create a healthy tension on scope. Agile teams deliver the best results when they consistently inspect and adapt with feedback. This sometimes translates to a team facing feedback after every sprint, which may alter their future direction. However, accepting or addressing feedback can be different from “changing priorities”. Part of the benefit of longer term planning is to understand higher level priorities and keep focused on big picture execution, rather than changing direction sprint to sprint.</p><p><strong>The fix — Make priorities clear, measurable and at the right level</strong></p><p>Longer term planning allows a team to prioritize a goal or solve a customer problem with simple metrics to keep them focused on the big picture. Some examples of a goal may sound like “improve customers’ ability to complete (specific) workflow from ten minutes to five minutes” or “increase conversion to do X by 5%”. These types of goals are quantifiable and unlikely to shift with feedback.</p><p>Naturally when a team plans they have more flushed out ideas on things that they will do to achieve the metrics. Nevertheless, having the prioritized goal is impactful. When they deliver incrementally, they can measure how they are doing against that goal and further update their plan with new ideas. While this may mean that the actual “stuff” built changes, the plan’s priority should not.</p><p>I worked with a team that planned a long backlog of unrelated items that they wanted to deliver in sequence. They believed this adhered to the “priority” rule. Yet, after each sprint when they demoed their work, they found that people had suggestions on how to change/improve what they had just built. The problem was, they didn’t know whether they should accept the suggestions or build the other items on their backlogs. Moreover, the team slowed down their execution because they fully believed they would have more “tweaks” to do in the future. Had they started with a prioritized goal and some metrics, they would have had insight on whether they should keep working on what they had just delivered or move onto other items and backlog the new suggestions.</p><p><strong>5. Problem — Culture or misunderstood expectations</strong></p><p>Culture is almost unfair to list as a problem that contributes to planning but I want to list it because I work with a lot of leaders who absolutely say and want the right things and yet their teams either don’t believe them or ignore it. Here is an example: a belief that long term estimates must be commitments. We know the accuracy of an estimate is related to the time frame we use (eg- estimating for a day is easier than estimating for a year). Yet I have worked with teams that absolutely believed that the guesses that they made in an annual planning offsite needed to be 100% accurately delivered. When I questioned them and the executive team about this, I found that often the execs were reasonable in understanding these were planning projections which needed to be vetted. In Acme’s case, it was the middle level managers who had created these estimates that most believed that they were fixed. When faced with feedback that the estimates were incorrect, they did everything in their power to deliver on them — including taking shortcuts or working in a way that didn’t make them proud — rather than change the estimate.</p><p>Another culture factor is the presence of a culture of fear. This one is tough to understand but can be easily seen. It looks something like this: “I have to deliver this plan. If I don’t, then something bad will happen.” No one ever can tell me *exactly* what the bad thing is (someone will yell? a bad performance review? someone gets fired? all of it?). Yet fear of this “bad thing” influences behaviors. The challenge with a culture of fear is that it prevents teams from taking risks, often learning and innovating. I have never seen teams in this environment deliver better than those in cultures without it.</p><p><strong>The fix: Create clear expectations, reinforced by practices</strong></p><p>Every company needs to understand what signals team members are getting and be comfortable with their intended and unintended consequences. For example, often teams that go the “extra mile” are rewarded by praise, bonuses or other. Without wishing to short change these hard working folks, everyone else is learning that in order to get recognized you must be a hero. And heroics are only needed when there are problems.</p><p>Companies should consider what percentage of their plans are truly required and how much flexibility they embrace. For example, at salesforce, we viewed teams that delivered about 80% of their plans as a success. For this culture, 80% meant be aggressive, take some risks but because of a high number of dependencies, don’t plan without thoughtfulness. In exchange, we promised the teams we would not shift priorities nor would we shift teams.</p><p>If someone (usually a leader) sets an expectation that “failure is not an option” or “don’t give me bad news, just make it happen” (as we had in Acme), it rarely delivers a healthy result. Teams have a long memory of these phrases even when the phrases and leaders change. I recently worked with one manager who flat-out refused to tell his leadership that his plan was wrong (despite their very nice requests and offers to help) because he didn’t want to disappoint them. While you may expect that he subsequently drove his team to work harder to achieve the unattainable plan, in fact the opposite happened. Since he and the team considered the plan to be unattainable, they worked at a very leisurely pace because they knew it was impossible and didn’t believe it was worth the push.</p><p><strong>Final Thoughts</strong></p><p>In summary, longer term planning is hard but very achievable in agile. For any team executing in a scaled environment with dependencies, it is crucial. There are lots of strategies to improve the reliability of planning and delivery, depending on the root cause of a team or company’s issues. I’ve tried to list the common ones I’ve seen.</p><p>In addition to all that I’ve said above, I also always recommend asking a team what they need in order to remove uncertainty and gain comfort in their plans <em>while they are still planning</em>. It’s a lot easier for teams to build longer term plans when we accept that the plan is simply the best guess that we have, based on what we know today.</p><p>Tomorrow, next week and next month, we’ll continue to know more. Hence, we want and expect that plans will need to be recalibrated throughout the delivery cycle. For the most successful teams I’ve worked with, planning is a regular activity rather than a one shot moment. Best of luck.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=400d1f040a45" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/agile-planning-delivery-five-common-mistakes-and-how-to-fix-them-400d1f040a45">Agile Planning &amp; Delivery: Five Common Mistakes and How to Fix Them</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How (and why) to do Agile bottom up release planning]]></title>
            <link>https://medium.com/@ndoura/how-and-why-to-do-agile-bottom-up-release-planning-244b28c07026?source=rss-c511c8c5442a------2</link>
            <guid isPermaLink="false">https://medium.com/p/244b28c07026</guid>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[planning]]></category>
            <dc:creator><![CDATA[Nicola Dourambeis]]></dc:creator>
            <pubDate>Wed, 13 Feb 2019 18:54:46 GMT</pubDate>
            <atom:updated>2019-02-14T04:56:07.785Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*F6L2VkIUa9NS-N2XQ6Nb9A.jpeg" /></figure><p>Whether you’re a successful startup that needs to hire and scale very quickly or a large enterprise trying to streamline and improve execution, the practice of agile bottom up release planning can make a big impact. Bottom up release planning is a scrum team practice to build a sprint map of the stories they believe they can do over a period of roughly four months. It isn’t a deployment schedule (although it could be if you bundle work for enterprise customers), but rather a medium term view of work to allow teams to make better decisions on design, research, experiments, cross training, dependencies and delivery. This still adds value even if a team ships work daily.</p><p>Bottom up release planning should not be used to drive “Commitment” (which can sometimes lead to hedging), but rather engage the hearts and minds of the people <em>who will be doing the work </em>to create and align on an achievable, believable plan.</p><p>For an organization, this can provide early insights into capacity, hiring needs, prioritization and trade-offs. I often say “hope is not a plan”. As a former executive, I was always happier getting bad news early, when I still had options to reprioritize or reallocate work. On the flip side, I never stop being amazed at the power of a team to deliver something that they believe in and want to do. Their desires and beliefs matter and we can only engage those when the plan comes from them.</p><p>Brief public service announcement on plans — in agile, we expect (and want) plans to change and improve as the team executes, learns and adapts. When I started at salesforce in 2008, we had about 40 scrum teams with a single product delivering, on average, 30% of their plans. Why? Yes, the plans were ambitious but they were also built by managers and leads, not the people who would do the work. By introducing the techniques below, we got teams to about 70% predictability — which was a gold star in that culture. It kept the organization energized and pushing, while staying adaptive to change. Plus it scaled — we were still doing this with over 200 teams across many products when I left six years later.</p><p>Here is my step-by-step how to’s. Try it and let me know how it works for you!</p><h3>Bottom up release planning how-to</h3><p>The goal — Figure out a range of features (stories, epics) that a scrum team believes they can complete in a fixed period of time, usually three or four months. In my experience, this can take a day or two. If there are several teams with dependencies, plan them together in the same room.</p><h3>Mechanics outline</h3><p>Step One — Whole-team backlog grooming</p><ul><li>Review every item in the product backlog. Ask questions and gain clarification of intent. Decisions and discussion are recorded as updated acceptance criteria of a story. Note that items at the top of the backlog should be smaller. Items near the bottom are expected to be chunkier. They will be decomposed just-in-time as the team executes.</li><li>Discuss Acceptance Criteria and Definition of Done.</li><li>Identify if there are any spikes (areas of research for the team to determine design, approach or estimate)</li><li>Determine if there is any tech debt or legacy that needs to be prioritized (review existing bug lists). If no tech debt backlog exists but should, build one and prioritize it. Assign it a budget.</li><li>Talk through any dependencies — write stories as needed for other teams</li><li>Create 1 post-it for each story with title, Jira ID (if available) and story priority.</li></ul><p>Step Two — Estimate your backlog</p><ul><li>Ignore previous estimates. We will re-estimate all backlog items comparatively using story points. There are lots of ways to estimate, so if the team has a technique that they like, go for it. I like comparative grouping all items and this can be done pretty quickly.</li><li>Ask the team to silently group post-its on table</li><li>Use affinity grouping, left to right, with no numbers, small to large, silent, fast. ~5 groups.</li><li>Look for areas of concentration and ask the team to further decompose those areas.</li><li>Put relative size numbers on the groups, using Fibonacci 1,2,3,5,8,13, 21+</li><li>Write size numbers on the post-its</li><li>Estimation is done by the delivery team only (not Managers, POs or SM unless the SM is also a team member — in which case they go last).</li></ul><p>Step Three — Build your plan and forecast future sprints</p><ul><li>Identify anything that will impact time. Consider: holidays, vacation, and other time away from the office, on-demand support, etc.</li><li>Whole team lays out the stories they believe they can do in the associated sprints, honoring the priorities. Look to build balanced sprints with no single points of failure. Address dependencies</li><li>If the team has a previous established velocity, use it to determine the capacity of a sprint. If none exists, then gut feel is ok. These plans will get better with execution.</li><li>Head’s up — the goal is not to put the entire backlog into sprints. The goal is to determine how much of the backlog can be done by building a map of sprint activity.</li></ul><p>Step Four — Get feedback &amp; Affirm confidence</p><ul><li>Review with stakeholders, leaders and/or dependent teams inside &amp; outside your product group.</li><li>Ask reviewers to give feedback and pose any questions to the team to spark their thinking on areas they may not have considered.</li><li>Let the team recalibrate their plan accordingly.</li><li><em>Coaching note for the leaders — ask questions (and hard questions are welcome) but do not tell the team the answers. The teams need to own their plans.</em></li><li>Review &amp; confidence vote (Fist of five voting).</li><li>Let the teams know that the plan will change as they go, and it’s equally important to recalibrate as they deliver their sprints.</li><li>Congratulate them on building a plan and applaud.</li></ul><p>Step Five — Execute the work</p><ul><li>After every sprint, recalibrate the plan with what just happened. The plan will get better with time and experience.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=244b28c07026" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>