<?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[getshipit - Medium]]></title>
        <description><![CDATA[Medium blog for getshipit.com - Medium]]></description>
        <link>https://medium.com/getshipit?source=rss----64986bd10cd5---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>getshipit - Medium</title>
            <link>https://medium.com/getshipit?source=rss----64986bd10cd5---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 00:52:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/getshipit" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <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----64986bd10cd5---4</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:32:43 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----64986bd10cd5---4</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[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----64986bd10cd5---4</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>
    </channel>
</rss>