<?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 Tolgay Budayici on Medium]]></title>
        <description><![CDATA[Stories by Tolgay Budayici on Medium]]></description>
        <link>https://medium.com/@tbudayici?source=rss-85bec1340635------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*A4sPHMDUjR0KKdRJTl4ypQ.jpeg</url>
            <title>Stories by Tolgay Budayici on Medium</title>
            <link>https://medium.com/@tbudayici?source=rss-85bec1340635------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 12:03:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tbudayici/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[3 takeaways from my first year as a team leader]]></title>
            <link>https://medium.com/@tbudayici/3-takeaways-from-my-first-year-as-a-team-leader-59da57905e33?source=rss-85bec1340635------2</link>
            <guid isPermaLink="false">https://medium.com/p/59da57905e33</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[team]]></category>
            <dc:creator><![CDATA[Tolgay Budayici]]></dc:creator>
            <pubDate>Wed, 21 Dec 2022 11:48:53 GMT</pubDate>
            <atom:updated>2022-12-21T11:48:53.737Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to succeed as a first-year Team Leader? This I don’t know 🤷‍♂️ However, I can share 3 key takeaways from my first year.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gFX9myRGc28wmeTXpFoWLw.png" /><figcaption>A Picasso painting of a software engineering team | Generated with <a href="https://openai.com/dall-e-2/">Dall-e-2</a></figcaption></figure><p>Your first steps as a team leader are critical and challenging. Critical because they establish the foundations of your team. Challenging because tasks are diverse and there are many things to put in place.</p><p>What to focus on first? How to get high engagement from team members? Is it possible to meet high expectations while having fun? What will the first year of our team look like?</p><p>In 2022, I stepped into a Team Leader position at one of the leading e-grocery companies in Switzerland. It was such an enriching year! In this article, I will share 3 takeaways that helped our team to get a strong start:</p><ol><li>Build a strong team culture</li><li>Map your activities onto your vision</li><li>Set up a clear working flow</li></ol><h3>1. Build a strong team culture</h3><h4>Team culture in a nutshell</h4><p>Team culture is the set of values that a team shares. It is how people behave working together towards a common goal. In my opinion, culture is the core foundation of a team.</p><p>Please note that team culture is not something you can buy, apply by the book, or impose. It is something that is created and maintained by team members. As a leader, you can identify characteristics that are important for your team. Then, you can trigger actions to support and enhance those characteristics.</p><p>A positive team culture fosters collaboration and coordination. It creates an environment where people support each other. As a result, it increases the team’s confidence in overcoming obstacles and taking on challenges.</p><blockquote>“Culture is simply a shared way of doing something with a passion.” — Brian Chesky, Co-Founder, CEO, Airbnb</blockquote><h4>3 characteristics of our team’s culture</h4><p>Throughout the year, 3 characteristics revealed themselves as key in our team.</p><ul><li><strong>Psychological safety</strong>: We want to share our thoughts, ideas, and emotions without the fear of being judged or humiliated. <em>Personal note: Training on “how to give feedback?” is very helpful.</em></li><li><strong>Openness</strong>: We are a team but we know we are part of a company. Therefore, we don’t limit our work to our scope. We build connections with other teams. <em>Personal note: Create opportunities for your team members to work with other people in the company.</em></li><li><strong>Fun</strong>: We laugh a lot. During meetings, we use humor quite often: fun facts, live meme creation, puns, etc. Humor brings a dose of humanity to our daily work. <em>Personal note: Get to know people and try to make them smile (even just a little bit).</em></li></ul><p>If you had to pick 3 characteristics that represent the identity of your team, what would they be? Feel free to share them in the comment section 😊</p><h3>2. Map your activities onto your vision</h3><h4>Team vision in a nutshell</h4><p>A vision is a statement that describes what a team is shooting for. It provides guidance so that everyone is focused and converges on a common goal.</p><p>A team vision shouldn’t be an abstract concept that people see once and forget afterward. It should rather be ubiquitous. It should be repeated frequently and its validity should be questioned over time.</p><p>A vision gets even more powerful when it is defined by the team members together. In fact, team members will take ownership of the vision and identify with it.</p><h4>IT Delivery’s team vision</h4><blockquote>Provide all delivery information and make sure the delivery process is smooth, and effective, from our warehouses to the customers’ doors.</blockquote><p>Then, we went a bit deeper in granularity, and we defined a vision for each domain of our scope.</p><ul><li><strong>Customer</strong><em>: Provide the best delivery experience to our customers</em></li><li><strong>Logistics</strong><em>: Ensure the best logistic processes to enhance delivery</em></li><li><strong>Tech</strong><em>: Ensure high technical quality and reliability</em></li></ul><h4>Mapping your activities onto a vision</h4><p>Once your vision is set, it gives you an opportunity to map your objectives onto it. Subsequently, you can map your activities to your objectives.</p><ul><li>Vision ↔️ Objectives ↔️ Activities</li></ul><p>To have this mapping, I like to use Objective Key Results (<a href="https://itamargilad.com/ebook-okr/">OKRs</a>). An OKR is an effective “tool” for setting goals and tracking results. It creates alignment and engagement around measurable goals.</p><p>Mapping your activities onto your vision will give your team members a clear idea of what they are thriving to achieve as well as the significance of tasks. This would result in team members being more engaged and more productive.</p><h4>Our team’s map</h4><p>Here is a snapshot of the mapping of some activities onto our vision:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bilp7m1I7Zx91O0VhzOqGw.png" /><figcaption>Mapping goals onto a vision</figcaption></figure><p>How many of your team members would know your team’s vision? Could you map all of your activities onto your vision or do you also work on other things?🤔</p><p><em>Note that this section is not about “how to define a team vision” or “how to use OKRs”.</em></p><h3>3. Set up a clear working flow</h3><h4>What do I mean by working flow?</h4><p>The working flow is the set of activities and practices that help a team to work together on a daily basis to reach its goals. In terms of activities and practices, it would include:</p><ul><li>Team members sync</li><li>Questions and answers sessions</li><li>Impediment tackling</li><li>Knowledge sharing</li><li>Roadmap and goals discussion</li><li>Etc.</li></ul><blockquote>New research shows that 70% of meetings keep employees from doing productive work. — <a href="https://hbr.org/2022/03/dear-manager-youre-holding-too-many-meetings">Harvard Business Review</a></blockquote><p>Have you ever worked in a team where everyone seemed perfectly synced and getting things done seemed effortless? Well, this is where a well-established working flow could lead you.</p><h4>Our team’s working flow</h4><p>The are many practices out there that can help you foster your working flow. From a personal perspective, I truly enjoy working with Scrum. It structures the events (each with a specific purpose) and gives the team a cruising flow ⛵️</p><ul><li><strong>Daily meeting</strong>: We inspect progress toward our sprint goal. Moreover, we make sure we have no impediments blocking us from reaching it. <em>Personal note: This should be a team event where people support each other and not a status meeting to track individual progress.</em></li><li><strong>Planning</strong>: We discuss the priorities and define our goal for the upcoming 2 weeks. Then we pick the backlog items that will help us reach it. <em>Personal note: Transparency on priorities is key.</em></li><li><strong>Review</strong>: We review what we achieved in the sprint and adapt our backlog based on feedback. <em>Personal note: Celebrate success and learn from feedback.</em></li><li><strong>Refinement</strong>: We go through our backlog, refine user stories, and estimate them. <em>Personal note: Foster discussions and knowledge sharing.</em></li><li><strong>Retrospective</strong>: We share our feelings and discuss what went right as well as areas for improvement. <em>Personal note: Psychological safety brings this meeting to the next level. Also, this meeting is a great opportunity to build strong relationships between people, and have fun.</em></li><li><strong>Bi-weekly meeting</strong>: Here, we present the company topics, and we also discuss team vision and values. <em>Personal note: This meeting is a great placeholder for a short training on “how to give feedback” for example.</em></li></ul><p>Within a cycle of 2 weeks, the program is clear. This cycle repeats itself, which makes it predictable. We know we have a dedicated time for basically “everything”.</p><p>Is your working flow enabling your team to collaborate better and be more productive 💪? Or, do your team members express frustration about it 😫?</p><h3>Conclusion</h3><p>Stepping into a team leader position is overwhelming. There is no magic formula to start on the right foot. However, you can learn from others’ experiences and use this knowledge to become the leader you aspire to be.</p><p>When I started in this new position, my main focus was to get people to work smoothly together, have a positive mindset, and enjoy the adventure.</p><p>Today, I am proud of our team’s first year. I know we have established strong foundations and achieved quite a lot. Based on my experience, if I could give 3 advice to a new team leader, it would be:</p><ul><li>Build a strong team culture</li><li>Map your activities onto your vision</li><li>Set up a clear working flow</li></ul><p>I believe there would be many other pieces of advice to give. These 3 reflect my experience the best.</p><p>Thank you for reading 😊</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59da57905e33" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hypothesis-driven practices to build better features]]></title>
            <link>https://medium.com/swlh/hypothesis-driven-practices-to-build-better-features-b5cc53c9fd24?source=rss-85bec1340635------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5cc53c9fd24</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[features]]></category>
            <dc:creator><![CDATA[Tolgay Budayici]]></dc:creator>
            <pubDate>Fri, 15 May 2020 10:24:41 GMT</pubDate>
            <atom:updated>2020-05-15T18:57:56.774Z</atom:updated>
            <content:encoded><![CDATA[<h4>Hypothesis-driven practices can help you make better decisions that will reduce your risks while building better features</h4><p>Should you really build that feature? Well, we all have great ideas for new features or improvements. Then, we implement them because we assume they will have an impact and help us reach some goals 🎯. But, we must admit that we face a lot of uncertainty in what we do.</p><p>Could you explain the path from your ideas to the solutions you deliver? Are you be able for formalize the uncertainty you face? How do you know your solution is satisfactory?</p><p>I have applied hypothesis-driven practices into my daily work as a product manager. It helped me answer questions and justify my actions. It pushed me to define measurable outcomes upfront. It taught me to formalize the unknown. And it allowed me to track lessons learned and act upon them.</p><p>In this post, you will find high-level theory about hypothesis-driven practices as well as different examples to make it all real. Finally, I’ll share 3 reasons I love working with hypotheses 🤓.</p><figure><img alt="Hypothesis-driven product management" src="https://cdn-images-1.medium.com/max/1024/0*gndMOk8ar4Klwdd_.png" /></figure><h3>Features usually come from assumptions</h3><p>An assumption is a statement for which we only have limited (to no) evidence. We tend to make assumptions based on experience, observations, data or gut feeling.</p><p><strong>Example of an observation</strong>: many customers rate their delivery on their first order, but they often don’t answer any of the questions on the satisfaction survey. Which is a pity because this feedback is key to improving our services.</p><p><strong>Example of an assumption</strong>: We can increase feedback (comments) from our customers on their first delivery.</p><p>Even though we cannot really work with such a high level statement, it is a great starting point for an improvement or a new feature. Isn’t it?</p><blockquote>“Assumptions are vague, optimistic, and untestable. The vaguer they are, the harder they are to disprove.” By Tristan Kromer in <a href="https://grasshopperherder.com/assumption-vs-hypothesis-to-the-death/">Lean startup hypothesis</a></blockquote><p>Let’s turn our assumption into something “usable”. To do so, we will convert it into a hypothesis. The difference between these is straightforward. A hypothesis is a statement that is actionable, and that we will attempt to prove is true by testing it with experiments 🔬.</p><blockquote>“The starting point for designing strong experiments is being explicit about what we are trying to learn. A clear and well stated hypothesis that is testable and precise is at the heart of everything.” <a href="https://www.strategyzer.com/blog/designing-strong-experiments">By Tendayi Viki &amp; Franziska Beeler</a></blockquote><p>let’s get to work.</p><h3>4 step process to working with hypotheses</h3><h4>1. Define</h4><p>When and where would you define a hypothesis?</p><p>It is possible to define a hypothesis at different granularity levels. In this post, I will focus on using hypotheses to create features 🎯.</p><p>Referring to the <a href="https://www.atlassian.com/agile/project-management/epics-stories-themes">traditional Agile hierarchy</a>, I like to capture new features or improvements in Epics. Hence, I believe an Epic is an ideal placeholder for a hypothesis. In fact, Epics are great to scope work and to structure it. They give vision and help teams work towards a common goal.</p><figure><img alt="Hypothesis-driven product management" src="https://cdn-images-1.medium.com/max/1024/1*XY4X4bclYv9RVQb--xWgvw.png" /></figure><p>How would you define a hypothesis?</p><p>Obviously, there are multiple formats to define a hypothesis. The one I like to use comes from the <a href="https://www.strategyzer.com/blog/posts/2015/3/5/validate-your-ideas-with-the-test-card">Test Card by Strategyzer</a> 🙌.</p><figure><img alt="Hypothesis test card" src="https://cdn-images-1.medium.com/max/464/0*CCA5-1-GIkENwh2X.jpeg" /></figure><p><strong>Start date: </strong>Set the start of your experiment. <strong>Duration: </strong>Define its length. <strong>We believe that</strong>: Describe one thing that must be true to validate your idea. Can you specify your target? <strong>To verify that</strong>: contains the test itself. What is the change you are making? <strong>And measure</strong>: What are you going to measure? This will validate or invalidate your hypothesis. <strong>We are right if</strong>: Defines your threshold. Here you’ll make a prediction. What do you expect to happen?</p><p>Also important, on the right side, you can see relative values that will help you assess and prioritize your hypothesis.</p><p><strong>Example of hypothesis:</strong></p><figure><img alt="Hypothesis-driven product management" src="https://cdn-images-1.medium.com/max/806/1*EeJ7rkAasB219TqgSCQo4g.png" /></figure><p>Here is the checklist I use to validate that my hypothesis is well written.</p><ul><li>Define a clear <strong>goal </strong>✅ (increase feedback comments)</li><li>Define a <strong>target </strong>✅ (new customers on their first order)</li><li>Explain<strong> how you will test</strong> ✅ (sending the feedback notification 2 hours after delivery)</li><li>Define the expected <strong>outcome </strong>✅ (&gt;20% of feedback)</li><li>Define <strong>how you will measure</strong> the results ✅ (reports with KPIs)</li></ul><h3>2. Implement</h3><p>Now, we will need to implement an artifact that will help us learn whether our hypothesis is true or false. The quality of the artifact will have a significant impact on the results you will get. Therefore, designing a well-crafted artifact is key to run an efficient experiment.</p><p>Your artifact could be a paper prototype, an online survey, a hi-fi prototype, a fake lading page, A/B testing, a real feature, etc.</p><figure><img alt="Hypothesis-driven artifacts" src="https://cdn-images-1.medium.com/max/1024/1*mEm_dhjpznHfZWXQsuiHdA.png" /></figure><p>Early in a process, you might want to implement a cheap artifact. As you learn more, you could go for a more expensive option that will produce stronger evidence.</p><p>What makes a good artifact?</p><p>I would say that a good artifact is one that helps you get enough evidence to make a decision at the right time.</p><p><strong>Example of an artifact</strong>: New notification with satisfaction survey sent 2 hours after delivery. I would implement it directly into production. Why? Because it would be “cheap” and results from real customers would be highly relevant.</p><h3>3. Test</h3><p>Testing a hypothesis actually means running an experiment. The goal of a test is to validate whether your hypothesis is true, or not. To do so, you will use your artifact and start gathering empirical evidence. Obviously, the way you run your test will depend on the artifact you decide to implement.</p><p><strong>Example of tests</strong>: For a hi-fi prototype, you would plan interviews with users and make them test your solution. If your artifact is directly in production, you would observe key indicators.</p><p>In your test card, you defined the duration of your test. During this time, you will most probably see tendencies. Your test might take the right direction towards validating your hypothesis. Or, it might quickly show you that your hypothesis will most probably be invalid. As you are running your experiment, I would recommend you to observe the evolution of your results. You might learn things along the way.</p><h3>4. Act</h3><p>The last step consists of assessing the results of your test and defining your next actions. With your test, you might learn that your hypothesis was right! Or, that it was almost right. You might also learn that your hypothesis was wrong.</p><p><strong>Example of test results</strong>: Before the experiment, only 9% (36 out of 400) of new customers would give feedback on their delivery. Let’s imagine that we ran our experiment during 3 months and that 22% (88 out of 400) of our new customers gave feedback when receiving the notification separately 2 hours after their delivery. This would validate our hypothesis 😊!</p><figure><img alt="Hypothesis-driven results" src="https://cdn-images-1.medium.com/max/527/1*v6GNCwIox2W5cwaeeFpFRw.png" /></figure><p>We are not not finished yet.</p><p>Every test that you make generates new insight that you can use for future product developments. This should help you define your next actions:</p><ul><li>What happens if your hypothesis is true? Will you scale it?</li><li>What happens if it is wrong? Will you rollback? Will you pivot?</li><li>Do you need more time to validate your hypothesis?</li></ul><p><strong>Example of next actions</strong>: Scale our solution to all the customers. Or, run the experiment a little longer to get more data.</p><p>We have now come full-circle with our hypothesis.</p><h3>3 things I learned with hypothesis-driven product management</h3><p>You can consider this section as my conclusion 👋.</p><h4>You can formalize the unknown</h4><p>Working with hypotheses taught me to accept and formalize the unknown upfront. We never start with guarantees but only with limited evidence. Our chances to predict exact outcomes are slim. It is not because a feature exists in a similar product that it will work for your product. It is not because your initial analysis and data expect your solution to reach your objective that it will happen.</p><h4>It is humbling</h4><p>Since I started using hypotheses, I have become less affirmative with my statements. In fact, the hypothesis format drives you away from affirmations. Instead, it helps you formulate beliefs with measurable criteria. It is humbling to accept the unknown ☝️.</p><h4>Closing the loop</h4><p>Hypothesis-driven product management pushes you to answer: “What’s next?”. And this is crucial. You basically keep on trying to deliver features that help you reach your objectives. You keep on running experiments until you are satisfied 😎.</p><figure><img alt="Hypothesis-driven product management" src="https://cdn-images-1.medium.com/max/1024/0*uWrN93pHzBnUc3Z6.png" /></figure><p>Thank you so much for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5cc53c9fd24" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/hypothesis-driven-practices-to-build-better-features-b5cc53c9fd24">Hypothesis-driven practices to build better features</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[Goal-oriented Daily Scrum]]></title>
            <link>https://medium.com/swlh/goal-oriented-daily-scrum-598a17773708?source=rss-85bec1340635------2</link>
            <guid isPermaLink="false">https://medium.com/p/598a17773708</guid>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[daily-scrum]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Tolgay Budayici]]></dc:creator>
            <pubDate>Wed, 20 Nov 2019 06:47:53 GMT</pubDate>
            <atom:updated>2019-11-20T07:56:38.515Z</atom:updated>
            <content:encoded><![CDATA[<h4>Make your Daily Scrum great (again)</h4><p>Many teams misunderstand the purpose of Daily Scrums. Most of the time, this meeting turns into a tasks’ status report. Isn’t that inefficient and boring? I believe that Daily Scrums should <strong>not be task-oriented</strong>. They should <strong>be</strong> <strong>goal-oriented</strong>.</p><p>How can you take the most of your Daily Scrums? Is it easy to make this meeting great (again)?</p><p>Our Daily Scrum was boring. But, from one day to the next, we managed to turn it into a meeting that drives our Scrum Team’s <strong>cohesion towards reaching its goals</strong>. So I would say it is possible to make this meeting great quickly.</p><p>In this post, I’ll first describe how I have found most Daily Scrums go. Then, I’ll explain why they often become boring. I’ll share a few sections from the Scrum Guide that will help define the purpose of this meeting. Finally, I’ll describe the way our Scrum Team does the Daily Scrum.</p><figure><img alt="Scrum Team" src="https://cdn-images-1.medium.com/max/1024/1*K7BaSvnYW2wineX14ce4Eg.jpeg" /><figcaption>Scrum Team</figcaption></figure><h4>How most of Daily Scrums go</h4><ul><li>It is 9:00 am. Same time everyday. ⏰</li><li>The team gathers around the Scrum Board. Same place everyday. Level of motivation is quite low. 💤</li><li>The Scrum Board contains 3 columns: To Do, Doing, Done. There are post-its representing tasks.</li><li>The meeting starts. One after another, each person answers the three BIG questions. What did you do yesterday? What will you do today? Any blocking points?</li></ul><blockquote>“Yesterday I worked on task 8976. Today I will still work on it. I have no blocking points.” (90% ( I guess) of people during Daily Scrums)</blockquote><ul><li>15 minutes later (at most), the meeting is over. Some people keep on discussing impediments. Others go back to their seat.</li></ul><h4>The problem</h4><p>In my opinion, Daily Scrums become inefficient when they turn into a<strong> task status report</strong>. Regrettably, this is quite common. 😤</p><p>Is it really interesting to know how Development Team members advance on their tasks every day? Isn’t that a form of micromanagement? 😐</p><h4>What does the Scrum guide tell us about Daily Scrums?</h4><p>The Scrum guide does not tell you HOW to conduct your events. It does more than that. I selected the 3 following sections to help us define and understand <strong>the purpose of the Daily Scrum</strong>. 📖</p><blockquote>“Daily Scrums improve communications, eliminate other meetings, identify impediments to development for removal, highlight and promote quick decision-making, and improve the <strong>Development Team</strong>’s level of knowledge. This is a key inspect and adapt meeting.” (<a href="https://scrumguides.org/docs/scrumguide/v2017/2017-Scrum-Guide-US.pdf">Scrum Guide</a>, p. 12)</blockquote><p>And…</p><blockquote>“Every day, the <strong>Development Team</strong> should understand how it intends to work together as a self organizing team to accomplish the Sprint Goal and create the anticipated Increment by the end of the Sprint.” (<a href="https://scrumguides.org/docs/scrumguide/v2017/2017-Scrum-Guide-US.pdf">Scrum Guide</a>, p. 12)</blockquote><p>Let’s not forget about the role of the beloved Scrum Master.</p><blockquote>“The Scrum Master ensures that the Development Team has the meeting, (…) The Daily Scrum is an internal meeting<strong> for the Development Team</strong>. If others are present, the Scrum Master ensures that they do not disrupt the meeting.” (<a href="https://scrumguides.org/docs/scrumguide/v2017/2017-Scrum-Guide-US.pdf">Scrum Guide</a>, p. 12)</blockquote><p>Is it a little clearer now?</p><h4>Takeaways from the Scrum Guide</h4><p>The first question you can ask yourself is:</p><ul><li>Who benefits from your Daily Scrum?</li></ul><p>If the answer is not “<strong>the Development Team</strong>”, then you can assume that you are doing it wrong. In the 3 sections above, I have put the “<strong>Development Team</strong>” in bold to emphasize it. And I meant it. This meeting is for the benefit of the Development Team.</p><p>The Scrum Master ensures that the meeting takes place. They also ensure that the Development Team is <strong>not disturbed</strong> by other stakeholders that might want to participate. It is important that the Development Team communicates freely.</p><p>The second question you can ask yourself is:</p><ul><li>Does your Daily Scrum serve the right purpose?</li></ul><p>To help you answer this question, I came-up with the following questions. They are inspired from the Scrum Guide’s section mentioned above. And I realize that I am asking questions to answer a question...</p><p>Does your Daily Scrum:</p><ul><li>Improve your team’s communication?</li><li>Eliminate other meetings?</li><li>Help you identify impediments?</li><li>Highlight and promote decision-making?</li><li>Improve the Development Team’s knowledge level?</li></ul><h4>Our improved Daily Scrum</h4><ul><li>It is 9:00 am. Same time everyday. ⏰</li><li>The team gathers around the Scrum Board. Same place everyday. The level of motivation is NOT low. 😺</li><li>The Scrum Board is a white board with sprint objectives on it.</li><li>The meeting starts. The Development Team is responsible for conducting the meeting. Each person talks freely. Important subjects and elements are written or drawn on the board. Once something is done, the team erases it. The team is focused on the sprint goals, the eventual impediments, and decisions to take. 🎯</li><li>At most, 15 minutes later, the meeting is over.</li></ul><blockquote>“I am advancing well on the stories for this goal. Solved the issue I had with CORS. I talked to the Customer Team to tell them we will be ready in 2 days. So we will test the new feature together. I’ll give you feedback on Thursday.” (A Development Team member)</blockquote><p>Notice the difference between this and the standard Daily Scrum script? The developers still answer the big 3 questions, but instead of focusing on tasks (and their numbers), they focus on <strong>the bigger picture of the sprint goals</strong>. And, it is natural speech.</p><figure><img alt="Goal-oriented Daily Scrum" src="https://cdn-images-1.medium.com/max/756/1*FBosYs5l0mH5f9YHBIZhyw.png" /><figcaption>Goal-oriented Daily Scrum</figcaption></figure><figure><img alt="Daily Scrum’s purpose" src="https://cdn-images-1.medium.com/max/649/1*-GsbgRLMe0UKjm_PEu7mlg.png" /><figcaption>Daily Scrum’s purpose</figcaption></figure><h4>Challenges</h4><p>The “goal-oriented” Daily Scrum works great with people physically standing-up around a Scrum Board. But, more and more teams are made up of people working remotely. Here is the challenge:</p><p>Can we take Daily Scrum online?</p><p>I am curious to know if such a meeting could be as efficient with remote attendees. I believe that having excellent tools is a prerequisite. But, won’t the quality of the interactions between people decrease? I am afraid so.</p><p>Still, I am looking forward to trying it with remote attendees.</p><h4>Conclusion</h4><p>Why do you do the Daily Scrum?</p><p>If you need the status of each task, then the <strong>task-oriented</strong> approach would meet your needs. But, you might miss the very essence of the Daily Scrum.</p><p>The Daily Scrum should<strong> help your Development Team to work efficiently towards its goal</strong>. Therefore, you might want to focus the Daily Scrum around goals and not tasks.</p><p>Each team is different and needs to work out what works best for them. But, it is worth making your Daily Scrum great (again). It is something that you do every day. It is important that your <strong>Development Team members enjoy this meeting</strong>.</p><h4>Shout out</h4><p>I got inspired to write this article after reading “<a href="https://medium.com/@morgler/why-your-daily-scrums-suck-part-1-f77a5a38ceac">Why your Daily Scrums suck (part 1)</a>”. In this article, the author shares “Alarm signals you should know”. I suggest you read this article to find out if your Daily Scrum sucks.</p><p>Thank you for reading !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=598a17773708" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/goal-oriented-daily-scrum-598a17773708">Goal-oriented Daily Scrum</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[Estimate user stories using animals]]></title>
            <link>https://medium.com/swlh/estimate-user-stories-using-animals-184c4c3381b2?source=rss-85bec1340635------2</link>
            <guid isPermaLink="false">https://medium.com/p/184c4c3381b2</guid>
            <category><![CDATA[sprint-planning]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[estimations]]></category>
            <dc:creator><![CDATA[Tolgay Budayici]]></dc:creator>
            <pubDate>Thu, 24 Oct 2019 06:28:09 GMT</pubDate>
            <atom:updated>2020-05-15T15:40:22.784Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to estimate user stories using animals</h3><h4>From story points to animals for a real sense of relative estimates.</h4><p>Hamsters, cats, wolves, bears and other animals help our Scrum Team estimate user stories in such an efficient way! And “WOW”, I just wrote the best introductory sentence of my life.</p><p>Most of “Agile teams” estimate user stories with Story Points. Short summary: Story Points are relative values that rate the complexity, the risk and the effort to implement a given task. This practice is widespread and offers many <a href="https://rubygarage.org/blog/3-reasons-to-estimate-with-story-points">benefits</a>. Our Scrum Team used Story Points for a few months. But, one major drawback made us change our approach.</p><p>Today, we use animals as an abstraction from Story Points. This approach gives a real sense of relative estimates. And, it unexpectedly improved our team cohesion.</p><p>In this post, I will explain my transition from using Story Points to animals. I will also explain how I calculate our Scrum Team’s velocity. Finally, I will explain how I translate animals into man/days if needed for business stakeholders.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*349vd7j9s6gpPafw4Ty2ng.png" /><figcaption>User story estimation with animals</figcaption></figure><h4>Relative values in brief.</h4><p>Relative estimates consist of judging how big or complex a task is in comparison to other tasks. And you know what? People tend to be very good and very quick at comparing things. For example: if you look at two people around you now, I am sure you can tell which one is bigger or whether they are of similar size.</p><p>And the star of relative estimates is Story Points…</p><h4><strong>Here is why I am not convinced with Story points.</strong></h4><p>Just as hours and man/days, Story Points are numerical values. Most of the time, they are based on the (<a href="https://www.mountaingoatsoftware.com/blog/why-the-fibonacci-sequence-works-well-for-estimating">modified</a>) Fibonacci sequence (1, 2, 3, 5, 8, 13, 20, 40, 100). With this approach, there is a high risk that people associate Story Points to hours or man/days.</p><p>This is exactly what happened to our Scrum Team. We unconsciously linked story points to man/days. Basically, 1 point was equal to 1 day, 3 points to 3 days, and so on. In the chart below, you can see our team’s commitment for the first 4 sprints. The sum of Story Points varies from 26 points to 30 points. Basically, each of the 3 developers committed to approximately 10 points. The 10 points per person represent the 10 days of the sprint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/403/1*V2N63yfGoFcUaNIHtlSPHA.png" /><figcaption>Scrum Sprint commitment with Story Points</figcaption></figure><p>We had a problem there. Our Story Points did not make any sense. We were unable to give a real sense to relative estimates. This is the reason why we stopped using numerical values to estimate user stories.</p><h4><strong>From Story points to animals.</strong></h4><p>We changed our approach. We started using non-numerical values as a way to « force » relative estimation. With relative values, the unit you use is irrelevant. But, there is one important thing. You must be able to identify how big an element is in comparison to the others.</p><p>Here is what we do.</p><p>We keep the Fibonacci sequence as a basis and we abstract it with animals. This way, 3 points is a rabbit, 5 points is a cat, 8 a wolf, etc. It is that simple.</p><figure><img alt="User story estimation" src="https://cdn-images-1.medium.com/max/1024/1*9tENlaZIy6ukWvwcy_nOIQ.png" /><figcaption>User story estimation with animals</figcaption></figure><p>It is critical for the product owner to never show the link between the Story Points and the animals to the Development Team. The worst thing that can happen is that a developer asks “what animal was 8 points again?”. Or even worse: “How many man/days is a lion again?”.</p><p>Not important but important: You can use any relative value you want. It is irrelevant. Other examples could be: t-shirt sizing (S, M, L), transportation (bike, car, plane), fruits (grape, apple, watermelon).</p><h4>Biggest benefits of animals.</h4><p>First and foremost, using animals enabled our Scrum Team to give a real sense to relative estimates. This approach, once and for all, unbound our estimations from man/days.</p><p>What does it really mean?</p><p>Using numbers, we focused on defining “how much time will this task take in this Sprint?”. We sought unwarranted precision and confused estimates for commitments. That was a heavy mental load on the team. Since we started using animals, we switched our focus to “how much complexity can we deliver in this Sprint?”. Now, our grounding for estimates is at best effort.</p><p>The chart below highlights that our team broke the psychological link between story points and man/days. For the first 4 sprints, we committed to ~ 30 points. After switching to animals, the same team with the same capacity committed to: 2 bees (2x1) + 4 hamsters (4x2) + 4 rabbits (4x3) + 2 cats (2x5) + 1 wolf (1x8) = 40 points in sprint 5. It goes without saying that our Scrum Team’s velocity started to increase from that point.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/754/1*fP--WcvBePFWvcXo_or0Mg.png" /><figcaption>Story points vs Animals commitment</figcaption></figure><p>But wait, there’s more.</p><p>Animals brought some fun to our Backlog Refinement sessions and Sprint Planning sessions. I would even say that it fostered our team-spirit. It truly lightens the mood to decide whether a user story is a hamster or a rabbit.</p><h4><strong>How do you calculate your velocity with animals ?</strong></h4><p>As a product owner myself, I like to push our Scrum Team to commit to the maximum (and a little more) of its velocity. But, talking velocity with animals does not make much sense. Therefore, I use a little trick to go back to numbers.</p><p>In fact, a velocity of 18 points is more understandable than a velocity of 6 hamsters, 5 chicken, 2 wolves and 1 lion. At least it makes it easier to communicate with your business stakeholders.</p><p>Here is what I do.</p><p>I use a basic Excel file where I assign the Story Point value to the animal. At the end of the sprint, I add the number of animals we completed. In the table below, you can see that in Sprint 4 we completed 4 hamsters. This way I am able to calculate the velocity of our team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/761/1*IQrxqd0ZO9XswXCA_yeewg.png" /><figcaption>Team velocity</figcaption></figure><p>Example of Sprint 4</p><ul><li><strong>Capacity</strong>: 30 man/days available. 3 developer for 10 days.</li><li><strong>Story points</strong>: (2x1)+(4x2)+(4x3)+(2x5)+(1x8) = 40.</li><li><strong>Velocity</strong>: (40 (story points) / 30 (capacity))*10 = <strong>14.3</strong>.</li></ul><p>Our velocity started to improve after we switched to animals. I am not saying that the switch is the only reason for this. But, I am confident it had an impact. I like to believe that our team finally unleashed its full potential :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/754/1*gZAOOvVoaIALU5BBJxEP4w.png" /><figcaption>Story points vs Animals velocity</figcaption></figure><h4><strong>What if the business stakeholders want man/days?</strong></h4><p>Most of the time, business stakeholders want estimations in hours or man/days, not in animals.</p><p>Here is how you can translate your animals into man/days.</p><p>It is easy to track the day when a developer starts working on a task and the day he completes it. So, I simply record these values. Let’s say someone started working on a cat on Tuesday and finished it on Friday (weird sentence if out of context). This story would count for 4 man/days. Then, if someone else took on a cat on Wednesday and finished it on Thursday, the cat now counts 2 days.</p><p>A simple Excel formula helps me record the average minimum days and the average maximum days per animal (or associated Story Point).</p><p>Here are the averages of our Scrum Team (I really hope no one from my team is reading this article).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/371/1*7apB675xX2J1VmuSzdEIBw.png" /><figcaption>From animals to man/days</figcaption></figure><p>One interesting thing that we can observe is that: the bigger the animals, the bigger the difference between min and max. This variation is due to the unknown part of the bigger, more complex tasks.</p><p>So, how many man/days for this project ?</p><p>A few month ago, we did the analysis for a project. We wrote the user stories and estimated them. At the end, it had 2 bees, 9 hamsters, 8 rabbits, 6 cats, 8 wolves, 2 lions, 1 bear.</p><p>My answer was ~140 man/days.</p><p><strong>Conclusion</strong></p><p>Please note that our Team did not manage to make the most of Story Points. We failed at that. But, using Story Points is a widespread approach that many Agile teams use successfully.</p><p>In this post, I wanted to share our Scrum Team’s transition from Story Points to animals. This approach truly helped us give a real sense to relative estimates.</p><p>At the end of the day, it is up to your team to find the perfect way to estimate user stories. But, don’t forget an estimate is not a blood-oath. I want to point out that the grounding for estimates should be at best tentative.</p><p>Thanks for reading and please clap for all the cats in Scrum Sprints :)</p><p>Finally, if you use relative estimates, could you comment with the values you use? E.g. “Story Points”, “Animals”, “Fruits”. Thank you !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=184c4c3381b2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/estimate-user-stories-using-animals-184c4c3381b2">Estimate user stories using animals</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[4 steps to manage unfinished stories at the end of a Sprint.]]></title>
            <link>https://medium.com/swlh/4-steps-to-manage-unfinished-stories-at-the-end-of-a-sprint-3b21edc16d55?source=rss-85bec1340635------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b21edc16d55</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[sprint]]></category>
            <category><![CDATA[product-own]]></category>
            <category><![CDATA[user-stories]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Tolgay Budayici]]></dc:creator>
            <pubDate>Fri, 30 Aug 2019 05:18:06 GMT</pubDate>
            <atom:updated>2019-08-30T11:59:07.660Z</atom:updated>
            <content:encoded><![CDATA[<h4>It is the last day of your Sprint. You still have unfinished stories in your Sprint Backlog. What do you do?</h4><p>It is common for Scrum Teams to have unfinished stories at the end of a Sprint. We all know that this trivial situation raises many questions.</p><ul><li>Can you avoid having unfinished stories at the end of a Sprint?</li><li>What do you do with the unfinished stories themselves?</li><li>Should the Scrum Team get any velocity points for completing only a portion of the story?</li></ul><p>These questions and their answers are subject to debate. It took me many sprints to come up with my own answers. I believe I have at last established a coherent and viable process to manage this situation.</p><p>Today, I like to apply the 4 following steps to manage unfinished stories in a sprint.</p><ol><li>Identify the stories that you won’t be able to finish.</li><li>Document and estimate the remaining.</li><li>Send these stories back to the Product Backlog.</li><li>Take the unfinished stories to the Sprint Retrospective.</li></ol><p>In this post, I will explain how our Scrum Team manages its unfinished stories in a sprint. Here, it is all about my personal experience (and preferences). I hope my practical tips and tricks can help you if you are seeking for guidance in this situation.</p><figure><img alt="Managing unfinished stories in a Sprint." src="https://cdn-images-1.medium.com/max/838/1*C_ePiWiNAE8-sJ5-hbn06Q.png" /><figcaption>Managing unfinished stories in a Sprint.</figcaption></figure><h3>Unfinished stories are inevitable.</h3><p><a href="https://www.scrum.org/resources/what-is-a-sprint-in-scrum">A Sprint is a time-boxed event during which a “Done”, usable and potentially releasable product increment is created</a>.</p><p>If a Development Team member starts working on a story, he should feel confident that he can complete it before the end of the Sprint. But, self-confidence is not a guarantee. Many reasons could prevent him from finishing stories before the end of a Sprint.</p><p>I selected the 4 main reasons why our Scrum Team ends up with unfinished stories.</p><p>Some tasks turn out to be more complex than expected and estimated. It happens that developers « finish » their stories late on the last day of the Sprint. If there is no time left for code review, our Scrum Team usually prefers not to rush it. Hence, the story remains « in progress ». Then, production issues and bugs impact the sprint. We always put production first! And, Development Team members get sick from time to time. This is part of being human I guess.</p><p>I truly believe that our Scrum Team has little to none control on these events. They happened many times and will happen again. We will assume it is probable that you end up with unfinished stories in a sprint. How do you manage this situation? This I don’t know…</p><p>But, here is what I do.</p><h3>1. Identify the stories you won’t be able to finish.</h3><p>The Scrum Team should quickly be able to identify the stories it will not finish. I see 2 reasons why this is important. The Scrum Team can react accordingly to finish the Sprint. The Product Owner can communicate accordingly with stakeholders. Therefore, a few days (2–3 days) before the end of the Sprint, our Scrum Team members start challenging each other on « in progress » stories.</p><p>Here is the trick.</p><p>During the Daily Scrum, we make sure participants answer to: « do you think you will finish your stories in this sprint ? ». This comes on top of the <a href="https://www.mountaingoatsoftware.com/agile/scrum/meetings/daily-scrum">3 well-know questions</a>.</p><p>Including this question does have an impact. It raises awareness among all participants. “We must finish this important story to reach our Sprint goal. It is currently in progress. Guys, let’s make sure we get it done !”.</p><figure><img alt="Daily Scrum meeting." src="https://cdn-images-1.medium.com/max/451/1*zopBq3c6kTFVBetrK_yOmw.png" /><figcaption>Daily Scrum meeting.</figcaption></figure><p>Very important.</p><p>It might be difficult for (some) developers to admit they won’t finish a story. But, this information is critical to manage the end of the sprint. If someone needs help, you better know it as soon as possible. Therefore, it is key for the Scrum Team to build a judgment-free environment where everyone can speak openly.</p><h3>2. Document and estimate the remaining.</h3><p>You have now reached a point where you know you will not be able to finish some stories. What do you do now? Scrum Teams are often torn on this situation. Some will not think about it and finish their stories asap, which I can understand. Others will try to find a proper way to manage their unfinished stories. Here is how our Scrum Team proceeds.</p><p>We first document the remaining.</p><p>We add a new section called “Remaining” to the story description. This can be done by the Development Team member (with the help of the Product Owner if necessary). In this section, the we describe what is remaining to complete the task. Or, the assignee could describe what has been implemented (only if it helps). This should not take much time.</p><p>Someone who just spent several days working on a story knows exactly what is remaining. Therefore, it is best to write this small extra description right away, while it is still fresh.</p><p>I am advocating for this “Remaining” section. In fact, it helps to put words on the reasons which are preventing the Development Team from finishing the stories. With words, you will get a better understanding of the situation. This is a great opportunity learn.</p><p>We finished documenting the story. We then estimate the remaining.</p><p>The Development Team member who worked on the story can use the “Remaining” section to give a new estimate to story. Or, the Scrum Team could do it during the Backlog Refinement. This is up to your planning.</p><p>Here is a scenario we often encounter.</p><p>Let’s say the initial estimation for a story was 8 points. The Sprint finishes. There is only the code review remaining to complete the story. The Development Team member who worked on it would probably estimate the remaining to 1 point. If the remaining consisted of writing acceptance tests, then the new estimation could be 3 points. This is up to the Development Team member’s experience and common sense.</p><figure><img alt="Documenting and (re)estimating unfinished stories." src="https://cdn-images-1.medium.com/max/776/1*RCVW6FDhuXqN7A98Vca_Kw.png" /><figcaption>Documenting and (re)estimating unfinished stories.</figcaption></figure><p>Time to answer the critical question.</p><p>Should the Scrum Team still get any velocity points for the stories it did not finish?</p><p>There are my ways to answer this question. Here, I am explaining how our Scrum Team decided to manage velocity points.</p><p>My personal view on this one is a little drastic. Our Scrum Seam only gets velocity credits for the stories it finishes. It is binary: “Done” or “Not done”. <strong>As a team, we want our velocity to reflect what we are able to complete in a Sprint</strong>. Therefore, our Scrum Team does not get any velocity points for unfinished stories.</p><h3>3. Move the story back to the Product Backlog.</h3><p>This is serious. You should never automatically move an unfinished story to the next Sprint. You should first move it to the Product Backlog where it will go through prioritization (again).</p><p>Why should you move it the Product Backlog first?</p><p>The Product Owner is responsible for prioritizing the Product Backlog. He should decide on what the Development Team will work on next. An unfinished story from a previous sprint will probably get a high priority. In fact, it is nice to finish something you started. But, the priority of a story might change from one sprint to another.</p><p>When should you move it to the Product Backlog?</p><p>This is a tricky question. I like to do it on the last day of the Sprint. Why so? Because it does not matter so much to do it earlier. And, because you never know… There is always a chance the Development Team manages to finish the story. For example, other Development Team members might finish their stories early. They could help. Or, the developer might have a stroke of genius.</p><h3><strong>4. Take the unfinished stories to the Sprint Retrospective.</strong></h3><p>This might be my favorite part of the process.</p><p>I really like to take the unfinished stories to the Sprint Retrospective. It is a great opportunity to reflect on what happened. Why were you not able to finish this story? Was the description incomplete or unclear? Did you have technical problems?</p><p>Here is what happens.</p><p>We start our Sprint Retrospectives discussing the stories we did not finish in our last sprint. The Development Team members share their insights on the unfinished work. At this point, the Scrum Team is (very) familiar with the stories. Therefore, we mainly focus on the « Remaining » section.</p><p>It only takes 5 to 10 minutes every 2 weeks. And this only happens if you have unfinished stories in a Sprint. This practice helped us detect recurring issues and work on them. For example, we noticed that we often did not finish stories because of tests. We realized that we underestimated these tests in our estimates. So, we reacted. Today, during the Sprint planning, we discuss the tests for the stories and take this aspect into consideration for the estimation.</p><p>This is a great learning opportunity that does not cost much.</p><h3>In Brief.</h3><p><strong>Step 1</strong>. A few days before the end of the sprint, during the Daily Scrum, we raise attention on stories we might not be able to finish. This gives an opportunity to act as a team to finish the necessary work. As for the Product Owner, he gets the chance to communicate with stakeholders accordingly.</p><p><strong>Step 2</strong>. The Sprint is about to end. The Scrum Team knows it will not be able to finish some stories. We document and estimate the remaining work.</p><p><strong>Step 3</strong>. We move the unfinished stories to the Product backlog. We close the Sprint. The Scrum Team only got velocity credits for completed tasks. The Product Owner can (re)prioritize them according to the remaining and the estimate.</p><p><strong>Step 4</strong>. We take the unfinished stories to the Sprint Retrospective. The Development Team members share their insights. We learn and we improve as a team.</p><h3><strong>Conclusion.</strong></h3><p>In this post, I wanted to share the most efficient way I experienced managing unfinished stories in a Sprint. I took you through 4 steps that frame this trivial situation. I really feel like these 4 steps smoothly lead the story through its natural life cycle.</p><p>How do you manage unfinished stories at the end of a sprint ? What are the main reasons that prevent your Team from finishing the Sprint Backlog? Do you also take these stories to the Retrospective ? What do you think about these 4 steps?</p><p>I’ll be more than happy to have your feedback and read your questions and comments.</p><p><em>My last article was definitely more fun than this one ! I explained what our Scrum Team does when </em><a href="https://medium.com/@tbudayici/finishing-a-scrum-sprint-early-means-time-for-innovation-1f7b09c45d4f"><em>finishing a Sprint early</em></a><em>.</em></p><p>Regarding the unfinished stories in a Sprint. I would also recommend you read:</p><ul><li><a href="https://www.mountaingoatsoftware.com/blog/handling-work-left-at-the-end-of-a-sprint">Handling work left at the end of a Sprint</a></li><li><a href="https://blog.codecentric.de/en/2016/09/scrum-unfinished-user-stories/">How to handle unfinished user stories in Scrum</a></li></ul><p><em>Thank you for reading !</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b21edc16d55" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/4-steps-to-manage-unfinished-stories-at-the-end-of-a-sprint-3b21edc16d55">4 steps to manage unfinished stories at the end of a Sprint.</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[Finishing a Scrum sprint early means time for innovation]]></title>
            <link>https://medium.com/@tbudayici/finishing-a-scrum-sprint-early-means-time-for-innovation-1f7b09c45d4f?source=rss-85bec1340635------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f7b09c45d4f</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[sprint]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[product-owner]]></category>
            <dc:creator><![CDATA[Tolgay Budayici]]></dc:creator>
            <pubDate>Tue, 26 Feb 2019 22:39:48 GMT</pubDate>
            <atom:updated>2019-02-26T22:39:48.642Z</atom:updated>
            <content:encoded><![CDATA[<h4>When you finish your sprint early, you get legit time to encourage forward thinking and push developers to innovate.</h4><p>Scrum imposes an intense pace. In fact, your team will work at the highest of its velocity to deliver product increments with high business value. It would not really make sense to commit to less than that. But, is it not at the detriment of innovation and creativity? Do you get any time in your sprint to let developers try out new things?</p><p>Well, you might not have realized it yet, but Scrum is a great framework for innovation. There is a trick that will: motivate your development team to adopt forward thinking in daily work; drive technical innovation across the company; and improve the general quality of products.</p><p>In this post, I will explain why I decided to introduce more innovation in our sprints. I will also tell you where I found the time to do so in sprints. And, what results our team got from this practice after more than 15 sprints (of two weeks each).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X2fDro4hA7ej0w2PqphOxA.jpeg" /><figcaption>Innovation with Scrum</figcaption></figure><p>It all started with some frustration.</p><p>During sprint plannings and sprint retrospectives, I noticed some frustration from developers. Why? Because with Scrum, they rarely get the chance to be creative, innovative, develop new technical skills, or experiment new technologies. In fact, sprints impose a high pace. The development team works at the highest of its velocity to mainly deliver product increments with high business value.</p><p>For a few sprint plannings, a member of the development team, named Gab, kept pushing for the implementation of Hystrix. And, this suggestion made absolute sense. In fact, in our microservices-based environment, Hystrix was a great solution to control the interaction between services by providing fault and latency tolerance. But, in our company, we were not using Hystrix. It had never been in the technological pipe either.</p><p>There, I was between a rock and a hard chair. On one hand, I did not see how I could add the implementation of Hystrix in a sprint. We had so many high value business features waiting in the product backlog. How would I justify the cost of implementing Hystrix to our business sponsor? How would I prioritize it over business features? On the other hand, I really wanted to encourage developers to think forward and take initiatives to drive technical innovation and improve our products. But when?</p><p>Do you get any “free” time during your sprints that you could use to introduce innovation?</p><p>When one sprint ends, the next one starts right away, right? This is best practice. But, does it mean that you have no free time in your sprints? Of course not.</p><p>Here is when you get this free time.</p><p>It is so difficult to plan a Scrum sprint in a way that the developers work at full capacity throughout the entire sprint. It might happen that a Scrum team over estimates the work and effort necessary to reach the sprint goals. I mean, who would know, in advance, what it takes to achieve a task or even reach a sprint goal?</p><p>Hence, it may happen that your team finishes the sprint early, or that a developer finishes off all of his tasks before the end of the sprint. In fact, people naturally tend to be careful. So, how would you manage this « unexpected » and « unplanned » available capacity you have until the end of the sprint?</p><p>I guess that most of the time, product owners will use the product backlog to assign new tasks to the developers. This practice raises many questions that I will not talk about in this article. I am sure there are many other practices that product owners use to manage a sprint finishing earlier the planned. Here is my favorite practice:</p><p>How about giving your team this free time to create, innovate, and improving your products?</p><p>Wait, giving developers free time to innovate does ring a bell, does it not?</p><p>This idea, or inspiration, originally came from Google’s legendary « 20% policy for side projects ». I am not quite sure how it works there, or even if it is still in place, but I truly believe it is a great idea for multiple reasons. In brief, you encourage forward thinking and give your employees a real opportunity to personally take initiatives, defend their ideas, and implement solutions.</p><p>As I said, Google’s “20% policy for side project” was just an inspiration. In this context, I am not talking about side projects. I am talking about finding quick wins to improve the products we are working on.</p><p>And, here is how it goes with Scrum.</p><p>I asked Gab to take some time to analyze Hystrix and plan a short presentation for our Scrum team. At the end of this meeting, we added the following Epic to the product backlog: « Hystrix implementation in the Delivery component ». Under this Epic, we had a 3 user stories. All together, we estimated the implementation of Hystrix to approximately 5 man/days. (Arf, I don’t like to talk estimates in man/days. The real estimates for these stories were 2 hamsters and 1 dog, but this is another story).</p><p>There we had theses stories in the product backlog. We now had to find a way to add them to a sprint.</p><p>A few weeks later, Gab finished his tasks early in a sprint (on a Wednesday). The other developers were on track with their tasks. No worry there. So, this was a great opportunity for Gab to start working on the implementation of Hystrix. By the end of the sprint, he had only one task left. We planned it as a priority for the next sprint. There, in two sprints, we added this new technology to our component. Today, Hystrix is implemented in multiple components in our company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HAnrVtcti2ewZpNnJ9nf2g.png" /></figure><p>Why does this work great with Scrum?</p><p>I truly believe that you cannot cheat with Scrum. As a Scrum team, you know your velocity. The product owner will challenge the team to achieve as much work as possible during the sprint. The team will most probably commit to quite aggressive sprint goals. At some point, all stakeholders (business sponsors and customers) get the idea of what the Scrum team can deliver in a sprint. They will expect no less.</p><p>As long as you maintain a high level of velocity (or improve it), and as long as your business sponsors and customers are happy, you should believe that you are doing right. For all these reasons, finishing a sprint early should not be a problem. It should not be considered as bad estimates. It is not cheating. So, why not giving this time to developers so that they can innovate?</p><h3><strong>5 rules to manage these innovation initiatives</strong></h3><ol><li>Any initiative must intend to improve a product. This is not a proper google-style side project.</li><li>The initiative should be presented to the Scrum team and concerned stakeholders, such as architects, for validation.</li><li>If accepted, then add the initiative to the backlog for the follow-up. I like to label these stories as “innovation-story”.</li><li>If you started it, you must finish it. Your initiative should not remain an unfinished PoC.</li><li>When implemented, communicate it to all interested stakeholders.</li></ol><h3><strong>The upside and the downside</strong></h3><p>On the upside, giving this free time to the development team will enhance forward thinking. Team members will know that they can share their ideas and actively contribute to the technical evolution of products. It will also be a chance for them to gain new technical skills. As a whole, the motivation of your team will remain high. This will also help you build more robust products while driving technical innovation in your company in general.</p><p>On the downside, this is quite complicated to manage due to its unpredictable nature. In fact, getting free time at the end of sprint will not happen on every sprint. It is more about being ready to seize an opportunity to innovate when it comes. Also, I want to raise two risks here. You have no control on who finishes a sprint early. What if it is always the same developer? And again, if you start something, you must finish it. Otherwise, you have the risk to have eternal proof-of-concepts (PoC).</p><h3><strong>Conclusion</strong></h3><p>Innovation is important. Your team members should feel that they can have an impact and drive technical innovation within the team, but also across the company in general. I believe this is key to maintain motivation high. Then, working with Scrum sets a high pace. Introducing innovation in sprints requires your team to have a high level of maturity.</p><p>I would definitely recommend trying this practice once you consider your team mature enough. Do you have a fast and constant cruising speed? Also, it is key to have a relationship of trust with your business sponsors and customers. If this is the case, I suggest you give this practice a try.</p><p>Working this way, our Scrum team implemented Hystrix, FlywayDB and Selenium within 12 sprints (6 months). In parallel, our team always committed to sprints at the level of our velocity, or higher. Our business sponsors and customers were still happy and satisfied with our work.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f7b09c45d4f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>