<?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 Amit Mutreja on Medium]]></title>
        <description><![CDATA[Stories by Amit Mutreja on Medium]]></description>
        <link>https://medium.com/@amitmutrezas?source=rss-ce9e265e6a80------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*zkFj3Y6kK1Xg9B9W.jpeg</url>
            <title>Stories by Amit Mutreja on Medium</title>
            <link>https://medium.com/@amitmutrezas?source=rss-ce9e265e6a80------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:32:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@amitmutrezas/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[Getting Dirty With Project Management]]></title>
            <link>https://medium.com/pm-crash-course/getting-dirty-with-project-management-3ac5fd09eea1?source=rss-ce9e265e6a80------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ac5fd09eea1</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Amit Mutreja]]></dc:creator>
            <pubDate>Wed, 31 Oct 2018 19:15:43 GMT</pubDate>
            <atom:updated>2018-10-31T19:17:18.818Z</atom:updated>
            <content:encoded><![CDATA[<p>A product manager needs to know about the processes and should communicate new projects to all the stakeholders. If there is no dedicated project manager at your company then as a product manager it is your duty to make sure that a given project is completed on time.</p><p>For this purpose, <a href="https://medium.com/@amitmutrezas/agile-project-management-scrum-on-trello-9e7cce78bca0">I have already written a blog with illustrations using Trello</a>. But let’s define Epics, User Stories and the Acceptance Criteria here.</p><h4><strong>Epics and Epic Spec Sheet</strong></h4><p>An epic is a grouping of one or more features or functionalities that we want to build. Epic spec sheet contains all the requirement for building a product. The spec sheet has four main areas:</p><p><strong>1) Introduction:</strong></p><ul><li>summary of what the features you’re building and why you’re building</li><li>what metrics you’re trying to improve</li><li>links to specific documentation</li><li>Marketing plans, legal requirements</li><li>early wireframes</li></ul><p><strong>2) Product Requirements:</strong></p><ul><li>what is required for the specific features that you want to build</li></ul><p><strong>3) Design Requirements:</strong></p><ul><li>this section is filled with the designer</li><li>sketches, prototypes</li></ul><p><strong>4) Dev Requirements:</strong></p><ul><li>mostly filled out by the engineers after an epic is discussed with them</li><li>contains what must be done on the technology side</li></ul><h4>User Story</h4><p>Epics are big and abstract stories that tell what should the product do for the user. But to detail out each and every use case, epics need to be broken down into short tasks called from “user stories” from the perspective of the end user.</p><p>The format for user stories is,</p><blockquote>As an X, I want to do Y, so that I can Z</blockquote><p>Example: As a user, I want to send pictures in a direct message to my friends, so that I can share my favourite photos with them</p><h4>Acceptance Criteria</h4><p>Acceptance Criteria allow you to describe the conditions that have to be fulfilled so that the story can be marked as done. The criteria enrich the story, they make it testable, and they ensure that the story can be demoed or released to the users and other stakeholders.</p><p>The acceptance criteria would be:</p><ul><li>A pop-up should be opened to upload the photo</li><li>An error should be thrown if the photo size exceeds the max allowed size</li><li>An error should occur if the photo format is different from the allowed formats</li></ul><p><strong>A criterion to assess users stories is I.N.V.E.S.T.</strong></p><ul><li><strong>Independent</strong>: User stories should be independent as any dependency would make it difficult to prioritize them one over the other</li><li><strong>Negotiable</strong>: The implementation details are not specified and are left to the team</li><li><strong>Valuable</strong>: User stories should have value to the customers</li><li><strong>Estimable</strong>: They should be broken down into the simplest form that the team can work with</li><li><strong>Small</strong>: They should be small enough to be finished within a <a href="https://medium.com/@amitmutrezas/agile-project-management-scrum-on-trello-9e7cce78bca0">sprint</a></li><li><strong>Testable</strong>: The incremental deliverable should be testable against the acceptance criteria specified</li></ul><h4>Where to write these user stories?</h4><p>You could use the solution as simple as Google Sheet to advanced solutions like <a href="http://www.trello.com/">Trello</a>, <a href="https://www.atlassian.com/software/jira">Jira</a>, <a href="https://www.aha.io/">Aha</a>, <a href="https://craft.io/">Craft</a> and many other tools.</p><p><a href="https://medium.com/@amitmutrezas/agile-project-management-scrum-on-trello-9e7cce78bca0">Agile Project Management using Trello</a></p><p><a href="https://medium.com/pm-crash-course/product-development-process-and-the-seven-stages-fecf394ed1e4"><em>Previous chapter: </em>Product Development Process and The Seven Stages</a></p><p><em>Next chapter: </em>(…<em>coming soon…</em>)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ac5fd09eea1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pm-crash-course/getting-dirty-with-project-management-3ac5fd09eea1">Getting Dirty With Project Management</a> was originally published in <a href="https://medium.com/pm-crash-course">PM Crash Course</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Management for Beginners]]></title>
            <link>https://medium.com/pm-crash-course/product-management-for-beginners-dbe30612f33e?source=rss-ce9e265e6a80------2</link>
            <guid isPermaLink="false">https://medium.com/p/dbe30612f33e</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[course]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Amit Mutreja]]></dc:creator>
            <pubDate>Sun, 23 Sep 2018 14:35:37 GMT</pubDate>
            <atom:updated>2018-09-23T14:35:37.582Z</atom:updated>
            <content:encoded><![CDATA[<p>Product Management is a strange and mysterious role. That is what I felt when I started looking up about it on the Internet.</p><p>I didn’t get to hear a lot about it in my grad school but after the graduation, I met many people working in the tech companies who claimed to have expertise in product ‘development’ but didn’t even write a single line of code. They considered themselves to be responsible for the success/failure of the product. It made me curious. I would spend day and night browsing, reading articles and watching videos about mainly 2 things:</p><ol><li>What is product management and what does a product manager do?</li><li>How does one get started? Any formal training available offline or online recognised by the industry?</li></ol><p>But the result was — I was quite lost while learning and researching the realm of product management as there was not a structured approach to it. This series of articles is my effort to close the knowledge gap and help the people who are just starting out but finding it difficult or even who just want to know what all the fuss is about.</p><p>The content of the handbook is brief and touches all the important aspects so that one can quickly get the taste of it and is able to dig deeper in a structured manner.</p><ol><li><a href="https://medium.com/pm-crash-course/what-is-a-product-and-product-management-c5581056890f">What is a Product and Product Management?</a></li><li><a href="https://medium.com/pm-crash-course/three-types-of-product-managers-8eb8b69c70c">Three Types of Product Managers</a></li><li><a href="https://medium.com/pm-crash-course/product-life-cycle-plc-and-the-four-phases-c46a5261b7a8">Product Life Cycle and The Four Phases</a></li><li><a href="https://medium.com/pm-crash-course/product-development-process-and-the-seven-stages-fecf394ed1e4">Product Development Process and The Seven Stages</a></li><li>Project Management for Product Managers (…<em>coming soon… </em><a href="https://medium.com/pm-crash-course"><em>follow the PM Crash Course for updates</em></a>)</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dbe30612f33e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pm-crash-course/product-management-for-beginners-dbe30612f33e">Product Management for Beginners</a> was originally published in <a href="https://medium.com/pm-crash-course">PM Crash Course</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Development Process and The Seven Stages]]></title>
            <link>https://medium.com/pm-crash-course/product-development-process-and-the-seven-stages-fecf394ed1e4?source=rss-ce9e265e6a80------2</link>
            <guid isPermaLink="false">https://medium.com/p/fecf394ed1e4</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[planning]]></category>
            <dc:creator><![CDATA[Amit Mutreja]]></dc:creator>
            <pubDate>Sun, 09 Sep 2018 16:22:42 GMT</pubDate>
            <atom:updated>2018-10-31T19:16:57.506Z</atom:updated>
            <content:encoded><![CDATA[<p>Every product, that is being developed, has a series of steps that they go through, we call this the product development process. There are seven main phases to this process: conceive, plan, develop, iterate, launch, steady state, and then finally we either maintain or kill the product.</p><h4>I) Conceive</h4><p>This is the R&amp;D stage for the idea generation for a particular problem or a set of problems. The ideas may come from different sources: user feedback, co-workers, competitors etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*51hr_rdNyFwm5GMo6KbSlw.jpeg" /><figcaption>source: ethos3.com</figcaption></figure><ol><li>Collect users’ problems, understand them and brainstorm solutions.</li><li>Identify the focus areas to work on.</li></ol><h4>II) Plan</h4><p>Market research is done on the ideas which are already accepted in the previous stage. These selected ideas are also called initiatives</p><ol><li>Evaluate the different selected ideas or initiatives.</li><li>Look at the business case and see what goal is getting fulfilled.</li><li>Customers may be interviewed to understand whether the feature conceptualised solves the actual problem.</li><li>Build a roadmap of the different initiatives, how long it might take, and at what point a particular initiative should be built.</li></ol><h4>III) Develop/Execute</h4><p>This is the stage where we get our hands dirty. We lay out the requirements and by the time dev team starts implementing these requirements should be set and shouldn’t really change until we get some sort of validation from the previous iteration or sprint.</p><ol><li>Make timelines and detail out the features that need to be built.</li><li>Write user stories and specs.</li><li>Give estimations after consulting with the Dev team.</li></ol><h4>IV) Validate</h4><p>Once an early prototype or MVP, Minimum Viable Product, of the product or service is developed, it’s time to test it with the real customers.</p><ol><li>Test the assumption made with the MVP.</li><li>Get early feedback from the users by using alpha and beta testing.</li></ol><h4>V) Launch</h4><p>Deciding when, how and where to launch the product will determine its early impact on the market. This may determine the early success of the product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/930/1*Kdjlx0YkkmAeT5YPdJUTbg.png" /></figure><ol><li>Work with the marketing &amp; sales, legal and PR team to position the product for public launch.</li><li>Develop &amp; implement a Go-To-Market (GTM) strategy to help potential customers discover the product and eventually purchase it.</li></ol><h4>VI) Post Launch</h4><p>We either hold the product in a steady state or continue iterating on it based on the customer feedback &amp; our analysis.</p><ol><li>Collect metrics on how people using the product.</li><li>Keep optimizing the product based on the analysis done.</li><li>Assess continued efforts to see how likely is the growth to keep moving forward.</li><li>Marketing &amp; sales continue.</li></ol><h4>VII) Maintain or Kill</h4><p>During this stage, we gather all the data we have collected and answer a few questions: how competitive the product is and what is the ROI. Based on this, we decide whether to continue maintaining the product or kill it.</p><ol><li>Follow sun-setting to kill the product. This is a slow transition to the end of life of the product.</li><li>Allow users to back up their data before the final shut down.</li></ol><p>Killing off brands is not a popular or pleasant thought. It can be tough to admit that it’s time to pull the plug, but we should do the needful to move up the ladder in the game.</p><p><a href="https://medium.com/pm-crash-course/product-life-cycle-plc-and-its-four-phases-c46a5261b7a8"><em>Previous chapter: </em>Product Life Cycle (PLC) and Its Four Phases</a></p><p><a href="https://medium.com/pm-crash-course/getting-dirty-with-project-management-3ac5fd09eea1"><em>Next chapter: </em>Getting Dirty With Project Management</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fecf394ed1e4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pm-crash-course/product-development-process-and-the-seven-stages-fecf394ed1e4">Product Development Process and The Seven Stages</a> was originally published in <a href="https://medium.com/pm-crash-course">PM Crash Course</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Life Cycle (PLC) and The Four Phases]]></title>
            <link>https://medium.com/pm-crash-course/product-life-cycle-plc-and-the-four-phases-c46a5261b7a8?source=rss-ce9e265e6a80------2</link>
            <guid isPermaLink="false">https://medium.com/p/c46a5261b7a8</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[tutorial]]></category>
            <dc:creator><![CDATA[Amit Mutreja]]></dc:creator>
            <pubDate>Sun, 09 Sep 2018 16:20:09 GMT</pubDate>
            <atom:updated>2018-09-09T16:21:11.808Z</atom:updated>
            <content:encoded><![CDATA[<p>There are four phases that a new product progresses through are Introduction, Growth, Maturity and Decline. PLC is associated with the changes in the marketing situation and thus impacting the marketing situation.</p><p>The product revenue and profits can be plotted as a function of the PLC phases as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*NgLuyEfUUsXoIunY.jpg" /><figcaption>source: Wikipedia</figcaption></figure><h4><strong>I) Introduction</strong></h4><p>The product has just been introduced in the market and therefore, the marketing communications seek to build the product awareness and to educate the potential consumers about the product. The salient features are:</p><ol><li>There is little or no competition</li><li>Pricing may be low to gain the market share</li><li>Distribution is selective until the consumers show acceptance</li><li>Promotion is aimed at innovators and early adopters</li><li>The business typically loses money at this stage</li><li>Example: <a href="https://www.dunzo.in/">Dunzo</a></li></ol><h4><strong>II) Growth</strong></h4><p>The product has been accepted by the market and the consumers have become habitual of the product. The sales volume grow steadily in this stage and the company continuously seeks to increase the market share.</p><ol><li>There is an increasing trend in the sales volume</li><li>More and more organic users join the club</li><li>Pricing is either maintained or increased as the firm enjoys increasing demand with less number of competitors</li><li>The company may or may not choose to add the improvements but the product quality is maintained</li><li>More distribution channels are added</li><li>Promotion is now aimed at a broader audience</li><li>Example: <a href="http://instagram.com/">Instagram</a></li></ol><h4><strong>III) Maturity</strong></h4><p>The sales volume reach its pinnacle and the growth diminishes. The main objective at this stage is to defend the market share while maximizing the profit.</p><ol><li>The field becomes more competitive and new and innovative competitors enter the market</li><li>New features are built to differentiate the product from that of the competitors</li><li>Pricing may be decreased to increase the volume</li><li>Distribution becomes more intensive and incentives may be offered to encourage usage</li><li>Product emphasizes differentiation</li><li>Example: <a href="https://twitter.com/">Twitter</a></li></ol><h4><strong>IV) Decline</strong></h4><p>The company reaches its saturation point and the sales begin to diminish due to a negative rate of growth.</p><ol><li>The product is deemed irrelevant in the market and is phased out of the market</li><li>It may continue to be offered to a loyal niche segment</li><li>Example: <a href="https://in.yahoo.com/?p=us">Yahoo</a></li></ol><p>[TIP: Hop over to <a href="https://trends.google.com/trends/?geo=IN">Google Trends</a> and correlate the product’s search trend with the life cycle phase]</p><p><a href="https://medium.com/pm-crash-course/three-types-of-product-managers-8eb8b69c70c"><em>Previous chapter: </em>Three Types of Product Managers</a></p><p><a href="https://medium.com/pm-crash-course/product-development-process-and-the-seven-stages-fecf394ed1e4"><em>Next chapter: </em>Product Development Process and The Seven Stages</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c46a5261b7a8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pm-crash-course/product-life-cycle-plc-and-the-four-phases-c46a5261b7a8">Product Life Cycle (PLC) and The Four Phases</a> was originally published in <a href="https://medium.com/pm-crash-course">PM Crash Course</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Three Types of Product Managers]]></title>
            <link>https://medium.com/pm-crash-course/three-types-of-product-managers-8eb8b69c70c?source=rss-ce9e265e6a80------2</link>
            <guid isPermaLink="false">https://medium.com/p/8eb8b69c70c</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[tutorial]]></category>
            <category><![CDATA[b2b]]></category>
            <category><![CDATA[b2b-marketing]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Amit Mutreja]]></dc:creator>
            <pubDate>Sun, 09 Sep 2018 16:18:31 GMT</pubDate>
            <atom:updated>2018-09-09T16:18:31.833Z</atom:updated>
            <content:encoded><![CDATA[<p>The product managers can be broadly classified into three types depending on the stakeholders they interact with and the product they build for.</p><h4><strong>Internal Product Manager:</strong></h4><ol><li>PMs are part of the team called internal tools.</li><li>They build the tools for the other teams inside the company.</li><li>For example, an HRM tool for the HR team to support the rest of the teams or an internal job portal.</li><li>This is a great role for the new product managers because it has less risk involved as the tool is built for a small number of users.</li><li>This role involves a lot of learning as one does a lot of <a href="https://medium.com/@amitmutrezas/agile-project-management-scrum-on-trello-9e7cce78bca0">Project Management</a> as well.</li></ol><h4><strong>B2B or SAAS Product Manager</strong></h4><ol><li>A type of product manager that builds products at a company whose clients are other companies.</li><li>Examples: Oracle, Salesforce, Freshworks etc.</li><li>Needs to make sure what they build meets the business requirements of the businesses that they’re selling to.</li><li>Interacts a lot with the sales team.</li><li>This role involves a smaller number of users than a B2C role.</li><li>PMs often have tighter deadlines.</li><li>Priorities are heavily weighted by the sales team and how much money a certain feature will bring in.</li></ol><h4>B2C Product Manager:</h4><ol><li>The most common type but the most challenging one.</li><li>The product is built for millions of users and usually have a product on multiple platforms.</li><li>Examples, Facebook, Snapchat, WhatsApp etc.</li><li>This type requires a wide range of skills to be successful and as well a lot of vision and creativity. In their consumer role, product managers are always trying to maximize usage or some other metric.</li><li>No one is there to tell them that item X is the best thing to do next. That contrasts to the business to business product manager, for example, because the salespeople are saying “Hey, we’re going to make $5 million if we build this feature.” On the consumer side, no one can really predict exactly what is the thing that is to be built for sure.</li><li>The consumer PM spends a whole lot of time talking to those users, the millions of them out there, coming up with multiple different prototypes, user testing, A/B testing, and just analyzing tons of data. The bigger the user base, the more powerful the testing becomes.</li></ol><p>There are other types of PMs out there, but these are the big three you’ve got to be familiar with.</p><p><a href="https://medium.com/pm-crash-course/what-is-a-product-and-product-management-c5581056890f"><em>Previous chapter: </em>What is a Product and Product Management?</a></p><p><a href="https://medium.com/pm-crash-course/product-life-cycle-plc-and-the-four-phases-c46a5261b7a8"><em>Next chapter: </em>Product Life Cycle (PLC) and The Four Phases</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8eb8b69c70c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pm-crash-course/three-types-of-product-managers-8eb8b69c70c">Three Types of Product Managers</a> was originally published in <a href="https://medium.com/pm-crash-course">PM Crash Course</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is a Product and Product Management?]]></title>
            <link>https://medium.com/pm-crash-course/what-is-a-product-and-product-management-c5581056890f?source=rss-ce9e265e6a80------2</link>
            <guid isPermaLink="false">https://medium.com/p/c5581056890f</guid>
            <category><![CDATA[course]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Amit Mutreja]]></dc:creator>
            <pubDate>Sun, 09 Sep 2018 16:07:32 GMT</pubDate>
            <atom:updated>2018-09-09T16:07:32.211Z</atom:updated>
            <content:encoded><![CDATA[<p>There has been a tremendous growth in new-age companies and in the last decade which has also given birth to the new roles in the digital space. The one role which has caught everyone’s eye is Product Management. Furthermore, in a world, where a user has a large number of choices, has low switching cost and is influenced from the public ratings, reviews and recommendations; product managers matter more than ever.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/833/0*l0pMBsYZ9-zlSWB2.jpg" /><figcaption>source: wfglobal.org</figcaption></figure><p>But question is, Who is a Product Manager and what does he do?</p><p>A Product Manager is not a manager of anybody but the product. The Venn diagram below sums up the entire existence of all the Product Managers out there. You are at the intersection of major stakeholders and enable a continuous flow of communication by removing the noise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/568/1*H7kF7FvW46tThcXFIlJDlg.png" /></figure><p>The role of the PMs and the responsibilities change across different industries and different companies. Therefore, let’s focus on the core tenants of it:</p><ol><li><strong>Identifying Profitable Opportunities</strong> — by understanding the market, overseeing the products already in the market and researching into user’s needs</li><li><strong>Defining the Product</strong> — deciding which features to be present in what releases based on market, target users, and impact of each feature on different user groups</li><li><strong>Guiding the development</strong> — by writing requirements, user stories and prioritizing features based on effort and impact</li><li><strong>Scaling the product </strong>— defining Go to Market Strategies, understanding the user interactions, experimenting and focusing on what’s working and leaving out what’s not, deriving and using market insights</li><li><strong>Product Strategy</strong> — Managing road-map as a function of the market, keep product goals aligned with the company’s goals</li></ol><p>In a nutshell, a PM is a researcher, a prioritizer and a presenter but most importantly, responsible for the ultimate success of the product.</p><p><strong>So, what’s a product then?</strong></p><p>A product can be anything. My laptop is a product, my phone is a product, medium.com is a product and the web browser, I am using, is a product. However, it’s not always the case that a product manager is in charge of an entire device or software. In many startups, and especially large companies, product managers are in charge of different sections or features. For example, when you’re using Facebook you are actually using multiple products like photos, news feed, comment section etc. At such large companies, each feature is so vital and complex that it’s usually assigned to a group of people, called a product team, to manage it.</p><p>But there are also situations when product managers are not split up by the features but rather split up by platform. For instance, at a company, each platform (Android, iOS and Website) may have its own in-charge managing everything.</p><p>These are just different models of working. So now, we should be clear that as far as the role of a product manager goes, a product can be anything from an entire real-life product as a consumer sees it, or in some cases split up into smaller sections for larger companies or complex products.</p><p><a href="https://medium.com/pm-crash-course/differences-between-different-types-of-product-managers-8eb8b69c70c"><em>Next Chapter: </em>Differences Between Different Types of Product Managers</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c5581056890f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pm-crash-course/what-is-a-product-and-product-management-c5581056890f">What is a Product and Product Management?</a> was originally published in <a href="https://medium.com/pm-crash-course">PM Crash Course</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How does tech blog help in scaling the team?]]></title>
            <link>https://medium.com/@amitmutrezas/tech-blogs-help-in-scaling-the-team-examples-d3054f3f04c2?source=rss-ce9e265e6a80------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3054f3f04c2</guid>
            <category><![CDATA[recruiting]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[blogging]]></category>
            <category><![CDATA[blog]]></category>
            <dc:creator><![CDATA[Amit Mutreja]]></dc:creator>
            <pubDate>Fri, 16 Mar 2018 19:58:39 GMT</pubDate>
            <atom:updated>2018-04-15T18:56:24.284Z</atom:updated>
            <content:encoded><![CDATA[<p>Good software developers are rare and harder to find. As a small tech startup, you’ll need all the help you can get to attract the best talent.</p><p>To make matters worse, most of the top engineers are not actively looking and they are certainly not scanning the plethora of job descriptions out there. This is why I’m a big fan of engineering blogs as a differentiator for startups.</p><p>How is an engineering blog going to help you with recruiting?</p><p>It’s a very effective and subtle way to attract candidates by showcasing your company’s tech, people, and culture. For instance, it can highlight the technologies being used at the company and the types of technical challenges candidates might help solve.</p><p>Let’s take a look at three strong examples:</p><ol><li><a href="https://codeascraft.com/">Etsy</a></li></ol><p>Etsy is a marketplace for handmade and vintage goods. Doesn’t sound too techno savvy? But wait, dive deep into <a href="http://codeascraft.etsy.com/">Code as Craft</a>, Etsy’s engineering blog.</p><p>You will notice a world full of big data, scaling, MongoDB, and Hadoop. In addition, you’ll notice that Etsy is committed to having its team learn from other experts in the industry via its Etsy Speaker Series.</p><p>Etsy tracks the number of referrals, interviews, and hires that originate in its blog. Although the company doesn’t share specific details, it does say the numbers are significant. It also stresses the importance of having the blog “speak with the voice of the engineering culture behind it”.</p><p>2. <a href="https://medium.com/airbnb-engineering">Airbnb</a></p><p>Personally, I am a big fan of <a href="https://medium.com/airbnb-engineering">Airbnb</a> blogs on Medium. I have learnt a lot from their experiments and results which they have shared. They have blogs for the <a href="https://medium.com/airbnb-design">engineering &amp; data-science</a> team to the <a href="https://medium.com/airbnb-design">design</a> team. They write actively on new frameworks to the side projects and share their learnings with the community.</p><p>Sharing this information with the engineering community is very positive, as this content is very useful for everyone. Remember, as with most things in life — <strong>the more you give, the more you get in return</strong>.</p><p>3. <a href="https://engineering.wayfair.com/">Wayfair</a></p><p>Wayfair is a rapidly-growing e-commerce company in Boston. It launched an <a href="http://engineering.wayfair.com/">engineering blog</a> for a couple of reasons:</p><p>i.) Wayfair executives have learned a lot from other engineering blogs and this was a great way for them to give back.</p><p>ii.) An engineering blog allows them to promote the engineering strength of the company, which in turn helps attract top talent.</p><p>The two biggest barriers for most companies in terms of setting up an engineering blog are time and content. We are all busy with constant demands and deadlines, but it can be worthwhile if your company creates a buzz in the engineering community as a top place to work.</p><p>I recommend you spread out the content creation across multiple team members and assign realistic goals to keep a continuous stream of content. Aim for at least one new post on the blog per week. A blog is only effective if it has fresh material, which keeps people coming back for more. Perhaps switch up the content by posting a video highlighting a recent event at your company or pictures of your team.</p><p>Over time, those followers of your blog just might end up being your next employees.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3054f3f04c2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile Project Management: Scrum on Trello]]></title>
            <link>https://medium.com/@amitmutrezas/agile-project-management-scrum-on-trello-9e7cce78bca0?source=rss-ce9e265e6a80------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e7cce78bca0</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[trello]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[sprint]]></category>
            <dc:creator><![CDATA[Amit Mutreja]]></dc:creator>
            <pubDate>Sun, 05 Mar 2017 10:33:16 GMT</pubDate>
            <atom:updated>2017-03-05T12:41:58.517Z</atom:updated>
            <content:encoded><![CDATA[<p>There are numerous tools available for the project management, but of all of them, Trello has been the choice of many start-ups tracking Agile tasks. It is a powerful tool which is free, adaptive and offers real-time collaboration amongst the team members. But as they say, “with great power comes great responsibilities” is more than true in this case. Trello, having no boundaries regarding how to integrate it into the daily workflow, can also become a complete mayhem.</p><p>Therefore, I want to share the framework I have been following to manage Scrum projects on Trello.</p><p>I recommend creating separate boards for Product Backlog, Active Sprint, Sprint History and Sprint Retrospective. You may also have a separate board the Roadmap of your product or maintain it in an excel sheet.</p><p>Let’s discuss each board one by one.</p><h4><a href="https://trello.com/b/4ht90nUH/roadmap">Roadmap</a></h4><p>A <strong>product roadmap</strong> is a general guideline for the stakeholders describing expected projects/features to be taken in the coming releases.</p><ol><li>It communicates a product’s shared vision, direction, strategy, and goals.</li><li>It keeps everyone in line but doesn’t impose a strict timeline.</li></ol><h4><a href="https://trello.com/b/gmzkT5iC/product-backlog">Product Backlog</a></h4><p>A product backlog is a prioritized list of epics and user-stories for the scrum team that is derived from the roadmap and its requirements. The most important product backlog items or PBIs are shown at the top so the team knows what to deliver first.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/833/1*dO2qoAOQHBTLuWKO4Yiv2Q.png" /><figcaption><a href="https://trello.com/b/gmzkT5iC/product-backlog">Sample product backlog for one or more products</a></figcaption></figure><p>Our board contains separate lists for different products and an aggregated list containing cards in priority order which is the list to be used during a Backlog Refinement meeting.</p><h4><a href="https://trello.com/b/ERbg8EfU/active-sprint">Active Sprint</a></h4><p>In the <strong>Scrum</strong> method of <strong>Agile</strong> software development, work is confined to a regular, repeatable work cycle, known as a <strong>sprint</strong> or iteration. Generally, It is two-weeks long and at the end of it, Scrum team is expected to deliver a “shippable product” containing the user stories committed during the sprint planning meeting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E0zXJa9bXVjB0bh9AlePFQ.png" /><figcaption><a href="https://trello.com/b/ERbg8EfU/active-sprint">Sample Active Sprint Board</a></figcaption></figure><p>The board contains six lists:</p><ol><li><strong>Sprint Backlog:</strong> It is a list of committed PBIs by the team moved from Product Backlog to Active Sprint during the sprint planning meeting. It is allowed to have only tickets/cards describing user stories and acceptance criteria. We, generally, do not tag any team member to a card here.</li><li><strong>ToDo:</strong> The cards which are yet to enter the sprint pipeline but already assigned to a team member. If a developer does not have any card associated with his/her name in ToDo list then (s)he can go to sprint backlog items and pick one from there.</li><li><strong>In Development:</strong> A list of all the tickets which are currently in progress.</li><li><strong>Code review:</strong> A list of all the tickets which are currently under code review.</li><li><strong>Staging (Testing):</strong> A list of the tasks which are ready to test and assigned to a QA.</li><li><strong>Done (DATE <em>from-to</em>):</strong> The sprint start date and end date is mentioned on the list name and the list contains all the tickets which are completed and ready to ship.</li></ol><h4><a href="https://trello.com/b/HXo3m8Tv/sprint-history">Sprint History</a></h4><p>The idea of archiving the completed items is bizarre. Therefore, a history of all the user stories delivered by the team is maintained on a separate board. This board is a stack of all the DONE items in a sprint having the latest at the top. At the end of every sprint, Done list is dumped here.</p><h4><a href="https://trello.com/b/yaszvmhH/sprint-retrospective">Sprint Retrospective</a></h4><p>This board is used during sprint retrospective meeting. You should have lists according to the format of retrospective meetings followed at your organisation. The sample template here has three lists:</p><ol><li>What went well: Describe all the positives.</li><li>What did not go well: Describe all the negatives.</li><li>Actions to take</li></ol><p>Following the above methodology will set you up with project management on Trello. Please refer the sample boards:</p><p><a href="https://trello.com/b/4ht90nUH/roadmap">Roadmap</a>, <a href="https://trello.com/b/ERbg8EfU/active-sprint">Product Backlog</a>, <a href="https://trello.com/b/ERbg8EfU/active-sprint">Active Sprint</a>, <a href="https://trello.com/b/HXo3m8Tv/sprint-history">Sprint History</a>, <a href="https://trello.com/b/yaszvmhH/sprint-retrospective">Sprint Retrospective</a></p><p><em>Since I keep constantly tweaking a little bit with the Trello. I’m curious to know how others are using Trello for Scrum. If you have any thoughts or suggestions please feel free to comment below.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e7cce78bca0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Git: Replace the master branch with a feature branch]]></title>
            <link>https://medium.com/@amitmutrezas/git-replace-the-master-branch-with-a-feature-branch-eb30e984bd5c?source=rss-ce9e265e6a80------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb30e984bd5c</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[git]]></category>
            <dc:creator><![CDATA[Amit Mutreja]]></dc:creator>
            <pubDate>Tue, 27 Dec 2016 11:18:47 GMT</pubDate>
            <atom:updated>2016-12-27T11:18:47.564Z</atom:updated>
            <content:encoded><![CDATA[<p>A product team has to work on different features at a time. The team members may create different branches to push their code so that dependency on others’ code is minimum while developing a feature and merge it later before releasing the feature. It is possible that master branch may become irrelevant in this case and you might want to replace master branch altogether with a feature branch.</p><p>Although there is no way to directly des­ig­nate your cur­rent branch to replace the mas­ter, you can how­ever do this indi­rectly by using a merge strategy.</p><p>If you check­out your feature branch and merge the mas­ter into it with the ‘ours’ strat­egy, it has the effect of absorb­ing the mas­ter into your cur­rent branch but not using any­thing of the mas­ter. This way, when you check­out the mas­ter and do an ordi­nary fast for­ward merge of your fea­ture branch, the merge com­mit will be exactly like your fea­ture branch, effec­tively mak­ing it seems like you replaced the mas­ter with your fea­ture branch.</p><h4>Step by step guide:</h4><p>Checkout to the feature branch</p><pre>git checkout feature_branch</pre><p>Merge with master. If you want your history to be a little clearer, I’d recommend adding some information to the merge commit message to make it clear what you’ve done.</p><pre>git merge -s ours --no-commit master<br>git commit          # add information to the template merge message</pre><p>Checkout to master and do a normal merge with feature branch</p><pre>git checkout master<br>git merge feature_branch #fast-for­ward merge</pre><p>These changes are done only in your local git repository. To push these changes to GitHub do:</p><pre>git push</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb30e984bd5c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>