<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Till Quack on Medium]]></title>
        <description><![CDATA[Stories by Till Quack on Medium]]></description>
        <link>https://medium.com/@till_68370?source=rss-26e38020d4b0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*WK6VVcB8RuCGQTSthBhk1g.jpeg</url>
            <title>Stories by Till Quack on Medium</title>
            <link>https://medium.com/@till_68370?source=rss-26e38020d4b0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 00:37:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@till_68370/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The 4T for startup success]]></title>
            <link>https://medium.com/@till_68370/the-4t-for-startup-success-9797cf2d2707?source=rss-26e38020d4b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/9797cf2d2707</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[startup-life]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Till Quack]]></dc:creator>
            <pubDate>Sat, 20 Aug 2022 08:33:08 GMT</pubDate>
            <atom:updated>2022-08-21T10:01:09.030Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bdagGcH1BSXlnqgIgNNTSA.jpeg" /><figcaption>By Dave Spiess on Unsplash</figcaption></figure><p>Back in 2014, after exiting our first startup (<a href="https://www.crunchbase.com/organization/kooaba">kooaba, a visual search engine</a>), I reflected on our journey and wrote down a few success factors.</p><p>Now, in 2022, I am starting a new venture (<a href="https://www.zerofy.net/">automated carbon emissions tracking app for households</a>) and I went back to check on my notes from back then.</p><p>Without further ado, here are my 4 T for startup success:</p><h3><strong>Timing</strong></h3><p>As a first-time founder, this was not on my radar at all. But timing is an external factor that can have a huge impact on success. If you’re early, you may waste a lot of resources trying to get traction, at a time when it is almost impossible. If you’re late, the market may be taken already. With our mobile visual search engine, which launched in 2006, we were early. The iPhone SDK came out only in 2008, and the big AI and machine learning wave started around 2016 (after we had exited our company). Since it is an external factor, one thing you can do is to have various startup ideas in your mind and wait until the timing for one of them seems right. (This is something I tried to do with my current venture, <a href="https://www.zerofy.net/">Zerofy</a> in the climate space.)</p><h3><strong>Trust</strong></h3><p>Trust is important internally and externally.</p><p>Internally, your team members put a lot of trust in you as a founder when joining an early startup. It’s paramount to be transparent, to trust your team members, and allow taking responsibility and accountability. These are generally good management principles, but they apply even more to startups.</p><p>Externally trust is essential with customers and users. Especially in a B2B scenario when doing larger enterprise deals as a tiny startup, someone on the other side may be taking a leap of faith and sometimes even risking their reputation working with a small innovative company. It’s important to recognize that and put oneself in the shoes of the buying party through the process.</p><h3><strong>Tenacity</strong></h3><p>It’s simply not gonna work without tenacity. There will be tough times, and startups are on a constant rollercoaster. For example in 2008 we tried raising funding during the financial crisis. It was very tough and we almost ran out of money. But we pulled through.</p><p>There are no overnight successes, and there are countless stories of unicorn-level startups who at some time in their early phases had difficulties getting any traction or even faced bankruptcy.</p><p>On the flip side: sometimes it’s simply time to stop and move on. It’s incredibly hard to recognize when to keep going and when to stop. Generally, though, you should expect to have to pull through several deep challenges or crises.</p><h3><strong>Team</strong></h3><p>This is probably the most commonly mentioned success factor, but rightfully so. Having a set of founders that can cooperate well, and a skilled team with deep trust for each other is essential to reaching your goals and making it through tough times. At my first startup, we were lucky to have a great team. I didn’t realize only until later that this is not a given. When working with other startups later in my career, I got to see situations with deep personal conflicts, which can endanger the company even when all other things are going well. So, at my new startup again the founders’ joint focus is building a great team.</p><p>Timing. Trust. Tenacity. Team.<br>I hope these 4T are helpful for your endeavours, too.</p><p>P.S. Interestingly my co-founder at kooaba, Herbert, also just started another venture, too: a <a href="https://earkick.com/">mental health tracking app</a>. I wonder if he’s applying the same 4T.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9797cf2d2707" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Cybertruck: f***ing fearless]]></title>
            <link>https://medium.com/quack-ventures/the-cybertruck-f-ing-fearless-69a3690a0e1c?source=rss-26e38020d4b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/69a3690a0e1c</guid>
            <category><![CDATA[tesla]]></category>
            <category><![CDATA[cyber-truck]]></category>
            <dc:creator><![CDATA[Till Quack]]></dc:creator>
            <pubDate>Mon, 25 Nov 2019 21:41:37 GMT</pubDate>
            <atom:updated>2020-11-15T12:18:32.520Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Cybertruck: “f***ing fearless”</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A8RWkNCGq7rLLEOCOu_JNg.png" /><figcaption>The cybertruck — frontal view</figcaption></figure><p>Just a few days ago the <a href="https://www.tesla.com/cybertruck">Tesla Cybertruck</a> was unveiled. A lot has been written since, mainly due to its polarizing design. For me it certainly has been the most exciting product reveals in a long time, even though it’s a car I probably won’t consider buying. I wrote this post in an attempt to explain to myself why it is so exciting.</p><h3>The genius of the unexpected</h3><p>“Unexpected” describes this product unveiling in so many ways. The style of the presentation: raw, almost unprepared. The failure with the broken window. And, of course, the design. After the initial shock and letting it sink in, feelings left are around boldness, strength, rawness, audacity, and counter-culture. Overall this product unveiling is a really impressive marketing achievement. Here’s why:</p><p>The truck (in general, not the cybertruck only) serves an audience that is looking for <strong>toughness</strong>. (This is best experienced in the US, albeit I assume similar trends can be found globally.)</p><p>Some of the folks most critical of Tesla and its mission to transition to sustainable transport are right at the core of the target audience for big, tough trucks such as the Ford F150. Heck, there is even a “sports” of sorts of so-called “coal rolling”, often targeted at Teslas. This is almost exclusively carried out with trucks. Google it — or watch this clip:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fy4rLs_itz_U%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dy4rLs_itz_U&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fy4rLs_itz_U%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/37ce66d636e055754eb067ecae57b067/href">https://medium.com/media/37ce66d636e055754eb067ecae57b067/href</a></iframe><p>(A similar hobby is to <a href="https://www.businessinsider.com/truck-owners-are-blocking-tesla-superchargers-in-ice-ing-protests-2018-12">“ICE” supercharger stations</a>.<a href="https://www.businessinsider.com/truck-owners-are-blocking-tesla-superchargers-in-ice-ing-protests-2018-12)">)</a></p><p>This is nothing the majority of truck customers would ever do, of course. But, it does illustrate the point, that if you build an electric truck, it better be tougher than anything else on the market. And I think Tesla nailed it! Imagine seeing the vehicle’s front with the mono light-bar in your rearview mirror. It doesn’t get any wilder than that! On top of it, the technical specs speak for themselves: almost indestructible steel shell. <a href="https://electrek.co/2019/11/25/tesla-cybertruck-tug-war-against-ford-f150-size-comparison/">Tug of war pulling an F150 </a>easily — uphill. Bulletproof (?) glass…</p><p>From that angle putting toughness at the core of the design makes total sense, and the result is maybe not so unexpected anymore.</p><h3>Form follows function</h3><p>But the design move is also unexpected from another angle: Tesla won in EVs by making one of the first electric vehicles that looked “normal”. (Of course, also performing extremely well.) Before Tesla, every incumbent car manufacturer designed EVs as “futuristic” and “innovative”. Which didn’t work out at all. Now all the incumbents are announcing EVs with “normal” design — and Tesla decides to go the total opposite way with the truck!</p><p>The reason the vehicle looks like Origami is that it is Origami. Well, almost. The way the body is built is that is “cut” from a steel sheet and then “folded” into its shape. Similar as you know it from folding a flat cardboard shape into a box. The benefit of this, as described in the presentation, is that no steel frame is needed and a tough exoskeleton gives strength stability. The steel is very tough, doesn’t scratch and doesn’t need a paint job.</p><p>So with the original requirement of toughness, form really follows function. On top of that, it makes the vehicle production much cheaper. The car comes at a very competitive price point compared to any truck, electric or not.</p><h3>Audacity</h3><p>Of course, the move to go public with a design like this takes a lot of courage. (Arguably <a href="https://www.youtube.com/watch?v=baBJwsIABO8">even more than removing a headphone jack or Flash</a>.)</p><p>Apparently, also the idea of the designing a car from a folded sheet of steel has been around for a while in the auto industry — just “no one had the balls to do it so far”, as explained by these guys:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F4qgO3A2pUr8%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D4qgO3A2pUr8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F4qgO3A2pUr8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/fa4be551f90158d9076e1312a39dfca2/href">https://medium.com/media/fa4be551f90158d9076e1312a39dfca2/href</a></iframe><p>One criticism that was voiced frequently is that the truck is too big, too uneconomical, and too dangerous. Smaller, lightweight cars for city use would be better. This is true. But it misses the point: we are talking about folks buying a big gas-guzzling truck. It will be hard to switch these folks to a Smart car. Switching them to electric (eventually from sustainable sources) is the lesser of evils.</p><p>So, bottom line, the cybertruck design choices really belongs on the very far right of this chart, which caught my eye at <a href="https://twitter.com/johnschoolcraft?lang=en">John Schoolcraft</a>’s <a href="https://youtu.be/KTRCfggLetw?t=13741">Slush presentation</a> last week:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E5FphPpCs2hjYAQPwM8QAg.png" /></figure><p>(We can argue about where Cybertruck lands on the y-axis :))</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69a3690a0e1c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/quack-ventures/the-cybertruck-f-ing-fearless-69a3690a0e1c">The Cybertruck: f***ing fearless</a> was originally published in <a href="https://medium.com/quack-ventures">Quack Ventures</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thinking in sprints: setting and communicating dates with Agile]]></title>
            <link>https://medium.com/getshipit/thinking-in-sprints-setting-and-communicating-dates-with-agile-61be5d8adeac?source=rss-26e38020d4b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/61be5d8adeac</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Till Quack]]></dc:creator>
            <pubDate>Sun, 13 Oct 2019 12:31:48 GMT</pubDate>
            <atom:updated>2019-10-13T12:31:48.136Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gO12pN0qHkL5JZPhrxqExg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@wwarby?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">William Warby</a> on <a href="https://unsplash.com/s/photos/ruler?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>“When” often is the word product development teams fear most. When is the release date for this feature in development? When is that feature a customer asked for scheduled on the roadmap? When will that nasty bug one of your investors discovered, be fixed?</p><p>Giving a confident answer to the question “when?”, is one of the objectives of making a plan. But, in the age of Agile development, is making plans and communicating dates still relevant? After all, two of the most common myths about Agile are:</p><ul><li>Agile = no planning, or</li><li>Agile is incompatible with longer-term planning</li></ul><p>It would be easy to dismiss questions for “when” with referring to being Agile, or with lectures about how long-term plans are doomed to fail. These are of course valid points, and they have been covered and proven in detail <a href="https://twitter.com/mikewcohn/status/1182370300278775808">elsewhere</a>. But the ones who ask for dates still deserve an answer. It’s important for Marketing and PR to plan release activities. (For example by activating press contacts or planning an on-stage announcement at a conference.) It’s important for the business development team to set expectations with your customers. And it’s always helpful to keep your investors happy. (Especially the ones who use your product.)</p><p>So how do you a) set and b) communicate product release dates in an Agile context? It’s quite simple: think and communicate in sprint granularity only.</p><h4>Communicating in Sprint granularity</h4><p>When you need to set a release date, instead of saying “October 13”, say “Sprint 19”. (In the appendix of this article we explain how to make this really easily understandable to everyone in your company.)</p><p>For far-out dates it’s often best to be less precise and, if possible, just target the calendar quarter. For example:</p><ul><li>for the current quarter: communicate sprint numbers as dates.</li><li>for the next four quarters or so: communicate the quarter.</li><li>anything beyond that: just communicate the year.</li></ul><p>It’s really that simple.</p><h4>Planning and estimating in Sprint granularity</h4><p>The simplest and standard way to do longer-term planning in Agile is using your velocity, i.e. the number of story points or tickets you complete each sprint. I recommend the book <a href="https://www.amazon.com/Agile-Estimating-Planning-Mike-Cohn/dp/0131479415">Agile Estimating and Planning by Mike Cohn</a>, but the gist of it is simple:</p><ul><li>estimate tickets in story points</li><li>track your velocity</li><li>to estimate a release date for a feature: estimate it’s size in story points.</li><li>Divide it by your Scrum team’s velocity. Voila, you got the number of sprints it will take to complete it. (You may, of course, need to account for working on a few efforts in parallel.)</li><li>issue management systems such as Jira these days also have automatic calculations of that sort for Epics and releases.</li></ul><p>This simple type of back-of-the-envelope math can be surprisingly effective and precise.</p><h4>Additional thoughts</h4><p>Most people would agree that a typical one- or two-week Sprint passes pretty quickly. If then you break down a quarter or a year into its number of sprints, you will notice that it is a really nice unit of size to “grasp”:</p><ul><li>1 calendar quarter: about 12 one-week or 6 two-week sprints, respectively.</li><li>1 year = about 52 one-week or 26 two-week sprints, respectively.</li></ul><p>So you have at least 6 major release slots in a quarter or 26 n a year for two-week sprints. That’s by far enough, even for fast-moving companies. At the same time, these are still “handy” numbers.</p><p>Finally, even when doing a longer-term product plan, it’s wise to stay true to the agile manifesto preferring “<a href="https://agilemanifesto.org/">responding to change over following a plan</a>”(). Simply adapt the plan and sprint-granularity dates as you go. It’s in fact much easier to keep track of changes of the sort Sprint 29 -&gt; Sprint 30, rather than October 25 -&gt; November 6.</p><p>In <a href="https://app.getshipit.com/">shipit</a>, all the product roadmaps are by default broken down in Sprint granularity. This means, employing the above approach is made really easy.</p><h4>Appendix: a few tactical details</h4><ul><li>Sprint naming: it’s best to use a simple naming and numbering of Sprints that is easily understandable and/or listed somewhere. One approach that works well is to name Sprints after calendar week numbers. If you run 1-week sprints each Sprint easily corresponds to the calendar week number. For example, Sprint 41 or Sprint 19–41 refer to the calendar week 41 (Oct 7–11 2019). If you have sprints of 2 or 3 weeks, just define the starting or ending week number as the sprint number. Or use just an ever increasing id.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61be5d8adeac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/getshipit/thinking-in-sprints-setting-and-communicating-dates-with-agile-61be5d8adeac">Thinking in sprints: setting and communicating dates with Agile</a> was originally published in <a href="https://medium.com/getshipit">getshipit</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What are product requirements documents and why do I need them?]]></title>
            <link>https://medium.com/getshipit/what-are-product-requirements-documents-and-why-do-i-need-them-56f983a1edf1?source=rss-26e38020d4b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/56f983a1edf1</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Till Quack]]></dc:creator>
            <pubDate>Sun, 11 Aug 2019 12:54:42 GMT</pubDate>
            <atom:updated>2019-08-11T16:34:53.214Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>What are product requirements documents and why do you need them?</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fHodGRuXwGfQvjLl_uM65Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@floriankrumm?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Florian Krumm</a> on <a href="https://unsplash.com/t/architecture?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Paul is a product manager, and he takes great care of writing proper user stories for all features and manages an up-to-date backlogs in Jira. Nevertheless he feels the “big picture” gets lost in translation while the engineering team is implementing the backlog. Heck, sometimes even Paul himself gets lost in the sea of tickets, and has to remind himself of <em>why </em>an initiative was started in the first place.</p><p>Maggy is responsible for Marketing and PR. She is often taken by surprise when a new product feature is ready to be shipped, and has to scramble to get the message crafted and distributed.</p><p>Bert runs business development. While Paul collects his input diligently, both Paul and Bert feel they could be better aligned on who they are launching a new product initiative with or for.</p><p>Does some of this sound familiar? Writing Product Requirements (usually in the form Product Requirements Document, PRD) can help to align cross-functional teams and to communicate the big picture around product plans. And it is really simple to do.</p><h3><strong>Product Requirements != Features</strong></h3><p>Product requirements are not features. At least not only. The product requirements should focus on the problem the product or a particular product initiative is trying to solve for the customer, and why it is relevant.</p><blockquote>So the product requirements are about the what and why. Whereas features, user stories, or technical requirements are about the how.</blockquote><p>Furthermore, the product requirements should address everything that is relevant for a product beyond its features and functionality. This includes in particular</p><ul><li>Communication, product marketing, and wording/terminology</li><li>Launch and going to market</li><li>Customers, customer needs, and launch customers</li><li>Addressed market segments and pricing</li><li>Non- functional product requirements (performance etc.)</li></ul><h3><strong>The anatomy of a product requirements document</strong></h3><p>Below I’ll introduce the sections you would typically find a product requirements documents, and what they may contain. Here’s a publicly available <a href="https://docs.google.com/document/d/1bPwE2E-_5yKjLqjCS9StvNJP3iX0pSITga7vcXm6SGw/edit?usp=sharing">Google doc template, in a long</a> and in <a href="https://docs.google.com/document/d/1IBWvJfDr6t6LgdZpV4WwLPueC22PGIlrdgdZIM9_GO8/edit?usp=sharing">a short version</a>. (Note: these templates are also provided as core part of the functionality of the <a href="http://www.getshipit.com/">shipit product management tool</a>. Both as Google Drive and Atlassian Confluence versions.)</p><h4>Introduction</h4><p>This should contain a quick overview of the initiative, and focus on the <em>why: why is this needed, why is it relevant for customers, why are we building this.</em></p><h4><strong>Customer needs, market and business model</strong></h4><ul><li>Who are the customers who will use this feature or asked for it? In general terms (personas), but also specific customer names</li><li>How many customers have asked for this feature? Ideally provide counts or list from feature requests or your CRM tool.</li><li>How will this initiative be priced? For a full product this is the full business model, for a new initiative for an existing product the question is how current pricing will change (or not).</li></ul><h4><strong>Expected results</strong></h4><p>What do we expect to happen after we launch? This is very important to write down and check back after launch. It also is crucial to explicitly align everyone’s expectations and have them explicitly recorded <em>before </em>launch.</p><h4><strong>Product marketing, marketing and communications</strong></h4><ul><li>Key metrics: relating to the above: how will traction and success be measured?</li><li>Product marketing and communication: key messages, wording, links to working docs of blog posts, press releases etc. (Before launch).</li></ul><h4><strong>Personas</strong></h4><p>The user personas of our product or initiative</p><h4><strong>Functional Requirements</strong></h4><p>This is the set of product functionality. You can write these in various ways:</p><ul><li>User story type: I recommend to stay on the “Epic” level and put further details and detailed user stories into your ticketing system.</li><li>“Jobs to be done”: what customers/users want to achieve.</li><li>It’s generally a good idea to link to your ticketing system, once you start entering epics, user stories, and tickets. For example you could link a list of relevant Jira epics.</li></ul><h4><strong>Non-Functional Requirements</strong></h4><p>These are typically requirements for uptime, performance etc. Most typical performance metrics to consider are throughput and latency.</p><h4><strong>Design and UX</strong></h4><p>Link to any design in UX materials you may have in for example Figma or Sketch.</p><h4><strong>Technical Specifications</strong></h4><p>Links to detailed technical and engineering notes, if relevant.</p><p>So you see that the PRD is a place that “holds everything together” by linking to various places. It is the umbrella unit for all the various disciplines that will be involved in shipping: engineering, design, business development, marketing, etc.</p><h3><strong>What’s the difference to Jira, Trello?</strong></h3><p>I get this question a lot when talking about product requirements. As you may have noticed, the PRD contains pretty much everything that is crucial for the launch and does not live in Jira/Trello typically. So, again, usually everything besides the stories and features. It’s also the place that should give one simple, quick overview to get started or check back. Something that’s often lost when faced with a long backlog of tickets.</p><h3><strong>The hierarchy of product, initiatives, epics, user stories, and tasks</strong></h3><p>You may wonder how the product roadmap items and the requirement documents (PRDs) relate to Epics and User Stories of Scrum. It’s quite simple, they are another, higher level of abstraction. The Product requirements typically stay at product or product initiative level. (An initiative would be some major effort for a larger, existing product. It would cover many epics and user stories, and could take many sprints, and up to 3 month or so to complete. Think of things such as adding an E-Mail Marketing tool to an existing CRM Software.)</p><p>Your <a href="https://medium.com/getshipit/how-to-ship-product-with-a-quarterly-product-roadmap-and-sprint-based-execution-610e286d20ee">product roadmap</a> would typically contain only things that are “large enough” i.e. on said initiative level. It would not list individual features. These stay in the backlog of your ticketing system. Furthermore, the roadmap does not have to reflect all the “little” changes and features that may be going on outside of the key initiatives.</p><p>A hierarchy of these artefacts and the tools they live in could thus be listed like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WqVF_IZIY6LYHLbGbQ6VaQ.png" /></figure><h3><strong>Format and alternatives</strong></h3><p>We have described one way of writing product requirements above. Even though there is a lot to cover, it’s recommended to keep the documents short. Alternatives to a PRD could also be the famous Toyota A3 report, which summarises everything that’s relevant on one A3 format of paper, or a simple one-page kind of document per initiative.</p><p>If you like this format, I recommend you try the tool <a href="http://www.getshipit.com/">shipit</a>, which helps you manage your roadmaps and product requirements with a straightforward approach.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56f983a1edf1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/getshipit/what-are-product-requirements-documents-and-why-do-i-need-them-56f983a1edf1">What are product requirements documents and why do I need them?</a> was originally published in <a href="https://medium.com/getshipit">getshipit</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Das Märchen vom schmutzigen Elektroauto]]></title>
            <link>https://medium.com/quack-ventures/das-m%C3%A4rchen-vom-schmutzigen-elektroauto-48588f6c7e8b?source=rss-26e38020d4b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/48588f6c7e8b</guid>
            <dc:creator><![CDATA[Till Quack]]></dc:creator>
            <pubDate>Mon, 15 Jul 2019 20:45:19 GMT</pubDate>
            <atom:updated>2022-08-20T08:48:03.332Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7WtjQvIYjhKFtjbBbxqxgw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@tesla3?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Taun Stewart</a> on <a href="https://unsplash.com/search/photos/tesla?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Regelmässig ist in der Presse zu lesen, dass die angeblich so umweltfreundlichen Elektroautos — oh Schreck! — gar nicht so sauber seien. Zuletzt zum Beispiel im <a href="https://www.tagesanzeiger.ch/wirtschaft/elektroautos-werden-die-welt-nicht-retten/story/10380024">Tages Anzeiger</a> und der <a href="https://www.nzz.ch/wirtschaft/strom-aus-erneuerbaren-schadet-dem-klima-ld.1482628">NZZ</a>. In der Regel folgt die Story dem Schema:</p><ul><li>Batterie-Herstellung erzeugt erhebliche Mengen von CO2</li><li>Der Strom für den Betrieb kommt nicht sauber „aus der Steckdose“ sondern vom schmutzigen Kohlekraftwerk</li><li>Ausserdem seien Rohstoffe wie Lithium, Cobalt, und „seltene Erden“ begrenzt, und zum Teil ethisch fragwürdig</li><li>Das Elektro-Tankstellennetz fehlt</li></ul><p>All diese Punkte sind zum Teil korrekt (mehr dazu unten). Was typischerweise folgt sind aber meist diese Schlussfolgerungen:</p><ul><li>dass ein Benziner / Diesel heute CO2 effizienter sei</li><li>dass Gas, Wasserstoff, oder synthetische Kraftstoffe eine bessere alternative Technologie zum batteriebetriebenen Elektroauto sind. (Oft wird allerdings gar keine Alternative genannt -sic)</li></ul><blockquote><em>Beides ist nicht korrekt und wurde mehrfach widerlegt. (Ich werde diesen Artikel über die Zeit mit </em><a href="https://www.wiwo.de/unternehmen/auto/studie-adac-rechnet-elektroautos-schlecht/24582284.html?social=twitter&amp;Echobox=1562839181#utm_term=Autofeed&amp;utm_medium=Social&amp;utm_source=Twitter"><em>Quellen</em></a><em> ergänzen, aber als Startpunkt empfehlen sich diese </em><a href="https://twitter.com/AukeHoekstra/status/1135963253484507136"><em>beiden</em></a><em> Twitter </em><a href="https://twitter.com/AukeHoekstra/status/1143848999067291653"><em>Threads</em></a><em> die wiederum auf die entsprechenden Originalquellen verweisen.)</em></blockquote><p>Viel wichtiger sind aber einige Punkte, die den Autoren immer vollständig entgehen:</p><p><strong>Ein Elektroauto kann schon heute mit 100% erneuerbarer Energie betrieben werden</strong></p><p>Als Elektroauto-Fahrer kann ich schon heute entweder eine Solaranlage installieren, oder bei meinem Stromanbieter (für einen Aufpreis) nur erneuerbare Energie beziehen. Das heisst der <em>durschnittliche</em> Strommix eine Landes, der für die meisten Berechnungen zum CO2 als Basis dient, wird irrelevant. In diesem Fall ist das Elektroauto heute bei weitem die beste Alternative zu jedem anderen Auto. Beim Benzinauto hat man keine Wahl. Der CO2 Ausstoß bleibt wie er ist.</p><p>Ausserdem geht auch der Strommix über die Zeit zu höherem Anteil Erneuerbare, wie in obigen Links auch dargelegt. Das heisst die Bilanz verbessert sich auch in diesem Fall über die Jahre, und ganz automatisch.</p><p><strong>Zukünftige Alternativen sind Zukunftsmusik — und wir brauchen Lösungen heute</strong></p><p>Wasserstoff, synthetische Treibstoffe, Power-to-Gas sind alles wichtige Technologien, allerdings sind sie heute nicht Marktreif und ökonomisch/ökologisch schwieriger einzusetzen als batteriebetriebene Fahrzeuge: Die Kette von der Herstellung von Wasserstoff oder anderen Gasen und deren Nutzung durch Brennstoffzelle oder Verbrennung ist über alles ca. 50% so effizient wie direktes Laden der Batterie und Antrieb mit Elektromotor. (Das kann man an verschiedenen Stellen online oder im Physikbuch nachlesen.) Das heisst mit jeder Kilowattstunde Strom die für die alternativen Technologien genutzt werden sind CO2 Ausstoss und Kosten immer ca. doppelt so hoch bei Nutzung im batteriebetriebenen Elektrofahrzeug. Jedes Argument bezüglich Strommix etc., das gegenüber dem CO2 Ausstoss des batteriebetriebenen Elektroauto vorgebracht wird zählt daher also doppelt für diese Technologien. (Ausnahme: Batterieherstellung. Die Frage is allerdings auch wie die CO2 Bilanz der Herstellung eines Wasserstoff Autos aussieht — ich weiss es nicht). Falls 100% Erneuerbare genutzt werden ist die CO2 Bilanz im Betrieb für beide gut, nur die Kosten für Alternativen zum Batteriebetrieb doppelt so hoch.)</p><p>Wichtig sind Lösungen jetzt und nicht in 20 Jahren: weil die nächsten 1–2 Jahrzehnte entscheidend sind um die Erderwärmung unter 2 Grad zu halten. Wir sollten zwar mit Hochdruck an neuen Technologien forschen, aber nicht auf diese warten.</p><p><strong>Nutzungsverhalten und Tankstellennetz</strong></p><p>Jeder, der ein Elektroauto (vor allem Tesla) über einige Monate nutzt, realisiert, dass die “Elektro-Tankstellen” gar nicht so wichtig sind. Meistens lädt man Zuhause über Nacht oder beim Arbeitgeber während des Tages. Letzteres ist in Kalifornien längst gang und gäbe. Ich lebte selbst für einige Jahre im Silicon Valley: mein Tesla wurde beim Arbeitgeber geladen, während ich bei der Arbeit war. 100% Solarstrom. Kostenlos. Ca 1–2 mal laden pro Woche reichte bei weitem.</p><p>Der Punkt ist: das Nutzerverhalten ist komplett anders. Man muss sozusagen nie mehr “zur Tankstelle”. Das realisiert man erst wenn man so ein Auto über einige Monate nutzt. Und die meisten Journalisten haben eben nie ein Elektroauto wie einen Tesla über mehrere Monate gefahren. Sie sollten es tun. Es führt einem vor Augen warum Tesla Nutzer so begeistert sind. Es hat wenig mit Tesla-Kult zu tun, sondern mit Einsicht und der Erfahrung am eigenen Leibe wie die Zukunft aussieht.</p><p>Natürlich braucht es Schnelllader für weite Distanzen. Die schnelle Ladung ist in der Tat vermutlich noch die einzige Hürde um das Elektroauto in allen Punkten dem Benzinauto Überlegen zu machen. Dies ist allerdings mehr ein “Engineering” Problem, und weniger ein fundamentales physikalisches Problem.</p><p>Man beachte ausserdem, dass man sowohl Benzin als auch Wasserstoff nicht zuhause laden kann. Und deshalb zum Beispiel das Wasserstoff Auto viel stärker von einem existierenden Tankstellennetz abhängig ist als das Elektroauto.</p><p><strong>Rohstoffe</strong></p><p>Gewinnung der Rohstoffe für EVs ist nicht optimal, aber dem Thema wird zuviel Aufmerksamkeit geschenkt. Es gibt genügend Lithium, Kobalt, und andere Rohstoffe. Sie können recycelt werden. Ethische Fragen müssen mit Hochdruck gelöst werden. Es sollte politischer Druck auf die Batteriehersteller und Abbauländer ausgeübt werden. <strong>Aber</strong>: das kann vor allem im Vergleich zur Ölförderung (erhebliche Umwelt und ethische/politische Probleme) oder Batterietechnologie in anderen Produkten kein Argument sein nicht auf Elektrautos zu setzen. Im besten Fall ist es scheinheilig. Die exakt gleichen Batterien und Rohstoffe finden sich in jedem Smartphone — nur <a href="https://www.theguardian.com/global-development/2018/oct/12/phone-misery-children-congo-cobalt-mines-drc">selten</a> liest man über die Problematik des Lithium oder Cobalt Abbaus im Kontext für die Nutzung in unserem Smartphone.</p><p>Eine Bemerkung zu „seltenen Erden“: in Batterien und den meisten Elektromotoren kommen keine Elemente der seltenen Erden zum Einsatz, wie oft fälschlicherweise geschrieben wird. Oben genannte Lithium, Cobalt etc gehören nicht in diese Gruppe. Zudem sind weder diese Rohstoffe, noch die eigentlichen seltenen Erden, wirklich selten.</p><p><strong>Zweck der kritischen Artikel?</strong></p><p>Man fragt sich also, was der Sinn eines Artikels sein soll, der das Elektroauto negativer als korrekt oder nötig darstellt. Denn es müsste ja jede Möglichkeit zur Reduktion des CO2 Ausstosses von uns mit Begeisterung aufgenommen werden. Mir Fallen drei Gründe ein:</p><ul><li>journalistische “Enthüllung” eines Missglaubens oder “Pointe” (allerdings eben basierend auf falschen Annahmen, wie oben dargelegt.)</li><li>Rechtfertigung des Status Quo („es ist ok Diesel zu fahren. Ich muss bei diesem neumodischen Zeug nicht mitmachen.“)</li><li>aufzeigen das *kein* Auto die einzige Alternative ist.</li></ul><p>Punkt 1) und 2) sind schlechter Journalismus, Punkt 3) leider vermutlich naiv.</p><p>Quellen und weiterführende Links:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FV-uJRnH450U%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DV-uJRnH450U&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FV-uJRnH450U%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/42d6c4a2cc1c612e219e6871db5ba7cd/href">https://medium.com/media/42d6c4a2cc1c612e219e6871db5ba7cd/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FTvlcVL6qiXs%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DTvlcVL6qiXs&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FTvlcVL6qiXs%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/b35bd44a2d2e56f4b7a4c1cc832fb421/href">https://medium.com/media/b35bd44a2d2e56f4b7a4c1cc832fb421/href</a></iframe><h3>AukeHoekstra on Twitter: &quot;Thread with tweets I refer to often.First my studies showing EVs are really much betterArticle Joule https://t.co/OzSgcEL8aOCO2 study with Prof Steinbuch https://t.co/IXdo7K4n1GUs in Der Spiegel https://t.co/qX7PI5dC5WTransport &amp; Environment toolhttps://t.co/oPxqB7fi82 pic.twitter.com/pLXbaXSSvd / Twitter&quot;</h3><p>Thread with tweets I refer to often.First my studies showing EVs are really much betterArticle Joule https://t.co/OzSgcEL8aOCO2 study with Prof Steinbuch https://t.co/IXdo7K4n1GUs in Der Spiegel https://t.co/qX7PI5dC5WTransport &amp; Environment toolhttps://t.co/oPxqB7fi82 pic.twitter.com/pLXbaXSSvd</p><ul><li><a href="https://www.nau.ch/news/wirtschaft/neue-schweden-studie-zeigt-e-autos-werden-umweltfreundlicher-65623742">Neue Schweden-Studie zeigt: E-Autos werden umweltfreundlicher</a></li><li><a href="https://www.theguardian.com/global-development/2019/dec/16/apple-and-google-named-in-us-lawsuit-over-congolese-child-cobalt-mining-deaths">Apple and Google named in US lawsuit over Congolese child cobalt mining deaths</a></li><li><a href="https://www.delta.tudelft.nl/article/how-clean-hydrogen-really">How clean is hydrogen really?</a></li><li><a href="https://www.wiwo.de/unternehmen/auto/iaa2019/iaa-vw-chef-herbert-diess-ueber-wasserstoff-autos-das-ist-einfach-unsinn-/25009062.html">IAA: VW-Chef Herbert Diess über Wasserstoff-Autos: „Das ist einfach Unsinn&quot;</a></li><li><a href="https://emobicon.de/news-kraftstoff-keine-alternative-zum-akku/">Warum Kraftstoffe trotzdem keine Alternative zum Akku sein können</a></li><li><a href="https://innovationorigins.com/fraunhofer-ise-was-wrong-hydrogen-cars-are-not-cleaner-than-battery-driven-electric-vehicles-and-diesel-cars-are-not-even-close/">Fraunhofer ISE was wrong: hydrogen cars are not cleaner than battery-driven electric vehicles and diesel cars are not even close - Innovation Origins</a></li><li><a href="https://www.tagesspiegel.de/wirtschaft/nachhaltigkeit-von-tesla-akkus-wenn-elf-avocados-umweltschaedlicher-als-eine-e-auto-batterie-sind/25291904.html">Wenn elf Avocados umweltschädlicher als eine E-Auto-Batterie sind</a></li><li><a href="https://ecomento.de/2019/07/30/batterie-elektroautos-sind-wasserstoff-stromern-ueberlegen-analyse/">Batterie-Elektroautos sind Wasserstoff-Stromern überlegen - ecomento.de</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48588f6c7e8b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/quack-ventures/das-m%C3%A4rchen-vom-schmutzigen-elektroauto-48588f6c7e8b">Das Märchen vom schmutzigen Elektroauto</a> was originally published in <a href="https://medium.com/quack-ventures">Quack Ventures</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to ship product with a quarterly product roadmap and sprint-based execution]]></title>
            <link>https://medium.com/getshipit/how-to-ship-product-with-a-quarterly-product-roadmap-and-sprint-based-execution-610e286d20ee?source=rss-26e38020d4b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/610e286d20ee</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[roadmaps]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Till Quack]]></dc:creator>
            <pubDate>Sat, 25 May 2019 14:30:18 GMT</pubDate>
            <atom:updated>2019-05-26T10:48:53.637Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NDSC6miXVxQOkT7SCpO1ig.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/1bhp9zBPHVE?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Edi Libedinsky</a> on <a href="https://unsplash.com/search/photos/binocular?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Every now and then I get asked how to best organise a product roadmap, and how to execute on it. I’ve been asked frequently enough to publish my suggestions here in this post.</p><h3><strong>Product management with “advanced common sense”</strong></h3><p>One of my all time favourite terms is how David Allen summarised <a href="https://en.wikipedia.org/wiki/Getting_Things_Done">his Getting Things Done</a> approach for personal productivity: “<a href="http://edition.cnn.com/2007/TECH/internet/02/09/david.allen/index.html">advanced common sense</a>”. It shows that an approach that works doesn’t have to be complex. In fact, maybe it mustn’t. A working method can just be common sense — or a slightly advanced form of it.</p><p>The same applies to managing product roadmaps. The organisations I’ve encountered so far, in practice sooner or later converge to two types of iterative process:</p><ul><li>Execution of product development with Agile. Frequently, <a href="https://www.scrumguides.org/">Scrum</a> is used. Sometimes <a href="https://en.wikipedia.org/wiki/Kanban_(development)">Kanban</a>.</li><li>Organisation-wide quarterly planning for higher level goals. (e.g Q1 2019 from Jan to Mar etc.)</li></ul><p>Hence it makes sense to structure a longer term product roadmap into calendar quarters. And to execute the implementation of the items in the current quarter with Agile, e.g. Scrum.</p><h3><strong>The topology of a quarterly product roadmap</strong></h3><p>A quarterly product roadmap can be represented quite easily in table format. Along the horizontal axis there is a column for each quarter. Typically you may want to represent 3–6 quarters, including the current one. For items that are beyond the number of quarters you represent, you can add one more column, for example for the next year, or simply “later”. Along the vertical axis you can add a row (or “swimlane”) for each product line or functional area. Imagine the product roadmap for a blockchain-based real-estate marketplace. With the above structure could look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/863/1*bP26b9hVoV-JWo1gwoQjVQ.png" /></figure><p>Now just add an item for each key activity. There should be at most a handful of items per quarter and track. I recommend to order them by priority in each track — items that are higher within each cell have higher priority.</p><p>You can implement a roadmap like this simply in a spreadsheet, or you can use a dedicated product such as <a href="http://www.getshipit.com/"><strong>shipit</strong></a>. The advantage of a dedicated product is that it integrates additional functionality, such as a short description for each item that shows on mouse hover, and a bunch of additional helpful features and integrations.</p><h3><strong>Planning and prioritising the roadmap</strong></h3><p>You use the roadmap with a “rolling” quarterly planning approach. When you approach the next upcoming quarter you plan it in detail. When a quarter completes you remove it and add one more at the end of the roadmap. Items can be slotted into any cell at any time (except for the current quarter — it should be considered “locked”).</p><p>Here’s an example: suppose it’s early June 2019. You are about to complete Q2 2019, and need to start planning Q3 in detail. These are the steps you would typically carry out:</p><ul><li>Check on status of Q2 items. Some of them may rolll over to Q3.</li><li>Do an initial pass over the items in Q3 and verify if all of them are still relevant. Move those that aren’t.</li><li>Check future quarters to see if anything should be tackled in Q3 instead.</li><li>Do an initial ranking by priority for the Q3 items in each track.</li><li>Discuss the draft of the Q3 priority list with your organisation’s stakeholders. Ask them for their input regarding priority of the items. Reprioritise as needed.</li><li>Do a prioritisation and cleanup pass over future quarters.</li><li>As Q3 approaches or starts communicate the key roadmap activities for Q3 to the teams, and give an update and outlook on the future quarters.</li></ul><h3><strong>Why quarters?</strong></h3><p>Quarters have a “comfortable” size: they are long enough to allow for making significant progress on major items. They are short enough to constrain the work and be able to “see the horizon” within that timeframe. They are a good timeframe to set some high level (product) goals and rally the teams round them. This applies to the current and the upcoming quarter.</p><p>Beyond 4 quarters (a year), planning and giving reasonable time estimates gets typically much harder. Just having a bucket for the next year or “later” in order to capture further out items addresses this inherent uncertainty in a pragmatic way.</p><p>With the above approach, the level of detail and certainty is high in the near term and low for things that are further out. This is exactly what you want to have.</p><h3><strong>Quarters and Sprints</strong></h3><p>The focus of the current quarter is on execution. The items on the product roadmap give only a high level direction and high level goals. Detailed planning and execution, and making sure to deliver value to the customer in frequent increments is the role of Agile process.</p><p>Within the current quarter you can easily apply Agile, for example Scrum. If you are running for example 2-week Sprints, you will have about 6 sprints to execute on the roadmap priorities for the current quarter. You may want to attack them by priority, but typically 2 or 3 may run in parallel, depending in your team size.</p><h3><strong>Is this still Agile?</strong></h3><p>As you can see from above, the quarterly roadmap planning approach integrates nicely with Agile execution. But is such a longterm planning and roadmap still truly Agile? I would argue it is complementary. In fact, one key-criticism of Agile/Scrum is that it lacks the longterm perspective. A simple quarterly roadmap as introduced may address this criticism.</p><p>At the same time the process is not expected to inhibit the key premise of Agile: being able to deliver value to the customer and to adapt and react based on feedback. The roadmap gives only the high level direction. Any details of the features for each item are carried out exactly in Agile fashion.</p><p>Furthermore, the product roadmap will only list “major” initiatives. Smaller features and increments will not be listed explicitly but just handled in your regular Agile process and ticketing system. For example with user story tickets in <a href="https://www.atlassian.com/software/jira">Jira</a> or Trello. Often times an item on the product roadmap may link to an Epic in your Scrum, or Jira respectively.</p><p>From an organisation perspective the product roadmap can be seen as the (often missing) layer or link between vision and daily execution:</p><ul><li><strong>Company or product vision: sets the course for multiple years</strong></li><li><strong>Product roadmap: sets the course for months up to a year</strong></li><li><strong>Agile / Sprints: sets the course for days to weeks.</strong></li></ul><p>Ideally all these levels should be connected so your team understands how the current sprint’s work relates to the product roadmap, and how the product roadmap in turn releases to the company or product vision.</p><p>In a next post we will talk about another important aspect of communication your product plans to your team and stakeholders: product requirements.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=610e286d20ee" width="1" height="1" alt=""><hr><p><a href="https://medium.com/getshipit/how-to-ship-product-with-a-quarterly-product-roadmap-and-sprint-based-execution-610e286d20ee">How to ship product with a quarterly product roadmap and sprint-based execution</a> was originally published in <a href="https://medium.com/getshipit">getshipit</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[European startup ranking per capita and per GDP]]></title>
            <link>https://medium.com/quack-ventures/european-startup-ranking-per-capita-and-per-gdp-be6a3a0ae04c?source=rss-26e38020d4b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/be6a3a0ae04c</guid>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Till Quack]]></dc:creator>
            <pubDate>Sun, 16 Dec 2018 13:36:12 GMT</pubDate>
            <atom:updated>2018-12-19T19:35:22.605Z</atom:updated>
            <content:encoded><![CDATA[<h3>European startup ecosystem ranking per capita and per GDP</h3><p><em>Update Dec 17: added new section on number of startups per country.</em></p><p>Recently the <a href="https://2018.stateofeuropeantech.com/">State of European Tech Report 2018</a> has been published. It contains a tremendous amount of information comparing various European countries and startup-hubs. However, most of the analysis does not take into account a country’s size in terms of population or GDP. This post aims at filling some of these gaps. In short: the goal is to analyse, which European countries “punch above their weight” when it comes to offering a flourishing startup ecosystem.</p><h4>Investment per capita and per GDP</h4><p>How much investment do startups in various European countries attract, compared to the size of the country’s population and economy?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/874/1*g4rEHmwThqJqaI_E-hmW5Q.png" /><figcaption>Cumulative capital invested since 2013, per capita. Showing top 25 European countries. See footer of this article for link to full list of European countries.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/795/1*p70CG2yJ8ZcTQD9Fr9fJdg.png" /><figcaption>Cumulative capital invested per $ GDP. Timeframe 2013 until Sept 2018. Showing top 25 European countries. See footer of this article for link to full list of European countries.</figcaption></figure><p>Looking at investment per country size in terms of population and GDP pushes some smaller countries like Luxembourg, Iceland, or Malta higher in the ranking. Overall top ranked startup ecosystems like the UK or Sweden are also in the top performers, as they are in the original State of European Teach Report. In other words: no matter what way you look at it, they do well. Other noteworthy countries include Estonia, Finland, Denmark, and Switzerland. Other larger countries/economies besides the UK, Germany and France, are ranked stably in the middle of the top 25 performers.</p><h4>Number of deals per capita and per GDP</h4><p>When it comes to the number of investments (“deals”) over the last 5 years, Nordic countries as well as other smaller countries dominate the top ranks, from the larger European countries only the UK stay in the upper ranks, Germany and France move lower.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/934/1*RwihPdoxmPL5IIYkZkBNXA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*vLJU0ZrMXEM-NhDaxZp0BQ.png" /></figure><p>When taking into account the size of the economy Estonia is the clear winner.</p><h4>Number of unicorns</h4><p>While the above metrics show the investor activity per country, the number of unicorns can be seen as one measure of success.</p><p>Estonia is the winner here, both when taking into account size of population and economy. However, it should be noted that the data for Estonia here is based on a single unicorn (and similarly for a few other countries in the list).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*IRcIlFPvFYcns_bx5tED6g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*JDnnWurrGsl5v26dKVCjTA.png" /></figure><h4>Number of startups per capita and per GDP</h4><p>The final question we try to answer is: which country has most startups per capita and per GDP unit? Note: the number of startups per country is not covered in <a href="https://2018.stateofeuropeantech.com/">State of European Tech Report 2018</a>. However, similar to that report the data for this analysis was gathered from dealroom.co.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/833/1*9ftctsfCN_7kcAX_Smb8PA.png" /><figcaption>Number of startups per capita. Showing top 25 European countries. See footer of this article for link to full list of European countries.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/832/1*dy8O-aFSziC8btOTjH1OAw.png" /><figcaption>Number of startups per $1000 GDP. Showing top 25 European countries. See footer of this article for link to full list of European countries.</figcaption></figure><p>It is evident from the charts that Estonia wins by quite a margin in both dimensions. Then mostly Nordic and smaller countries follow. The UK are the top ranked from the larger European countries.</p><h4>Data Sources</h4><ul><li>All startup related data: <a href="https://2018.stateofeuropeantech.com/">https://2018.stateofeuropeantech.com</a></li><li><a href="https://en.wikipedia.org/wiki/List_of_countries_and_dependencies_by_population">Population</a> and <a href="https://en.wikipedia.org/wiki/List_of_countries_by_GDP_(nominal)">GDP</a> data from Wikipedia</li><li>Number of startups from <a href="http://www.dealroom.com/">dealroom.co</a></li><li>Explore the full data set, including list that cover ranks beyond the top 25: <a href="https://docs.google.com/spreadsheets/d/e/2PACX-1vTaVpKYCwYimyryV_x_h58WOHxsqXu9SAQ1jIvhSgStvj_1zrnYFkwu4ptMzpTdp4r0prp1jE7a7u0e/pubhtml">Google Doc Link</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be6a3a0ae04c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/quack-ventures/european-startup-ranking-per-capita-and-per-gdp-be6a3a0ae04c">European startup ranking per capita and per GDP</a> was originally published in <a href="https://medium.com/quack-ventures">Quack Ventures</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>