<?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 Vikash Koushik on Medium]]></title>
        <description><![CDATA[Stories by Vikash Koushik on Medium]]></description>
        <link>https://medium.com/@svikashk?source=rss-831ba2648b14------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ulAWps7qs0kQ8Aq0rZ2sLA.jpeg</url>
            <title>Stories by Vikash Koushik on Medium</title>
            <link>https://medium.com/@svikashk?source=rss-831ba2648b14------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 22:02:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@svikashk/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[13 Git Commands Every Developer Must Know]]></title>
            <link>https://svikashk.medium.com/13-git-commands-every-developer-must-know-3239a1df5e02?source=rss-831ba2648b14------2</link>
            <guid isPermaLink="false">https://medium.com/p/3239a1df5e02</guid>
            <category><![CDATA[git]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[git-commands]]></category>
            <category><![CDATA[basic-git-commands]]></category>
            <dc:creator><![CDATA[Vikash Koushik]]></dc:creator>
            <pubDate>Thu, 01 Oct 2020 14:29:53 GMT</pubDate>
            <atom:updated>2020-10-09T03:49:09.240Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*q1TqiXH-onOTmVre.png" /></figure><p>I can’t begin to tell you how confused I was when I first started learning Git commands.</p><p><em>“I typed </em><em>git commit. Why didn&#39;t my teammate get my changes? Oh, I have to do </em><em>git push as well?!&quot;</em></p><p>I’m sure I can list at least a dozen occasions where I was totally confused with Git commands and what they did.</p><p>That’s why I’m going to share 13 frequently used Git commands in this blog post.</p><p>Of course, there are more commands. But to avoid overwhelming you, we’ll cover just the ones you’ll use frequently.</p><p>Here are 13 Git commands that can speed-up your <a href="https://zepel.io/blog/simple-software-development-workflow/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=13-git-commands">development workflow</a> and allow you to go from a brand new repository to creating a new branch and merging it.</p><p>Let’s jump in and look at each of them in detail.</p><h3>1. Git Init</h3><p>The git init command is usually the first command you’d run in any new project that is not already a Git repository.</p><p>It can be used to convert an existing, un-versioned folder into a Git repository. Also, you can use it to initialize an empty repository.</p><p><strong>Using Git Init Command</strong></p><p>cd into the directory you want to initialize.</p><p>Then, run this command.</p><pre>$ git init</pre><p>This will transform the current directory into a Git repository. A .git sub-directory will be added. This will allow you to start recording multiple versions of your project.</p><p><em>Note: Running</em> git init <em>on an already initialized directory will not override any of your settings.</em></p><h3>2. Git Clone</h3><p>The git clone command is used to download the source code from a remote repository (like GitHub, Bitbucket, or GitLab).</p><p><strong>Using Git Clone Command</strong></p><pre>$ git clone &lt;<a href="https://url-of-the-repository/">https://url-of-the-repository</a>&gt;</pre><p>When you clone a repository, the code is automatically downloaded to your local machine.</p><p>As a convenience, the downloaded version is linked to the origin (the repository from where you downloaded). I say this is a convenience because when you’re collaborating on the same project, you’d want to push your changes (more on that below) to a single repository.</p><p>But sometimes, people wouldn’t want to have this link. If your use case is similar, run</p><pre>$ git remote rm origin</pre><p>This will disassociate the downloaded repository from the origin.</p><h3>3. Git Branch</h3><p>Branch is one of the most important functionalities of Git. This allows teams to work on the same code base in parallel. It enables teams to create <a href="https://zepel.io/blog/5-git-workflows-to-improve-development/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=13-git-commands">Git Workflows</a> and make their workflows more efficient.</p><p>Say, you’re working on “ <em>Feature A</em>”. And your teammate is working on “ <em>Feature B</em> “. By creating a separate branch for each feature, both of you can work on the same code base in parallel without having to worry about conflicts (at least while you’re writing the code).</p><p>You can use this command to create a new branch, view existing branches, or delete a branch.</p><p><strong>Using Git Branch to create a new branch</strong></p><pre>$ git branch &lt;branch-name&gt;</pre><p>This command will create a new branch only in your local system. If you want this to be visible to all the members in the repository, you’ll still have to push the branch.</p><p>To push a newly created branch, run</p><p><strong>Command to view all branches</strong></p><pre>$ git branch</pre><p>or</p><pre>$ git branch --list</pre><p><strong>Git command to delete a branch</strong></p><pre>$ git branch -d &lt;branch-name&gt;</pre><h3>4. Git Checkout</h3><p>A mistake I often made when I first started learning git commands was forgetting to switch to the new branch I just created. Yes, after you create a branch, you’ll have to switch to it with another command. That’s where the Git Checkout command comes in.</p><p><strong>Using Git Checkout Command</strong></p><pre>$ git checkout &lt;branch-name&gt;</pre><p>This will automatically switch you to the branch name you mentioned in the command.</p><p>However, when switching from one branch to another, you need to keep two things in mind:</p><ul><li>If you made some changes in the previous branch, you will have to first commit and push them (I’ll cover this command below) to your remote repository.</li><li>The branch you want to switch must be present in your local system. If not, you can pull them (covered below).</li></ul><p>If you’re as lazy as I am, I’m sure you’d want one single command that will both create a new branch and automatically switch to it.</p><p>The below command does exactly that.</p><pre>$ git checkout -b &lt;branch-name&gt;</pre><h3>5. Git Add</h3><p>Every time you create a new file, delete it, or make a change, you’ll have to tell Git to track it and add it to the staging area. Otherwise, the files you made changes to wouldn’t be added when you try to push your changes.</p><p><strong>Using Git Add Command</strong></p><pre>$ git add &lt;file-name&gt;</pre><p>This command will add only a single file to your next commit. If you want to add all the files to which changes were made, you can use</p><pre>$ git add -A</pre><p>It’s important to remember that using git add will not make any changes in the remote repository. Your changes will be recorded only when you commit them.</p><h3>6. Git Commit</h3><p>Think of Git Commit command like a checkpoint in your development process.</p><p>It’s commonly used to save your changes. Maybe after completing a specific work item assigned to you in your <a href="https://zepel.io/agile-tools/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=13-git-commands">agile tool</a>.</p><p>Every time you commit your code changes, you’ll also include a message to briefly describe the changes you made. This helps other team members quickly understand what was added, changed, or removed.</p><p><strong>Using Git Commit Command</strong></p><pre>$ git commit -a</pre><p>This will commit all the changes in the directory you’re working in. Once this command is run, you’ll be prompted to enter a commit message.</p><p>Alternatively, you can enter the commit message in the command itself and skip the additional step where you’ll be prompted to enter the commit message.</p><p>To do this, run the following git command:</p><pre>$ git commit -am &quot;&lt;commit-message&gt;&quot;</pre><p><em>Note: The git commit command saves the changes only in your local repository. It does not push to the remote origin and make your changes accessible for others to collaborate.</em></p><h3>7. Git Push</h3><p>To make all your committed changes available to your teammates, you’ll have to push them to the remote origin.</p><p><strong>Using Git Push Command</strong></p><pre>$ git push &lt;remote&gt; &lt;branch-name&gt;</pre><p>It’s important to remember that git push command will upload only the changes you’ve committed.</p><h3>8. Git Pull</h3><p>Of course, you’d want to have the latest updates from teammates as well!</p><p>The git pull command allows you to fetch all the changes that your teammates pushed and automatically merge them into your local repository.</p><p><strong>Using Git Pull Command</strong></p><pre>$ git pull &lt;remote&gt;</pre><p>In many cases, you will run into conflict because you had changed a line in a file that another teammate added. In such cases, you need to resolve the conflicts manually.</p><h3>9. Git Diff</h3><p>Git Diff is my go-to command when I want to quickly see the difference between my current branch and another branch (usually the branch I’m merging into).</p><p><strong>Using Git Diff Command</strong></p><pre>$ git diff</pre><p>This will show you any uncommitted changes in your local repository.</p><p><strong>To compare two branches</strong></p><pre>$ git diff branch1..branch2</pre><p>This will show all the file differences between the two branches.</p><p><strong>To compare a file from two branches</strong></p><pre>$ git diff branch1 branch2 ./path/to/file.txt</pre><p>This command will show a comparison of the changes made to file file.txt across the branches branch1 and branch2.</p><h3>10. Git Stash</h3><p>Git Stash temporarily shelves your work, so you can switch to another branch, work on something else, and then come back to this at a later time.</p><p>It’s perfect if you need to work on something else and you’re midway through a code change, but aren’t ready to commit the code.</p><p><strong>Using Git Stash Save Command</strong></p><pre>$ git stash save &quot;&lt;stash-message&gt;&quot;</pre><p>This will stash your changes with the message you entered. This can be helpful when you want to come back and restore your stash, especially when you have several stashes.</p><p>However, this will only stash your tracked files that you added using git add. If you want to include the untracked files as well, run</p><pre>$ git stash save -u</pre><p><strong>Using Git Stash List Command</strong></p><p>When you want to view all the stashed code, you can view them using this command. Once you stash your code, git will assign a stash id, so you can restore a specific stashed code later.</p><p>For example:</p><pre>$ git stash list</pre><p>This might show the following</p><pre>stash@{0}: On master: Stashed with message1 <br>stash@{1}: On master: Stashed with message2</pre><p><strong>Using Git Stash Apply Command</strong></p><p>This will automatically restore and apply the topmost stash in the stack.</p><pre>$ git stash apply</pre><p>If you want to restore a specific stash that you want to apply, using the above example, you can simply run git stash apply stash@{1}.</p><p><em>Note: When you use</em> git stash apply<em>, the stashed version will be applied to your current working branch. However, it will not delete the stash from the stack.</em></p><p><strong>Using Git Stash Pop Command</strong></p><p>To automatically also delete the stash from the stack, the git stash pop command is used.</p><p>If you want to do it for a specific stash in the stack, run git stash pop stash@{0}.</p><h3>11. Git Status</h3><p>When you’re feeling a bit lost with what’s happened in your repository (yes, it can happen) the Git Status command can tell you all the information you’ll need to know.</p><p><strong>Using Git Status Command</strong></p><pre>$ git status</pre><p>This can give you information such as:</p><ul><li>Your current branch</li><li>Whether your current branch is up to date</li><li>If there’s anything in the branch that needs to be committed, pushed, or pulled.</li><li>If you have any files that are either staged or not staged.</li><li>And if you have any files that are created, modified, or deleted.</li></ul><h3>12. Git Log</h3><p>While git status gave you nearly all the information you’d have needed, it wouldn’t give you the information about the commit history for the repository.</p><p>This is where the git log command comes into the picture.</p><p><strong>Using Git Log Command</strong></p><pre>$ git log</pre><p>This displays the entire commit history. If your commit history is large, it’ll show only a portion of it and you can hit <em>[space]</em> to scroll or type <em>q</em> to quit.</p><ul><li>If you want to view only the last 3 commit history, you can use the following command: git log -n 3.</li><li>To condense the commit history into a single line and view them, run git log --oneline. This is the easiest way to get a high level overview of all the commit history. It might still be a bit too much if you&#39;ve got a lot of commits.</li><li>If you want to view the commit history by a specific author, run git log --author&quot;&lt;author-username&gt;&quot;.</li></ul><h3>13. Git Merge</h3><p>Once you’re done with development inside your feature branch and tested your code, you can merge your branch with the parent branch. This could be either a develop branch or a master branch depending on the git workflow you follow.</p><p>When running a git merge command, you first need to be on the specific branch that you want to merge with your feature branch.</p><p>Let’s see how to use the git merge command with an example.</p><p><strong>Using Git Merge Command</strong></p><p>Imagine you’re currently in your feature branch called feature1 and you’re ready to merge it to the develop branch.</p><p><strong>We must first switch to the develop branch using the checkout command</strong>.</p><pre>$ git checkout develop</pre><p><strong>Before merging, you must make sure that you update your local develop branch. </strong>This is important because your teammates might’ve merged into the develop branch while you were working on your feature. We do this by running the pull command.</p><pre>$ git pull</pre><p>If there are no conflicts while pulling the updates, you can finally merge your feature1 branch into the develop branch.</p><p>We do this by using the git merge command followed by the branch name that we want to merge into our current branch.</p><pre>$ git merge feature1</pre><h3>Streamline your Development Workflow</h3><p>These 13 git commands should enable you to go from creating a brand new repository all the way to merging it to the parent branch.</p><p>But as a developer, your work doesn’t stop there.</p><p>One of the things you’ll have to constantly juggle is updating your progress in your project management tool.</p><p>That’s where Zepel goes beyond being just another project management tool and lifts some weight off your shoulders!</p><p>With Zepel, you can automate your progress updates just the way you want. This way, Zepel does all the boring, grunt work of updating progress, while you can spend more of your time on the most important work — writing code and solving problems.</p><p>Here’s how we use it 👇🏼</p><p>While Zepel integrates with <a href="https://zepel.io/guide/integrations/github/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=13-git-commands">GitHub</a>, <a href="https://zepel.io/guide/integrations/bitbucket/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=13-git-commands">Bitbucket</a>, and <a href="https://zepel.io/guide/integrations/gitlab/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=13-git-commands">GitLab</a>, internally we use GitHub.</p><p>Once the integration is enabled, we set the <a href="https://zepel.io/guide/integrations/setup-git-workflow-automation/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=13-git-commands">Git Automation Workflow</a> to define how the statuses should update whenever developers commit, push, or merge.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MUIH4CoJcY44-kaKu2dSZQ.png" /><figcaption>Git Workflow Automation in Zepel</figcaption></figure><p>As developers make progress, Zepel automatically pulls in this information so product and engineering managers don’t just see that a work item was moved from “ <em>In Progress</em>” to “ <em>Review</em> “, but they can also see what triggered this progress.</p><p>And with the help of <a href="https://zepel.io/guide/integrations/link-with-slack/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=13-git-commands">Slack integration</a>, we automatically send the most pressing updates to the respective channel in real-time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HWreU_IbAL0wLbA8aQrmmA.png" /><figcaption>Automating developer workflow with Zepel</figcaption></figure><p>If you’re looking to streamline your development workflow, go ahead, give <a href="https://zepel.io/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=13-git-commands">Zepel</a> a shot.</p><p><em>Originally published at </em><a href="https://zepel.io/blog/13-git-commands/"><em>https://zepel.io</em></a><em> on October 1, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3239a1df5e02" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[9 Best Scrum Software Tools of 2020]]></title>
            <link>https://svikashk.medium.com/9-best-scrum-software-tools-of-2020-f0cca3bf9d34?source=rss-831ba2648b14------2</link>
            <guid isPermaLink="false">https://medium.com/p/f0cca3bf9d34</guid>
            <category><![CDATA[agile-scrum-methodology]]></category>
            <category><![CDATA[scrum-tool]]></category>
            <category><![CDATA[agile-scrum-tools]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Vikash Koushik]]></dc:creator>
            <pubDate>Wed, 24 Jun 2020 06:48:00 GMT</pubDate>
            <atom:updated>2020-12-02T10:08:24.977Z</atom:updated>
            <content:encoded><![CDATA[<p>There is no shortage of scrum software tools today. And it’s becoming a nightmare for teams to pick a tool that’d suit their needs.</p><p>Scrum methodology, after all, has gained tremendous popularity over the last decade. And for good reasons too!</p><p>Scrum, an agile framework, is used primarily for software development with the goal of delivering new, usable, and valuable software to customers quicker.</p><p>Fortunately, I spent the last several months signing up and trying new scrum software tools. And this blog post should help you pick a scrum software tool for your team.</p><p>I’ll walk you through the 9 scrum software tools in the market that can help teams to get work done. I’ll share in-depth about what capabilities they provide, why they’re a better choice than the others, and of course, their pricing. This will allow you to take an informed decision on which scrum tool you can use within your organization.</p><p><em>If you’re new to Scrum, you might be interested in this in-depth </em><a href="https://zepel.io/agile/scrum/?utm_source=zepelblog&amp;utm_medium=text&amp;utm_campaign=scrum-software-tools"><em>guide to Scrum Software Development</em></a><em>.</em></p><h3>Best Scrum Tool Selection Criteria</h3><p>The scrum software tools available in the industry come with different features that allow you to plan, execute, and ship software. But there isn’t a single tool that can act as a gold standard and is perfect in every aspect.</p><p>In our experience, the best scrum tools:</p><ul><li><strong>Enable you to run Sprints:</strong> This is of course is an obvious requirement. But you’d be surprised at how many scrum tools are out there without even a dedicated view for you to run your sprint.</li><li><strong>Keeps the customers at the centre:</strong> Customer feedback and requests should be at the centre of your software development. While it is the product owner’s duty to manage feedback and prioritize, it shouldn’t be a pain to collect these feedback and bring them together from your helpdesk software, live chat app, error monitor tools, and other channels your customers use to communicate with you.</li><li><strong>Promotes transparency &amp; helps gain visibility of the progress:</strong> The best scrum tools helps you track at the micro level and at the macro level without any chaos.</li><li><strong>Developer-friendly:</strong> At the end of the day, it’s the developers who are going to update progress. If they aren’t happy with the tool and don’t update progress, knowing who’s doing what and when the feature will ship will become nearly impossible.</li></ul><p>With this being said, let’s jump in and look at the top 9 scrum software tools you should consider for your organization.</p><h3>1. Zepel</h3><p><a href="https://zepel.io/solutions/scrum/?utm_source=medium&amp;utm_medium=heading&amp;utm_campaign=scrum-software-tools">Zepel</a> is the simplest project management tool that is built for product teams.</p><p>Zepel allows you to collect customer requests from multiple tools, turn them into priorities, and track its development progress every step of the way.</p><p>It shows you a snapshot of the work at every level. With Progress, you can simply drag-drop cards to prioritize features, visually track progress of the feature, and use it as a roadmap to align your entire team on a common goal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KVr-gX8PajQ6E8K8.png" /></figure><p>Once you’ve prioritized your feature, Zepel lets you quickly plan features you’re working on with a simple document-like interface. It lets you add user stories, tasks, subtasks, enhancements, and bugs. Of course, you can add estimation points, assign to users, add comments, files, and descriptions too!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EqDB1ZlA42Y_UCBZ.png" /></figure><p>Zepel gives you a dedicated Sprint view, where you can view your Sprint Backlog and get a detailed scrum report in real-time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zQHyZe8DtuuBfEME.png" /></figure><p>Zepel is simple enough to support Scrum and Kanban. That means, you can track your sprint with a <a href="https://zepel.io/features/scrum-board/">scrum board</a> or simply follow Kanban methodology to track your team’s progress.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oj9flET_QX_FqRo9.png" /></figure><p>Since Zepel is built for software product teams, it recognizes the importance of a developer’s productivity and integrates fully with version control systems like GitHub, Bitbucket, and GitLab. This allows developers to link to pull requests, branch, commits, and automate Zepel to update progress based on their Git workflow.</p><p><strong>Top scrum features in Zepel:</strong></p><ol><li>Simple document-like interface to plan features with User Stories, Bugs, Tasks, Subtasks, and Enhancements.</li><li>Dedicated view for Sprints</li><li>Allows you to add scrum boards</li><li>Burnup, burndown, and cumulative charts</li><li>Desktop Widget to track Sprints from your desktop</li><li>Deep integrations with version control systems like GitHub, Bitbucket, and GitLab.</li><li>Developer friendly APIs</li></ol><p><strong>Pricing:</strong></p><ul><li>Free — For 5 members. No feature restrictions</li><li>Standard plan — From 6th member starts at $5/member.</li></ul><figure><a href="https://zepel.io/solutions/scrum/?utm_source=medium&amp;utm_medium=mid-image&amp;utm_campaign=scrum-software-tools"><img alt="Try Zepel Scrum Software" src="https://cdn-images-1.medium.com/max/1024/1*5u9WgNIeS551ypER39fMDQ.png" /></a></figure><h3>2. <a href="https://trello.com/">Trello</a></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wOZXqqywfD2_ThcM.png" /></figure><p>There probably isn’t a single best-of-project-management-tools article that doesn’t include Trello in it.</p><p>Thanks to its simplicity, nearly everyone who has looked for project management tools has heard about Trello. You can create any number of Boards in Trello and use each Board to plan and track just about anything from a roadmap, simple task list, sprints, to even something as generic as a wedding. You can create a card, categorize it, add comments, set due dates and owners.</p><p>If this is all the functionality you’re looking for, then Trello is great. You can use power-ups, their integrations, if you want more functionalities. Capabilities like scrum reports are not available as a first-class feature, which is why several teams look for a Trello alternative as they scale.</p><p><strong>Top scrum features in Trello:</strong></p><ol><li>Simple Kanban Boards that can be used to plan and track sprints</li><li>Ease of use</li><li>Power-ups to integrate with other tools</li></ol><p><strong>Pricing:</strong></p><ul><li>Basic: Free forever</li><li>Business Class: $9.99/user/month</li><li>Enterprise: $20.83/user/month</li></ul><p>Is Trello not powerful enough to meet your needs? You might want to have a look at these <a href="https://zepel.io/blog/trello-alternatives/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=scrum-software-tools">11 Trello alternatives</a> that are simple yet more powerful than Trello.</p><h3>3. <a href="https://www.atlassian.com/software/jira/">JIRA</a></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PDW6R1Mg5t9PK3um.png" /></figure><p>JIRA is the go-to scrum software tool for bigger teams. JIRA is marketed as the agile tool in the industry and provides nearly every agile capability you can think of.</p><p>But this is also one of the main reasons why several teams are moving away from JIRA. Due to its steep learning curve, slowness, and clutter, it can be hard to get started with JIRA if you haven’t already used it previously.</p><p>JIRA has an extensive list of integrations that you can use for your projects — over 3000 when I checked. You can use these integrations to track time, connect to external tools and more.</p><p><strong>Top scrum features in JIRA:</strong></p><ol><li>Backlog</li><li>Scrum Board</li><li>Scrum analytics</li><li>Integrations</li></ol><p><strong>Pricing:</strong></p><ul><li>Free for up to 10 users with feature restriction</li><li>Standard plan from $7/member</li></ul><p>Not a fan of JIRA? Here are <a href="https://zepel.io/blog/jira-alternative/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=scrum-software-tools">9 JIRA alternatives</a> that are as powerful without the clutter.</p><h3>4. <a href="https://www.zoho.com/sprints/">Zoho Sprints</a></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7dcScEFNhs9yDGsK.png" /></figure><p>Zoho Sprints is project management software catered to teams who run Sprints.</p><p>Since it focusses only on the Sprints aspect of working, you’ll have a Backlog to collect all your work to plan your next sprint, Epics to group and structure your all tasks, and a Board to customize statuses.</p><p>Unlike other scrum tools, Zoho Sprints allows you to even schedule meetings and send invites with location and duration. This is great when you want to run Scrum Meetings. With reports such as burndown, burnup, and cumulative, backed by logged times that you can manually enter, Zoho Sprints allows you to see how your team is progressing.</p><p><strong>Scrum features in Zoho:</strong></p><ol><li>Sprints</li><li>Integrations</li><li>Epics</li></ol><p><strong>Pricing:</strong></p><ul><li>Free for 5 users and 5 projects</li><li>Standard plan at $10 per month per user</li></ul><h3>5. <a href="https://yodiz.com/">Yodiz</a></h3><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*b31hiO4ynbDLRrXWEFF4aQ.png" /></figure><p>Yodiz is a project management tool that is easy to get started with. It supports both Kanban and Scrum methodologies.</p><p>One of the best functionalities of Yodiz is its capability to take any raw data and turn it into charts that you can use to see if you’re team is blocked and need help.</p><p>This tool also provides you the capability to add time estimates, add multiple columns to track work, and add priorities. And if you’re an NGO or a non-profit organization, Yodiz is for free.</p><p><strong>Scrum features in Yodiz:</strong></p><ol><li>Backlog</li><li>Estimations</li><li>Prioritizations</li></ol><p><strong>Pricing:</strong></p><ul><li>Free for 3 users</li><li>Issue Tracker: $3/user/month</li><li>Agile Tool: $5/user/month</li></ul><h3>6. <a href="https://sprint.ly/">Sprintly</a></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/905/0*i3XxMYn3suOyWfDO.png" /></figure><p>Sprintly is a project management tool for scrum teams and lets you run sprints. It makes it effortless for startups and agencies to work together and collaborate by giving them a full view of what the team is working on.</p><p>It integrates well with Github and allows your development team to automatically update their work from Github. For other integrations, if you need them, it relies on Zapier.</p><p>Sprintly offers an advanced search syntax with a nice type-ahead UI. If you prefer using the mouse, they have a point-and-click search filters that makes finding tickets a breeze.</p><p>One of Sprintly’s biggest drawback according to some reviews on the internet is there are no due dates or a dedicated view for sprints or scrum board. It also tends to get slow and hamper the team’s productivity.</p><p><strong>Scrum features in Sprintly:</strong></p><ol><li>Backlog</li><li>Scrum Reports</li><li>Github Integrations</li></ol><p><strong>Pricing:</strong></p><ul><li>$19 per month to $399 per month</li></ul><h3>7. <a href="https://www.ntaskmanager.com/">nTask</a></h3><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*b31hiO4ynbDLRrXWEFF4aQ.png" /></figure><p>nTask is primarily a project management tool that provides a set of features that will make Scrum implementation easy for you. It comes with capabilities such as Gantt charts and time sheets that can be useful for tracking progress and deciding the next steps.</p><p>Similar to Zoho Sprints, nTask also comes with advanced meeting participant controls that can be used to schedule and productively execute your daily scrum meetings without any fear of losing productivity along the way.</p><p><strong>Scrum features in nTask:</strong></p><ol><li>Kanban Board to track tasks</li><li>Meeting management capabilities to manage scrum meetings</li><li>Time estimation</li></ol><p><strong>Pricing:</strong></p><ul><li>Free with a limit of 100 MB storage</li><li>Premium starts at $2.99/user/month</li><li>Business starts at $7.99/user/month</li></ul><h3>8. <a href="https://www.collab.net/products/versionone">VersionOne</a></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/749/0*pOyJITtTnefxeSwQ.png" /></figure><p>VersionOne is an agile project management tool that’s packed with features and flexible. It supports Kanban, Scrum, a hybrid of the two, and even SAFe. This allows companies to scale quicker and efficiently.</p><p>VersionOne allows you to plan your portfolio and program level initiatives and track them It provides an end-to-end capability for you to gain visibility of your project’s performance and gives you reports to take data-driven decisions.</p><p><strong>Scrum features in VersionOne:</strong></p><ol><li>Sprint Planning</li><li>Scrum Reports &amp; Analytics</li><li>Story, defect, and test tracking</li><li>Release planning</li></ol><p><strong>Pricing:</strong></p><ul><li>Free with limited capabilities</li><li>Other plans requires you to contact the team for a quote</li></ul><h3>9. <a href="https://www.vivifyscrum.com/">VivifyScrum</a></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*HF5NuH7DO_L-OGM_.png" /></figure><p>VivifyScrum lets you manage your projects and supports kanban and scrum methodologies.</p><p>It provides basic collaboration capabilities such as assigning, giving roles to team members, and more. One of its better features is where projects can be linked to relevant collaboration boards from which team members can track their work.</p><p>As a part of scrum features, it provides you with a product backlog, lets you have multiple sprints active, have a goal for a sprint, and view its progress as a report.</p><p><strong>Scrum features in VivifyScrum:</strong></p><ol><li>Product Backlog</li><li>Multiple Sprints</li><li>Sprint Goal</li><li>Burndown charts</li><li>Stats per user</li><li>Planning poker to estimate user stories</li></ol><p><strong>Pricing:</strong></p><ul><li>Premium starts at $10/user/month</li><li>Enterprise plan requires you to contact the team for a quote</li></ul><h3>Further Helpful Articles When Considering Scrum Software Tools</h3><ul><li><a href="https://zepel.io/agile-tools/">4 Best Agile Tools for Software Development in 2020</a></li><li><a href="https://zepel.io/blog/jira-alternative/">9 Best JIRA Alternatives To Try In 2020 For Agile Software Teams</a></li><li><a href="https://zepel.io/blog/switching-project-management-tools/">5 questions to ask when switching to a new project management tool</a></li></ul><figure><a href="https://zepel.io/solutions/scrum/?utm_source=medium&amp;utm_medium=bottom-cta&amp;utm_campaign=scrum-software-tools"><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jB_i3Gz43oGr8suV.png" /></a></figure><p><em>Originally published at </em><a href="https://zepel.io/blog/scrum-tools/"><em>https://zepel.io</em></a><em> on June 24, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f0cca3bf9d34" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Git Workflows you can use to deliver better code]]></title>
            <link>https://svikashk.medium.com/5-git-workflows-you-can-use-to-deliver-better-code-9b8c84e0135f?source=rss-831ba2648b14------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b8c84e0135f</guid>
            <category><![CDATA[workflow]]></category>
            <category><![CDATA[gitlab]]></category>
            <category><![CDATA[git-workflow]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Vikash Koushik]]></dc:creator>
            <pubDate>Wed, 27 May 2020 13:15:54 GMT</pubDate>
            <atom:updated>2020-06-09T08:46:09.259Z</atom:updated>
            <content:encoded><![CDATA[<p>I haven’t met a developer who looked at a conflict message and did not pull their hair strands with frustration.</p><p>Trying to resolve each merge conflict is one of those things that every developer hates. Especially if it hits you when you’re gearing up for a production deploy!</p><p>This is where having the right Git workflow set up can do a world of good for your <a href="https://zepel.io/blog/simple-software-development-workflow/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=git-workflow">development workflow</a>.</p><p>Of course, having the right git workflow will not solve all your problems. But it’s a step in the right direction. After all, with every team working remotely, the need to build features together without having your codebase getting disrupted is critical.</p><p>How you set it up depends on the project you’re working on, the release schedules your team has, the size of the team, and more!</p><p>In this article, we’ll walk you through 5 different git workflows, their benefits, their cons, and when you should use them. Let’s jump in!</p><h3>1. Basic Git Workflow</h3><p>The most basic git workflow is the one where there is only one branch — the master branch. Developers commit directly into it and use it to deploy to the staging and production environment.</p><figure><img alt="Basic git workflow" src="https://cdn-images-1.medium.com/max/1024/1*otT50CH1Y4ehSuJQuIHNQw.png" /></figure><p>This workflow isn’t usually recommended unless you’re working on a side project and you’re looking to get started quickly.</p><p>Since there is only one branch, there really is no process over here. This makes it effortless to get started with Git. However, some cons you need to keep in mind when using this workflow are:</p><ol><li>Collaborating on code will lead to multiple conflicts.</li><li>Chances of shipping buggy software to production is higher.</li><li>Maintaining clean code is harder.</li></ol><h3>2. Git Feature Branch Workflow</h3><p>The Git Feature Branch workflow becomes a must have when you have more than one developer working on the same codebase.</p><p>Imagine you have one developer who is working on a new feature. And another developer working on a second feature. Now, if both the developers work from the same branch and add commits to them, it would make the codebase a huge mess with plenty of conflicts.</p><figure><img alt="git workflow with feature branch" src="https://cdn-images-1.medium.com/max/1024/1*zb5uMFkdE3K5nHnolAaytQ.png" /></figure><p>To avoid this, the two developers can create two separate branches from the master branch and work on their features individually. When they’re done with their feature, they can then merge their respective branch to the master branch, and deploy without having to wait for the second feature to be completed.</p><p>The Pros of using this workflow is, the git feature branch workflow allows you to collaborate on code without having to worry about code conflicts.</p><h3>3. Git Feature Workflow with Develop Branch</h3><p>This workflow is one of the more popular workflows among developer teams. It’s similar to the Git Feature Branch workflow with a develop branch that is added in parallel to the master branch.</p><p>In this workflow, the master branch always reflects a production-ready state. Whenever the team wants to deploy to production they deploy it from the master branch.</p><figure><img alt="git workflow with develop and feature branch" src="https://cdn-images-1.medium.com/max/1024/1*eEYmh3IaRX6Fotb0bKldHg.png" /></figure><p>The develop branch reflects the state with the latest delivered development changes for the next release. Developers create branches from the develop branch and work on new features. Once the feature is ready, it is tested, merged with develop branch, tested with the develop branch’s code in case there was a prior merge, and then merged with master.</p><p>The advantage of this workflow is, it allows teams to consistently merge new features, test them in staging, and deploy to production. While maintaining code is easier, it can get a little tiresome for some teams since it can feel like going through a tedious process.</p><h3>4. Gitflow Workflow</h3><p>The gitflow workflow is very similar to the previous workflow we discussed combined with two other branches — the release branch and the hot-fix branch.</p><h3>The hot-fix branch</h3><p>The hot-fix branch is the only branch that is created from the master branch and directly merged to the master branch instead of the develop branch. It is used only when you have to quickly patch a production issue. An advantage of this branch is, it allows you to quickly deploy a production issue without disrupting others’ workflow or without having to wait for the next release cycle.</p><p>Once the fix is merged into the master branch and deployed, it should be merged into both develop and the current release branch. This is done to ensure that anyone who forks off develop to create a new feature branch has the latest code.</p><h3>The release branch</h3><p>The release branch is forked off of develop branch after the develop branch has all the features planned for the release merged into it successfully.</p><p>No code related to new features is added into the release branch. Only code that relates the release is added to the release branch. For example, documentation, bug fixes, and other tasks related to this release are added to this branch.</p><p>Once this branch is merged with master and deployed to production, it’s also merged back into the develop branch, so that when a new feature is forked off of develop, it has the latest code.</p><figure><img alt="gitflow git workflow" src="https://cdn-images-1.medium.com/max/1024/1*AXbAL5H9KvDbBycrvHWqFA.png" /></figure><p>This workflow was first published and made popular by <a href="http://nvie.com/posts/a-successful-git-branching-model/">Vincent Driessen</a> and since then it has been widely used by organizations that have a scheduled release cycle.</p><p>Since the git-flow is a wrapper around Git, you can install git-flow in your current repository. It’s a straightforward process and it doesn’t change anything in your repository other than creating branches for you.</p><p>To install on a Mac machine, execute brew install git-flow in your terminal.</p><p>To install on a Windows machine, you’ll need to <a href="https://git-scm.com/download/win">download and install the git-flow</a>. After the installation is done, run git flow init to use it in your project.</p><h3>5. Git Fork Workflow</h3><p>The Fork workflow is popular among teams who use open-source software.</p><p>The flow usually looks like this:</p><ol><li>The developer forks the open-source software’s official repository. A copy of this repository is created in their account.</li><li>The developer then clones the repository from their account to their local system.</li><li>A remote path for the official repository is added to the repository that is cloned to the local system.</li><li>The developer creates a new feature branch is created in their local system, makes changes, and commits them.</li><li>These changes along with the branch are pushed to the developer’s copy of the repository on their account.</li><li>A pull request from the branch is opened to the official repository.</li><li>The official repository’s manager checks the changes and approves the changes to get merged into the official repository.</li></ol><h3>Automating your Git Workflows for better productivity</h3><p>One of the things that developers have to constantly juggle with is updating their <a href="https://zepel.io/blog/scrum-tools/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=git-workflow">scrum tool</a> to keep their teammates updated. That’s why, at Zepel, our developers automate their workflow, so they can spend more of their time building the software.</p><p>Here’s how we automate our git workflow to keep everyone in sync:</p><p>While Zepel integrates deeply with <a href="https://zepel.io/guide/integrations/github/">GitHub</a>, <a href="https://zepel.io/guide/integrations/bitbucket/">Bitbucket</a>, and <a href="https://zepel.io/guide/integrations/gitlab/">GitLab</a>, we use GitHub internally. So, once we’ve integrated GitHub with Zepel, our development team sets up the git workflow automation within Zepel. Here’s how it looks today:</p><p>As developers continue to make progress, our team automatically gets a Slack notification and their changes are recorded within the user story.</p><h3>Your own workflow!</h3><p>The git workflows I’ve shown in this article are examples of some of the popular and best working workflows for the development team. Some teams create a branch for Staging and it works perfectly for them.</p><p>If you use other workflows that work well for you, tweet to us <a href="https://twitter.com/@getzepel">@getzepel</a>. We’d love to showcase them!</p><figure><a href="https://zepel.io/?utm_source=medium&amp;utm_medium=bottom-cta&amp;utm_campaign=git-workflow"><img alt="call to action button to improve development process with zepel" src="https://cdn-images-1.medium.com/max/1024/0*EChCUyIPb1yBK2aR.png" /></a></figure><p><em>Originally published at </em><a href="https://zepel.io/blog/5-git-workflows-to-improve-development/"><em>https://zepel.io</em></a><em> on May 27, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b8c84e0135f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I purchased a bag of protein powder. And boy, was I in for a surprise!]]></title>
            <link>https://svikashk.medium.com/i-purchased-a-bag-of-protein-powder-and-boy-was-i-in-for-a-surprise-bb26f466b948?source=rss-831ba2648b14------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb26f466b948</guid>
            <category><![CDATA[comedy]]></category>
            <category><![CDATA[humor]]></category>
            <category><![CDATA[short-story]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[funny]]></category>
            <dc:creator><![CDATA[Vikash Koushik]]></dc:creator>
            <pubDate>Sat, 18 Apr 2020 13:20:10 GMT</pubDate>
            <atom:updated>2021-04-27T11:51:46.302Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/317/1*VPboaIDN6RPsJ4sZLIUCEA.jpeg" /></figure><p>So there I was, looking at this bag of protein powder.</p><p>The packaging looked great. Had sufficient amount of protein content per scoop. And it had less than 1 gram of carbohydrates and 0 sugar!</p><p>What more do you want from a bag of protein powder?!</p><p>So I went ahead, swiped my card, and purchased it. It was going to make me strong and muscular, I thought.</p><p>I went home, opened it, took a scoop full it, and put it in my shaker. Before the powder hit the bottom of the shaker, I knew my worst fears were coming to life.</p><p>Here was a scoop of protein powder so bad that I bet the manufactures went to the nearest stone quarry and shovelled rocks into it so I can see what I’m putting into my body.</p><p>You see, when you drink protein powder, you expect certain things. Like fine texture, essential amino acids, and taste… You want to feel reassured you’ll look like Dwayne “The Rock” Johnson. You imagine the muscularity, the strength, and the confidence running through every fibre of your body, even while wearing a double XL t-shirt.</p><p>Of course, I lowered my expectations on this a bit more. After all, I just purchased this from the nearby medical store that barely had people walking in even before the lockdown.</p><p>Now, of course, it would be just rambling if I didn’t walk you through what specifically wasn’t great about this specific product. So, let’s talk specifics.</p><p>First, let’s talk about the taste. It tastes like tonic that was mixed with 4 different powdered tablets and dosa batter. And you feel this ugly taste and texture all the way till it reaches the bottom of your stomach.</p><p>Then, there’s the texture and how well it mixes with water or milk. In my experience, most powders mix well with water after a minute of shaking. Some require you to go on for a little longer. This specific product required me to learn cocktail shaking techniques and still ended up looking like a lump of sand had been thrown into my shake.</p><p>Next, you have its appearance. You see, food, like many things in life, needs to be dressed up if you want someone to appreciate it in first sight. But this particular dish, even if it was only a shake, was nothing but a gooey substance that’d ooze out of a 3-headed monster’s mouth when it has its prey right where it wants them to be. In a scale ranging from “Maruthi 800” and a “Porsche”, the appearance of this shake would be the equivalent of an abandoned car in your street end with only three wheels, engine missing, and the seat cushion removed. Practically speaking, it’s the equivalent of metal scrap.</p><p><a href="https://www.myprotein.co.in/sports-nutrition/pea-protein-isolate/11654740.html?affil=thggpsad&amp;switchcurrency=INR&amp;shippingcountry=IN&amp;variation=11654742&amp;thg_ppc_campaign=71700000049699151&amp;product_id=11654742&amp;gclsrc=ds">This bag of protein powder</a> is perfect if you are looking for a reason to punish yourself with guilt and shame.</p><p>If you’re like me and just want a protein powder that isn’t made with sand, plastic, and serve their purpose, I’d suggest you look for them from another brand.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb26f466b948" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 steps to master sprint planning.]]></title>
            <link>https://svikashk.medium.com/5-steps-to-master-sprint-planning-template-included-for-free-97936eb5580e?source=rss-831ba2648b14------2</link>
            <guid isPermaLink="false">https://medium.com/p/97936eb5580e</guid>
            <category><![CDATA[sprint-planning]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[sprint-planning-template]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[sprint]]></category>
            <dc:creator><![CDATA[Vikash Koushik]]></dc:creator>
            <pubDate>Tue, 24 Mar 2020 09:52:19 GMT</pubDate>
            <atom:updated>2020-04-03T12:40:54.889Z</atom:updated>
            <content:encoded><![CDATA[<p>Few things are as crucial as running a well-executed sprint planning meeting.</p><p>Get it right and you’ll be on your way to shipping quality software. Get it wrong, and it’ll snowball into a giant mess.</p><p>In product development, the definition of success is vague. Inefficiencies are invisible. But failures are apparent.</p><p><strong>Development workflows in businesses are ridden with inefficiencies due to misalignment of teams, tools, and processes.</strong> And running an effective sprint planning meeting can be your first step to streamlining your development process.</p><p>But more than that, a <a href="https://zepel.io/agile/scrum/sprint-planning/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=sprint-planning-template">sprint planning meeting</a> is critical because it aligns the development team with the product owner. Much like all relationships, the one between you and your team requires communication and clarity.</p><p>And what better way to take the time to sit down and ensure the expectations are understood and can be done by your team?</p><p>This article will walk you through 5 steps you can follow every time you run a sprint planning meeting. It’s the only template you’ll ever need.</p><h3>Step 1: Mind the roadmap</h3><p>The best way to make sure your sprint is successful is by not thinking only about your sprint, but about your product as a whole!</p><p>This, of course, is easier said than done. As a product manager, you’re tasked with keeping track of the micro-level changes that your team makes (think tasks and user stories) and connecting it with the macro-level goals you need to accomplish (think, product roadmap and vision).</p><p><strong>How do you zoom in, zoom out, and make sense of all the updates from design, development, and QA teams? How do you do it when all their work is split between sticky notes, simple task lists, and inside GitHub?</strong></p><p>The key is to ask yourself some serious questions:</p><ul><li>Is your roadmap of features derived from a product strategy that moves the needle?</li><li>Are you reacting to loud customers? Or are you prioritizing the right features?</li><li>As your team completes multiple sprints, how is it affecting your entire roadmap?</li></ul><p>There are always too many features you can build. But as a product manager, it’s <a href="https://www.mindtheproduct.com/a-product-managers-guide-to-saying-no/">your job to say no</a>. If you want to build a product that stands out, you’ll have to make sure what your team is building today will take your product to where you want to be at the end of this quarter, 6 months, or a year later.</p><p>Zepel offers a unique way for you to plan your roadmap and keep track of its progress effortlessly, even as members from multiple teams make changes and progress.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MwKUm_PcrJDtmTLf7-Pvjw.png" /><figcaption>Get a quick overview of the roadmap and track its progress</figcaption></figure><h3>Step 2: Have an updated list of user stories before the sprint planning meeting</h3><p>In a perfect, simple world, your team can pick up the user stories you wrote a month ago and start working on them immediately. In reality, that’s rarely the case.</p><p>Since the last time you wrote the user stories, your customers would’ve asked for several functionalities to be added to your feature and their usage within your product would’ve changed. You’ll have to factor in all these variables and changes into your user stories and ensure they are updated before you walk into the sprint planning meeting.</p><p>Now, the question most teams have is “ <em>how many user stories should you update?</em> “ The ideal case is to have all of them updated. But in reality, that’s an impossible task unless your product is relatively new and small.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wXhKEcFWWHe_AB6f8HchYg.png" /><figcaption>A list of user stories along with bugs, enhancements, and subtasks</figcaption></figure><p>The best practice is to have enough user stories updated to plan the next two sprints. That way, you’ll have the context of what the sprint is building towards — ideally, towards hitting the roadmap goals you reviewed in the previous step.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PHIVeYaTuvNIq5yNK2Ph6Q.png" /><figcaption>An updated user story with description, linked commits and branches.</figcaption></figure><p>If you’re using <a href="https://zepel.io/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=sprint-planning-template">Zepel</a>, you can quickly add more details to your user story by adding detailed <a href="https://zepel.io/agile/user-stories/acceptance-criteria/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=sprint-planning-template">acceptance criteria</a>, attachments, and comments. That way, when you bring your teammates, everyone has the full picture of what each user story tries to achieve and everyone is on the same page.</p><h3>Step 3: Estimate user stories and tasks</h3><p>Now that you’ve updated your user stories, it’s time to bring in your development team and estimate how long it would take to complete each of these user stories you updated. Estimating accurately is one of the hardest things to do.</p><p>Of course, not every user story will be hard to estimate. We’ve noticed things we have experience with are much easier to estimate. A huge reason for this is the fact that our team is already equipped with the working knowledge and the intricacies involved in building it.</p><p>When working on things we don’t have previous experience with, we make sure we break the user story down into subtasks and estimate each of those subtasks. Once we break the user story down, we take a step back and look at all the tasks. Often, we notice there are a bunch of work that we can start working on immediately, few that look vague, and a couple that look as mysterious as the dark side of the moon.</p><p>We group each of them into three categories — known, partially known, and unknown — and work our way to finding more information about them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/592/0*yb9WXfXv8OuaR9tb.png" /></figure><blockquote><em>When you haven’t thought about what you’re going to do, you can’t know how long it will take.<br>~ Joel Spolsky, CEO of Stack Overflow</em></blockquote><p>We’ve written a beginner’s guide to estimate a user story with story points <a href="https://zepel.io/agile/scrum/story-points/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=sprint-planning-template">over here</a>. And shared some best practices you should follow <a href="https://zepel.io/blog/project-estimation/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=sprint-planning-template">over here</a>.</p><h3>Step 4: Come up with a clear sprint goal</h3><p>With all user stories updated and estimated, as a product manager everything should slowly start to make sense like an M. Night Shyamalan movie.</p><p>While you might have an initial objective in mind for the sprint, coming up with a sprint goal is a collaborative effort. A sprint goal, simply put, is what you would’ve delivered at the end of the sprint. They’re a great way to get your team to rally around a common goal and keep them motivated.</p><p>An example of a sprint goal may look like this: “ <em>Develop the checkout process for the store</em> “.</p><p>But before you even begin discussing what the goal of the sprint should be, make sure that you’re setting the right expectations for the sprint depending on the sprint duration. That means, understanding your team’s capability, factoring in unforeseen delays, and setting aside some time for bug fixes, code reviews, and optimizations.</p><p>As we get deeper into running a sprint planning meeting you need to remember:</p><blockquote><em>Your sprint goal intersects with your customer’s problem at a specific touchpoint. The software you deliver at this intersection is another opportunity to “wow” them and gain their loyalty.</em></blockquote><h3>Step 5: Collaboratively plan a sprint backlog</h3><p>With a sprint goal in place, it’s time to talk about “how” you’re going to achieve it.</p><p>This is a collection of multiple user stories you updated and estimated in the previous steps. The difficulty is identifying a list of user stories, tasks, and bugs that will help you achieve the goal and can be completed within the sprint duration.</p><p>It’s essential the team collectively selects the sprint items and size of the sprint backlog. Since they’re the people committing to completing the items, they must also be the ones to choose what they are committing to.</p><blockquote><em>When you involve your team in the sprint planning process, you don’t have to run behind them every other day asking for updates. Because they’re motivated by a far greater power — extreme ownership.</em></blockquote><p>Of course, once your sprint backlog is finalized, make sure you assign, set due dates, and share all the assets your team needs to do their best work.</p><h3>Key points to remember during the sprint planning meeting</h3><ol><li>The sprint planning meeting is a collaborative effort.</li><li>According to scrum guide, the sprint planning meeting should be time boxed to 8 hours for a sprint that’s 1 month long.</li><li>As a product manager, be sure to discuss and specify acceptance criteria for each user story.</li></ol><h3>Get the Sprint planning template: So you can streamline the entire process!</h3><p>Here’s a sprint planning template you can use that uses all the best practices we discussed above.</p><p>A sprint planning template should enable teams to get a quick overview of what’s planned for the upcoming sprint along with its details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Is1b32F5G57T5X4nrnsq8g.png" /><figcaption>A template of a sprint plan in progress</figcaption></figure><p>A template should include the following 6 parts to help teams effectively plan their sprint:</p><ol><li><strong>The sprint name:</strong> This helps teams understand the goal of the sprint.</li><li><strong>An overview of the sprint:</strong> This includes its duration, status, number of open items, estimates remaining, and a completed percentage. It’s helpful before you begin the sprint to see the amount of work your team will be working on. It’s also helpful to give you a quick report of the update when the sprint is in progress.</li><li><strong>Sprint reports:</strong> The burnup and burndown charts based on estimates or count helps product managers get a deep understanding of the progress.</li><li><strong>Scrum boards: </strong>Enables teams to track each item in a board.</li><li><strong>Items:</strong> A list of items in the sprint along with its properties, such as assignees, due dates, and estimates.</li><li><strong>Description, comments, and attachments: </strong>An icon next to an item indicating it has more details in it.</li></ol><figure><a href="https://zepel.io/solutions/scrum/?utm_source=medium&amp;utm_medium=bottom-cta&amp;utm_campaign=sprint-planning-template"><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*44QXAMeOns5qjbOj.png" /></a></figure><p><em>Originally published at </em><a href="https://zepel.io/blog/sprint-planning-template/"><em>https://zepel.io</em></a><em> on March 24, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97936eb5580e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Best Product Managers Remove Uncertainties. Here’s Why.]]></title>
            <link>https://svikashk.medium.com/best-product-managers-remove-uncertainties-heres-why-8b23b4f7cf14?source=rss-831ba2648b14------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b23b4f7cf14</guid>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Vikash Koushik]]></dc:creator>
            <pubDate>Mon, 24 Feb 2020 09:31:34 GMT</pubDate>
            <atom:updated>2020-02-27T07:09:56.206Z</atom:updated>
            <content:encoded><![CDATA[<p>Every once in a while, a new product comes along and changes everything — the way we work, the way we think, and how we behave.</p><p>Open up any blog post on product management and it’ll tell you to solve a problem. The key, it would say, is to understand your customers. While people may be accurate commentators on the problem they’re facing and the emotional state it causes — usually pain and frustration — the causes of that emotional state are often unknown to them.</p><p>This is often the reason why features don’t get adopted by the very same customer who demanded it in the first place.</p><blockquote><em>For all the talk of providing value to customers, there’s a significant and often unspoken factor at work in great products: </em><strong><em>uncertainty</em></strong><em>.</em></blockquote><p>Just last week, I made a rather expensive purchase on an e-commerce store and received a message saying it would arrive the following day between 9am and 9pm. My problem was, I had to go to work the following day and nobody would be at home to collect the package.</p><p>I know it’s bad news, but I didn’t have sufficient information to act on it. What if they delivered the package at 1pm? I couldn’t risk losing it. After all, I did spend a fortune on it. By taking the day off, I was sure to receive my package, but the degree of uncertainty involved in waiting for the delivery person to show up was still a form of mental torture.</p><p>Anyone who has spent even a few hours waiting for their package to arrive knows that it’s a bit like being in a house arrest. You can’t have a bath or pop out to get a bag of crisps, because you fear that the second you do, the delivery guy will turn up.</p><p>Similarly, <strong>for all the technological prowess that Google Maps achieved, its greater achievement is psychologically removing not just the uncertainty of how to get from point A to B, but also the time it would take to get there</strong>. The number of billion-dollar companies who deliver their primary value using this method is just staggering — Uber, Lyft, food delivery apps, to name a few.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*cI4ai8X_OBB6tJ4mIC4j6g.jpeg" /><figcaption>Uber removes uncertainty by showing you where your cab is and when it’ll arrive</figcaption></figure><p>Today, it would be weird to go on a road trip with an extra passenger whose only job throughout the journey is to look at a giant A3 paper and ensure you’re going in the right direction.</p><h3>Not just in tech, uncertainties are everywhere</h3><p>The city I live in has suburban and metro trains, both of which have a frequency of one train arriving every 10 minutes on a weekday.</p><p>However, when waiting for a train to arrive, the levels of anxiety displayed by passengers who use the suburbs is rather high and visible. They’d be fidgeting and be looking at the railway track to see if there’s any visible sign of a train arriving. On the other hand, folks who use metros are calm, often busy watching Tik-tok videos, and sometimes even walk out for a quick bite before the train arrives.</p><p><strong>The only difference between the suburban station and a metro station, apart from the obvious cost per ticket, is the display that’s put in place on every platform at a metro station that tells people precisely when the next train will arrive.</strong></p><p>Similarly, if you’re feeling rather mischievous and you’re looking to create chaos in an airport, all you have to do is remove the information on how long the flight is delayed from the departure board. Because anyone who has had their flight delayed also knows that “delayed” is merely a predecessor to “cancelled”.</p><blockquote><em>The loss of power and control that uncertainties create can cause far stronger feelings of annoyance.</em></blockquote><p>You can see similar examples at play in traffic signals where you have a countdown timer of when the signal will go from red to green.</p><p>Which brings me to an interesting point in building products and features.</p><p>Luckily, most of us are already spending time and energy removing uncertainties on things like onboarding or things related to payments -sending payment receipts quickly. But it doesn’t have to stop there.</p><p>Regardless of your industry and target audience, uncertainty in the minds of your customers play a significant role in the success of your product. By identifying where those uncertainties lie in their daily workflow and solving for them within your product, you can bolster your product’s quality and its metrics.</p><p>So, the next time you sit down with your team to build a new feature or <a href="https://zepel.io/blog/product-improvement/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=best-pm-remove-uncertainties">improve an existing one</a>, be sure to also ask what uncertainty you’re removing.</p><figure><a href="https://zepel.io/solutions/product-development/?utm_source=medium&amp;utm_medium=bottom-cta&amp;utm_campaign=best-pm-remove-uncertainties"><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UdbYORZXx3Ka6K3p.png" /></a></figure><p><em>Originally published at </em><a href="https://zepel.io/blog/best-product-managers-remove-uncertainties/"><em>https://zepel.io</em></a><em> on February 24, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b23b4f7cf14" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to identify and make product improvements?]]></title>
            <link>https://svikashk.medium.com/how-to-identify-and-make-product-improvements-82ccee7c0e5f?source=rss-831ba2648b14------2</link>
            <guid isPermaLink="false">https://medium.com/p/82ccee7c0e5f</guid>
            <category><![CDATA[product-improvements]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[improvement]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Vikash Koushik]]></dc:creator>
            <pubDate>Mon, 17 Feb 2020 07:18:10 GMT</pubDate>
            <atom:updated>2020-02-26T08:41:04.408Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s no secret that building a quality product is hard. But keeping your customers engaged and happy as you make product improvements is equally hard.</p><p>At any given time, there will be more than a handful of improvements you can make within your product. You’ll have some ideas. Your teammates will pitch in with what they think should be improved. And of course, your customers will have a few opinions of their own.</p><p>Any product improvement you make will not satisfy everyone. You need to pick your battles. But taking an informed decision on which specific improvement you should work on isn’t straight forward either.</p><h3>What is product improvement?</h3><p>Product improvement is the process of making changes within your product in such a way that it enables you to either improve engagement or retention within your product, and move the needle for your business.</p><p>There are two kinds of improvements you can do:</p><ol><li>Build a new feature</li><li>Improve existing features</li></ol><p>When building a new feature, you’d consider three things:</p><ol><li>What people say they want</li><li>What people actually want</li><li>What they will pay for (or stick around for)</li></ol><p>These three things are separate and are often identified through a series of qualitative and quantitative discovery methods like having customer interviews, running A/B tests, and watching people use your product.</p><p>Trickier part, however, is when you want to improve an existing feature. <strong>The reason why an existing feature didn’t move the needle could vary from users saying </strong>“ <em>it was difficult to use the feature</em>” <strong>to</strong> “ <em>I didn’t know the feature existed</em>”.</p><p>So, how do you identify which opportunities to go after? And an equally important question to ask, how do you unearth where the scope for <strong><em>real</em></strong> improvements lie?</p><h3>4-step process to identify product improvement opportunities for an existing product</h3><h3>1. Map feature usage to your user’s product journey</h3><p>Not every feature you built carries the same impact. There will be features that will make your users go “ <em>Wow!</em> “. And there’ll be features that rarely get noticed. This is a function of the feature’s goal.</p><p>Every user who signed up for your product can be bucketed into six categories:</p><p>Nearly all the features you build will have its primary goal of moving users one step closer to the delighted bucket. This allows you to directly map all your features to specific buckets mentioned above.</p><p>Of course, this requires you to have at least a rough idea of how users flow within your product. What feature they should use first, followed by what should be used next, all the way till they accomplish what they set out to achieve with your product.</p><p>By creating a timeline of all the top paths customers take within your product, you can gain insight into how your users sequentially perform events in your product, and identify when drop-offs happen or where unsuccessful behaviour occurs. If you’re using a tool like Mixpanel, Amplitude, or Heap, you should be able to get this data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2qriKToeNQ0q1ID8ulN7WQ.png" /><figcaption>An example of a flow diagram on <a href="https://help.amplitude.com/hc/en-us/articles/229792148-Pathfinder">Amplitude</a></figcaption></figure><p>Once you have an idea of the most common paths users take within your product, you should be able to map each feature to your user journey and map them to the buckets mentioned above.</p><p>There’s a good chance that you will have multiple paths within your product. After all, your user’s journey is rarely linear. Which is why it is best to pick one path — usually the most frequently used by paying customers — and focus on improving it first.</p><p><strong>At the end of this step, you should have:</strong></p><ul><li>a clear representation of what features your users use and when,</li><li>where your users drop off, and</li><li>how users flow within your app.</li></ul><p><strong>Takeaway: Map your users’ journey within your product based on the features they use.</strong></p><h3>2. Measure feature success throughout the journey</h3><p>Any good process that helps you identify opportunities will require you to gather data. A great process, however, goes a step further and takes a holistic approach.</p><p>Most teams when trying to understand a feature’s success simply track a few key events and look at how the numbers change on a daily, weekly, or monthly basis. This leads to teams over-indexing on a single data point, and leaving them vulnerable to gaps, blind-spots, and biases.</p><blockquote><em>Half the battle with identifying if a feature is used for its original intent is understanding of why users used them in the first place.</em></blockquote><p>To truly understand how people are using your product,<strong> it isn’t enough to identify how each feature is being used, but for what purpose it is being used, why it’s being used, and if the feature was successful in achieving its goal</strong>.</p><p>By measuring the success of each feature throughout the user’s journey you identified in the previous step, you’ll get a clear picture of what needs to be improved. We wrote an in-depth guide on how to measure the success of a feature. 👇🏼</p><p><a href="https://zepel.io/blog/measure-metrics-for-feature-success/">How To Measure The Success Of Your Feature?</a></p><p><strong>At the end of this step, you should have data points on:</strong></p><ul><li>how people are using each feature in your product,</li><li>why they’re using the feature,</li><li>what purpose they’re using the feature for, and</li><li>if the feature was successful in achieving what it was originally built for.</li></ul><p><strong>Takeaway: Measure the success of each feature your customers use in their journey.</strong></p><h3>3. Find the correlation between feature usages and business goals</h3><p>The success of a feature is irrelevant if it can’t have a meaningful impact on your larger business goals.</p><p>When looking at data, most teams say, “ <em>people who performed X converted</em>” or “ <em>people who converted did X</em> “. This is an effect of thinking in a single dimension. They make the mistake of not considering people who performed X but didn’t convert, nor do they take into consideration the people who converted without performing X. This is a typical example of first-order thinking.</p><p>By using the <a href="https://en.wikipedia.org/wiki/Phi_coefficient">Phi coefficient</a>, a measure of association for two binary variables in statistics, we can take a multi-dimensional approach to find if there is any relationship between a specific feature usage within your app and the number of occurrences of a feature usage that is likely to maximize the outcome.</p><p><strong>To get started with the Phi coefficient you need two things:</strong></p><ul><li>an ideal frequency of usage for the feature, say n, and</li><li>to what goal you’re trying to find a correlation. For example, second-week retention.</li></ul><p>By digging into your analytics tool or your database, you should now be able to fill in the cells a, b, c, and d into the 2x2 matrix table below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bz-rMssCE2Fy1pi3mLRJ0A.png" /><figcaption>Calculating users who used feature for a certain number of times and did goal or didn’t do goal</figcaption></figure><p>where,</p><p><strong>n</strong> = ideal frequency of usage for the feature.</p><p><strong>a</strong> = number of people who used the feature &gt;= n times AND achieved the goal.</p><p><strong>b</strong> = number of people who used the feature &gt;= n times AND did not achieve the goal.</p><p><strong>c</strong> = number of people who used the feature &lt; n times AND achieved the goal.</p><p><strong>d</strong> = number of people who used the feature &lt; n times AND did not achieve the goal.</p><p>The ideal frequency of usage for a feature, n, depends largely on the product, how the feature impacts the product as a whole, the market you’re after, and your business model. So, if you don’t have a clear picture of what n is, it’s okay to start with a hypothesis and work from there.</p><p>Using this data, you can then find Phi’s correlation coefficient by using the above data in the below formula:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l2BhoIm2IUOQY3iUAW521A.png" /><figcaption>Formula to calculate Phi’s correlation coefficient</figcaption></figure><p>This determines the correlation strength between the ideal frequency of feature usage and the goal. The value you get can vary between -1 and +1, where +1 indicates a positive relationship between your feature and the goal, -1 indicates a negative relationship, and 0 indicates no relationship.</p><p>A lot of the times, a single feature by itself can not help you improve your goal of increasing engagement or improve retention. To counter this, we recommend identifying the correlation strength between all the features in the user journey that we identified from the first step.</p><p>A good example of this is an analytics dashboard. Say you’re building a social media management tool and you’re trying to increase the usage of your report. You might receive a ton of requests from your customers wanting different types of charts to visualize. However, if they aren’t scheduling enough posts to make the reports meaningful, adding more types of charts will not help you achieve your goal.</p><p><strong>At the end of this step, you should have:</strong></p><ul><li>a relationship between the number of occurrences of feature usage and the outcome.</li></ul><p><strong>Takeaway: Identify the relationship between the number of times a feature is used and your goal.</strong></p><h3>4. Identifying what improvement to work on</h3><p>Now that you know what number of occurrences of every feature usage is likely to improve the outcome, how people use those features, when, and also why, we can focus on specific feature improvements backed by data.</p><p>There are two types of improvements you can make for your existing features in your product:</p><p><strong>1. Adoption improvements</strong></p><p>Adoption improvements are meant to target your current users who aren’t using it at the moment but would benefit from it. Three possible reasons why users did not adopt the feature:</p><ul><li>The feature didn’t have enough capabilities. These are users who say, “<em>I’ll use X if it can do A, B, and C</em>”.</li><li>Discovering the feature was hard.</li><li>Understanding how to use the feature was hard.</li></ul><p><strong>You should focus on improving adoption when</strong> there’s a positive correlation between the frequency of usage of a feature and the goal, but only a small number of people are using it.</p><p><strong>2. Frequency improvements</strong></p><p>Frequency improvements are meant to target users who are already using the feature but aren’t using it enough number of times. A possible reason why people aren’t using the feature enough number of times could be that users aren’t sure why they should use a feature.</p><p><strong>You should focus on making a frequency improvement when</strong> there’s a positive correlation between the frequency of usage of a feature and the goal, but a large number of your users aren’t using the feature enough number of times.</p><p><strong>Takeaway: Make product improvements based on the relationship between a feature and the goal, how many people adopted the feature, and how frequently they use the feature.</strong></p><h3>Product improvement examples at Zepel</h3><p><strong>1. Git Integration</strong></p><p>A few months ago, Git integration in <a href="https://zepel.io/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=product-improvement">Zepel</a> only allowed you to complete a linked item when you merged pull request. This wasn’t enough.</p><ul><li>Not all users were using it since it was difficult to find.</li><li>Users who used it were able to only complete an item, but not update its statuses.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZRQv6KpzePLXdUuB3wJ6SQ.png" /><figcaption>An improved Git Workflow Automation in Zepel</figcaption></figure><p>With the introduction of Git Workflow automation, teams today update their team members automatically based on their activity in their version control system. This led to an increase in the number of people who adopted the feature, enabling them to be in sync with the reality of what’s happening effortlessly.</p><p><strong>2. Item Details Pop-up</strong></p><p>The item details pop-up in Zepel is where a user story’s description, comments, and all its properties can be viewed in one shot. Plenty of times, while writing acceptance criteria in the description area, teams realize the current user story requires an additional subtask.</p><p>Previously, users couldn’t view or add subtasks from within the details pop-up. This meant, our users had to go back and then add new subtasks. To solve this, we made a few design tweaks and enabled teams to add new subtasks from within the details pop-up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zVp8T-iaWzT89ZXLU4gtTQ.png" /><figcaption>Improvement made to an item’s details pop-up to allow users to add subtasks</figcaption></figure><p>While it sounds trivial, by removing an additional step and unnecessary friction, we were able to increase the frequency of items created.</p><h3>Final thoughts on product improvement</h3><p>Gone are the days where you can spew a few features every fortnight and win over customers. The only <a href="https://zepel.io/blog/product-strategy/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=product-improvement">strategy to keep customers</a> happy is by continually delivering value. And that means, consistently improving your existing features.</p><p>Truth is, the product improvements most of us do today are based on gut feeling, or at best, a response to the number of customers who shout and leave. That’s the equivalent of throwing spaghetti at a wall to see what sticks. While it may make for a fun evening, it’s not a sustainable strategy. At some point, you’ve got to know your numbers and live by them. But even numbers can’t guarantee good decision-making.</p><blockquote><em>Without context, data is plain numbers represented with fancy charts.</em></blockquote><p>By following a process that doesn’t just consider numbers, but also takes the big picture into account, you can make a better judgement on which features need improvements and <a href="https://zepel.io/blog/prioritize-product-feature-backlog/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=product-improvement">priorities the right features</a>.</p><figure><a href="https://zepel.io/solutions/product-development/?utm_source=medium&amp;utm_medium=bottom-cta&amp;utm_campaign=product-improvement"><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lBs3k-43tHL69RjE.png" /></a></figure><p><em>Originally published at </em><a href="https://zepel.io/blog/product-improvement/"><em>https://zepel.io</em></a><em> on February 17, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82ccee7c0e5f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[11 Best Trello Alternatives To Try in 2020]]></title>
            <link>https://svikashk.medium.com/11-best-trello-alternatives-to-try-in-2020-a26f7d6cf6f?source=rss-831ba2648b14------2</link>
            <guid isPermaLink="false">https://medium.com/p/a26f7d6cf6f</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[trello]]></category>
            <dc:creator><![CDATA[Vikash Koushik]]></dc:creator>
            <pubDate>Tue, 17 Dec 2019 12:12:15 GMT</pubDate>
            <atom:updated>2020-06-21T11:32:04.248Z</atom:updated>
            <content:encoded><![CDATA[<p>Is Trello not meeting your requirements? Are you looking for Trello alternatives for your team?</p><p>Not to worry, cause this article has 11 Trello alternatives to help you make a decision.</p><p>Trello rose to popularity among small businesses thanks to its ease of use but just because it’s widely adopted doesn’t make it a default choice.</p><p>While Trello is easy to get started with, teams who needed more than just a simple kanban tool realized it didn’t have all the functionalities they needed to build products.</p><p>For example, Trello’s capabilities are limited to simple task management, it doesn’t provide in-depth reports out of the box, and doesn’t have a dedicated way to run Sprints. And to top it all, you can have only 10 team boards open at any given point if you’re on the free plan.</p><p>These drawbacks have led to teams look for Trello alternatives that can help their product development efforts. And if you’re one of them, read on.</p><h3>11 Trello Alternatives For Project Management</h3><h3>1. Zepel</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qsSm-F_bO3WGsUUcOwx7Bw.png" /></figure><p><a href="https://zepel.io/compare/trello-alternative/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=trello-alternatives">Zepel</a> is the project management tool that lets you streamline your product development process at every phase. It lets you plan features, collaborate across disciplines, and track the progress of an entire feature in real-time.</p><p>The biggest difference between Zepel and Trello, apart from the functionalities is that Zepel goes beyond simple task tracking and allows you track an entire feature while remaining simple and easy to use.</p><p>What does this mean?</p><p>With a simple, document-like interface, planning features in Zepel is as effortless as typing into a word document. Once you’ve created a Project, you can quickly plan a feature you’re building with User Stories, Tasks, Subtasks, Enhancements, and Bugs.</p><p>Once you’re ready to bring members, you can add any number of boards within the project to track your work and get work done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XyhuE_W4ZbKs6WxzmESELA.png" /></figure><p>And if you’re someone who runs Sprints, Zepel has a dedicated view for Sprints, Sprint Boards, and Reports, so you know exactly where your Sprint stands.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HlbQyAZiqft3ssOtitiruA.png" /></figure><p><strong>Why use Zepel instead of Trello?</strong></p><ol><li>Document like editor to plan features.</li><li><a href="https://zepel.io/features/kanban-board/">Kanban Board</a> within a project to accommodate design, development, QA, and others in a single project.</li><li>Dedicated Sprint view.</li><li>Detailed Reports.</li><li>Simple drag-and-drop cards to prioritize features.</li><li>Progress view to track an entire feature.</li><li>Advanced filters for you to find exactly what you want.</li><li>Github, Bitbucket, Gitlab, and Slack Integrations.</li><li>Developer friendly public APIs.</li><li>One-click Trello import to get started quickly.</li></ol><figure><a href="https://zepel.io/compare/trello-alternative/?utm_source=medium&amp;utm_medium=mid-image&amp;utm_campaign=trello-alternatives"><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*30jagMdQhblRVSCf.png" /></a></figure><h3>2. Asana</h3><p>Asana, like Trello, is one of the most popular project management tools. It’s widely adopted by several non-technical teams to track who is doing what and by when.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7rrCUJu_L4Siu7DDwj0oaw.png" /></figure><p>Asana has several views, including list, boards, and calendar that allows teams to track their work. However, one of the biggest disadvantages of Asana is that it gets really expensive even to use simple project management capabilities.</p><p><strong>Why use Asana over Trello?</strong></p><ol><li>List view to view your tasks</li><li>Multiple views</li><li>Intuitive to use</li><li>Dashboard view</li><li>Integrations</li></ol><h3>3. Github Projects</h3><p>If you’re a developer and you use Github for version control, then you might want to give Github projects a go. With Github project management, your team can also track and fix issues, with the code by their side.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lAyW-71OmMWd8F2lG5XCLg.png" /></figure><p>Github lets you link issues and pull requests to specific tasks, so members in your team can quickly track updates without a complicated workflow. This linking will help your team to automatically close tasks when the pull request is merged.</p><p><strong>Why use Github Projects over Trello?</strong></p><p>If you’re using Zepel, <a href="https://zepel.io/guide/integrations/github/?utm_source=zepelblog&amp;utm_medium=text&amp;utm_campaign=trello-alternatives">you can already do this with Zepel’s integration with Github</a> and other version control systems.</p><h3>4. Kanbanize</h3><p>Kanbanize is practically a Trello on steroids.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/856/1*zFq6kXkbPwERMmALw3sBLw.png" /></figure><p>Kanbanize’s most popular and loved feature is that it allows you to break down a card in a board into smaller cards. These cards can be automated to go through a series of steps based on your workflow. Kanbanize also has a time-tracking feature built in to their product. So, if you’re a services company, then you’d love it.</p><p>As Kanbanize is a powerful tool, one of the bigger drawbacks with it is that it can be a bit hard to get started.</p><p><strong>Why choose Kanbanize over Trello?</strong></p><h3>5. JIRA</h3><p>JIRA is one of the go-to tools for most teams when Trello can’t meet their needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cs0f-HpdMW6LfqyD4EzyiQ.png" /></figure><p>It is known for being an agile project management tool and having plenty of features. It lets you customize every nut and bolt of your workflow and integrates with plenty of tools.</p><p>However, JIRA’s nearly endless capabilities has also lead to developers not adopting the tool due its steep learning curve, its slowness, and its clutter.</p><p><strong>Why consider JIRA over Trello?</strong></p><p>Here’s an <a href="https://zepel.io/blog/jira-vs-trello/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=trello-alternatives">in-depth review and comparison of how JIRA vs Trello</a> to help you understand their differences. However, if you’re not a fan of JIRA and much rather prefer other tools, <a href="https://zepel.io/blog/jira-alternative/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=trello-alternatives">here are 9 JIRA alternatives</a> that you can use today.</p><h3>6. Taskboard</h3><p>Taskboard is an open source Trello alternative that teams can self-host and use if they want a simple interface without plenty of functionalities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*QzveHYMU7E0KPsuunMkP8g.png" /></figure><p>It provides teams with unlimited boards and standard customizations to help you manage your projects easily. It comes with inline markdown support for descriptions so you can quickly share more information about any task.</p><p><strong>Why choose Taskboard over Trello?</strong></p><h3>7. Taiga</h3><p>Taiga is an agile project management tool that provides both cloud and self-hosted options.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/795/1*_UW5e9XQo39TlPDvngJxig.png" /></figure><p>Using Taiga, teams can manage and keep a list of issues, categorize them, and assign it to the right people. It also provides kanban boards and sprints for you to keep track of what your team is working on.</p><p><strong>Why consider Taiga over Trello?</strong></p><ol><li>Simple task management</li><li>Wiki spaces</li><li>Time tracking</li><li>Customizable kanban boards</li><li>Gamification</li></ol><h3>8. MeisterTask</h3><p>MeisterTask is a task management tool built for teams.</p><p>Plenty of teams use MeisterTask to organize and manage tasks in a beautifully designed, customizable environment that adapts to their individual needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KHt8GfEwcryytELINfS8JA.png" /></figure><p>Much like Trello, MeisterTask’s kanban-style project boards allow teams to create streamlined, automated workflows and get more done together.</p><p><strong>Why consider MeisterTask over Trello?</strong></p><ol><li>Easy to use.</li><li>Includes time tracking capability.</li><li>Integrates with Zapier that allows you to connect with several apps.</li></ol><h3>9. Paymo</h3><p>Paymo is a project management tool that several small companies use to manage their projects. It helps teams to track time, collaborate in projects, and track the project all the way to completion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*ABLwBAFy8zo5M7Q3SMHD8g.png" /></figure><p>It’s quite popular among services companies since it lets you track expenses, generate quotes and invoices, and get paid.</p><p><strong>Why use Paymo instead of Trello?</strong></p><ol><li>Includes Gantt charts.</li><li>Allows you to track time.</li><li>Provides a way to generate quotes, invoices, and to get paid.</li></ol><h3>10. Taskworld</h3><p>Taskworld is a simple project management tool that lets you track time, manage files, and gives your team the ability to easily manage their projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*y5cdCIn5ZPl-vd-mPQDhmQ.png" /></figure><p>Taskworld also provides an ability to message your teammates, see who is online, and who has read your messages.</p><p><strong>Why use Taskworld instead of Trello?</strong></p><ol><li>Team messaging.</li><li>File management capabilities.</li><li>Time tracking.</li><li>Project timeline to visualize the project in a timeline view.</li></ol><h3>11. Bitrix24</h3><p>Bitrix24 is an online project management tool that can easily be the Trello alternative you’re looking for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*r9SZmvC6hhUxwowe6UA7AA.png" /></figure><p>It’s extremely user friendly, easy to collaborate with team members, and even gives a CRM module for you to work with non-technical teams. It provides video conferencing option that remote teams would find useful.</p><p><strong>Why use Bitrix24 instead of Trello?</strong></p><ol><li>Simple task management.</li><li>Remote friendly with video conferencing options.</li><li>Provides task templates.</li><li>Has a centralized news-feed to stay ahead of your team’s activities.</li></ol><h3>Further Helpful Articles When Evaluating Trello Alternatives</h3><p><a href="https://zepel.io/blog/switching-project-management-tools/">5 questions to ask when switching to a new project management tool</a></p><p><em>Originally published at </em><a href="https://zepel.io/blog/trello-alternatives/"><em>https://zepel.io</em></a><em> on December 17, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a26f7d6cf6f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Issue Trackers Can’t Help You Develop Products]]></title>
            <link>https://svikashk.medium.com/why-issue-trackers-cant-help-you-develop-products-4be8ba08d6e6?source=rss-831ba2648b14------2</link>
            <guid isPermaLink="false">https://medium.com/p/4be8ba08d6e6</guid>
            <category><![CDATA[project-management-tool]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Vikash Koushik]]></dc:creator>
            <pubDate>Tue, 10 Dec 2019 05:05:36 GMT</pubDate>
            <atom:updated>2020-02-19T11:46:33.969Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xtqp2GdQtBdBR0clUCeZFA.png" /></figure><p>I’ve been watching our team build Zepel for several months. And I also happen to have a front-row seat to see how others build their products using Zepel.</p><p>If there’s one thing I’ve learned after multiple conversations over Zoom calls and chats and observing how teams build their products, it’s this:</p><blockquote><em>The road to shipping anything that isn’t a bug fix is filled with distractions, diversions, and speed bumps.</em></blockquote><p>If you think about it, product development is a lot like a criminal investigation — when viewed in retrospect, it’s a simple, linear narrative that appears to be a series of if-then-else logical steps. But inexplicably random, messy, and a gruelling process when experienced in real-time.</p><p>A million and a half questions need your attention from multiple disciplines that comes with different levels of context and at every phase of the development.</p><p>What can seem like a small or trivial question at first, ultimately ends up becoming the difference between a product that makes people cringe, and a product that makes people want to come back.</p><h3>“That’s why there’s Agile!”</h3><p>I’m certain you’d be inching to tell me all about Agile, so let me dive straight in.</p><p>Luckily, a good chunk of businesses are able to streamline their product development efforts with processes, tools, and workflows. However, in the book <a href="https://www.amazon.com/Actionable-Agile-Metrics-Predictability-Introduction/dp/098643633X/ref=sr_1_1?s=books&amp;ie=UTF8&amp;qid=1474829007&amp;sr=1-1&amp;keywords=actionable+agile+metrics+for+predictability">Actionable Agile Metrics for Predictability</a>, Daniel S. Vacanti states we spend only 15% of the time doing the actual work and the rest on waiting.</p><p>And that doesn’t sound right.</p><p>If a greater part of your time doesn’t involve coming up with killer product strategies, building creative mockups, or creating magic inside terminals and code editors, there is something fundamentally wrong.</p><p>Not with the processes, but with the fundamental assumptions that issue trackers and generic project management tools are built upon.</p><h3>So what’s the problem with using issue trackers for product development?</h3><p>Issue trackers are great when you want to track, well, issues. The only three things you need to keep track of an issue are:</p><ol><li>Steps to reproduce,</li><li>What you expected to see, and</li><li>What you saw instead.</li></ol><p>The moment you know the above three, issues then go through a sequence of steps that boils down to a binary answer of “is it fixed or not”.</p><p>Today’s issue trackers and other generic project management tools are built with only this knowledge at their core. Product development, by its very nature, is the exact opposite — non-linear.</p><p>You see, when you’re building a product, it has possibilities for being interpreted in many ways. It includes obscurities and involves interlaced relationships across multiple disciplines. And to top it all, this happens at an unpredictable scale.</p><blockquote><em>It’s one thing to track and fix issues, but it’s a whole different ball game when you want to build products.</em></blockquote><p>If you’re thinking, “ <em>You can configure your tool to meet your needs</em>” I hear you. The fact that you have to go through a steep learning curve and configure it <em>just the right way</em>, speaks a lot about the fact that issue trackers weren’t built for product development.</p><p>This mismatch between the fundamentals of today’s tools and the needs of the team building products has created havoc even to track progress.</p><p>At the surface level, it seems like a simple problem with a simple solution of knowing who is doing what by when. But the reality is far from it.</p><p>Of course, assigning and setting due dates is a step-up from completely sitting in the dark. But when you have members from multiple disciplines working towards churning out chunks of work piece by piece, just knowing it’s “in progress” is hardly sufficient.</p><p>The below illustration by Intercom is a great way to visualize how things can quickly become chaotic as more people get involved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pB8ovI0-E2AYF7KPjmb_qQ.png" /><figcaption>An illustration by Intercom on communication and its complexity.</figcaption></figure><p>An issue tracker or a generic project management tool works just fine as long as you have 2–3 people. But when you bring more members from other disciplines to build your feature, that’s where things get out of hand. Because your needs evolve by infinite levels as more people get involved and the development progresses.</p><p>Sure, you might only need to know where a task is sitting when your team is just getting started with the development. But when you’re only a week away from the deadline, just to get a grip of what’s happening, you need to make sense of everything everyone has done, how much work is pending in each and every discipline involved, and how it all fits together.</p><p>To think you can get all of this context with fancy charts is ambitious at best.</p><p>For a product manager, for example, this means she would want to know:</p><ol><li>Who is doing what and when,</li><li>What are the different disciplines involved in building the feature,</li><li>Where the work stands in each of these disciplines, and</li><li>How all of this connects to the overall progress of the entire feature, across disciplines, in real-time.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uJZ3AR8HtnVMjmZesP3sqg.png" /><figcaption>The pyramid of development tracking needs</figcaption></figure><p>See how her needs vary?</p><p>And if you’re a developer building the product, your needs, a lot of times, are completely different.</p><p>Because at different phases of the product development process, people have unique priorities and needs that require different and sometimes multiple contexts to be efficient.</p><blockquote><em>The greatest trick issue trackers ever pulled was convincing the world you could do all of this and streamline your entire product development process.</em></blockquote><h3>So, how do you capture and track this non-linear nature of product development?</h3><p>Get the fundamental building blocks right and be process agnostic. Because slapping even the most efficient and finest processes on a broken foundation will get you nowhere.</p><p>What does this mean?</p><p>Now, imagine if you could plan features and capture actionable chunks of work on a word document. And what if this piece of document connected to the tracking aspects of your development? To your Kanban Boards. To Sprints. And ultimately allowed you to track the progress of your feature in every discipline. At every phase of the development process. Without the clutter or messy configurations.</p><p>We’ve built <a href="https://zepel.io/solutions/product-development/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=why-no-issue-trackers">Zepel</a> with exactly this in mind. It keeps all the building blocks of agile you already love and use while allowing you to build products with your team seamlessly.</p><p>This keeps the tool light-weight and you don’t have to go through a tedious learning process and tweak multiple settings just to get started.</p><p>Here’s a quick glimpse of how it looks:</p><h3>1. Spec, plan, and capture in seconds</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SS12oburWxo4c4rXURC66w.png" /><figcaption>Zepel’s document-like interface to help you quickly plan a feature.</figcaption></figure><p>Planning and building features are hard enough already. Zepel’s document-like editor removes all the friction and distraction, so you can quickly plan every step and aspect of your feature effortlessly.</p><p>Capture user stories, tasks, subtasks, enhancements, and bugs in seconds. And when you want to assign, set due dates, or estimate, it’s all just a / command away.</p><p>The best part?</p><p>What looks like a simple document at first, quickly becomes the single source of truth for everyone about this feature — from showing who is working on what and when, to the different disciplines involved in building it.</p><h3>2. Track progress in each discipline</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XyhuE_W4ZbKs6WxzmESELA.png" /><figcaption>Track progress in each discipline involved in building the feature using multiple Boards.</figcaption></figure><p>When you bring members from design, dev, and QA, you need to be able to see where their work stands. And more importantly, everyone should be able to seamlessly handover work from any discipline to another (say, design to dev).</p><p>Zepel lets you add a board for each discipline, so everyone can easily move work around within the board and update statuses. When you want to handover work, you just have to move the item to another board. And it’s as simple as changing statuses!</p><p>This allows everyone to focus on just the things they care about and move work around without having to set anything up.</p><h3>3. Align everyone on the big picture</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sg-f9cU-BJ5nKfEsTCUthA.png" /><figcaption>Keep everyone aligned on the same goals and watch your feature come to life.</figcaption></figure><p>When you collaborate with members, the Progress view gives each member a holistic view of the entire product development plans and updates.</p><p>Team members can see how each update from multiple disciplines effects a feature’s progress. With the Kanban view, product managers use simple drag-and-drop cards to prioritize features and plan for the road ahead.</p><p>Now, I can continue to tell you about how you can run Sprints, see reports, and all the integrations we’ve got in Zepel.</p><p>But this article isn’t about features. It isn’t about speed. And it isn’t about agile either!</p><p>It’s about the fundamentals of product development. Fundamentals that aren’t tied to simple issues and tasks, but to people who come with unique context and have varying needs.</p><p>Most teams understand this and are already tweaking processes to meet their team’s requirements. <strong><em>The tools, however, haven’t evolved</em></strong>.</p><p>At <a href="https://zepel.io/solutions/product-development/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=why-no-issue-trackers">Zepel</a>, we’re just getting started with tackling this problem.</p><p>But if you’re looking for a tool that lets you streamline your product development efforts, lets you minimize unnecessary overheads and side-effects of a rigid process, you should give Zepel a shot!</p><figure><a href="https://zepel.io/solutions/product-development/?utm_source=medium&amp;utm_medium=bottom-cta&amp;utm_campaign=why-no-issue-trackers"><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vBOOthJHvLp7V4AR.png" /></a></figure><p><em>Originally published at </em><a href="https://zepel.io/blog/why-issue-trackers-and-pm-tools-fail/"><em>https://zepel.io</em></a><em> on December 10, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4be8ba08d6e6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s a product strategy? How to develop one that sets you apart?]]></title>
            <link>https://svikashk.medium.com/whats-a-product-strategy-how-to-develop-one-that-sets-you-apart-7b48228fd7d2?source=rss-831ba2648b14------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b48228fd7d2</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Vikash Koushik]]></dc:creator>
            <pubDate>Tue, 12 Nov 2019 07:14:39 GMT</pubDate>
            <atom:updated>2019-11-20T04:39:45.280Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qEwrgI95PIZ-NRg43NtZCA.png" /></figure><p>Far too many companies think product strategy means having a prioritized backlog and spewing features every other week.</p><p>But gone are the days when you could solve a problem by developing features and build a successful product out of it.</p><p>Your potential customers have a ton of options at their disposal today. If a market has enough demand, it will quickly get flooded with products attempting to sell with similar features.</p><p><strong>Today, the job of every product is three folds:</strong></p><ol><li>Solve a large problem for a user.</li><li>Be defensible to time and market conditions.</li><li>Establish as a leader in the market.</li></ol><p>With increasing costs to acquire new customers, your product not only has to stand out, but it must be good enough to retain these customers. And you have to do all this while ensuring your product doesn’t get bloated or become yet another “me-too product”.</p><blockquote><em>You develop a good product strategy when you take your users’ needs into account.</em></blockquote><blockquote><em>But you’ll make a difference and move the needle when you take holistic approach.</em></blockquote><p>And this crisp guide is all about helping you achieve just that — develop a sound product strategy.</p><h3>What’s a product strategy?</h3><p>A product strategy is often defined by what features are prioritized in the roadmap. This, however, must not be mistaken to mean that a roadmap <strong><em>is</em></strong> the product strategy. Because in reality, a product strategy is so much more than that.</p><p>A clear product strategy outlines the steps needed to achieve the vision. It challenges long-held assumptions in the market by taking into account several variables such as:</p><ol><li>Vision</li><li>Customer needs</li><li>Customer behaviour</li><li>Current market conditions</li></ol><blockquote><em>“Good product managers know the market, the product, the product line and the competition extremely well and operate from a strong basis of knowledge and confidence.”</em></blockquote><blockquote><em>~ Ben Horowitz, </em><a href="https://a16z.com/2012/06/15/good-product-managerbad-product-manager/"><em>A16Z</em></a></blockquote><p>Look at all the great companies.</p><ol><li>Netflix went from renting DVDs, to online streaming, to producing interactive shows.</li><li>Amazon went from selling books online, to becoming an online retail store, to selling smart devices that can talk to you.</li></ol><p>These companies that we all love and admire weren’t built by following the trends of yesterday. They challenged the status quo and created an inflection point in the market.</p><p>When developing a product strategy, product managers must learn to not just worry about what customers want today. If you want to build a product strategy that sets your product apart, you’ll have to lead with market conditions and customer behaviour.</p><p>So, how do you develop a product strategy that gives you the competitive edge? Let’s jump in and find out.</p><h3>How to develop a product strategy?</h3><h3>1. Develop a product vision to guide your strategy</h3><p>Every step you take to develop a product strategy will be based on one thing sitting at its core — product vision.</p><p>A product vision isn’t just a random statement that talks about the future. It sets the direction for where the product is heading and talks about what the product will accomplish for its target users in the future.</p><p><strong>A product vision achieves five things:</strong></p><ol><li>It describes the motivation behind the product.</li><li>Keeps the target user in mind.</li><li>Looks beyond the product.</li><li>Employs a shared vision.</li><li>Guides key decisions.</li></ol><p>A good product vision leads with the needs of the market.</p><p>It captures the ultimate purpose of your product and describe the positive change it should bring about. It acts as a way to get members from every team aligned on a common goal and get them excited about what they’re doing.</p><p>And since the product vision sits at the foundation of everything you do, without it in place, you will end up becoming a bloated software that nobody will understand or know how to use.</p><blockquote><em>Because it is a lot easier to give in to every request your customer throws at you when you don’t stand for something.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/869/0*GvMxwq7G6YAq7-jB.png" /></figure><p>Once your product vision is developed, every action your team takes during the product development process will be guided by your vision. At every phase. In every step.</p><h3>2. Use data to set an actionable goal for your product</h3><p>Once your vision is in place, it’s time to break it down into an actionable goal that you and your team can execute on in the coming quarter or year.</p><p>Every actionable goal is based on data which you either want to improve or form a hypothesis to validate.</p><p>To do this, you’ll first have to determine how your current users use your product. Provided you are actively <a href="https://zepel.io/blog/measure-metrics-for-feature-success/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=product-strategy">tracking your feature metrics</a>, a simple query into an analytics tool like Mixpanel or Amplitude should give you a good indication.</p><p>What you should be looking for is the frequency of usage for each feature in your product. That means, looking at functionalities that ties to your product’s core selling points and eliminating basic, administrative features.</p><p>When going through this data, it’s normal to see certain features having more usage than others. But that in itself is only half as useful as plain numbers in a random spreadsheet.</p><p>You need to combine your product metrics with your customers’ expected behaviour to see if they make any sense. Because data, at the end of the day, is only useful if it gives you clarity and leads you to an outcome.</p><blockquote><em>And best product goals are tied to outcomes.</em></blockquote><blockquote><em>Not outputs.</em></blockquote><p><strong>Armed with this information, you can do two things:</strong></p><ol><li>If your feature adoption and usage are as expected, you can choose to set a new goal that will take your product vision further.</li><li>If the adoption and usage aren’t as expected, you’d be better off on understanding why they aren’t performing as expected and improving them.</li></ol><p><strong>For example:</strong> For an app like Instagram, if you see more people scrolling through their feeds and liking others’ photos, but aren’t uploading more photos themselves, you know there’s engagement within the product. But on the flip side, not uploading more pictures isn’t the expected behaviour. It will lead to eventual to drop in engagement within the product.</p><p>Once a mismatch in behaviour is identified, it is important to articulate how it will impact the business and derive a goal from it. A product goal should be at a fundamental level.</p><p>In the example above, it is easy to settle down on a goal of increasing the number of photos people post. That only describes what you are going to do.</p><p>But when you connect it to an outcome of improving network effects, it will open up a wide array of possibilities that your team can then prioritize and execute on.</p><h3>3. Prioritize features to reflect your product goal</h3><p>With a product goal that will inch you closer to your vision, it is time to break your goal down to things you’ll be working on to execute your product strategy.</p><p>Depending on the goal you articulated in the previous step, you might have to implement make improvements to existing features, develop new features, or even do a combination of both. Not to forget the technical debts that you’ll have to take care of.</p><p>To ensure you aren’t spending time building something that barely has an impact, you need a process in place that lets you tie your decisions about what you build back to your product goals.</p><p>When prioritizing features, it is important to keep in mind the complexity, effort, and the impact it’ll have. But it is equally important to understand where the majority of your users are in their lifecycle and if your goal aligns to these users.</p><p>Because not every user will need the feature you are currently building. And the goal you set in the previous step will help you identify which part of your users’ lifecycle you are building you are trying to improve and optimize for.</p><p>We’ve written in detail about how to <a href="https://zepel.io/blog/prioritize-product-feature-backlog/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=product-strategy">prioritize features before</a>. The process we’ve written in detail should help you through this step.</p><p>If you’re using <a href="https://zepel.io/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=product-strategy">Zepel</a>, you can prioritize features within a project effortlessly using drag-and-drop cards, assign owner to ensure someone is responsible for the quality of the feature, and track the progress of the entire feature across disciplines.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tVgfIKxzg8_LDzjw.png" /></figure><h3>4. Go beyond aligning members on the product strategy</h3><p>The norm today is to align team members on a common goal, usually the product strategy. It’s a step in the right direction, but that’s rarely enough.</p><p>Product development is a multi-disciplinary effort. When you have members from multiple disciplines <a href="https://zepel.io/blog/cross-functional-collaboration/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=product-strategy">collaborating cross-functionally</a>, you need to peel the onion and break goals down to team-specific goals.</p><p>Why?</p><p>From the moment features are prioritized all the way till they are pushed to production, members from multiple disciplines get involved — design, development, QA. Features will get broken down to work items that will then be collaborated within and across disciplines. And there will be changes that’ll be made as new information and questions arise.</p><p>To handle this <a href="https://zepel.io/blog/product-development-process/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=product-strategy">non-linear process in product development</a>, you need to have a system in place that aligns members from every discipline on two levels:</p><ol><li>On a common goal.</li><li>On a goal specific to their discipline.</li></ol><p>Because when you align everyone on a product strategy, you only align them on what you are going to do.</p><p>But when you go a step further and break your product strategy down to a goal specific to their discipline, you align them on how you are going to execute the product strategy.</p><p>And the difference between knowing “what you are going to do” and “how you are going to execute” is the difference between just shipping features and shipping features that customers will love and use.</p><p>If you are loosing sleep over planning the right features, conceptualizing them, and keeping track of its progress across disciplines, you should give <a href="https://zepel.io/?utm_source=medium&amp;utm_medium=text&amp;utm_campaign=product-strategy">Zepel</a> a try already.</p><h3>Further Reading</h3><ul><li><a href="https://zepel.io/blog/product-development-process/">The Product Development Process To Go From Idea To Happy Users</a></li><li><a href="https://zepel.io/blog/feature-tracking/">What is Feature Tracking?</a></li><li><a href="https://zepel.io/blog/switching-project-management-tools/">5 questions to ask when switching to a new project management tool</a></li><li><a href="https://zepel.io/blog/agile-tools/">11 Best Agile Tools For Project Management in 2019</a></li></ul><p><em>Originally published at </em><a href="https://zepel.io/blog/product-strategy/"><em>https://zepel.io</em></a><em> on November 12, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b48228fd7d2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>