<?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[Dennis Nerush’s Blog - Medium]]></title>
        <description><![CDATA[Software, Management and People - Medium]]></description>
        <link>https://medium.com/dennis-nerush?source=rss----720a8b8ea39b---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Dennis Nerush’s Blog - Medium</title>
            <link>https://medium.com/dennis-nerush?source=rss----720a8b8ea39b---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 20:22:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/dennis-nerush" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Localization sounds simple, but it is not: Part 2 — Supporting multiple currencies]]></title>
            <link>https://medium.com/dennis-nerush/localization-sounds-simple-but-it-is-not-part-2-supporting-multiple-currencies-204d5bf60e38?source=rss----720a8b8ea39b---4</link>
            <guid isPermaLink="false">https://medium.com/p/204d5bf60e38</guid>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[localization]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[currency-exchange]]></category>
            <category><![CDATA[currency]]></category>
            <dc:creator><![CDATA[Dennis Nerush]]></dc:creator>
            <pubDate>Fri, 20 Oct 2017 11:18:17 GMT</pubDate>
            <atom:updated>2017-10-20T11:18:05.272Z</atom:updated>
            <content:encoded><![CDATA[<h4>Full guide for localizing your application covering Translation, Currency, Global vs. Local content, UI adjustments and R&amp;D culture.</h4><p>This is the second post in the localization guide series. In this post will cover the second aspect of localization, which is supporting multiple currencies across the different locales.</p><p><a href="https://medium.com/dennis-nerush/localization-sounds-simple-but-it-is-not-part-1-intro-translation-95796b5b99f5">Part 1: Translation</a></p><p><strong>Part 2: Supporting multiple currencies (We are here)</strong></p><p>Part 3: Serving Global vs. Local content (Not published yet)</p><p>Part 4: Handling UI adjustments (Not published yet)</p><p>Part 5: Creating localization aware R&amp;D culture (Not published yet)</p><h3>Currency</h3><p>Your application might sells products, services or displays prices for any reason. You want to make sure that users will see these prices in their locale currency. Users who browse your site from France expect to see the prices in Euro, while those who browse from England expect to see pounds.</p><p>Before we dive into the importance of displaying the currency in its correct format, let’s first understand what is the correct type to use when working with prices in your code base.</p><h4>int? double? decimal? Money?</h4><p>What would be the best type for the price property of your product? It cannot be <em>int </em>since prices can have fractions. It might be <em>double</em>, however it is not best practice for prices.</p><p><a href="https://stackoverflow.com/questions/6341855/how-to-decide-what-to-use-double-or-decimal">How to decide what to use - double or decimal?</a></p><p>So we are left with <em>decimal</em>. It will allow us to easily display a 10.55 price. Hold on. 10.55 what? Dollar? Euro? NIS? Canadian dollar?</p><p><strong>Price is not only a number</strong>. Price is a number <strong>with currency, </strong>so the best type for currency is actually <strong>an object</strong> that has both the amount and currency properties. You can implement it by yourself, however you need to remember that simply putting the currency sign is not enough. Every currency has its own format and display.</p><h4>Currency Formats</h4><p>Every currency has its own format and rules:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/0*XaNyme2jTXCdc4KC.png" /></figure><p>It might be very confusing for your users to see prices in wrong formats. Money is a very sensitive topic to the users, we don’t want to make them distrust our site due to wrong currency formatting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/289/1*pD3DxprtYGyvd6EvGg0xhA.png" /><figcaption>Note the difference between using a dot and a coma</figcaption></figure><p>Etsy has a great post about the challenges of supporting and displaying currencies in their correct formats:</p><p><a href="https://codeascraft.com/2016/04/19/how-etsy-formats-currency/">How Etsy Formats Currency</a></p><p>There are great open sources out there that solve this problem, like the one we’ve chosen — <a href="https://github.com/remyvd/NodaMoney">Noda Money</a>.</p><p><a href="https://github.com/remyvd/NodaMoney">remyvd/NodaMoney</a></p><p>It provides you both the Money object along with all the currency formats and also variety of Money arithmetical operations and casts.</p><h4>Don’t perform pricing calculations in the client side</h4><p>On of the biggest difficulties that we had while refactoring the code to support multiple currencies was pricing operations that took place in the client. Some javascript string manipulators like:</p><p><em>var price = 10 +’$’;</em></p><p>You need to avoid performing such operations in the client since it will be extremely hard to introduce other currency signs besides $ and exposing pricing calculation logic in the client is both dangerous and wrong, since it’s probably not the client’s responsibility to own the pricing logic. The server should be the only place where such logic happens.</p><h4>Exchange rates</h4><p>There is a good chance that your application will allow users to see items from different currencies. However you don’t want to present items with different currencies side by side, you’ll want to exchange the different item’s currencies to a single, locale relevant currency. In order to achieve that you’ll need to find the exchange rate and convert the $ into Euros. There is a simple and fast exchange API that is maintained by Google.</p><p><a href="http://fixer.io/">Foreign exchange rates and currency conversion JSON API</a></p><p>You can store the exchange rates in cache every ~10 minutes and use them for the price conversion to reduce API calls.</p><h4>“Price is only approximate”</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/209/1*YqDB3OjaPvphUxH4EkaGKA.png" /><figcaption>This is how exchanged prices are displayed on Ebay</figcaption></figure><p>Even if you exchange the prices using real-time exchange rates, <strong>the price is only approximate</strong>, since the actual final price is determined by the payment provider. Every provider has its own exchange rates — Paypal is different from your credit card company i.e.</p><p>By the way, as a user you should always pay using the local currency of the site, don’t let the site or PayPal do the conversion for you since they will usually have a higher exchange rate than your bank.</p><p><a href="https://www.currencyfair.com/blog/avoid-paypal-hidden-fees-for-international-money-transfers/">Avoid PayPal Money Transfer Currency Conversion Fees | CurrencyFair</a></p><h3>Summary</h3><p>Your need to get yourself ready for some refactoring in case you need to support multiple currencies. Avoid calculations in the client, make price an object with both amount and currency properties and use proven open source that handles all the different formats for you.</p><h3>Localization sounds simple, but it is not:</h3><p><a href="https://medium.com/dennis-nerush/localization-sounds-simple-but-it-is-not-part-1-intro-translation-95796b5b99f5">Part 1: Translation</a></p><p>Part 2: Supporting multiple currencies (We are here)</p><p><strong>Part 3: Serving Global vs. Local content (Go here — link will be added soon)</strong></p><p>Part 4: Handling UI adjustments (Not published yet)</p><p>Part 5: Creating localization aware R&amp;D culture (Not published yet)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=204d5bf60e38" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dennis-nerush/localization-sounds-simple-but-it-is-not-part-2-supporting-multiple-currencies-204d5bf60e38">Localization sounds simple, but it is not: Part 2 — Supporting multiple currencies</a> was originally published in <a href="https://medium.com/dennis-nerush">Dennis Nerush’s Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Localization sounds simple, but it is not: Part 1 — Intro & Translation]]></title>
            <link>https://medium.com/dennis-nerush/localization-sounds-simple-but-it-is-not-part-1-intro-translation-95796b5b99f5?source=rss----720a8b8ea39b---4</link>
            <guid isPermaLink="false">https://medium.com/p/95796b5b99f5</guid>
            <category><![CDATA[localization]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[translation]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Dennis Nerush]]></dc:creator>
            <pubDate>Fri, 13 Oct 2017 07:59:27 GMT</pubDate>
            <atom:updated>2017-10-20T11:19:12.595Z</atom:updated>
            <content:encoded><![CDATA[<h4>Full guide for localizing your application covering Translation, Currency, Global vs. Local content, UI adjustments and R&amp;D culture.</h4><p>Every business wishes to have a worldwide appearance and influence. The process of supporting different languages, currencies and serving the right content is called Localization.</p><p>In theory, this process may sounds simple. How hard can it be to translate some text and replace the $ sign with something else? In reality, is hard. It is a very complex process with many difficulties, lots of alternatives with different pros and cons as well as and plenty unknown-unknown aspects.</p><p>In most cases, applications are built to support only a single locale, language, currency, content and appearance. That makes the localization process much harder since major refactoring efforts are almost inevitable. It even becomes more complexity when the original product is still being developed while you try to localize it. It feels like changing wheels on a driving car.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*hvwLfldVhbnJTBQT.jpg" /></figure><p>Recently I had the experience to localize an American web application. I survived to tell the story and I want to share it with you in a series of 5 posts which are listed as follows:</p><p><strong>Part 1: Translation (This is where we are)</strong></p><p><a href="https://medium.com/dennis-nerush/localization-sounds-simple-but-it-is-not-part-2-supporting-multiple-currencies-204d5bf60e38">Part 2: Supporting multiple currencies</a></p><p>Part 3: Serving Global vs. Local content (Not published yet)</p><p>Part 4: Handling UI adjustments (Not published yet)</p><p>Part 5: Creating localization aware R&amp;D culture (Not published yet)</p><h3>What does localization actually mean?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*6aW9iAxpQV_xPKY-.jpg" /></figure><p>So what does localization mean? It means that your application could be used in different countries, languages and cultures around the world. It doesn’t have to support ALL the languages and ALL the cultures, but it should support more than just English and USD.</p><h4>So what do we need to do to make our American application localized for let’s say Israel?</h4><ol><li>It should be translated to native language (Hebrew).</li><li>It should display the local currency sign (NIS — ₪) instead of USD ($).</li></ol><h4>Is that all?</h4><p>The answer is ‘not exactly’. There are many more aspects that must be taken into account like separating the content of one locale from the others, changing UI according to different locales, monitoring, testing and logging activity per locale, and much more.</p><p>In this series we’ll cover all the aspects, starting with translation which by itself is a very complex process that has different ways of implementation.</p><h3>Translation</h3><p>Translation is just about replacing strings from one language to a different language, however that is not that simple and there are different ways and approaches to achieve proper translation.</p><p>Before we jump into the details, it is important to define right from that start which content you wish to translate and which one you don’t. For example, you probably don’t need to translate users or items names, description and UGC (user generated content like reviews or statues). You do want to translate the application layout which includes buttons, menus, and titles, etc.</p><h4>Machine translation vs. Human translation</h4><p>There are two ways to translate your content. One way is to use machine translation, a translation service, like google translate. To achieve this, you simply need to send it your texts and get back its translated version. It might sound perfect but if you’ve ever used google translate you probably know that its translation is far from perfect. It doesn’t handle sentences well, and it doesn’t have context for different words (right vs. right). Despite the quality of the translation, there are some huge and famous applications which use this approach. <a href="https://www.aliexpress.com/">Ali Express</a> , for instance, is one of them. It supports all the languages by using machine translation. See some “qualitative” examples below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/599/1*UROBgSvzeHFIh9Yjqyu1zg.png" /><figcaption>The original text: “Save big on our app”. The meaning of the translation in Hebrew: “Persist big on our app”</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/305/1*Onnx2fyTrLyt8fsoILFGQQ.png" /><figcaption>The order of the words remained the same, but it has no meaning in Hebrew</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/376/1*RtdK3lLLbD5PcEbQTvRRkQ.png" /><figcaption>The timer is messed up, there is no proper translation for “flash deals” in Hebrew and USD was translated to USA</figcaption></figure><p>Funny enough, this application is considered to be the <a href="https://www.forbes.com/sites/greatspeculations/2017/05/19/alibaba-continues-to-see-growth-across-segments/#33bb3c9a6d36">largest marketplace</a> in the world. So in some cases, this approach might work.</p><p>On the other hand, human translation is done by, human beings. It can be in house content managers or a 3rd party agency that specializes in translation. The disadvantage of a 3rd party agency is that they also don’t fully understand the context of the words or sentences of the app. However, I’ve found out, that in-house translation is the best solution in terms of money, time and quality of work.</p><h3>Translation mechanisms</h3><p>Once you know what content you wish to translate and you’ve defined the way you are going to translate it, it is time to think about the actual mechanism that will perform the translation. How will the translated content be delivered to your users?</p><h4>Server-side translation</h4><p>This is the most common way. Many frameworks have server-side translation built into their API. This method uses resource files which are key-value dictionaries that hold the key of the target to translate and its translation. Usually, there will be a resource file per language.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/604/0*r6oEk3Il55BtDeog.png" /><figcaption>English resource file in .NET</figcaption></figure><p>When rendering a page, the system finds resource keys in the code and replaces them with the matching resource values; hence the page is rendered with the translated content. This is a big advantage since there are no latency issues while presenting the page.</p><p>On the other hand, this approach forces you to create keys for every piece of text that you write. Sometimes the keys are readable, and sometimes they look something like this:<em> btn_enter_store_closed_error </em>which makes it difficult to read through the code and understand it.</p><p>Another disadvantage of this mechanism is that one time when the translation mechanism fails for some reason and you are left only with your keys as a fallback. Do you recognize the site?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fk2imtyU26ukz3jSkRvieA.png" /></figure><h4>Gettext()</h4><p>Another option for server-side translation is using <a href="https://en.wikipedia.org/wiki/Gettext">Gettext</a> is an internationalization and localization (i18n) mechanism that was originaly created for supporting multi-language programs on Linux. Unlike the key based option, using Gettext allows you to write your text in plain English and the phrase serves as a key to the alternative translations.</p><pre>printf(gettext(&quot;My name is %s.<strong>\n</strong>&quot;), my_name);</pre><p>The translations are kept in special files PO files which you need to maintain and load with your system in order for the translation to work. The advantage is that you no longer need to create wired keys inside your code. The disadvantage, however, is that you need to remember to add every new phrase to these files and make sure that it has a translation in all your supported languages. Nowadays, PO file became standard, hence there are applications that help you in managing and operating these files.</p><h4>Client-side translation</h4><p>The second approach is to render the page in English and let the client change the content to the correct language. The big difference here is that you no longer need key-value dictionaries. You write plain English, and in case of error your fallback is English. The translation itself happens using a 3rd party tool/layer that captures parts of the content and replaces them with the translated version.</p><p>There are two ways to achieve this. You’ll need to mark the content that you wish to translate for it to capture and replace it or you will mark what you don’t want to be translated. The latter is more preferable, since it automatically detects every phrase you have in your app besides the ones you’ve explicitly decided not to translate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/365/1*fSsaQZjG31vMyFTpoSNuvw.png" /><figcaption>Note the special “notranslate” attribute</figcaption></figure><h4>Proxy translation</h4><p>The translated content is loaded to proxy servers (CDN) and the server response is being processed by the server before it gets back to the client.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*Rap58_uQyDiM5NJo.png" /><figcaption>A request from a Russian client is being made to the server, the server returns an English response “Hello”, the proxy captures this phrase and replaces it with its Russian version.</figcaption></figure><p>The disadvantage comes when you wish to test the translated version while developing it. Proxy translations are usually integrated only to production due to integration difficulties. That makes it hard to catch UI glitches or even perform some acceptance tests on the specific language.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/651/1*BqV4-PTGs37U1lC7JYThcQ.png" /></figure><h4>Pure client side translation</h4><p>The last approach is to store the translations on the client itself and switch the content during page load. This approach usually persists the translations as a key value dictionary when the key is an English phrase (a word or a sentence) and the value is the translated content of the desired language. The user will fetch the entire translation (or parts of it) upon his first page load and then it will perform the switches in the client. The data is usually persisted in the locale storage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M3lTPq2FyYLSJYgMHFm57w.png" /><figcaption>Here you can see the English-Spanish dictionary</figcaption></figure><p>We’ve found that this approach is the best for us for several reasons:</p><ol><li>Simple management : A translation framework like <a href="https://localizejs.com/">localize.js</a> automatically detects all the existing strings in the website, publishing them to a dedicated dashboard and allowing you to decide whether to translate the phrase or not (in case of UGS i.e.).</li><li>Immediate effect : After you save the translation all the clients that will view this phrase will be updated with the new content. This way you can fix issues immediately without contacting support of some 3rd party proxy app or redeploying your code.</li><li>Works on local machines : Since the translation is persisted on the clients, it allows to translate also text during development.</li></ol><h3>Difficulties</h3><p>There are two places where translating text becomes extremely hard: CSS and JS. Sometimes we add text using <em>before/after CSS </em>selectors or simply in JS code (error messages i.e.). No framework is smart enough to detect such texts, usually we end up in refactoring the code so that the text will be delivered from the html. I strongly recommend to avoid putting strings inside client side code from the beginning.</p><h3>Summary</h3><p>As you can see, there is more than one way to translate your site. It is important to know them and also take into account their pros and cons. In my personal opinion, the process must be simple to both the one who performs the translation and for the developers to both implement and test the translation on their local machines.</p><p>Now let’s move to the next chapter (Currency). As you can guess, it is not just replacing the $ to a different sign.</p><h3>Localization sounds simple, but it is not:</h3><p>Part 1: Translation (We are here)</p><p><a href="https://medium.com/dennis-nerush/localization-sounds-simple-but-it-is-not-part-2-supporting-multiple-currencies-204d5bf60e38"><strong>Part 2: Supporting multiple currencies (Go here)</strong></a></p><p>Part 3: Serving Global vs. Local content</p><p>Part 4: Handling UI adjustments</p><p>Part 5: Creating localization aware R&amp;D culture</p><p>I want to thank <a href="https://medium.com/@thegreymatter">Omri Fima</a> for reviewing this post.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95796b5b99f5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dennis-nerush/localization-sounds-simple-but-it-is-not-part-1-intro-translation-95796b5b99f5">Localization sounds simple, but it is not: Part 1 — Intro &amp; Translation</a> was originally published in <a href="https://medium.com/dennis-nerush">Dennis Nerush’s Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weekly thoughts]]></title>
            <link>https://medium.com/dennis-nerush/weekly-thoughts-9b1af77ff4d7?source=rss----720a8b8ea39b---4</link>
            <guid isPermaLink="false">https://medium.com/p/9b1af77ff4d7</guid>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Dennis Nerush]]></dc:creator>
            <pubDate>Fri, 03 Feb 2017 16:20:40 GMT</pubDate>
            <atom:updated>2017-02-03T16:20:22.782Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/678/0*CL4AK0mLJZz0uyQv." /></figure><p>Previously I’ve talked about <a href="http://dennis-nerush.blogspot.co.il/2016/08/manage-your-life-like-you-manage-project.html">the importance of a dedicated time for personal reflection</a>, a retrospective of your life. This tool helps me to improve in all aspects of my life. However, my job is a huge part of my life — and I want to make sure that I also constantly improve in it. Moreover, I want to make sure that I constantly improve <strong>it</strong>. Therefore I’ve create a method that allows me to retrospect my work in all its aspects and, most importantly — to share it with my manager. I call it “Weekly Thoughts”.</p><p>Every Wednesday evening, I have a scheduled slot in my calendar for some time for myself (it has to be in your calendar, because <a href="http://dennis-nerush.blogspot.co.il/2014/11/that-is-not-on-calender-does-not-exist.html">what is not in your calendar doesn’t exist</a>). I write it down in an email and then send it to my manager. Unlike an actual retro, I use a slightly different format:</p><p><strong>Things I’m excited about</strong>:</p><p><strong>Things I’m concerned about</strong>:</p><p><strong>Inbound</strong></p><ol><li>What is working and we should keep doing</li><li>What is not working for me</li><li>Opportunities</li></ol><p><strong>Outbound</strong></p><ol><li>What is working and we should keep doing</li><li>What is not working for me</li><li>Opportunities</li></ol><p><strong>People</strong></p><p><strong>Recruiting</strong></p><p><strong>What concerns my manager and how I can help him</strong></p><p>As you can see, the format is different from a regular retro. The main reason is that it isn’t only a retro. Retro is a method for reflecting previous events. However, this method has several other purposes.</p><h3>What is on your mind?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/434/0*ktG3qxsAkO-V2nPi." /></figure><p>I call it “weekly <strong><em>thoughts</em></strong>” on purpose. Look at the first two points: “<em>Things I’m excited about” and “Things I’m concerned about</em>”. Unlike a usual retro, I’m not looking for action items; I just try to understand what’s made me tick this week and what’s stopped me from ticking. It can be a cool feature that I delivered, a meetup that I’ve hosted or a simple conversation that made my week. Things that make you tick, that make you happy during the day, are worth mentioning. It is easy to talk about the bad stuff — I want to cherish the good stuff, too.</p><p>The things I’m concerned about, on the other hand, I do want to address. So sometimes I’ll create personal action items for them. However, sometimes I don’t know how to treat something — like if one of my team members is leaving, or if a decision takes too long to approve.</p><p>Those things are on my mind. They concern me. For good and for bad. There is someone who should know about them: <strong>my manager</strong>. I schedule the time for my weekly thoughts on a Wednesday since it is the day before my 1 on 1 with him. This allows me to be more prepared for our meeting and also allows him to better understand me. Weekly thoughts is such a powerful tool because it allows me to share the full context of my work with my manager.</p><p>Don’t keep your thoughts to yourself. Share, ask for advice or direction.</p><h3>What is your role in the manager-employee relationship?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/431/0*Z0QSVJdpa8VrjTvD." /></figure><p>There is an important truth that all of us sometimes forget.</p><blockquote>We are not the only concern of our managers</blockquote><p>They also have goals and tasks that do not necessarily concern us. Decisions that they want to take, some efforts they are pushing and, of course, tasks from their own manager. I’ve realized along the way that the fact I have a manager doesn’t mean this is a one-way relationship. I can help him as much as he helps me. I want my manager to succeed in his goals as much as he wants me to succeed in mine.</p><p>Therefore I have a special part in my format that is dedicated for the things that concern my manager and ways <strong>I </strong>can help<strong> him.</strong></p><h3>What happens in other aspects of your job?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*ZiRR3_kedHlhA33U." /></figure><p>“Job” is a short word (so is “work”) that has many parts, aspects and responsibilities — so when I say that I want to improve my work, I want to improve it in all of its parts. I choose to divide my job into 4 aspects:</p><p>Inbound, outbound, people and recruiting (I know that in the future this format will change, since I’ll have more or different responsibilities. But it works for now).</p><p>I want to separately focus on each part, and try to see what “works for me” and what doesn’t. Each of these parts deserves its own retro.</p><p>In the <strong>inbound</strong> part, I focus on my team. How is our communication? How can we increase velocity? Are we happy? Do we celebrate wins? Do we achieve our goals, and so on.</p><p>In the <strong>outbound</strong> part, I focus on everything that is external to my team. The interfaces with our stakeholders, the product owner, peers and other teams in R&amp;D, and the company in general. Does our work hurt them? How can we share our knowledge with them? And how can we improve our process?</p><p>The <strong>people</strong> part may seem unnecessary since I already have the “inbound” part. However, my team members deserve a focused and dedicated part just for them. In the inbound section I think mostly about us as a team, a group of people who work together and can do it better. In the “people” part, I try to better understand every one <strong>individually</strong>. What makes them tick, what concerns them and how can I help them?</p><p>The last part is <strong>recruiting</strong>.<strong> </strong>Not only is recruiting a very important responsibility, it also requires a lot of time and attention. Therefore it has a dedicated part in my format, in order to see what works for me in the recruiting process and what doesn’t. Where do I and all the other recruiters waste time that shouldn’t be wasted? And what methods I find better than others.</p><h3>What opportunities are you missing?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/401/0*1GBhx77vmmevwXHH." /></figure><p>You can see that in almost every section there is an “<strong>Opportunities</strong>” part. Here I try to think a little about the future. What we should start doing now in order to improve or be ready for in the near-future. This is very powerful, since we rarely think about the future. We are so focused on today’s “fire” and tomorrow’s delivery that we basically never think about the opportunities we might be missing. By the way, you will need to miss some of those opportunities for whatever important reason. But there is a big difference when you knowingly miss opportunities and when you simply miss them because you are not aware of them in the first place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/405/0*u2nNZBthheySTIMF." /></figure><p>My first job was at the age of 12 (I washed the stairs of my building), and since then I have worked almost all the time — after school, in the summer, during my military service (I consider my army duty as a software engineer as work) and now. So for the last 13 years I’ve been constantly working. I have learned that if you try to think further ahead, constantly try to improve yourself and your surroundings, and share your thoughts with your manager, you will gain two very important things: <strong>Change </strong>and<strong> Trust</strong>.</p><p><strong>Think</strong> about it ;)</p><p><em>Originally published at </em><a href="http://dennis-nerush.blogspot.com/2016/12/weekly-thoughts.html"><em>dennis-nerush.blogspot.com</em></a><em> on February 3, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b1af77ff4d7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dennis-nerush/weekly-thoughts-9b1af77ff4d7">Weekly thoughts</a> was originally published in <a href="https://medium.com/dennis-nerush">Dennis Nerush’s Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Adventures in the Interviews Jungle]]></title>
            <link>https://medium.com/dennis-nerush/my-adventures-in-the-interviews-jungle-6e14ce126452?source=rss----720a8b8ea39b---4</link>
            <guid isPermaLink="false">https://medium.com/p/6e14ce126452</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Dennis Nerush]]></dc:creator>
            <pubDate>Wed, 04 Jan 2017 08:17:32 GMT</pubDate>
            <atom:updated>2016-03-14T06:28:51.253Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/725/1*mRpUtd5Qzr-zi-E92XF3Kw.jpeg" /></figure><p>As you know I recently switched jobs and while finding a new one I’ve done quilt a lot of interviews in different companies.</p><p>I really enjoyed the process! Some days I had 3 interviews in a row! My friends called me insane but hey, I can easily talk about software all day long!</p><p>While looking for my next job I took the way a company’s interview process as a major factor for my final decision.</p><p>In my opinion the interview process should reflect the <strong>values, the culture and the professional level</strong> of the company. A company that values my time, tries to make me feel like home and asks question that actually reflect my knowledge is most likely a better company than a one that does the opposite.</p><p>In this post I want to share some of the questions and tasks that I had in my interviews. Some of them were great. They actually allowed me to show what I know and the overall process made me feel wanted and special. On the other hand there were some that were a complete waste of time.</p><p>Let’s start.</p><h3><strong>Ridiculous, exhausting and a waste of time</strong></h3><h4><strong>Bizarre questions</strong></h4><p>“How many hair cut places are there in Tel Aviv? How many golf balls can fit into a bus?” These questions were famous due to Google’s interview process where candidates had to answer super hard and bizarre questions.</p><p>Few years ago even <a href="http://www.businessinsider.com/google-hiring-practices-interviews-2014-7">Google stopped asking these questions</a>!</p><p>“<strong><em>They are a complete waste of time</em></strong>” — Laszlo Bock, Google’s senior vice president of people operations. 2014.</p><p>I couldn’t agree more — these questions don’t test anything and furthermore don’t have anything to do with the candidate’s future work.</p><p>When my interviewer asked me these questions I asked if their company found it useful. He replied ‘<em>yes, Google does it and so do we</em>’.</p><p>That was a red sign for me — if you copy from someone at least stop when they do.</p><h4><strong>Endless trivia questions</strong></h4><p>By “trivia” I mean questions that don’t make the candidate think. Usually they start with <em>what</em> and not with <em>why.</em> Those questions check whether the candidate knows the answer or not. “<em>What is HTTP? What is a transaction</em>?” They don’t focus on the candidate understanding of why something is used or how is it used. Only if he knows the definition.</p><p>Honestly — when was the last time that you used a Mutex? Or had trouble with the GC? Either way it’s googlable. So it’s ok not to know <strong>all</strong> the answers.</p><p>I think that <strong>some </strong>trivia questions can be useful for three reasons:</p><p>1. To check if the candidate is serious about the job and that he took his time to prepare for the interview. Serious candidates usually prepare themselves and come ready for interviews.</p><p>2. To check that the candidate is not a complete noob/code monkey. It’s a bad sign if he cannot answer <strong>any</strong> question.</p><p>3. To check if the candidate knows how to say that he <strong>doesn’t</strong> know something. If he tries to lie and make up an answer in the interview then he will probably do it again in a real situation.</p><p>In one interview I had <strong>an hour and a half</strong> of trivia questions! Needless to say that it was one of the most exhausting interviews I’ve ever done.</p><p>In the end I asked the interviewer if they actually need all this knowledge to their day to day work. He told me <strong>no</strong>. They don’t even use multi threading but he questioned me for 40 minutes about mutexes, threadpool and thread synchronization.</p><h4><strong>Writing code for hours</strong></h4><p>In one company I had a coding test as the second interview phase. I think that it’s essential to check the way the candidate writes code <strong>but</strong> and this is a big <strong>but</strong> it shouldn’t <strong>take 6 hours</strong>@#$!</p><p>A small coding task should check if the candidate writes tests (perhaps TDD), uses SOLID principles and that his code is clear and well written. A simple calculator task can check all these. Writing a 6 hours long project is a waste of both the candidate’s time and the interviewer’s.</p><p>The worst part is that it’s in the company office (and not a home task) so the candidate will be stuck for 6 hours in a row writing code for some test in some company. Writing some code in the company office is good but only if it doesn’t takes the whole day.</p><h4><strong>Text exams</strong></h4><p>As I mentioned before, there shouldn’t be more than a few trivia questions in an interview. The only thing that is worse the asking 30+ trivia questions is having them in a written exam while the interviewer is not even present.</p><p>Those tests give the candidate the feeling that his time is not valuable enough for an interviewer to be present while he answers.</p><p>As a candidate I want to have the feeling that I’m wanted and that my time is valued. Leaving a candidate in a room alone with a text exam does exactly the opposite.</p><p>It can be even worse if the text exam is <a href="http://www.hanselman.com/blog/WhatGreatNETDevelopersOughtToKnowMoreNETInterviewQuestions.aspx">Scott Hanselman’s 25 things that every .NET developer ought to know</a> and the interviewer tells that it is his private collection of questions.</p><h3><strong>The Good Parts</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*lCdN-m3INAk25UEMl5A3Tg.jpeg" /></figure><p>Now let’s go through the interviews that I really enjoyed, the technics and questions which allowed me to truly show my skills and made me feel wanted.</p><h4><strong>Home project, code review and pair programming</strong></h4><p>In one company I also got a coding project however it was a home project meaning that I could go home, work on it whenever I wanted and send them back the solution when I’m done.</p><p>This is so much better than working on it at the company during the interview. It allows me to put in as much effort as I want while doing it in a familiar and comfortable environment.</p><p>After I sent them the code I was invited to a code review. I think that this is the best possible interview since it checks <strong>everything</strong>! Both my coding skills, my ability to explain my choices and to see how I accept critics.</p><p>After the code review I was asked to change something in the code — it took just 10 minutes but the interviewer set with me the whole time and was part of my design choices. It was more like a pair programming than a test. It allowed me to show how I think before I code, my TDD skills and it also allowed me to see how it feels to actually work with someone from that company. This was the <strong>best interview process!</strong></p><h4><strong>Team Leader/Group leader who is in charge of the interviews process</strong></h4><p>As a candidate you usually talk to the HR in order to schedule your interviews, to get more info about the company and simply talk between the interviews. The HR are usually really nice girls (never met a HR guy) but it’s way more welcoming and respectful when your point of contact is a team or a group leader of that company.</p><p>It makes you feel important and that you are taken seriously since a manager is investing time from his busy schedule to walk you through the interview process in his company. A company that shows this kind of respect to a candidate must show even bigger respect to it’s employees and that is a company that I want to be part of.</p><h4><strong>CEO that talks to the candidates</strong></h4><p>I really valued the companies that their CEO invested ~30 minutes to get to know me and tried to make me feel like home even before I decided to sign with his or her company. When the CEOs shared their visions for their companies and told me their missions and values I felt an immediate connection. These talks were the last step of the interview process and companies who’s CEO actually called me or invited me to come and talk to him made me appreciate that company more than others and that is a major decision factor.</p><p>One CEO even called me from San Francisco just “to get to know me”. He is the CEO of ~100 people. If he could find the time then most of the high level managers in not huge corporate can.</p><h4><strong>Architectural and design questions</strong></h4><p>I was surprised to see that most of the companies didn’t ask me architectural questions. Only 2 companies wanted to know if I understood the architecture of the projects that I’ve worked on.</p><p><em>“Why do you have a load balancer? Why don’t you use micro services? Did you have a DRP? How does it work? What is the most fragile place of your architecture? What should you change? How? Why?”</em></p><p>If the <em>trivia questions</em> have usually the “<em>What</em>” prefix then the deep design questions will have the “<em>Why</em>” and “<em>How</em>” prefixes. This way the candidate must understand the pros and the cons of the architecture and more importantly to understand <strong>why</strong> the architecture is the way it is.</p><p>I think that these sort of questions show whether the candidate was just a code monkey or if he truly cared and understood his project.</p><h4><strong>White board role playing</strong></h4><p>Almost every company asks the candidates to approach the white board to solve a problem or design an algorithm. Remember that the<strong> solutions doesn’t matter</strong>! It’s how you thinks what’s important. This is why it’s important to think loudly and share your thoughts with the interviewers.</p><p>This is a great test however I think that it can be even better.</p><p>In one company after I solved the problem at the white board the interviewer stood up and told “now it’s my turn”. He asked another question (something about modeling and design) and then approached to the white board and started to sketch a solution.</p><p>Then he asked me if that works and if his solution was good. It wasn’t and I had to spot the problem and then explain him why his solution wasn’t good enough. <strong>It was great</strong>!</p><p>We switched roles and I felt like the interviewer. It was a simulation of a technical argument and he wanted to see if I can spot the design problem and most important part to see if I can hold on to my position and be able to convince him that he was wrong in a good and calm way. This is also <strong>one of the best</strong> interviews I had.</p><h4><strong>“How do you keep learning?”</strong></h4><p>There are plenty of developers out there. Only a small part of them are truly great developers. Many things distinguish them from the meritocratic ones. One of them is what I call “<strong>Continuous Learning</strong>”.</p><p>The truly great developers always keep learning. They code, they read they write about it, they go to meetups and they are always up to date. Every company want these developers since they will always bring you progress.</p><p>If someone asks you to share this then they probably also care about learning and that place will probably have great developers who work there.</p><h4><strong>“Tell me about something that you are proud of?”</strong></h4><p>Enthusiasm and ownership are extremely important qualities. Every company wants their developers to be enthusiastic about their work, to have ownership for their features and to feel accountable for the application that they are building.</p><p>In order to be proud of something you must be involved in all aspects of the product development. You must feel that you own that something to the bones. If someone is truly proud of a feature or a product then he will talk enthusiastically while describing it.</p><p>I really liked when in one interview I was asked to tell about a feature that I was proud of. I could explain why did I think that this feature is important, it’s complexities and how did I actually developed it. It allowed me to show my understanding of that feature and my enthusiasm of software development. This is impossible to reproduce with only trivia questions.</p><h3><strong>That’s it</strong>.</h3><p>This was a summary of most of my interviews. It was really interesting to see other companies and developers and to be tested for my skills. My personal advice is that when you go to an interview don’t be in the state of mind of a candidate that needs “to pass” the company’s tests. Go there and be the interviewer. Sure answer their questions, but don’t forget to ask yours. Remember that you are special and not every company deserves you. So be smart when choosing one. I think that the interview process can really help in deciding whether the company is worth going to. I hope that this post helped you know what to look for.</p><p>Good luck and feel free to share your experience!</p><p>This post was originally published in my blog:</p><p><a href="http://dennis-nerush.blogspot.co.il/2016/03/my-adventures-in-interviews-jungle.html">http://dennis-nerush.blogspot.co.il/2016/03/my-adventures-in-interviews-jungle.html</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e14ce126452" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dennis-nerush/my-adventures-in-the-interviews-jungle-6e14ce126452">My Adventures in the Interviews Jungle</a> was originally published in <a href="https://medium.com/dennis-nerush">Dennis Nerush’s Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Estimations in Agile development — Epics, User Stories and Tasks]]></title>
            <link>https://medium.com/dennis-nerush/estimations-in-agile-development-epics-user-stories-and-tasks-2570ba9f9d3d?source=rss----720a8b8ea39b---4</link>
            <guid isPermaLink="false">https://medium.com/p/2570ba9f9d3d</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Dennis Nerush]]></dc:creator>
            <pubDate>Wed, 04 Jan 2017 08:17:10 GMT</pubDate>
            <atom:updated>2017-07-20T11:44:02.721Z</atom:updated>
            <content:encoded><![CDATA[<p>Agile, scrum, Kanban and Lean are no longer “new” methods for software development. There are hundreds of articles, books and courses about them. However, most of them include introduction material that mainly focuses on the basics. If you actually start using one of these methodologies you’ll quickly ask yourself with a missing — <strong>how are you supposed to estimate your work?</strong></p><p>If you search the web you will see that there is not much data about estimations, simply because it is HARD. It is <strong>very hard</strong> to estimate correctly. Jeff bezos used to say <em>“If you are planning for more than twenty minutes ahead in this kind of environment, you are wasting your time”</em>. We cannot predict the future, but we can maximize our chances in getting as close as possible to it.</p><p>After reading several agile books (e.g. <a href="http://www.shopyourway.com/agile-estimating-and-planning-paperback/1237095">Agile Estimating and Planning</a> by Mike Cohn), scrum courses and 6 years of practicing Scrum and Kanban in various projects I’ll try to add that missing piece called <strong>estimations in Agile development.</strong></p><p>This is the first of 4 posts in the “Agile Estimations” series.</p><ol><li>Epics, User Stories and Tasks (<strong>you are here</strong>)</li><li><a href="https://medium.com/dennis-nerush/estimations-in-agile-development-estimating-the-backlog-with-story-points-358d12b566d1">Estimating User Stories with Story Points</a></li><li><a href="https://medium.com/dennis-nerush/estimations-in-agile-development-sprint-planning-methods-capacity-vs-velocity-vs-feature-a5b4bb1a159e">Sprint Planning Methods: Capacity vs. Velocity vs. Feature</a></li><li><a href="https://medium.com/dennis-nerush/estimations-in-agile-development-improving-estimations-using-burndown-burnup-and-c2f6fff37ff3">Improving Estimations using Burndown, Burnup and Actual Time metrics</a></li></ol><p>This series is not an introduction to Scrum. Before you keep reading, you should be familiar with the <a href="http://agilemanifesto.org/">agile manifesto</a> and Scrum in general. There is no “right” way to do Agile. You should change it so that it fits your needs. However, it is very important to understand the root principles and evolve from them.</p><h4><strong>Making the series practical</strong></h4><p>In order for this entire series to be practical and not just theoretical we’ll apply the content on a Youtube like application that I’m building right now. It should allow users to upload and watch videos. It should allow users to edit their videos details and rate others videos. It should have search, tags and filters (top seen, recently added and more). It also should recommend different users videos that matches their interests.</p><h4><strong>Let’s start</strong></h4><p>Before we jump to the different approaches regarding estimations let’s first understand what is it that we need to estimate. A project’s specification evolves with time. It starts with large and unknown features requests and eventually transforms to some tiny and technical tasks. In this post we’ll understand how this transformation does happen and why.</p><h4><strong>It is not just User Stories</strong></h4><p>Everybody knows that in Scrum and most of the other agile methodologies you must have a board and some sticky notes on it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/433/0*1muBcesJT0D5yEd2." /></figure><p>*Maybe your board is not a physical board but it is still <strong>a</strong> board. With notes.</p><p>What are those notes? They are the actual work that is currently being done. The actual <strong>tasks</strong> that the team is working on in order to accomplish some <strong>user stories</strong>. User stories represent the user’s need. A feature that should be added to the application that will gain the user value. The tasks are the <strong>technical</strong> representation of that need.</p><p>A user story represents a feature. However sometimes that feature doesn’t stand on its own or it is part of some bigger feature or a business concept that incorporates several features. That is called an <strong>Epic</strong>.</p><h4><strong>Epic</strong></h4><p>An epic is the biggest representation of a feature. In order to deliver an epic to the user we must divide the epic to smaller pieces — user stories.</p><p>*In the Agile books epic is not divided directly to user stories it first divides to something that is called “<strong>Themes</strong>” and only they are divided to “User Stories”. However in the last 6 years I have never seen any team that uses Themes therefore we’ll not use them either.</p><p>In our application we have three epics:</p><ol><li>Allow users to find, play and comment on videos</li><li>Allow users to upload and edit content</li><li>Recommend videos to users based on their interests</li></ol><p>This is our current <strong>product</strong> <strong>backlog</strong>. A backlog is basically a list of features that represents all the user’s needs and wishes. The backlog has two main principles that we should always apply:</p><p>1. The backlog must always be prioritized from high to low according to the user’s needs.</p><p>2. Every backlog item must have a “<strong>DoD</strong>” — <strong>D</strong>efinition<strong> o</strong>f <strong>D</strong>one that defines when the feature is actually complete. Sometimes it is called “Acceptance criteria”. It doesn’t replace the full description of the feature or its design. It is only a single sentence (maybe a couple) that describes how the feature will behave in the end.</p><p>Our backlog is already prioritized so let’s add DoD to the epics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/446/0*aj2AcgvbP5jcjth8." /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/0*PGghOkwBrXtrWTHU." /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/453/0*lQAe0F987kFe-2HT." /></figure><p>*there are many agile management tools out there. You don’t have to use them, a physical board and sticky notes can be enough. However, when working on big project a dedicated virtual tool might be really useful. I personally recommend on <a href="https://www.visualstudio.com/en-us/products/what-is-visual-studio-online-vs.aspx">Visual Studio Team Services</a>.</p><p>Remember that the epics should <strong>not</strong> include any technical or implementation details. They should only describe the business value. A more detailed description will be found inside the epic’s user stories.</p><p>By prioritizing the backlog we know what is the most important feature that the user needs, hence it will be developed first. After we’ll finish it we’ll move to the next one in the list. This way we always deliver the user what he wants the most.</p><p>I think that this is one of the best concepts in Agile development that is so different from the traditional ones. This way we can deliver small and valuable features to the user and receive feedback along the way.</p><h4><strong>Breaking Epics into User Stories</strong></h4><p>So the first epic is “<em>Allow users to find and play videos</em>”. In order to get a better understanding of what it really means we should divide it to smaller pieces — user stories. Every user story should match the following template: “<em>As X I need/want Y to do/so that Z</em>”.<em> As </em><strong><em>a logged in user</em></strong><em> I want to </em><strong><em>update the details of my videos </em></strong><em>so that </em><strong><em>they be correct.</em></strong></p><p>It is extremely helpful when a user story has at least X and Y defined since it clearly expresses the main role of the feature (As a logged in user) and by so the relevant business stakeholders of this feature.</p><p>Will we fail if we won’t name our user stories like that? Of course not.</p><p>Do all the user stories need X Y and Z defined? Definitely not. However doing so makes you truly understand the scope and value of the feature.</p><p><strong>Epic: <em>Allow users to find, play and comment on videos</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/442/0*K_nNEiSpdleLl4sX." /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/443/0*uY9ZmEnbhB5u9b9s." /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/446/0*WzfYyG-yiamVw5uv." /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/444/0*z2A2aFF7mgrG8aIU." /></figure><p>Few things to note:</p><ul><li>The DoD adds meaningful information for the implementation of the feature.</li><li>The use of <em>user</em> and <em>logged in user</em> for separating the action of an anonymous user and a logged in one.</li><li>The priorities of the user stories determine what the most important feature to the user is and which one is the least.</li><li>Every user story gives actual value to the user and brings us closer to the <strong>epic’s </strong>DoD.</li></ul><p>Now we can split the top user story to its technical parts — the tasks.</p><p><strong>User story: <em>As a user I want to play videos from a list of videos</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/430/0*pEKm66EryN7PKADS." /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/434/0*mETrAuL0qPUm53AH." /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/434/0*3dzAMLLGfhEZ3Y3I." /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/433/0*tsfA9r1AbZMg5224." /></figure><p><strong>The complete backlog:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/503/0*vCqtB9ILYCc0xemL." /></figure><p>So now after we are familiar with all the product backlog items it is time to give them estimations.</p><p>But how do we estimate?</p><p>What estimation units should we use?</p><p>What are story points?</p><p>Do we have the same estimation units to all the backlog items?</p><p>All the answers and much more are in the next post.</p><p>Estimations in Agile development — Epics, User Stories and Tasks (you are here)</p><p>Estimations in Agile development — Estimating User Stories with Story Points (<strong>soon to be</strong>)</p><p>Estimations in Agile development — Improving estimations with Capacity planning, Burndown and Actual work charts</p><p>Estimations in Agile development — A Glance to the Future with the Burnup chart</p><p><em>Originally published at </em><a href="http://dennis-nerush.blogspot.co.il/2016/07/estimations-in-agile-development-epics.html"><em>dennis-nerush.blogspot.co.il</em></a><em> on July 18, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2570ba9f9d3d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dennis-nerush/estimations-in-agile-development-epics-user-stories-and-tasks-2570ba9f9d3d">Estimations in Agile development — Epics, User Stories and Tasks</a> was originally published in <a href="https://medium.com/dennis-nerush">Dennis Nerush’s Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Project of Your Life]]></title>
            <link>https://medium.com/dennis-nerush/the-project-of-your-life-f05833fefd49?source=rss----720a8b8ea39b---4</link>
            <guid isPermaLink="false">https://medium.com/p/f05833fefd49</guid>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Dennis Nerush]]></dc:creator>
            <pubDate>Wed, 04 Jan 2017 08:17:00 GMT</pubDate>
            <atom:updated>2024-10-29T16:02:49.305Z</atom:updated>
            <content:encoded><![CDATA[<p>By settings personal goals we improve ourselves and become better. I use Lean and Scrum principles for creating and tracking my personal goals.</p><p>Keep reading and see how it works.</p><p>When working on some project we set milestones, long term goals, short term goals and KPIs.</p><p>We track progress and learn from our work by having retrospective meetings and checkpoints along the way.</p><p>Now imagine that you have a very large project ahead of you and <strong>you don’t plan at all</strong>. You just float and react to the different events on the way. Do you think you can make it right? On time? On budget? The answer like always is “it depends”, however most likely that you won’t.</p><p>In order to succeed we <strong>need to manage our life</strong> and not be managed by it. You need to manage it exactly like you would manage that project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/759/0*gwYZZTK46ZAdWawD." /></figure><p><strong><em>Your life is a project and you are its developer, designer and product manager</em></strong></p><p>How many times did you say to yourself that you need to be better in this and that you should learn that? How many of those goals have you actually accomplished?</p><p>The first step is to define what you want. I personally like this <a href="http://www.careerealism.com/mid-year-review-questions/">article</a>. It makes me think about my strengths, weaknesses and just the things I want to know. I have a dedicated time every 6 months when I go over these questions and create my <strong>long term goals</strong>. These goals are the things that I want to accomplish in order to be successful and better than I am today. I keep them in my <a href="https://keep.google.com/">Google Keep</a> notes.</p><p>*these are my personal goals:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/585/0*c3wpkVUN3W1jDkps." /></figure><p>Every personal (and not just personal) goal should be <a href="http://topachievement.com/smart.html">well defined</a> (SMART goal).</p><p><strong>S</strong>pecific — your goal definition should answer these question who is involved? What do I want to accomplish? When? <br><strong>M</strong>easurable — how can you measure progress and know if you are done?<br><strong>A</strong>ttainable — How can this goal come true?<br><strong>R</strong>ealistic — be honest with yourself. Don’t define unreachable goals.<br><strong>T</strong>imely — provide a time frame. Then creating a 6month goals you are already do it.</p><h4><strong>Breaking down long term goals to short term goals</strong></h4><p>Defining long term goals is the first step in improving. Setting a goal is better than setting no goals at all. <strong><em>Writing down is a commitment to yourself</em></strong><em>.</em></p><p>In order to accomplish a long term goal, which is usually a big goal (I want to master JavaScript, etc.) we need to break it down to smaller pieces — smaller goals (milestones) that we’ll accomplish along the way. Those goals should also be SMART goals. I have a reoccurring monthly time when I go over my long term goals and decide what I want to do this month in order to get closer to accomplishing the whole goal. Like in lean development I constantly adopt and change my goals according to the situation (perhaps there is no reason why I should learn JavaScript anymore?).</p><p>The monthly short term goals don’t always have to correlate to the long term goals. Perhaps I want to take care of something in my job or maybe learn something that is not part of my long term goals and is important for the following month. To be honest, it doesn’t really matter. As long as you take time to think about it, take a decision and commit to it by writing it down you will improve and be better. That is the whole point.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/0*fzCbLtU1il0ItabB." /></figure><p>If you have never tried to “manage” your life and set goals to yourself then I suggest you start with monthly goals. Think about the month ahead of you and try to define how this month will become to a successful one.</p><p>If you had set personal goals before then I suggest to take it further.</p><p>A month is a lot of time — 4 whole weeks! Usually when we have so much time a head of us we won’t start any task until the very end and that is only if someone reminds us about it in the first place. That’s called <em>the </em><a href="https://en.wikipedia.org/wiki/Student_syndrome"><em>student syndrome</em></a>.</p><h4><strong>Weekly and Daily goals</strong></h4><p>Scrum uses sprints in order to prevent the student syndrome. I like to look on my weeks as sprints. Every week has a <a href="http://www.scrum-institute.org/Sprint_Planning_Meeting.php">sprint planning</a> and a <a href="https://www.mountaingoatsoftware.com/agile/scrum/sprint-retrospective">retro</a>. I go over the previous week calendar and see how it was. I try to find the things that I need to be better in and things that I need to preserve and keep doing. This way I can improve and track my progress <strong>weekly</strong>. In the beginning of the week I have a dedicated time for planning my weekly goals which are subsets of my monthly goals and the tasks that I need to accomplish this week regardless of any long/short term goal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*o98L9ZFyYbQ35TfB." /></figure><p>During the week I have a “<a href="https://www.mountaingoatsoftware.com/agile/scrum/daily-scrum">daily standup meeting</a>” (I however do it when I’m on the train on my way to work) using <a href="https://www.any.do/">Any.DO</a> which has a very cool feature that at 08:00 makes me go over my daily tasks and decide when do I want to do them (sometime today or later this week).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/377/0*HNZp_y6fbVg-f0p9." /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/378/0*UfDY7XKqfGDRo_NM." /></figure><p>It is simply a todo list that reminds me of the tasks I need to accomplish every day.</p><p>Every week ends with a retro. I go over my previous week and write down important notes, facts and decisions. I write them in <a href="https://penzu.com/">Penzu</a> which is basically a diary with a very cool feature — it sends me every week the note I’ve written a year before. This way I’m constantly being reminded of my decisions (you need to use it for a year in order for it to be effective, don’t give up!).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/482/0*n4miWZe71vGfnzwI." /></figure><h4><strong>Summary</strong></h4><p>If you want to improve you need to set personal goals.</p><p>The goals should be both long and short term.</p><p>Track both of them in Google Keep.</p><p>Every week set yourself weekly goals and have e retro for the previous week. Write it down in Penzu and be reminded of it afterwards.</p><p>Have a daily meeting using Any.Do.</p><p>This works for me, perhaps it can also work for you.</p><p>Or maybe I’m just crazy</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/19/0*_12A9vrpNjPMbY_5." /></figure><p>Acknowledgments:</p><p>Netanel Lev and Shani Raba for reviewing the post.</p><p><em>Originally published at </em><a href="http://dennis-nerush.blogspot.co.il/2016/08/manage-your-life-like-you-manage-project.html"><em>dennis-nerush.blogspot.co.il</em></a><em> on August 2, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f05833fefd49" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dennis-nerush/the-project-of-your-life-f05833fefd49">The Project of Your Life</a> was originally published in <a href="https://medium.com/dennis-nerush">Dennis Nerush’s Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[This is what I read]]></title>
            <link>https://medium.com/dennis-nerush/this-is-what-i-read-43e5a56ca603?source=rss----720a8b8ea39b---4</link>
            <guid isPermaLink="false">https://medium.com/p/43e5a56ca603</guid>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[reading]]></category>
            <dc:creator><![CDATA[Dennis Nerush]]></dc:creator>
            <pubDate>Wed, 04 Jan 2017 08:16:52 GMT</pubDate>
            <atom:updated>2016-08-13T17:17:04.925Z</atom:updated>
            <content:encoded><![CDATA[<p>I read a lot. I think that reading is one of most important activities one can do in order to <a href="http://dennis-nerush.blogspot.co.il/2016/08/manage-your-life-like-you-manage-project.html">improve and become better</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/622/0*sFYglmEPDTi-2hTi." /></figure><p>I share most of what I read on my <a href="https://twitter.com/DennisNerush">Twitter account</a>. Recently more and more people ask me where I find the stuff I read. So I decided to share with you my sources.</p><p>There are 5 main sources where I constantly find great articles, videos and posts:</p><blockquote><em>1. </em><strong><em>Feedly</em></strong><em> — here I keep my blog roll (you can find the full list in the end of this post). It is a simple RSS reader where I subscribe to the blogs that are the most relevant to me and which I want to be up to date with their content. if I land on a good post in an unfamiliar blog, I go through the last 3–4 posts and if most of the content is actually good and relevant, then I add the blog to </em><a href="https://feedly.com/"><em>Feedly</em></a><em>.</em></blockquote><blockquote><em>2. </em><strong><em>Twitter</em></strong><em> — unlike Facebook, that is full of my friends posts (and pictures), in </em><a href="https://twitter.com/DennisNerush"><em>Twitter</em></a><em> I follow business newspapers, tech news, engineering content, leading CEO’s and tech world “celebrities”.</em></blockquote><p><a href="https://www.linkedin.com/in/lnetanel">Netanel Lev</a> wrote once a post describing the difference between Twitter and Google Reader (like Feedly) — <a href="https://lnetanel.com/2009/09/16/twitter-is-my-radio-station-google-reader-is-my-disc-player/"><em>Twitter is my radio station, Google Reader is my disc player!</em></a><em> </em>This post describes perfectly the difference between a RSS reader that has predictable content that you have chosen like music on a CD (Yes I know, that is an old post). And Twitter, that is unpredictable and “<em>every new tweet is a song that maybe I like or not”.</em></p><blockquote><em>3. </em><strong><em>Pocket</em></strong><em> </em><strong><em>recommendations</em></strong><em> — </em><a href="https://getpocket.com/"><em>Pocket</em></a><em> is my favorite and most used app. I keep there everything I find interesting, in order to read it later, when I have time. Another cool Pocket feature is a recommendations feed that is created by different members of the Pocket community (the content that they recommend to others, and by Pocket itself using personalization mechanisms). The more you read the better recommendations Pocket will provide for you.</em></blockquote><blockquote><em>4. </em><strong><em>Software Lead Weekly</em></strong><em> — this is a weekly </em><a href="http://softwareleadweekly.com/"><em>mailing list</em></a><em> created by </em><a href="https://www.linkedin.com/in/orenellenbogen"><em>Oren Ellenbogen</em></a><em>. It aggregates great articles and videos regarding tech, leadership, startups and engineering culture.</em></blockquote><blockquote><em>5. </em><strong><em>Books</em></strong><em>! Posts, articles, videos, tweets are great way to learn new things and be updated with what happens in the world. However, if you wish to master something and become a true expert you have to read books. A post by some expert can get you this far, but a whole book that is written by that same expert will teach you whole lot more. </em><a href="https://readthink.com/95-business-books-for-people-who-dream-big-36e63a563153#.52qis0rkm"><em>This post</em></a><em> has a list of 95 books in various topics that are probably relevant to you. This is a great place to start building your library.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*gR32sKjUDtehQ29V." /></figure><p>I think that you should have at least 2 sources (besides reading books):</p><p>(1) A blog roll that you have picked based on your interests (you can use any RSS reader, Feedly is my choice).</p><p>(2) “An unpredictable radio” — Twitter, Pocket, Medium and more in order to be exposed to new sources and things you didn’t know that exist.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/616/0*TLWGHMXCWxJQecNE." /></figure><p>Keep reading!</p><p>As promised here is my blog roll:</p><p><strong>.NET</strong></p><blockquote><em>1. </em><a href="http://dailydotnettips.com/"><em>http://dailydotnettips.com/</em></a><em> — Short posts of great tips in .NET and Visual Studio</em></blockquote><blockquote><em>2. </em><a href="https://visualstudiomagazine.com/Home.aspx"><em>https://visualstudiomagazine.com/Home.aspx</em></a><em> — .NET news</em></blockquote><blockquote><em>3. </em><a href="https://shonnlyga.wordpress.com/"><em>https://shonnlyga.wordpress.com/</em></a><em> — a friend of mine who writes about .NET related stuff</em></blockquote><blockquote><em>4. </em><a href="http://www.dotnetrocks.com/"><em>http://www.dotnetrocks.com/</em></a><em> (podcast) — no need to listen to all of the episodes — pick the ones that you feel are relevant to you</em></blockquote><blockquote><em>5. </em><a href="https://codeblog.jonskeet.uk/"><em>https://codeblog.jonskeet.uk/</em></a></blockquote><blockquote><em>6. </em><a href="https://ayende.com/blog/"><em>https://ayende.com/blog/</em></a><em> — Oren Eini, one of the best developers in Israel (some say that in the world). He used to write about .NET low level stuff but now most of his posts are about RavenDB (his product — .NET based DB), Sometimes he shares some bugs that they had and more interesting stuff</em></blockquote><blockquote><em>7. </em><a href="https://visualstudiomagazine.com/rss-feeds/blogs.aspx"><em>https://visualstudiomagazine.com/rss-feeds/blogs.aspx</em></a><em> — Visual studio blog posts</em></blockquote><blockquote><em>8. </em><a href="https://visualstudiomagazine.com/rss-feeds/news.aspx"><em>https://visualstudiomagazine.com/rss-feeds/news.aspx</em></a><em> — Visual Studio news</em></blockquote><blockquote><em>9. </em><a href="https://blogs.msdn.microsoft.com/dotnet"><em>https://blogs.msdn.microsoft.com/dotnet</em></a><em> . NET announcements</em></blockquote><blockquote><em>10. </em><a href="http://feedly.com/i/subscription/feed/http:/visualstudiomagazine.com/rss-feeds/features.aspx"><em>http://feedly.com/i/subscription/feed/http://visualstudiomagazine.com/rss-feeds/features.aspx</em></a><em> -new features in the NET world</em></blockquote><p><strong>Architecture:</strong></p><blockquote><em>1. </em><a href="https://lostechies.com/"><em>https://lostechies.com/</em></a><em> a blog with several great writers: the creator of AutoMapper, CQRS and event Sourcing experts and more</em></blockquote><blockquote><em>2. </em><a href="http://martinfowler.com/"><em>http://martinfowler.com/</em></a><em> — The one and only Martin Fowler.</em></blockquote><blockquote><em>3. </em><a href="http://www.aviransplace.com/"><em>http://www.aviransplace.com/</em></a><em> — Head of WIX backend. He writes about software solutions, architecture and management</em></blockquote><blockquote><em>4. </em><a href="http://www.softwarearchiblog.com/"><em>http://www.softwarearchiblog.com/</em></a><em> — The best Israeli Hebrew blog.</em></blockquote><blockquote><em>5. </em><a href="http://enterprisecraftsmanship.com/"><em>http://enterprisecraftsmanship.com/</em></a></blockquote><p><strong>UX:</strong></p><blockquote><em>1. </em><a href="http://uxi.org.il/"><em>http://uxi.org.il/</em></a></blockquote><p><strong>Tech stuff:</strong></p><blockquote><em>1. </em><a href="http://www.hanselman.com/blog/"><em>http://www.hanselman.com/blog/</em></a><em> — Scott Hanselman’s blog</em></blockquote><blockquote><em>2. </em><a href="http://www.hanselminutes.com/"><em>http://www.hanselminutes.com/</em></a><em> — Scott Hanselman’s podcast</em></blockquote><blockquote><em>3. </em><a href="https://thefutureorganization.com/"><em>https://thefutureorganization.com/</em></a><em> — Hebrew Tech podcast. My favourite episodes are “Bumpers” — one hour of 2–3 minutes short discussion about variety of technology topics like frameworks, tools, announcements , posts and more</em></blockquote><blockquote><em>4. </em><a href="http://blog.house-of-code.com/"><em>http://blog.house-of-code.com/</em></a><em> — Yossi Shmueli’s blog</em></blockquote><p><strong>Culture</strong>:</p><blockquote><em>1. </em><a href="http://blog.crisp.se/"><em>http://blog.crisp.se/</em></a><em> — Used to work in Spotify and now in Lego!! Greatposts about agile, lean and culture</em></blockquote><blockquote><em>2. </em><a href="http://www.joelonsoftware.com/"><em>http://www.joelonsoftware.com/</em></a><em> — Joel Spolsky the creator of Stack Overflow and Trello. Worth following him on Twitter.</em></blockquote><blockquote><em>3. </em><a href="http://blog.karmona.com/"><em>http://blog.karmona.com/</em></a><em> — Moti Karmona’s blog</em></blockquote><blockquote><em>4. </em><a href="https://blog.8thlight.com/"><em>https://blog.8thlight.com/</em></a><em> — culture and leadership — software oriented</em></blockquote><blockquote><em>5. </em><a href="http://www.mngttips.com/"><em>http://www.mngttips.com/</em></a><em> — Hebrew podcast about management</em></blockquote><blockquote><em>6. </em><a href="http://shavua.net/"><em>http://shavua.net/</em></a><em> — The BEST Hebrew podcast! It’s about startups. They interview the biggest Israeli CEO’s, CTO’s and enterpanures about their startups success or failure.</em></blockquote><blockquote><em>7. </em><a href="https://thefutureorganization.com/"><em>https://thefutureorganization.com/</em></a><em> — Podcast regarding the culture in different organizations and startups</em></blockquote><blockquote><em>8. </em><a href="https://lnetanel.com/"><em>https://lnetanel.com/</em></a><em> — Netanel Lev’s blog</em></blockquote><blockquote><em>9. </em><a href="https://lnetanel.com/"><em>https://medium.com/@rabashani/</em></a><em> — Shani Raba’s blog</em></blockquote><blockquote><em>10. </em><a href="http://randsinrepose.com/"><em>http://randsinrepose.com/</em></a></blockquote><blockquote><em>11. </em><a href="http://www.timeninjablog.com/"><em>http://www.timeninjablog.com/</em></a><em> — time management tips</em></blockquote><p><strong>Web:</strong></p><blockquote><em>1. </em><a href="https://fivejs.codeschool.com/"><em>https://fivejs.codeschool.com/</em></a><em> — 10 minutes podcast episodes about the latest libraries and feature in JS.</em></blockquote><blockquote><em>2. </em><a href="https://internet-israel.com/"><em>https://internet-israel.com/</em></a><em> — Hebrew blog</em></blockquote><p><strong>Tech companies blogs:</strong></p><blockquote><em>1. </em><a href="http://blog.wix.engineering/"><em>http://blog.wix.engineering/</em></a><em> — Wix blog</em></blockquote><blockquote><em>2. </em><a href="https://code.facebook.com/"><em>https://code.facebook.com/</em></a><em> — Facebook blog — Priceless!!!!</em></blockquote><blockquote><em>3. </em><a href="https://labs.spotify.com/"><em>https://labs.spotify.com/</em></a><em> — Spotify</em></blockquote><blockquote><em>4. </em><a href="http://nerds.airbnb.com/"><em>http://nerds.airbnb.com/</em></a><em> — Airbnb</em></blockquote><blockquote><em>5. </em><a href="https://baremetrics.com/"><em>https://baremetrics.com/</em></a></blockquote><blockquote><em>6. </em><a href="https://blog.twitter.com/"><em>https://blog.twitter.com/</em></a><em> — Twitter</em></blockquote><blockquote><em>7. </em><a href="http://githubengineering.com/"><em>http://githubengineering.com/</em></a><em> — Github</em></blockquote><blockquote><em>8. </em><a href="http://engineering.instagram.com/"><em>http://engineering.instagram.com/</em></a><em> — Instagram</em></blockquote><blockquote><em>9. </em><a href="https://engineering.pinterest.com/blog/rss"><em>https://engineering.pinterest.com/blog/rss</em></a><em> — Pinterest</em></blockquote><blockquote><em>10. </em><a href="http://techblog.netflix.com/"><em>http://techblog.netflix.com/</em></a><em> — Netflix</em></blockquote><p><em>Originally published at </em><a href="http://dennis-nerush.blogspot.co.il/2016/08/this-is-what-i-read.html"><em>dennis-nerush.blogspot.co.il</em></a><em> on August 13, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=43e5a56ca603" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dennis-nerush/this-is-what-i-read-43e5a56ca603">This is what I read</a> was originally published in <a href="https://medium.com/dennis-nerush">Dennis Nerush’s Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Estimations in Agile development — Estimating the Backlog with Story Points]]></title>
            <link>https://medium.com/dennis-nerush/estimations-in-agile-development-estimating-the-backlog-with-story-points-358d12b566d1?source=rss----720a8b8ea39b---4</link>
            <guid isPermaLink="false">https://medium.com/p/358d12b566d1</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Dennis Nerush]]></dc:creator>
            <pubDate>Wed, 04 Jan 2017 08:16:43 GMT</pubDate>
            <atom:updated>2020-11-23T09:51:41.508Z</atom:updated>
            <content:encoded><![CDATA[<p>This is the second post in the Estimations in Agile development series.</p><ol><li><a href="https://medium.com/dennis-nerush/estimations-in-agile-development-epics-user-stories-and-tasks-2570ba9f9d3d">Epics, User Stories and Tasks</a></li><li>Estimating User Stories with Story Points (<strong>you are here</strong>)</li><li><a href="https://medium.com/dennis-nerush/estimations-in-agile-development-sprint-planning-methods-capacity-vs-velocity-vs-feature-a5b4bb1a159e">Sprint Planning Methods: Capacity vs. Velocity vs. Feature</a></li><li><a href="https://medium.com/dennis-nerush/estimations-in-agile-development-improving-estimations-using-burndown-burnup-and-c2f6fff37ff3">Improving Estimations using Burndown, Burnup and Actual Time metrics</a>t</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/412/0*C0OwLRq5_HJq7OFE." /></figure><p>In the <a href="http://dennis-nerush.blogspot.co.il/2016/07/estimations-in-agile-development-epics.html">previous post</a> I’ve introduced the different product backlog items, their hierarchy and scope.</p><p>In this post we’ll learn how to estimate user stories using <em>story points</em>. I’ve introduced the videos website project that I’m building. This is its current epics backlog:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/711/0*PXBOMPuqU1JPF2wP." /></figure><h4><strong>Story points</strong></h4><p>We need to estimate those epics, but how? The trivial option is time. We usually estimate effort in time “<em>It takes two hours to get to Tel Aviv”, “The renovations will be over in a week”. </em>However, it is extremely hard to estimate long term effort in time.</p><p>Let’s look at the first epic <em>Allow users to find, play and comment on videos. </em>This is obviously a lot of work. It is more than a week and probably less than a year. Every time driven estimation won’t be accurate. It is hard to estimate accurately something that is longer than a week. Months? Impossible. We need something else.</p><p>When estimating long term effort we should use a more <strong>relative</strong> unit like size or complexity.</p><p>These units allow us to easily compare features by their size or complexity. “<em>This one is 2 times bigger/more complicated than this one”. </em>It allows to easily separate the complex features from the easy features or from the small ones to the large features.</p><p>Since the units are relative to one another we can choose any numeric representation that we want. We only have to stay consistent while using it.</p><p>It can be 1,2,3 story points when 1 is super easy and 2 is harder, or 10, 20, 30… . It doesn’t really matter and that is the beauty in story points. Personally I prefer reflecting size in story points. “How long does it take to get from Tel Aviv to Herzelia? Same as getting from Tel Aviv to Holon which is 2 (some relative representation of this size)”.</p><p>Another option is ideal days. “<em>How many days will it take if the days have absolutely no distractions?</em>” The problem in this way is that yet again it is time based and we suck in estimating long term in any time based method. Hence it is not recommended.</p><h4><strong>Prioritize, estimate and prioritize again</strong></h4><p>The backlog will be constantly prioritized and changed due to business requirement, estimations and new discoveries along the way.</p><p>In order to properly prioritize we need to have the business prioritization along with the estimated R&amp;D effort. Usually it will take 3 rounds:</p><ol><li>The first one is a “business prioritization” round. The product manager will prioritize the epics based on their business values. <em>What feature does the user must have first?</em></li><li>The second round is a “<em>technical effort estimation</em>” round. The R&amp;D will go through the list of epics and spot the ones with the highest level of uncertainty and risks. We don’t want to leave the unknowns to the end — we want to tackle them from the beginning in order to increase our level of certainty in the required effort. Unknown effort usually is a big effort, hence its story points value will be big.<br>The recommendations epic has many uncertainties like introducing intersects into the system and understanding what videos the user will actually want to watch. It seems like it is <em>3 times</em> bigger effort than the other two epics. We’ll estimate it with a value of <em>30 </em>while the other epics are 10. The cool part is that it doesn’t have to be “3 times bigger” it can be 5 or 10 times bigger. It is relative. It means that a new epic will have an estimation that is relative to the previous ones: is it “<em>more like” </em>the big one (30) or more like the first one (10).</li><li>The third and last one is the “business prioritization” round again. This time the product manager sees the required effort for all the epics and decides whether some of the highly estimated epics should be moved higher or lower in the backlog. Perhaps if a feature is so difficult to implement then it shouldn’t be implemented at all. Our product manager is fine with our estimations and he decides to leave the epic in its current priority. The first two are more valuable than the recommendations.</li></ol><p>This is our current estimated backlog:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*esgmJPcULIrVyKKg." /></figure><h4><strong>Estimating User Stories</strong></h4><p>The epics are prioritized and estimated. Now what? We can start all the epics simultaneously but then it will take us much longer to finish the first one as opposed to focusing only on the first epic. Keep in mind that every epic has a real value to the user hence we want to decrease the <strong>time to market</strong> of every epic. In order to achieve that we must strive to <strong>start only a single epic at a time</strong>. There is a great phrase that one of my managers used to tell “<strong><em>stop starting — start finishing</em></strong><em>”. </em>We should strive to focus on the most important feature first. Finish it and only then move to the next one. The feedback that we’ll get from real users might change our initial priorities.</p><p>Now it’s time to split the first epic to user stories. We’ve done it already in the previous post:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/0*0Tzv0rbsiQayBWN5." /></figure><p>The estimation process of user stories is identical to the epics. User stories also give actual value to the user, hence we need to deliver the feature with the most value first. Watching videos in a video library application is probably more important than commenting or searching (without videos to search or comment on).</p><p>Now it is time for technical estimations round using story points — same as before. In this case the first user story is bigger than the other two since this is the first feature. We need to build the application’s first screens, create the project, build continuous deployment (hell yeah! From the start) and allow to actually watch videos.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/701/0*CsDh-UsN0xFMUytv." /></figure><p>*If you try to add up the estimations you won’t reach 10. That’s alright since 2 SP and 1 SP are not equal to 3 SP. In the next posts we’ll talk about ways to sum estimated effort in a more precise way.</p><p>The filter user story has the smallest estimation since it has no persistence complexity and it feels like less effort than the other features.</p><p>If a user story receives a big estimation then it is a sign that we don’t understand it well enough or perhaps it is just too big as a single feature. In both cases the best practice is to split it to 2 or more user stories while every user story will give actual value to the user. That is exactly what I meant in my previous post when I mentioned that epics split to themes and only then to user stories. Since this is our first estimations round we still don’t know what a too big estimation is. In the next post we’ll learn how to define our limit and by doing so define when we should break the user story further more.</p><p>Time for the last business round of prioritization. This round is the most important one since it determines the next feature that the R&amp;D will work on and that the user will see.</p><p>After we’ll complete it and deliver it to the user we’ll receive feedback that might change these priorities. This is good. Our job is to deliver what the user wants. Having a real product at his hands might change some of his first assumptions. This is why the prioritization will happen again and again. Along with the priorities the estimations will also change. Something that we thought was 2 S.P. appeared to be much easier or much harder and it is no longer should be like other 2 S.P. user stories. It may sound depressing to constantly re-prioritize and re-estimate the backlog, however, this is the only way it will truly reflect the product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/0*zi8LcUNQF_33y4RC." /></figure><h3><strong>Starting the sprint</strong></h3><p>We know the user story that we should work meaning we are ready to start our sprint. The sprint starts with a “sprint planning meeting”. In this meeting the team splits the user story to technical tasks and estimates them.</p><p>Should we also use story points for estimating tasks?</p><p>How do we know that we filled our team’s capacity?</p><p>What is capacity?</p><p>How do we improve our estimations?</p><p>All that and more in the next post.</p><p><a href="http://dennis-nerush.blogspot.co.il/2016/07/estimations-in-agile-development-epics.html">Estimations in Agile development — Epics, User Stories and Tasks</a></p><p>Estimations in Agile development — Estimating User Stories with Story Points (you are here)</p><p>Estimations in Agile development — Improving estimations with Capacity planning, Burndown and Actual work charts (<a href="https://medium.com/dennis-nerush/estimations-in-agile-development-sprint-planning-methods-capacity-vs-velocity-vs-feature-a5b4bb1a159e"><strong>go here</strong></a>)</p><p><em>Originally published at </em><a href="http://dennis-nerush.blogspot.co.il/2016/09/estimations-in-agile-development.html"><em>dennis-nerush.blogspot.co.il</em></a><em> on September 4, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=358d12b566d1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dennis-nerush/estimations-in-agile-development-estimating-the-backlog-with-story-points-358d12b566d1">Estimations in Agile development — Estimating the Backlog with Story Points</a> was originally published in <a href="https://medium.com/dennis-nerush">Dennis Nerush’s Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Estimations in Agile development — Sprint Planning Methods: Capacity vs. Velocity vs. Feature]]></title>
            <link>https://medium.com/dennis-nerush/estimations-in-agile-development-sprint-planning-methods-capacity-vs-velocity-vs-feature-a5b4bb1a159e?source=rss----720a8b8ea39b---4</link>
            <guid isPermaLink="false">https://medium.com/p/a5b4bb1a159e</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[estimations]]></category>
            <dc:creator><![CDATA[Dennis Nerush]]></dc:creator>
            <pubDate>Wed, 04 Jan 2017 08:16:34 GMT</pubDate>
            <atom:updated>2020-11-23T09:50:19.010Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*C0D3EBDV-G0HWNHR." /></figure><p>This is the third post in the Estimations in Agile development series.</p><ol><li><a href="https://medium.com/dennis-nerush/estimations-in-agile-development-epics-user-stories-and-tasks-2570ba9f9d3d">Epics, User Stories and Tasks</a></li><li><a href="https://medium.com/dennis-nerush/estimations-in-agile-development-estimating-the-backlog-with-story-points-358d12b566d1">Estimating User Stories with Story Points</a></li><li>Sprint Planning Methods: Capacity vs. Velocity vs. Feature <strong>(you are here)</strong></li><li><a href="https://medium.com/dennis-nerush/estimations-in-agile-development-improving-estimations-using-burndown-burnup-and-c2f6fff37ff3">Improving Estimations using Burndown, Burnup and Actual Time metrics</a></li></ol><p>In the previous posts we’ve learned how to breakdown features to epics, user stories to tasks, and how to estimate epics and user stories. We talked about the three prioritization cycles and their importance, and why relative units like story points work better than time based units like ideal days.</p><p>In this post I want to focus on the sprint and on the meeting that starts the sprint — the sprint planning. I’ll show you why technical tasks, unlike epics and user stories, <strong>should be estimated in time based units like hours.</strong></p><p><strong>The Purpose of the Sprint</strong></p><p>A sprint’s purpose is to <strong>deliver value</strong> to a user and <strong>receive feedback.</strong> If by the end of the sprint, a user doesn’t receive any value or the team doesn’t receive any feedback for their work, the sprint wasn’t successful. Only after seeing real working features, a user can tell that they are, indeed, what he needs.</p><p>A “user story” shares the exact same purpose — deliver a value to a user, that means that <strong>we should be able to accomplish at least a single user story in a sprint.</strong></p><p><strong>Capacity planning vs. Velocity planning vs. Feature planning</strong></p><p>The top user story in the backlog is the one that we need to deliver first since it is the most valuable to the user. But how do we know if that user story actually fits into a single sprint?</p><p>There are 3 methods to decide how many user stories can fit in a sprint:</p><ol><li><strong>Feature Planning</strong></li><li><strong>Velocity Planning</strong></li><li><strong>Capacity Planning</strong></li></ol><p>Let’s drill down to each of those methods.</p><h4><strong>Feature planning</strong></h4><p>This method basically states that by the end of the sprint, a chosen feature(user story) must be ready. This method is usually used when the team has a deadline that cannot be changed like a commitment for stakeholders or an external constraint. The team will literally do whatever it takes to accomplish the feature. Including long hours and even weekends. The team will not be able to keep up with this for long.<br><strong>Avoid using this method if possible</strong>. However if the company does work like this, then it is important to take the right buffers and plan ahead in order to remove the dependency between the external and the internal dates.</p><h4><strong>Velocity planning</strong></h4><p>Velocity planning method uses the team’s average ‘velocity’ in order to determine the amount of user stories for the sprint.</p><p>Velocity is a metric that defines the amount of story points a team accomplishes in a single sprint. <br>For example, if a team finished a total of 10 story points 2 sprints ago and another 10 story points in the last sprint, then its velocity is 10 story points. <br>When planning based on previous velocity, in the upcoming sprint the team should take user stories with total of 10 story points.</p><p>This method is obviously better than the previous one. However this method <strong>is not accurate enough</strong> for a two weeks sprint resolution.</p><p>The velocity based planning is relying on addition of relative units — story points. The problem with adding these values is that 1SP + 2SP != 3SP.</p><p>A story point is a relative unit that describes a story’s complexity relatively to another story (X is 2 times harder than Y). This unit is great for comparing stories and deciding on their priority, however a 2SP task doesn’t equal to two 1SP tasks. As a matter of fact, 2SP task doesn’t necessarily take the same amount of time that as another 2SP task.</p><p>Let’s assume that our project is already running for 10 sprints. We could look back at every user story in every sprint and give it the <strong>actual time</strong> it took. This will allow us to convert story points to time. Let’s say that after that calculation 1SP is equal to an average of 12 hours.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/596/0*xCL_5kUxnUdDobsE." /></figure><p>*<a href="http://www.shopyourway.com/agile-estimating-and-planning-paperback/1237095">Agile Estimating and Planning</a> by Mike Cohn page 162</p><p>As you can see that despite the fact that the average is 12, we had tasks that took less and some that took more. The standard deviation becomes bigger as the SP number value is higher (some 3SP tasks will take 30 hours while others may take 45 -50% more). It should not be a surprise — after all 2SP states that it is 2 times more complex than 1SP task, it doesn’t mean that every time it will take twice as long.</p><p>Therefore if you plan your sprint using velocity don’t be surprised if some of the tasks take longer than others although they have the same SP value, and that you won’t finish all the planned tasks by the end of the sprint.</p><h4><strong>Capacity Planning</strong></h4><p>There are many unknowns when we try to plan months ahead (like in the beginning of the project). However things are different then we plan a sprint (which is only 1–4 weeks long). There are several known facts that allow us to plan more accurately:</p><ol><li>A sprint’s length is <strong>constant</strong> (read <a href="https://www.benday.com/2014/07/24/really-bad-idea-change-sprint-length/">here</a> why) it can be 1–4 weeks longs. Either way it is known, hence we know how many working days there are in the sprint.</li><li>We also know of how many working hours are there in a single day of a sprint.</li><li>And we also know how many team members to we have.</li></ol><p>For example in a 2 week sprint we have 10 work days, 9 hours a day and 4 team members. 10 X 9 X 4 = 360 hours.</p><p>However we don’t actually have 360 hours right? What about all the meetings? The days off and other <strong>known wastes.<br></strong>We know most of our wastes when we plan for 2 weeks ahead. We also know another thing — we don’t actually work 9 hours a day, take off lunch, breaks, vacations, support hours and other context switches and it will be more like 6. <br>Each team member can easily calculate his capacity by simply looking at his calendar, so in order for the total capacity to be accurate, a sprint capacity calculation should consider every team member individually.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/561/0*jIfydmopFldEs9Hx." /></figure><p>That is the sprint capacity (for a 1 week sprint).</p><p>The capacity represents the absolute amount of work that the team can handle in <strong>hours</strong>. The sprint’s capacity is like an empty glass which size is determined by the team members working time (also hours).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/318/0*fC2ef4_14dVrgvIA." /></figure><p>The size of the glass is in hours, therefore in order to fill it we also need to use hours. Unlike big features, epics or user stories which are hard to estimate, tasks should be well defined and should require a relatively small effort (no longer than 3 days). The tasks estimation is created using “<a href="https://www.mountaingoatsoftware.com/tools/planning-poker">poker planning</a>”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/718/0*Dmk5k3T1MJwb50-l." /></figure><p>After estimating the first task we add it to our sprint backlog and basically “fill the glass” a little.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/0*SGytvBGTrhMlQsth." /></figure><p>We can see that we haven’t reached our capacity yet. Therefore we can keep estimating until we’ll reach it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/199/0*ZV822Z34Wcvs2RaT." /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ilZT-nyQPCK7L9yw." /></figure><p>We had successfully filled our time with…time! Before the planning we have removed all the known potential wastes and therefore we have a pretty good reason to believe that we’ll complete all the tasks in the sprint on time.</p><p>We could wait for the end of the sprint and find out whether our estimations were correct, or we could use some useful metrics to verify <strong>daily</strong> that we are on track. <br>We could also use some other metrics that will allow us to improve our estimations over time, and for the grand finale, we can use a very special metrics that will help us to predict the future.</p><p>Read about all that and more in the next and the last post of this series.</p><p><a href="http://dennis-nerush.blogspot.co.il/2016/07/estimations-in-agile-development-epics.html">Estimations in Agile development — Epics, User Stories and Tasks</a></p><p><a href="http://dennis-nerush.blogspot.co.il/2016/09/estimations-in-agile-development.html">Estimations in Agile development — Estimating User Stories with Story Points</a></p><p>Estimations in Agile development — Sprint Planning Methods: Capacity vs. Velocity vs. Feature <strong>(you are here)</strong></p><p>Estimations in Agile development — Improving Estimations using Burndown, Burnup and Actual time metrics <strong>(</strong><a href="https://medium.com/dennis-nerush/estimations-in-agile-development-improving-estimations-using-burndown-burnup-and-c2f6fff37ff3"><strong>go here</strong></a><strong>)</strong></p><p><em>Originally published at </em><a href="http://dennis-nerush.blogspot.co.il/2016/10/estimations-in-agile-development-sprint.html"><em>dennis-nerush.blogspot.co.il</em></a><em> on October 8, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5b4bb1a159e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dennis-nerush/estimations-in-agile-development-sprint-planning-methods-capacity-vs-velocity-vs-feature-a5b4bb1a159e">Estimations in Agile development — Sprint Planning Methods: Capacity vs. Velocity vs. Feature</a> was originally published in <a href="https://medium.com/dennis-nerush">Dennis Nerush’s Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Estimations​ ​in​ ​Agile development​ ​-​ ​Improving Estimations​ ​using​ ​Burndown, Burnup​ ​and​…]]></title>
            <link>https://medium.com/dennis-nerush/estimations-in-agile-development-improving-estimations-using-burndown-burnup-and-c2f6fff37ff3?source=rss----720a8b8ea39b---4</link>
            <guid isPermaLink="false">https://medium.com/p/c2f6fff37ff3</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[estimations]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Dennis Nerush]]></dc:creator>
            <pubDate>Wed, 04 Jan 2017 08:15:50 GMT</pubDate>
            <atom:updated>2017-07-20T11:46:46.778Z</atom:updated>
            <content:encoded><![CDATA[<h3>Estimations​ ​in​ ​Agile development​ ​-​ ​Improving Estimations​ ​using​ ​Burndown, Burnup​ ​and​ ​Actual​ ​Time metrics</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/642/0*hXDfNvWiZjnA__2e." /></figure><p>This is the fourth and the last post in the Estimations in Agile development series.</p><ol><li><a href="https://medium.com/dennis-nerush/estimations-in-agile-development-epics-user-stories-and-tasks-2570ba9f9d3d">Epics, User Stories and Tasks</a></li><li><a href="https://medium.com/dennis-nerush/estimations-in-agile-development-estimating-the-backlog-with-story-points-358d12b566d1">Estimating User Stories with Story Points</a></li><li><a href="https://medium.com/dennis-nerush/estimations-in-agile-development-sprint-planning-methods-capacity-vs-velocity-vs-feature-a5b4bb1a159e">Sprint Planning Methods: Capacity vs. Velocity vs. Feature</a></li><li>Improving Estimations using Burndown, Burnup and Actual Time metrics (<strong>you are here</strong>)</li></ol><p>In the previous post we’ve discussed the different methods for the sprint planning and the benefits of using absolute units like hours for estimating small efforts in a known time frame — the sprint.</p><p>In this post we’ll see some metrics that will help us verify and improve our estimations over time and even allow us to predict whether we’ll achieve our long term goals.</p><h3>Burndown</h3><p>After we finish estimating all the tasks we can create a rough estimation regarding the amount of work that has to be done (according to the daily capacity) in order to finish all the tasks on time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SohYypVDwQgyGdfc." /></figure><p>The green line displays that available capacity for a current day. In other words — we need to make sure that our remaining work for the sprint is below the green line. Otherwise we won’t complete all the tasks on time.</p><p>Each day developers should update the “remaining work” field for their tasks — how much time is left for finishing the task. That metric will allow us to know whether we’ll finish all the estimated tasks or not.</p><p>The burndown might go up when new tasks are added or new information is discovered during the sprint.</p><p>The remaining work should be updated daily and the team should look at the chart in the <a href="https://www.mountaingoatsoftware.com/agile/scrum/daily-scrum">daily stand up meeting</a>. In this event we can easily see that our estimation are not correlating with our actual performance. The impact is clear: if the team proceeds with the current phase they won’t finish all the planned tasks for the sprint on time. Hence the user won’t receive a working product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/770/0*knFfh2swXmxP-cGU." /></figure><p>In this very moment the team should decide on the action to make the chart to convergent.</p><p>They can decide on giving some extra work to close the gap or perhaps remove the least prioritized task from the sprint — this is of course done with the product manager who is the stakeholder of the sprint.</p><p>The burndown chart is a daily feedback tool. it is effective only when it is updated on a daily basis. it is also another reason why I think one should use hours and not story points for the sprint’s tasks. when working with story points you don’t update the remaining time — you don’t change 3 SP tasks to 1 SP task, you simply work on it until it’s done. This way the burndown will not reflect your actual progress daily and it will be hard to understand if you are on track.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/453/0*jyuUkoLssPz75rw8." /></figure><h3>Actual vs. Estimated — Improving the team’s estimations</h3><p>Even in a two weeks sprint we cannot know everything. Something will always surprise us. A larger than estimated task, an external requirement, un-expected technical support and more. Sometimes there is absolutely nothing we can do about it, however sometimes we can learn from these unaccurate estimations and correct them in the future. Therefore I suggest another metric which purpose is to compare our initial estimations to our actual performance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*CC7QsB3LlrCuwMcE." /></figure><p>After finishing a task, the team member will fill another field “Actual Work” with the actual time that took him to complete the task. This way we’ll create another graph that will compare the planned estimation to the actual one, Allowing us to see which tasks were underestimated, overestimated and which were exactly as we predicted. Our purpose is to minify the gap between the actual and the estimated. ”why did the task take longer/less than we estimated? Could we do something in order to predict it?” This graph is a great topic to start the <a href="https://www.mountaingoatsoftware.com/agile/scrum/sprint-retrospective">retro meeting</a> with.</p><h3>Predicting the future with Burnup chart</h3><p>The burndown chart allows us to monitor only a single and the current sprint. It allows the team a clear view on their progress in the sprint. However, it doesn’t tell if the team if the whole project is on track or will they finish it on time? Every stakeholder and manager wants to know when will the project, milestone or a release be ready. It is hard to predict a date 3–6 months into the future. Any estimations for this feels like a hunch. “<em>Well, we have 3 months left and 2 more big features, so I guess will make it on time</em>”. How can we monitor our progress on a ~weekly basis?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*0Fw1Ad8gySXqmzGg." /></figure><p>Actually we can predict all this using our previous progress. Let’s say we are 4 sprints in (2 months) in a 6 months project. Will we make it on time? To answer this we need only 2 things:</p><ol><li>Estimated backlog (Epics/ user stories with their SP values)</li><li>The Team’s average velocity</li></ol><p>Average Velocity is the amount of story points that we finish in each sprint divided by the number of sprints (those who read the <a href="http://dennis-nerush.blogspot.co.il/2016/10/estimations-in-agile-development-sprint.html">previous post</a> probably understand that this metric won’t be too accurate but it is enough for this purpose).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*QH904FBrqeMmBrCY." /></figure><p>Team’s average velocity for the last 4 sprints = (10 +8 + 6 +11)/ 4 = ~9.</p><p>The beauty of the team’s average Velocity is that it gets more accurate with every sprint. Therefore if we know the end date (4 months from now) and the average velocity, then we can predict how many story points the team will finish by that time.</p><p>We’ll take the previous chart and we’ll turn it into a cumulative</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/469/0*lzS5U4woNsHQt78-." /></figure><p>Now, based on the average velocity we can calculate how much SP we’ll finish in the future sprints.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/481/0*vRFzpWLQ8jQENzNJ." /></figure><p>All the data on the right of the black line (the present sprint) is predicted based on actual data from the previous sprints. You can see that after 12 sprints the team will finish ~110 Story Points. If the total required amount is 100–110 then it seems that we have the right velocity and we’ll finish the project on time. But we all know that the above chart is too good to be true. The below one is probably more realistic:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/484/0*8sbBMGkmVADqI6hn." /></figure><p>This chart is called burnup and it allows a clear, data driven, look at the future. Based on this data the team, and everyone else, knows that the project won’t be ready on time. The velocity should be higher, the ETA should move or the project scope should change. Either way -this is not a hunch.</p><h3>Summary</h3><p>In this post we’ve seen 3 ways to improve our estimations and predictability. The actual vs. estimated is the best tool to verify and improve your estimations over time and the burnup will let you know you need to speed up your development, even if you finish all sprints on time. The key is to constantly check yourself and improve.</p><p>In this series we covered lots of topics regarding Agile development and estimations. It is important to remember that there is no “right” way to do Agile. There are common fundamentals but different teams should use and adopt the principles and process that suits them best. And remember that nothing is constant — something that used to be “right” for you then, may not be right anymore. So keep retroing yourself and your process, keep fine tune it all the time and I hope that you’ll find what is best for you.</p><p>Feel free to share and comment.</p><p><a href="http://dennis-nerush.blogspot.co.il/2016/07/estimations-in-agile-development-epics.html">Estimations in Agile development — Epics, User Stories and Tasks</a></p><p><a href="http://dennis-nerush.blogspot.co.il/2016/09/estimations-in-agile-development.html">Estimations in Agile development — Estimating User Stories with Story Points</a></p><p><a href="http://dennis-nerush.blogspot.co.il/2016/10/estimations-in-agile-development-sprint.html">Estimations in Agile development — Sprint Planning Methods: Capacity vs. Velocity vs. Feature</a></p><p>Estimations in Agile development — Improving Estimations using Burndown, Burnup and Actual time metrics<strong> (you are here)</strong></p><p><em>Originally published at </em><a href="http://dennis-nerush.blogspot.com/2016/12/estimations-in-agile-development.html"><em>dennis-nerush.blogspot.com</em></a><em> on December 20, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2f6fff37ff3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dennis-nerush/estimations-in-agile-development-improving-estimations-using-burndown-burnup-and-c2f6fff37ff3">Estimations​ ​in​ ​Agile development​ ​-​ ​Improving Estimations​ ​using​ ​Burndown, Burnup​ ​and​…</a> was originally published in <a href="https://medium.com/dennis-nerush">Dennis Nerush’s Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>