<?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 Zenhub on Medium]]></title>
        <description><![CDATA[Stories by Zenhub on Medium]]></description>
        <link>https://medium.com/@zenhub?source=rss-1d8c444e0857------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*oMAo9paTS03FZHpWrOAiOQ.jpeg</url>
            <title>Stories by Zenhub on Medium</title>
            <link>https://medium.com/@zenhub?source=rss-1d8c444e0857------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 03:28:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@zenhub/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[How ZenHub is helping Philippine Red Cross fight Covid-19]]></title>
            <link>https://zenhub.medium.com/how-zenhub-is-helping-philippine-red-cross-fight-covid-19-2ad8a65a688e?source=rss-1d8c444e0857------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ad8a65a688e</guid>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[red-cross-volunteers]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[agile-teams]]></category>
            <dc:creator><![CDATA[Zenhub]]></dc:creator>
            <pubDate>Wed, 21 Oct 2020 18:33:02 GMT</pubDate>
            <atom:updated>2020-10-21T18:33:02.121Z</atom:updated>
            <content:encoded><![CDATA[<p>To say this has been a year filled with global unprecedented challenges would be an understatement. However, this has also provided an opportunity for exemplary individuals and organizations to step up and make a huge impact. One such organization is the Philippine Red Cross.</p><p>They’ve been building the biggest Covid-19 testing lab in the Philippines, and the results speak for themselves — as of October 2020, <a href="https://www.philstar.com/headlines/2020/10/06/2047500/philippine-red-cross-swab-tests-reach-1-million-more-labs-eyed"><strong>they have administered a million tests</strong></a>, despite opening their first laboratory only six months ago. Today, we’ll be showcasing how they’ve streamlined the Covid-19 testing process, and how ZenHub is helping them do it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KcDJA5C1pg-kuqyLoguhIQ.jpeg" /></figure><h3>The challenge</h3><p>Philippine Red Cross is the largest Covid-19 testing lab in the Philippines; they are responsible for 25–30% of all tests done nationwide. For a country with a population of nearly 110 million, this is no easy feat! To accomplish testing at this scale with the efficiency that they do, they’ve utilized technology to automate as much of the process as possible.</p><p>In response to the crisis, Philippine Red Cross has built the<strong> </strong><a href="https://c19.redcross.org.ph/"><strong>Red Cross Covid-19 Platform</strong></a> — an efficient, streamlined system to manage the tracking of Covid-19 tests. When a patient is swabbed, their information is coupled with the test specimen, and this is tracked throughout each step of the process, from intake to the Red Cross lab. This allows Philippine Red Cross to accurately estimate when results will be ready, as well as automate the delivery of negative results.</p><p>An operation of this scale is not without its challenges. For example, one area that needed improvement was the registration of individuals who needed to be tested. At the beginning, Philippine Red Cross relied on paper forms. However, this led to both disorganization and invalid data. Forms were filled in with erroneous or illegible information, such as misspelled names or incorrect dates. These paper forms were then sent off to be entered into the system by volunteers — another point in the process vulnerable to error, where information could be accidentally miscoded. Incorrect information compromised the ability of the testing labs to deliver results. Delays meant individuals often waited up to a week to get their results.</p><p>To combat this, Philippine Red Cross applied significant changes to the way patient information gets associated with testing swabs. Instead of relying on paper forms, that were error-prone and time-consuming, the Red Cross Covid-19 Platform digitized this process. Every person traveling into the Philippines must be swabbed and tested at the airport before they can enter the country. Patients are required to register information three days before their flight, capturing personal information before they even fly. Once they land at the airport, they get swabbed and enter an approved hotel to begin their quarantine period until they receive negative test results. The patient’s test swab is registered to their personal information.</p><p>Digitizing patient information not only keeps things organized — it also allows for more efficient communications throughout the process. Passengers are provided a tracking code, which follows their specimen through the lab. Passengers are able to see exactly which step of the process their test results are in, which manages expectations and prevents additional stress during a difficult time. Additionally, with the Covid-19 Platform,<strong> the Red Cross has substantially sped up the delivery of results. Instead of waiting a week, patients are able to get results in under 48 hours.</strong> The impact of this is significant — less time waiting means people get to go home to their families sooner.</p><p>Philippine Red Cross handles more than just airport testing — they also manage the testing done at government-mandated testing centers as well as mobile swabbing for emergencies. For example, as Red Cross developer Martin Gomez explains, when borders for other cities were shut down, a mobile swab team was deployed to be able to test individuals before allowing them to return home.</p><p>As you might imagine, managing the testing of millions of individuals leaves various points in the process vulnerable to disorganization or inefficiency. Just like with the digitizing of intake forms, Philippine Red Cross has applied their learnings to streamline various parts of the process. One way they have done this is by introducing ZenHub as a way to manage their project.</p><h3>ZenHub, as part of the solution</h3><p>As a volunteer-based organization, Philippine Red Cross has unique needs. Like an open-source project, the development of the project relies on a large team, with each engineer contributing in a limited and unpredictable capacity. However, the management team requires accurate project tracking and predictable timelines. ZenHub helps them meet these specific needs, with solutions that cater to Philippine Red Cross’ various stakeholders.</p><p>Bryan Giger and Philly Tan, two developers on the project, recommended ZenHub after having used it in the past. They were having difficulties keeping their work organized, and they felt that ZenHub might provide a solution to some of their problems. For example, meeting minutes were recorded with Google Docs. However, this sometimes meant that action items would get left behind or forgotten. To fix this, they looked to ZenHub as a unified dashboard where they’d be able to see all information pertaining to their project. Harry Paragas, another developer on the project, explained that he felt Zenhub would increase efficiency across the project, and provide oversight and visualization of the process.</p><p>The team was able to set up ZenHub for their project with relative ease. The first step was to create a GitHub repository, and the second was to create Issues representing pieces of work. Once these prerequisites were met, they were able to begin using ZenHub. Their project management repository is used in conjunction with frontend, backend, tooling, and management repositories. As Bryan explains, almost all work has both business and development elements. <strong>Other project management solutions weren’t able to work for both business and development needs, but ZenHub was able to manage both sides in one tool.</strong> They can use Dependencies to mark with Issues that are blocking other Issues, even when these Issues don’t live in the same repository.</p><p>The organization has three types of users that benefit from ZenHub in different ways — developers, management, and the chairman.</p><p>The development team’s biggest priority is to progress the project as quickly as possible. The team is largely volunteer-based, which brings about specific challenges. For example, many developers on the project work in a limited capacity. To maximize the output of this team, volunteers are given tasks with less complexity and requiring less time commitment, leaving the core team to focus on the most complicated issues. New volunteers are given non-critical tasks until they’ve demonstrated engagement and interest in the project. ZenHub’s estimation feature gives the core team a way to easily communicate the prioritization and complexity of tasks with a wide team. This allows the team to utilize developers in the most effective way.</p><p>Because of the way ZenHub is built on top of GitHub, volunteers are able to work with the project right inside of GitHub. Issues can be triaged, labeled, and assigned to volunteers, and information stays synced with the ZenHub Board, without the volunteer ever needing to install ZenHub. As Issues are closed inside of GitHub, ZenHub’s Board, Reports, and Roadmaps are automatically updated. Code commits and Issue progress all live in one place, making it easy for volunteers to communicate the status of their work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ld0ZQif5Lmyum_B8.png" /></figure><p>The management team uses ZenHub to organize and assign work. Philippine Red Cross uses <a href="https://blog.zenhub.com/working-with-epics-in-github/"><strong>ZenHub’s Epics to organize work</strong></a> — at the start of each month, the team identifies the most important pieces of work. Epics are created, with an Epic representing each individual product or feature. Related tasks are grouped together. Epics ensure that no task is missed, and allow the management team to assign work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/995/0*yHv-IUH1jlYVyo8H.png" /></figure><p>Because the requirements of the project are constantly changing, it is critical that the team is able to react quickly and work iteratively. As Harry explains, optimization is rapid and a lot of flexibility is required. The team has optimized their process to move fast — work is reprioritized as needed, resources are reallocated when things finished early, and completed features are deployed as soon as they’re ready, with the team releasing changes every two days or so.</p><p>Additionally, the <a href="https://www.zenhub.com/reporting"><strong>ZenHub Reporting Suite</strong></a> gives the management tool better insight into the progression of their work. It is clear exactly which Issues are prioritized, and the team can see what they hope to accomplish in the upcoming time period. The Burndown Chart allows the management team to keep track of sprint progress, and ensures that no work falls through the cracks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*vFeeT3b7TuLZa1sZ.png" /></figure><p>The Control Chart communicates how good the team has been at closing Issues that have been created, and identifies any bottlenecks in their process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bLxYgd0mnXF0UQky.png" /></figure><p>The chairman relies on ZenHub to see the big picture. The <a href="https://www.zenhub.com/roadmaps"><strong>ZenHub Roadmapping </strong></a>tool is ideal for this. It integrates with the Epics set up by the management team, which allows the chairman to see the progress of each task in one visualization. Additionally, the Roadmapping tool places the Epics into one comprehensive timeline. The chairman can tweak deadlines as needed, and the management team can see how their actual progress matches up to the pace they need to work at to meet these deadlines.</p><p>Despite the various challenges and limitations, the Phillipine Red Cross team is doing amazing work during an incredibly difficult time. The progress they have made is a true testament to the dedication of their team. That being said, this is only the beginning of their journey. They are still looking to expand their labs to be able to handle a greater volume of tests, with new labs opening up across the country.</p><p>ZenHub couldn’t be more honored to be a part of this undertaking. If you’d like to follow their story or get involved, they can be found on their website: <a href="https://redcross.org.ph/"><strong>https://redcross.org.ph/</strong></a>.</p><p>The post <a href="https://blog.zenhub.com/how-zenhub-is-helping-philippine-red-cross-fight-covid-19/">How ZenHub is helping Philippine Red Cross fight Covid-19</a> appeared first on <a href="https://blog.zenhub.com/">ZenHub Blog.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ad8a65a688e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meet Automated Workflows: Automate hand-offs, 
status updates, and more!]]></title>
            <link>https://zenhub.medium.com/meet-automated-workflows-automate-hand-offs-status-updates-and-more-3cb0c65465f4?source=rss-1d8c444e0857------2</link>
            <guid isPermaLink="false">https://medium.com/p/3cb0c65465f4</guid>
            <category><![CDATA[developer-productivity]]></category>
            <category><![CDATA[automation-tools]]></category>
            <category><![CDATA[workflow-automation]]></category>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[project-management-tool]]></category>
            <dc:creator><![CDATA[Zenhub]]></dc:creator>
            <pubDate>Tue, 15 Sep 2020 18:25:27 GMT</pubDate>
            <atom:updated>2020-09-15T18:25:27.247Z</atom:updated>
            <content:encoded><![CDATA[<h3>Meet Automated Workflows: Automate hand-offs, status updates, and more!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t2Ij6Re4gk4CAKglYHSJpA.jpeg" /><figcaption>ZenHub Automated Workflows</figcaption></figure><p>At ZenHub, we envision a future where no one has to “do” project management. A solution where projects manage themselves based on the work performed and completed. We aim to bridge the communication gap between development teams and the rest of your organization without any additional effort. Plain and simple, that is our mission.</p><p>We started as the first kanban board for GitHub and quickly evolved from a single repository board into a multi-repository view. Last year, we launched Workspaces, giving every team the flexibility to personalize their individual space and decide the preferred steps in their workflow. For example, every team in the organization can follow their own Agile methodology. Whether it is Scrum or Kanban, teams can create their own workflow over the same set of underlying GitHub issues.</p><p>Since then, one common problem we’ve heard from new and existing teams is, “it takes too much effort to update the status of my work across my team, teams I’m working with, and again to other stakeholders in the company.” And we heard the same sentiment from the stakeholders as well: managing progress from a “bird’s eye view”, needing to go to every team for updates, having to be the point of contact and the source of delays.</p><p>Today, <strong>we are thrilled to announce Automated Workflows</strong>, the first solution of its kind that brings workflow automation to project management and development tasks all within GitHub.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w_nCSpQaOjIT4wpdPci0Ew.gif" /></figure><p>With <a href="https://www.zenhub.com/automated-workflows">Automated Workflows</a>, each team can continue working through their unique workflow while communicating their progress to a collective team Workspace. Automated Workflows allows pipelines in different Workspaces to be synchronized to automate hand-offs from one team to the next. This opens up the possibility of breaking a large, shared Workspace down into smaller teams.</p><h3>Surfacing the “Big Picture”</h3><p>As we looked into the problems of cross-team communication, we quickly discovered that not every team is structured in perfect team sizes and standard roles. Some organizations form multiple engineering teams with a single QA team; others have dedicated QA team members on every development team. No matter the team size, defined roles per team, or even the strength of an individual team’s process, every team struggled to see how everything connects together.</p><p>We saw project stakeholders and team leads often don’t have the time to click through an individual team’s Workspace to understand the progress of key initiatives. Despite that, they still need to remain informed on progress in order to address potential blockers and communicate new product enhancements and features to customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DI33bCbC4_tHbtdOQz6ZIQ.png" /></figure><p>Automated Workflows grants stakeholders a “big picture” by aggregating individual team updates into a single view. By funneling each team’s “In Progress” issues into a single pipeline or by separating each team into their own pipelines (see image above), stakeholders now have an automated view of everything happening across their development teams.</p><p>As a result, management and stakeholders no longer need to ask developers to provide updates or hold meetings with multiple teams to understand and verify the state of a project. Together with ZenHub’s Roadmap view, executives and stakeholders can get an always accurate view into the status of a project.</p><h3>Eliminate manual hand-offs between teams</h3><p>Throughout the lifecycle of a development project, there are typically a number of hand-offs that occur between teams, such as in moving from design to development or development to QA. Each hand-off represents an opportunity for delays if the status of a task is not properly communicated. To avoid these potential delays, teams are typically forced to schedule meetings or overload the team with messages and notifications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7aasLM6zm0UYkT9x9-8H-w.png" /></figure><p>Automated Workflows puts an end to this by allowing the movement of issues in one team’s Workspace to trigger the movement of issues in another team’s Workspace. For example, if an issue is moved from “In Progress” to “Ready for QA” on the development team’s Workspace, Automated Workflows can trigger the movement of that same issue to the “Backlog” on the QA team’s Board, signaling it is ready to be prioritized by a member of the QA team.</p><p><strong>Every ZenHub team has access to Automated Workflows. Learn everything you need to know to hit the ground running with Automated Workflows in our upcoming webinar next week! </strong><a href="https://go.zenhub.com/automated-workflows-in-zenhub"><strong>Save my spot!</strong></a></p><h3>What’s next? More automation!</h3><p><a href="https://www.zenhub.com/automated-workflows">Automated Workflows</a> is the first major piece in a series of automation improvements throughout ZenHub. Next, we’ll be focusing on automating the connection between issues and pull requests through <a href="https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword">GitHub keywords</a> as well as allowing a pull request to be connected to multiple issues at the same time — the two biggest requests we’ve received from developers.</p><p>Speaking of developers, we will also be improving the experience for them throughout ZenHub. Some of these improvements include: enabling reviews and reviewers on the Board, seeing the issue-pull request connection in the Closed pipeline, automating sprint schedules, and viewing the most up-to-date pull request status throughout the app. Keep an eye open over the next couple of months to see these changes pop up in ZenHub!</p><p>Another substantial focus of the series: creating automation rules based on changes to your issues and pull requests. What does this mean for you and your team?</p><ul><li>When an issue receives the “In progress” label, move the issue to the “In progress” pipeline</li><li>When you move an issue to the “In progress” pipeline, assign yourself</li><li>When an issue receives an estimate, move it to your “Backlog” pipeline</li></ul><p>These are just a few examples and, of course, we’ll make sure to allow for full customization based on your team’s unique workflow. Do you have your own ideas of how you would use this type of automation? <a href="https://portal.productboard.com/zenhub/1-zenhub-s-roadmap/c/100-issue-and-metadata-automation">Add your thoughts here!</a></p><p>As always, we relied on an enormous amount of feedback received through our <a href="https://portal.productboard.com/zenhub">open product roadmap</a>. We may not reply to every piece of feedback but we definitely read through and categorize each piece. Thank you to those who followed up with us on Automated Workflows and spoke with us in design discovery and user testing sessions to help shape what we delivered today.</p><p>That’s all from us for now. Stay tuned!</p><p>Not using ZenHub? Sign up today for a <a href="https://www.zenhub.com/signup">free 14-day trial.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3cb0c65465f4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ZenHub vs. GitHub Projects for agile software development]]></title>
            <link>https://zenhub.medium.com/zenhub-vs-github-projects-what-are-the-key-differences-eeafbf477183?source=rss-1d8c444e0857------2</link>
            <guid isPermaLink="false">https://medium.com/p/eeafbf477183</guid>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Zenhub]]></dc:creator>
            <pubDate>Mon, 31 Aug 2020 20:32:30 GMT</pubDate>
            <atom:updated>2021-06-17T22:36:11.441Z</atom:updated>
            <content:encoded><![CDATA[<h3>ZenHub vs. GitHub Projects: Which is the best agile project management software?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ioYbumr3pukW-rjNEvnafg.jpeg" /></figure><p><em>Editor’s note: This article has been updated in June 2021. Originally published at </em><a href="https://blog.zenhub.com/zenhub-vs-github-projects-what-are-the-key-differences/"><em>www.zenhub.com.</em></a></p><p>We love GitHub. We love what it does for product leaders and development teams. We love that it’s become the place “where the world builds software.” We understand why some teams feel GitHub Projects is the natural place for project management, but we also know that sometimes teams need more — more collaboration, more automation, and more reporting — to get their sprints sprinting faster. That’s why we built ZenHub.</p><p>We are often asked what’s the difference between ZenHub and GitHub Projects (and it’s a great question). We created ZenHub to seamlessly bridge the gap between the people facilitating the work and the people doing the work.</p><p>In this post, we answer how ZenHub’s various features work together to give everyone — from developers to product owners to business stakeholders — a complete view of project progress and more.</p><h3>What is ZenHub?</h3><p>ZenHub is the only purpose-built agile project management solution built directly into GitHub for GitHub users. Its simple browser extension or web app allows teams to add powerful tracking, planning and reporting features to their GitHub instance, so they can make their agile development processes even more agile and maximize team efficiency. With ZenHub, project leads, Scrum Masters, and business stakeholders can quickly see when a project is on track and when there’s a risk of falling behind.</p><p>ZenHub supports agile development &amp; project management through:</p><ul><li>Single and Multi-Repository Support</li><li>Multi-Organization Support</li><li>Automated Issue Movement</li><li>Set Default Pipeline for PRs</li><li>Estimates &amp; Planning Poker</li><li>Velocity Tracking</li><li>Burndown Charts</li><li>Board Filters</li><li>Automated Workflows</li><li>And more!</li></ul><p>For comparison, let’s take a look at GitHub Projects next.</p><h3>What is GitHub Projects?</h3><p>GitHub Projects is one feature in the larger GitHub suite that allows product managers and developers to coordinate, track, and update their work. With GitHub Projects, users can organize work by project status, add tasks, share their work, and see activity on a project.</p><h3>Set the standard for your next sprint: agile product management &amp; development with ZenHub</h3><p>With ZenHub, developers can focus on coding and product managers can focus on managing timelines, backlog grooming, and progress all in one place. No context switching between tools, no interrupting co-workers to get their input on estimates, or check in on their progress. The addition of Automated Workflows means that teams can bypass common friction points, like confusing hand-offs of tasks from one team to the next.</p><h3>Boards and Workspaces</h3><p>Everybody loves the simplicity of a Kanban board, which is probably why boards are the foundation of both ZenHub and GitHub Projects. In ZenHub, Teams can create multiple Workspaces with a board within each Workspace. Each Board allows you to see all your team’s work (in GitHub Issues) and priorities in one place. Set up pipelines that map to each stage in your workflow pipeline and add Issues for each individual issue so that everyone knows what tasks are moving forward and which ones might be lagging behind.</p><p>ZenHub’s Workspaces have some additional functionality that makes filtering views a whole lot easier; you can filter by sprints and epics. While the ability to add labels is available in GitHub, ZenHub lets you add a “high priority” flag, so you can get an even more granular look at the work that’s happening. This added refinement makes ZenHub powerful for both developers and product owners.</p><h3>Epics</h3><p>To track larger bodies of interconnected work that may span multiple weeks and sprints, <a href="https://blog.zenhub.com/working-with-epics-in-github/">ZenHub Epics</a> give you the power to track several Issues needed to complete a larger goal (for example, a new feature release) while also tracking interdependencies between tasks.</p><p>ZenHub’s Epics add a crucial extra layer of hierarchy to your GitHub Issues by making it easier and more efficient for managers and product owners to have end-to-end control over the release process. For folks operating in Agile, scrum-based teams, Epics ought to be your go-to.</p><h3>Predictive Project Roadmaps</h3><p>Product managers can track all the development work in GitHub with Roadmaps. Roadmaps provide a single-window-view into all the projects and epics happening across teams. If your team uses story point estimation, progress bars will show if work is tracking against estimates. Built-in predictive analytics — a feature you can only find in ZenHub — helps PMs automatically assess how long it might take teams to tackle projects in the future based on their past velocity and performance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gTySsEu22rMjtXydwyI4DQ.png" /><figcaption>Predicted end dates on ZenHub Roadmaps</figcaption></figure><h3>Automated Sprint Planning</h3><p>Agile teams using GitHub Projects will likely experience the frustration of having to imperfectly adapt the platform to suit the “Scrum” working cycles, as sprints and epics are not a part of GitHub Projects. This creates a ton of annoying manual work. We wanted to fix this with ZenHub.</p><p>ZenHub’s sprint planning feature allows product managers to create sprints in GitHub via their ZenHub Board or Workspace. Just pick a start and end date, and ZenHub will instantly create a current sprint and two future sprints. And because the sprint planning feature is part of the Workspace where you’re already tracking Issues, product managers can rely on automation for tedious tasks like moving unfinished Issues to the next sprint.</p><p>For teams still using Milestones, ZenHub allows you to attach Milestones to all their relevant repositories across GitHub.</p><h3>Automated Workflows</h3><p>Just because you <em>can</em> do something manually, doesn’t mean you should have to keep doing it that way. We’re probably preaching to the choir when we say this, but automation saves so much time and, more importantly maybe, it frees smart, hard-working talent up to focus on high-value work.</p><p>There are several layers of workflow automation in ZenHub. They’re all designed to either relieve you from manual and repetitive tasks or help to deliver insights and data that make you more effective at planning and executing your work.</p><p>ZenHub’s Automated Workflows allow you to do things like automate hand-offs of tasks between teams and signal a shift in priorities or needs, without having to add more meetings to your calendars.</p><p>Our automation doesn’t just apply to planning work, it also applies to <a href="https://www.zenhub.com/reporting">reporting on development work</a> in progress. ZenHub uses your GitHub data to create real-time updates on the team’s performance (things like tracking story points, issues and pull requests) and the velocity or rate at which teams are accomplishing their work. ZenHub then turns all that data into easy-to-read charts that can be shared with project stakeholders.</p><h3>Planning Poker Estimation</h3><p>Do you loathe long planning meetings where you have to recall previous projects from memory and then just throw out a guess? Us too. Hence why we built our newest feature: Planning poker.</p><p>Planning poker is our way of improving estimation accuracy while also allowing multiple team members to contribute to the process whether in real-time or on their own time (that’s a win-win in our books).</p><p>Product owners and Scrum Masters can use it to request estimates from individuals prior to sprint planning. The estimates are applied directly to Issues in GitHub, making it effortless for technical folks to provide an estimation and then get back to work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n_iL3Wg9loW4avGG1p6UKQ.gif" /><figcaption>ZenHub’s planning poker</figcaption></figure><p>The data generated by the estimates leads to more accurate planning discussions. Estimates that the team agrees on will be automatically applied. Product owners and Scrum masters can easily spot outlier estimates (estimates on either the higher or lower end) and use that input to have a more focused discussion with the team, only discussing Issues that the team didn’t agree on. Simply put: you get more efficiency in fewer meetings.</p><h3>One tool to rule them all…</h3><p>GitHub has proven to be a powerful tool for developers. Our main mission with ZenHub is to build on that incredible foundation and provide tools that bring even more pivotal members of the production team together, namely product owners and managers. We know from experience that the best work happens when these two functions come together seamlessly under one virtual roof.</p><p><strong>So, when it comes to the question of “ZenHub vs. GitHub Projects?”. The answer is — what is your team trying to accomplish?</strong></p><p>For teams just started out with project management in GitHub, GitHub Projects may provide enough basic capabilities to get started down this path.</p><p>ZenHub is ideal for teams that:</p><ul><li>Want to improve their Agile processes and ship faster, using Kanban, Scrumban, or Scrum</li><li>Want automation for common Scrum events, like sprint planning and planning poker</li><li>Don’t want all the added complexity, fluff, and set-up overhead that big-name project management tools bring</li><li>Need reporting, like velocity reports and burndown charts, to show their teams progress and efficiency</li><li>Are part of a “team of teams” and need a tool that has the ability to scale and handle multiple teams, projects, and priorities</li><li>Need something more powerful to provide stakeholders added visibility into their workflow</li></ul><p>Ready to see how ZenHub can transform your team’s project management process? <a href="https://www.zenhub.com/sign-up?utm_source=blog&amp;utm_medium=post&amp;utm_campaign=gh-projects-relaunch">Give it a try today with a free trial</a>.</p><p>Want to learn how top performing teams ship faster by doing project management in GitHub? <a href="https://www.zenhub.com/ebooks/github-project-management?utm_source=blog&amp;utm_medium=post&amp;utm_campaign=gh-projects-relaunch">Download our free eBook</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eeafbf477183" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ZenHub’s move to Kubernetes]]></title>
            <link>https://zenhub.medium.com/zenhubs-move-to-kubernetes-22bf0256381?source=rss-1d8c444e0857------2</link>
            <guid isPermaLink="false">https://medium.com/p/22bf0256381</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Zenhub]]></dc:creator>
            <pubDate>Thu, 20 Aug 2020 17:18:07 GMT</pubDate>
            <atom:updated>2020-08-20T17:18:07.579Z</atom:updated>
            <content:encoded><![CDATA[<p>ZenHub recently migrated its entire production and CI/CD infrastructure to Kubernetes. This blog post documents the history of containers at ZenHub, why we eventually went with Kubernetes, how we got there, and what we are looking to accomplish in the future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oxznkdTVEb2vYePJLbIHfg.jpeg" /></figure><p>When I joined ZenHub, almost 2 years ago, our deployment process was a script in TravisCI that manually deployed the frontend and backend code to AWS VMs. It had problems, one of the biggest was not always updating all of our VMs, causing debugging headaches. We began to research improved deployment solutions and it became clear containers were the way to go. Docker has all but becomes the standard container system, and in addition, our on-prem customers were asking for ZenHub to be deployed via containers instead of a VM.</p><p>We researched container deployment technologies and settled on Docker Swarm because it was cloud-agnostic and relatively easy to understand with a small scope of features. After getting our application running inside Docker containers, we started to build out Docker Swarm and additional tools needed to complete the infrastructure:</p><ul><li><a href="https://www.terraform.io/">Terraform</a> to manage the base cloud infrastructure on GCP.</li><li><a href="https://www.packer.io/">Packer</a> to create base images for VMs running Swarm workers.</li><li><a href="https://www.consul.io/">Consul</a> to store application configuration and operate as service discovery.</li><li><a href="https://www.vaultproject.io/">Vault</a> to store application secrets.</li><li><a href="https://www.jenkins.io/">Jenkins</a> to handle CI and CD <a href="https://pritunl.com/">Pritunl</a> to manage access to internal service access.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w1VvduAR1eYnE4t9tOGClQ.jpeg" /><figcaption>ZenHub’s first container-based infrastructure</figcaption></figure><p>ZenHub’s first container-based infrastructure After all these tools were set up and ZenHub was running on Docker Swarm we started to feel the pain of having a completely self-built system. In isolation, each tool is very powerful, but gluing them all together was difficult and hard to manage for our team of 2 dev-ops engineers. The glue became very fragile, and we were not confident in making changes to the infrastructure. Besides, it was hard for developers to inspect the running system to debug application problems. Ingesting and searching logs, running one-off commands, inspecting configuration required finding the VM where the docker service was running, SSHing into that instance, finding the container ID, and finally running the correct docker commands. This was tedious and annoying to perform on a daily basis or when solving problems.</p><h3>Why Kubernetes?</h3><p>After running Docker Swarm for around one year we came together to review the infrastructure we had now and discuss if we wanted to migrate. We unanimously decided to investigate using Kubernetes, hosted by GKE, to run our container infrastructure. It would solve many of the headaches we were having with our current Docker Swarm infrastructure, and also set us up to deliver Kubernetes to our on-prem customers that have been requesting it.</p><p>After a week-long spike, we were able to run the ZenHub application in Kubernetes locally and on GKE. We reviewed the outcome with the team and decided to continue refining our implementation. We picked a few tools to help us:</p><ul><li><a href="https://www.terraform.io/">Terraform</a> to manage the base cloud infrastructure on GCP.</li><li><a href="https://helm.sh/">Helm</a> to template our Kubernetes resources across multiple environments.</li><li><a href="https://github.com/roboll/helmfile">Helmfile</a> to manage multiple sets of configuration and secrets for each environment.</li><li><a href="https://github.com/mozilla/sops">SOPS</a> to allow us to commit encrypted secrets to our Helm chart repository.</li><li><a href="https://buildkite.com/">Buildkite</a> for CI/CD.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NpT9qlZ0ALBtW3p2vlQR0w.jpeg" /><figcaption>ZenHub’s Kubernetes based infrastructure</figcaption></figure><p>ZenHub’s Kubernetes based infrastructure Along with deploying Kubernetes we had the challenge of picking a new CI/CD system. Our previous infrastructure used Jenkins, which is a very powerful tool but suffered from the same general problem as our previous infrastructure: it was hard to set up and manage. We also briefly researched using <a href="https://cloud.google.com/cloud-build">GCP’s Cloud Build</a> but, unfortunately, it cannot connect to VPCs. So if we wanted to use it, it would require us publicly exposing our Kubernetes cluster, which we did not want to do for security concerns. We eventually settled on Buildkite: it provides a great Web-UI and integration with GitHub and allows you to run their build agents inside of your own infrastructure. This gives you a lot of flexibility in how they are set up and configured but avoids you having to manage any of the glue. As soon as you have build agents running you can start creating pipelines in your repositories and triggering builds via GitHub. It also provides additional security since you don’t have to allow connections from outside of your infrastructure.</p><p>After two more weeks, we had our staging environment migrated to Kubernetes, and after another few weeks of improvements and testing, we started migrating traffic from our existing Docker Swarm infrastructure to our new Kubernetes infrastructure.</p><p>We immediately gained massive useability improvements:</p><ul><li>Logs were automatically ingested and parsed (JSON) for easy searching, filtering, and metric creation.</li><li>GKE provides a relatively simple web interface for quickly inspecting the state of the cluster and each deployment.</li><li>For developers, accessing the cluster was trivial using kubectl commands.</li><li>Simple autoscaling via CPU metrics.</li><li>Easier understanding of how our application is deployed and how to make changes to it.</li><li>Fine-grained permissions via RBAC to grant access to specific Kubernetes resources.</li></ul><h3>Learnings</h3><p>Everything wasn’t perfect however, we did run into a few gotchas as we rolled out Kubernetes:</p><ul><li>Helm’s templating syntax (<a href="https://golang.org/pkg/text/template/">Go templates</a>) leaves a lot to be desired, and can sometimes be confusing to read and use.</li><li>Kubernetes resources can be killed and rescheduled when cluster nodes are “rebalanced” — you must set up a <a href="https://kubernetes.io/docs/concepts/workloads/pods/disruptions/">PodDisruptionBudget</a> to control how and when this happens. This bit us with long-running Kubernetes jobs that were created right after scaling down other resources: the cluster would reclaim nodes that were no longer needed, which sometimes involved killing the job while it was running, and restarting it on another node.</li><li>Having multiple docker images deployed by a single Helm chart is hard to manage: you need to either know all the image tags at deploy time or be OK with deploying a default image tag (ie. master/production) which may trigger an unnecessary deployment update.</li></ul><p>We are still refining our Kubernetes deployment and have some ideas to explore in the future:</p><ul><li>Improved autoscaling via custom metrics.</li><li>Using Kustomize, instead of Helm, to configure our Kubernetes resources. We hope this will help fix our Helm deployment problem mentioned above and give the modularity needed to push forward with per pull request environments and ZenHub Enterprise.</li><li>Packaging ZenHub Enterprise 3 using Kubernetes and rolling it out to our on-prem customers.</li></ul><p><strong>Where are we today?</strong> Overall we are very pleased with Kubernetes and our new infrastructure. There are still many things to improve but, in general, we are in a much better position than we were with Docker Swarm.</p><p>Our infrastructure is more stable, easier to scale and modify, and (maybe most importantly) easier to understand. We also gained better insights via the out-of-the-box metrics provided by Kubernetes and GKE, and finally, we improved our security via GCP IAM and Kubernetes RBAC.</p><p><strong>So, what’s next?</strong> Currently, we are focusing our efforts on bringing this new Kubernetes based infrastructure to our on-prem customers so they start seeing some of the same benefits.</p><p><strong>We surveyed over 500 software engineers, developers, and project managers to find out what happens when a software development team adopts ZenHub. </strong><a href="https://blog.zenhub.com/what-happens-when-a-software-development-team-adopts-zenhub/"><strong>Read the results!</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22bf0256381" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My transition into Product Management from Customer Success]]></title>
            <link>https://zenhub.medium.com/my-transition-into-product-management-from-customer-success-9b67c92d2da6?source=rss-1d8c444e0857------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b67c92d2da6</guid>
            <category><![CDATA[company]]></category>
            <category><![CDATA[professional-development]]></category>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Zenhub]]></dc:creator>
            <pubDate>Tue, 28 Jul 2020 17:40:57 GMT</pubDate>
            <atom:updated>2020-07-28T17:40:57.141Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9FNkQWqQmCwYLZutcnA2Gw.jpeg" /></figure><p>Earlier this year I switched my career path from Customer Success to Product. Working as a Customer Success Manager had been a natural fit — I’ve always loved working with people and enjoyed the challenge of fully understanding a customer’s needs, then finding a creative solution for them.</p><p>I find that so much of the work a CSM does with customers is on the periphery of the product, rather than in the product directly. Coaching on best practices has just as much to do with the team and their processes as it does with teaching product knowledge. I spent a lot of my time trying to understand a customer’s goals and developing a plan to get them there. I would capture these needs, collect feedback, and act as the customer’s advocate within ZenHub.</p><p>More and more, however, I found myself getting curious about the product itself. I started to wonder if there was a way to solve these problems before they even got to the customer. Instead of me anticipating the needs of the customer and providing them support resources, how could the product anticipate their needs?</p><p>Armed with this curiosity (and a few other factors) I decided to make the leap into a Product Owner role. There’s been a steep learning curve, as expected, and I still have a long way to go. However, I truly believe that my background in CS has given me a unique perspective and valuable set of skills that have helped me in this transition.</p><h3>Walk a Sprint in their shoes</h3><p>Most obvious is the user perspective; as anyone in product already knows, looking at the product from the user’s point of view is absolutely vital. But sometimes you end up too close to the product, and too far from the user.</p><p>Recently I was working on a project around onboarding new users into ZenHub, and I found myself stuck. Then I thought to myself, how did I used to explain this to customers? What features did I start with? When you’re talking to a customer, you get instant feedback: “I don’t get it” or “that’s really cool! I can see how that will save me time”. I used this experience to guide the project and ensure I’m starting from the most logical point.</p><h3>Sometimes solutions are the problem</h3><p>Talking with customers every day is a good reminder that usually they know a lot more than you! Our users are subject matter experts, and many have spent their entire careers working in this field. Our users provide excellent feedback, and it’s important to listen to what they’re saying. What’s equally important though, is identifying the underlying problem, not just the symptoms.</p><p>Due to the nature of ZenHub, our user base is made up of people who love to build things. This resourcefulness is what makes them so wonderful to work with, but also means they often provide feedback in the form of solutions — a skill that is incredibly useful in every other application, except for product feedback! I learned in CS to dig into this feedback, to prod and poke until I understood the real challenge.</p><p>In fact, understanding the true pain point is how ZenHub was created. Several years ago, a Project Manager in our parent company, Axiom Zen, introduced a new project management tool. The engineering team was initially resistant, and the PM had a difficult time getting the team to keep their project status up-to-date (a challenge I’m sure many of you can relate to). Instead of making assumptions about why this process wasn’t being followed, the team dug deeper into the issue. They were able to uncover the real pain point: context switching between GitHub and the other tool slowed the engineers down and interrupted their flow of work. The team came up with the idea to build project management directly in GitHub, and thus ZenHub was born.</p><h3>You can’t always get what you want</h3><p>The hardest lesson I learned in CS is that if you try to please everyone, you risk pleasing no one. Being clear about the value of the product and demonstrating how it’s meant to be used, is a key part of ensuring success for your users. But it’s also important to be upfront about what the product is not designed to do.</p><p>I’ve seen customers adapt ZenHub for use cases we never could have imagined. It’s incredible to see how innovative our users are, and it’s wonderful when these creative solutions are able to address an ongoing pain point. However, no tool does it all, and your users will appreciate your directness. Communicate the rationale behind product decisions and the best practices that the tool is designed for. This will build credibility with the users and help them implement better practices for their teams.</p><h3>So, what’s the takeaway?</h3><p>If I could share one piece of advice, it’s to get in front of your users as much as possible. I credit some of my most valuable attributes as a Product Owner — empathy, curiosity, and communication skills — to the time I spent working one-on-one with users. Oh, and become best friends with your local CSM. They’re full of amazing insight and usually ahead of the curve in customer’s trends. Plus, their middle names are literally ‘Success’. What more could you ask for in a friend?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b67c92d2da6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Difference Between Agile and Design Thinking]]></title>
            <link>https://medium.com/axiomzenteam/the-difference-between-agile-and-design-thinking-45f99d41b771?source=rss-1d8c444e0857------2</link>
            <guid isPermaLink="false">https://medium.com/p/45f99d41b771</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Zenhub]]></dc:creator>
            <pubDate>Tue, 13 Jun 2017 20:32:19 GMT</pubDate>
            <atom:updated>2017-06-16T23:30:16.407Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*DhBU9B2_4IDpbE3LVvjPsQ.jpeg" /></figure><p>It’s been over a decade since Agile methodologies took over the world of software development. While large corporations are often still enmeshed in the structures of old, startups and other tech companies have learned another way. <strong>Agile has seen such an incredible success</strong>, increasing team output by <a href="https://www.infoq.com/articles/standish-chaos-2015">as much as 28%</a>, that savvy project managers are beginning to apply those Agile principles to disciplines outside of development.</p><p>But meanwhile, other disciplines have taken their own trajectories towards innovation. Design Thinking is one of those paths. It’s made its way up the ranks through project management and design departments. In the last five years the tech industry has seen major companies taking on their own versions of this process, from Google to IBM.</p><p>Now, <strong>the two schools of thought of Agile and Design Thinking are beginning to intersect.</strong> Companies are being faced with a new conundrum: a difference in language. One of the biggest reasons for failure in software development is communication breakdown. If one department is sprinting while another is diving into a workshop process, it can cause chaos — until you realize there is no wrong way to embrace innovation. <strong>These philosophies are really sets of tools and processes</strong>, and not only do you need to choose what works for your company — you can actually choose more than one.</p><p>The answer to which is the best is simple: <strong>yes.</strong></p><h3>Wash, rinse, repeat</h3><p><strong>Agile is an umbrella term that describes a philosophy of work more than the actual tools and processes that are used by its proponents</strong>. Agile is all about iterative loops; the heart of the movement is having cross-discipline teams that work from the ground up, never passing an idea along the chain. Instead they build together in short bursts, cycling back to iterate and address changing needs as new information becomes available.</p><p>The term Agile was coined by <a href="https://techbeacon.com/agility-beyond-history%E2%80%94-legacy%E2%80%94-agile-development">a group of technology thought leaders</a> (and spirited rivals) working on Extreme Programming, Adaptive Software Development, Scrum, and other techniques, who realized that their values and philosophies aligned. They came together to form a movement, something that was intended as a philosophy as much as a set of processes. That philosophy was straightforward: a determination to rely on rapid empirical feedback and full transparency.</p><p>From its origin in 2001, Agile rapidly overtook its roots as a bootstrapped ideation for startups, gaining prominence in large organizations such as <a href="http://contentmarketinginstitute.com/2015/04/agile-content-development-icc-panel/">Facebook and Google</a>. Small teams in Fortune 500s began to play with the idea, bringing sprints and standups into their offices, and other disciplines eyed the prize, realizing this format worked best when everyone was on the same page. Agile was eating software.</p><h3>Embrace the sticky note</h3><p><strong>Meanwhile, Design Thinking was following a similar development.</strong> The term itself was coined decades ago, in Herbert A. <strong>Simon’s 1969 book The Sciences of the Artificial, to refer quite literally to the way designers come up with new ideas.</strong> From there the term broadened and generalized, moving from design to architecture to teaching before landing, in 1991, in the world of business. Even then, Design Thinking was slow to catch on. Technology companies began embracing it slowly over the next twenty years, with mainstream adoption not vaulting up <a href="https://trends.google.com/trends/explore?q=design%20thinking">until 2014</a>.</p><p>Linus Pauling famously said, <strong>“The best way to have a good idea is to have a lot of ideas.”</strong> This is one of the foundational elements of Design Thinking. The philosophy encourages participants to open up and consider every idea, only paring down once every avenue has been explored. It often takes the shape of a week-long working session, where each day is <strong>dedicated to a slightly different avenue: customer interviews, idea creation, prototyping, and testing are generally hallmarks</strong>.</p><p><strong>Design Thinking is best used to come up with a new idea.</strong> It usually starts with a problem, where the shape of the workshop is set in trying to solve that problem.</p><p>There is no one way to explore Design Thinking. <a href="https://www.ibm.com/design/thinking/">IBM’s formula</a> is available for anyone to internalize, while other companies make their living providing Design Thinking exercises to forward-thinking businesses who need a hand getting started.</p><h3>Have your cake and eat it too</h3><p>You may be wondering how much of a struggle it will be to integrate Agile and Design Thinking into your organization. <strong>The truth is, the two philosophies run parallel, not at an intersection.</strong></p><p>Every product starts with a problem you want to solve. Design Thinking is the process by which you discover the shape of that problem’s solution, while Agile is the method you use to refine the solution once it’s been found. <strong>But there isn’t a moment of handoff where you context switch from Design Thinking to Agile.</strong> Rather, it’s a layered process, a soft slide from one to the other.</p><p>The people creating (designers and engineers) absolutely must be in the room during design strategy sessions. This ensures they understand not only the “idea,” but also where that idea came from. Similarly, strategy must stay in the room to help guide the decisions and shifts that are integral to the Agile process.</p><p>Smart companies are already using Agile and Design Thinking in tandem. <a href="http://www.bain.com/publications/articles/agile-innovation.aspx">Bain and Company’s description of Agile</a> assumes that your company will already know about Design Thinking, describing a team’s “initiative owner, who typically comes from a business function and divides his or her time between the Agile team and key stakeholders, [as using] techniques such as design thinking to build a catalog of promising ideas or features. The initiative owner continuously (and ruthlessly) ranks that list based on the latest estimates of value to customers, financial results and other innovation initiatives.”</p><h3>Don’t waste time</h3><p>The first step to incorporating both Agile and Design Thinking into your organization is <strong>making sure everyone is on the same page</strong>. Teams need to understand the philosophy behind both systems, and agree on how to work them into the process. Remember, these aren’t cookie cutters, they’re living (and malleable) solutions. Each organization will have different needs — you won’t get anywhere trying to fit a square peg into a round hole, no matter how great you think circles are.</p><p><strong>Start small.</strong> If your team is already Agile, considering running a Design Thinking exercise for your next feature rollout. Remember, Design Thinking is best for solving the question of “Why,” not “How,” so don’t try to apply it to something where you’re defining a solution, not a problem. Know that you might spend a little more time on this the first few times you do it. Set aside a week to really embrace the process; don’t expect to fit Design Thinking into a weekly Sprint! If you cut it down to a day or two the first time you do it, you won’t get the full benefit.</p><p>If you’re already using Design Thinking and want to integrate Agile, your first step is to <strong>bring developers and designers to your next Design Thinking workshop</strong>. Get them involved from the ground up, and stay involved as they take those ideas and bring them to production. Remember, rapid empirical feedback and full transparency are the keys of Agile. Scrum boards and sprints can come once you’re used to working as cross-discipline teams!</p><p><em>Do you have questions about ZenHub? We’d be more than happy to help on </em><a href="http://www.twitter.com/zenhubhq"><em>Twitter @ZenHubHQ</em></a><em> or </em><a href="/service/mailto:support@zenhub.com"><em>email us directly</em></a><em>.</em></p><p><em>Originally published at </em><a href="https://www.zenhub.com/blog/the-difference-between-agile-and-design-thinking-2/"><em>www.zenhub.com</em></a><em> on June 13, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45f99d41b771" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axiomzenteam/the-difference-between-agile-and-design-thinking-45f99d41b771">The Difference Between Agile and Design Thinking</a> was originally published in <a href="https://medium.com/axiomzenteam">Axiom Zen Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Developers Should Get on the Phone With Customers]]></title>
            <link>https://medium.com/axiomzenteam/developers-should-get-on-the-phone-with-customers-21cbea36629b?source=rss-1d8c444e0857------2</link>
            <guid isPermaLink="false">https://medium.com/p/21cbea36629b</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[general]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Zenhub]]></dc:creator>
            <pubDate>Tue, 30 May 2017 16:30:00 GMT</pubDate>
            <atom:updated>2017-06-15T22:42:29.362Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TeeAVKl-iuEkqTlR858Oxg.jpeg" /></figure><p>There’s a common mantra in the world of software development: “A lot of times, people don’t know what they want until you show it to them.” What companies often fail to remember is that when Steve Jobs came out with that famous quote, he was talking about creating new technology from the ground up, not making an app or debuting a new service. While those areas also require constant innovation, the playing field is incredibly different — and the customer is a much more integral part of the machine.</p><p>Still, innovation is the keyword of the day, and every intelligent business strives to create in a fluid environment. The best of them are adopting agile methodologies for every avenue of business, using sprints and milestones to align engineering, design, and sales departments. Getting those teams on the same page is an important first step, but for many teams, that’s where the journey ends. They forget that the customer is an important part of the circle.</p><p>It’s self-evident that the sales team should have contact with customers, but researchers <a href="http://bear.warrington.ufl.edu/weitz/mar7786/Articles/sethi%20cross-functional%20product%20teams.pdf">Rajesh Sethi and Carolyn Nicholson</a> found that when development teams also engaged directly with end users, they were actually more likely to create successful products (and to be more motivated to work harder). They studied 114 teams, and found that teams that relied more on customers’ input during new product development produced more innovative outcomes.</p><h3>A Meaningful Connection</h3><p>The number one corollary for job satisfaction <a href="https://www.forbes.com/sites/valleyvoices/2017/02/09/developers-dont-care-how-much-you-pay-them/#4cf490e52564">isn’t high paycheques</a>, or team lunches, or foosball tables — it’s mattering. No one wants to work in a vacuum, writing lines of code for a product they never see, or shipping products that no one ever uses. In a <a href="http://www.sciencedirect.com/science/article/pii/S0191308510000067">2010 study</a>, scientists found that finding meaning in one’s work increased motivation, engagement, <em>and</em> job satisfaction. But how do companies manufacture meaning? Not everyone will be employed doing positive works for the greater good, but meaning can also come from something simpler: a direct connection between employees (in this case, developers) and customers.</p><p>The science backs it up. End users who benefit from a company’s products or services are surprisingly effective in motivating people to work harder, smarter, and more productively.</p><h3>Honest Opinions</h3><p>Meeting face-to-face with users can also motivate developers to make changes that they might fight coming from “on high.” Organizational psychologist David Hofmann and journalist Adam Grant have found that employees tend to see <a href="https://hbr.org/2011/06/how-customers-can-rally-your-troops">end users as more credible</a> than team leads. The user doesn’t have an agenda — they won’t just tell you what they think you want to hear — which can make their opinions feel more valuable, and more reliable.</p><p>In the book “<a href="https://www.kirkusreviews.com/book-reviews/michael-a-cusumano/microsoft-secrets/">Microsoft Secrets</a>,” a lab manager described how developers immediately empathized with users they met in person, even when before those concerns would have been brushed off. “The usual nonsense answer — ‘Well, they can just look in the manual if they don’t know how to use it,’ or ‘My idea is brilliant; you just found ten stupid people’ — that kind of stuff just goes out the door.” A face-to-face connection with end users causes a stronger emotional connection among the developers, motivating them to design software with users in mind.</p><h3>Designing With People in Mind</h3><p>Of course, meeting with end-users has one final benefit: being able to truly understand them as human beings. It’s one thing to hand developers a deck describing “Christopher Condo Owner” and “Sally CEO,” but those are archetypes, not people. A truly human connection can only be created by listening to their stories, ideally by phone or in an electronic face-to-face.</p><p>Put your developers on the line — metaphorically, of course — and you’ll be amazed by what they can achieve.</p><p><strong>If you’re new to ZenHub, </strong><a href="http://zenhub.com/"><strong>download it for free</strong></a><strong> and discover how you can spend 52% more time writing code in GitHub, and no time in other clunky project management tools.</strong></p><p><em>Do you have questions about ZenHub? We’d be more than happy to help on </em><a href="http://www.twitter.com/zenhubhq"><em>Twitter @ZenHubHQ</em></a><em> or </em><a href="/service/mailto:support@zenhub.com"><em>email us directly</em></a><em>.</em></p><p><em>Originally published on </em><a href="https://www.zenhub.com/blog/developers-should-get-on-the-phone-with-customers/"><em>The ZenHub Blog</em></a><em> on May 30, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21cbea36629b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axiomzenteam/developers-should-get-on-the-phone-with-customers-21cbea36629b">Developers Should Get on the Phone With Customers</a> was originally published in <a href="https://medium.com/axiomzenteam">Axiom Zen Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Empower Quality Assurance and Developers to Work Together]]></title>
            <link>https://medium.com/axiomzenteam/how-to-empower-quality-assurance-and-developers-to-work-together-aab45ede6b5f?source=rss-1d8c444e0857------2</link>
            <guid isPermaLink="false">https://medium.com/p/aab45ede6b5f</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[general]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Zenhub]]></dc:creator>
            <pubDate>Tue, 09 May 2017 21:41:00 GMT</pubDate>
            <atom:updated>2017-06-15T22:42:02.687Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*2_O__12iup3qAkBCXVV1Ug.jpeg" /></figure><p>The rise of new software engineering trends such as DevOps and continuous integration means that <a href="http://randsinrepose.com/archives/the-qa-mindset/">Quality Assurance</a> (QA) and development are more closely linked than ever — or, at least, they should be. Unfortunately, it isn’t uncommon for testers and developers within an organization to be at odds.</p><p>If you’re practicing agile software development, or thinking about doing so, it’s absolutely critical for QA and developers to interact and work together as often as possible. Here are a few of the most common causes of friction between QA and development — and a list of ways you can work through them.</p><h3>Common QA Complaints</h3><p>Although they’re crucial for the successful release of any software product, QA teams (and testers) often face hostility in the workplace. QA has been described as a “<a href="https://www.linkedin.com/pulse/quality-assurance-impediment-necessary-evil-rajeev-mudumba">necessary evil</a>” of the engineering process, which understandably hurts job satisfaction! No one wants to come to work feeling like their team members dread the feedback they’re there to provide. A hallmark of the waterfall method is that developers and QA are divorced from each other’s workflow. This can be incredibly frustrating for both parties, as simple fixes have to go back and forth many times. It’s especially difficult for QA, however, when their work feels tacked on at the end of the process. Many of their recommendations would be easier to implement sooner, but they aren’t given that option. Instead they feel like an afterthought, which drives dissatisfaction.</p><h3>Common Developer Complaints</h3><p>In traditional software development lifecycles, development is broken into a sequential series of steps. Creating a software requirements specification always comes before building the software, which always comes before testing and deployment. When the engineering team is rushed for time, developers can feel under pressure to deliver results faster so that QA can get started.</p><p>It’s unfortunate how often a waterfall methodology can create resentfulness between developers and QA. The role of developers (and the team as a whole) is to create a fantastic product. QA’s role is to provide a perspective an engineer may not have had, ultimately helping create a much stronger product. But when they aren’t working in step together, it can feel like QA is coming in after the fact and finding fault with the product. As a result, those developers want to interact with QA as little as possible, “throwing code over the wall” and waiting to hear back about any bug fixes.</p><h3>Getting QA and Developers on the Same Page</h3><p>QA and testing can be so much more for your business than their stereotypical role of “bug finders.” Not only should they identify defects after developers have finished their work, they should also take a proactive role in preventing problems in the first place, like a good doctor. To do so, your testers should take an advisory role, recommending tools and processes in order to help streamline development. In addition, QA and development should meet at the beginning of every sprint to ensure everyone understands what will be built, how it will be broken up, and how it will be tested. This way they’ll feel like different parts of <a href="https://techbeacon.com/blurring-lines-how-development-tester-role-changes-agile-teams">the same team</a>, working together to create an amazing product.</p><p>If your developers are working on one iteration while QA and testing are working on the previous iteration, you aren’t practising agile software development. Instead, you’re using a “mini-waterfall” methodology that has all the drawbacks of the waterfall model with few of the benefits of agile. Testing and development need to happen simultaneously during a sprint. Break issues into smaller, bite-size pieces that can be resolved more quickly.</p><p>Incorporating QA and testing into the development process as soon as possible is an approach known as “<a href="http://www.hugeinc.com/ideas/perspective/evolving-qa">shifting left</a>” — because testing is moved left on the software project management timeline. Shifting left requires a great deal of collaboration and cooperation between QA and development. For example, in order to free up testers for other duties, developers should help build an <a href="https://techbeacon.com/were-all-testers-now-5-steps-get-ready-shift-left-automation">automated testing framework</a> as part of their commitment to agile software development.</p><p>Make sure the project requirements are very clear to both QA and development at the very start of the project. QA should play a critical role in determining a project’s definitions of ready (DoRs) and <a href="https://www.zenhub.com/blog/diagnosing-your-chronically-late-software-releases/">definitions of done</a> (DoDs) — in other words, the entry and exit conditions for adding an item to or removing an item from a sprint.</p><h3>Final Thoughts</h3><p>The key to cooperation between QA and development is the realization that quality assurance is everyone’s job. If you want your products to be known for their quality, then that commitment needs to be baked into the software development process from the very beginning. Instead of making “quality” the job of a select few, insist on quality performance from <a href="https://blog.testlodge.com/qa-and-development-working-in-parallel/">every member</a> of the engineering team.</p><p>If you’re unsure how to get developers and QA closer together, try simple physical proximity. Just putting some desks together can do wonders for improving communication and breaking down barriers. In addition, you should put less emphasis on performance metrics around bug finding, and more emphasis on resolving issues and deploying a quality product that delivers value to your end-users.</p><p><strong>If you’re new to ZenHub, </strong><a href="http://zenhub.com/"><strong>download it for free</strong></a><strong> and discover how you can spend 52% more time writing code in GitHub, and no time in other clunky project management tools.</strong></p><p><em>Do you have questions about ZenHub? We’d be more than happy to help on </em><a href="http://www.twitter.com/zenhubhq"><em>Twitter @ZenHubHQ</em></a><em> or </em><a href="/service/mailto:support@zenhub.com"><em>email us directly</em></a><em>.</em></p><p><em>Originally published on </em><a href="https://www.zenhub.com/blog/how-to-empower-quality-assurance-and-developers-to-work-together/"><em>The ZenHub Blog</em></a><em> on May 9, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aab45ede6b5f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axiomzenteam/how-to-empower-quality-assurance-and-developers-to-work-together-aab45ede6b5f">How to Empower Quality Assurance and Developers to Work Together</a> was originally published in <a href="https://medium.com/axiomzenteam">Axiom Zen Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Rise of Agile Transformations and What Organizations Should Consider]]></title>
            <link>https://medium.com/axiomzenteam/the-rise-of-agile-transformations-and-what-organizations-should-consider-f7740f8e08e?source=rss-1d8c444e0857------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7740f8e08e</guid>
            <category><![CDATA[agile-development]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[general]]></category>
            <category><![CDATA[agile-transformation]]></category>
            <dc:creator><![CDATA[Zenhub]]></dc:creator>
            <pubDate>Tue, 18 Apr 2017 15:21:00 GMT</pubDate>
            <atom:updated>2017-06-15T22:41:34.766Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*LRqSFLk9mM-2F9FP1ZNoOA.jpeg" /></figure><p>Like “DevOps” and “continuous integration,” “agile” is one of the biggest buzzwords in the software world. With all of the hype and excitement surrounding agile software development practices, it’s understandable if the actual definition of the term has slipped by you. So what does it mean when we say that a business is “agile,” and what is an “agile transformation”?</p><h3>What It Means to Be “Agile”</h3><p>Agile is a movement that began in software development, but has now spread to other parts of technology organizations, and even to other industries. The original “Agile Manifesto,” written by seventeen software developers in 2001, laid out the four major priorities of the movement:</p><ol><li>Individuals and interactions over processes and tools</li><li>Working software over comprehensive documentation</li><li>Customer collaboration over contract negotiation</li><li>Responding to change over following a plan</li></ol><p>This initial outline, though rough, has served as the basis for a wide-ranging variety of agile implementations. Although people and companies have interpreted these four directives in many different ways over time, the unifying thread between them is their emphasis on the human side of business.</p><p>Above all, the agile movement focuses on what goals people have and how they communicate and collaborate to achieve them. In addition, it seeks to make organizations more flexible and resilient in a fast-changing world — exactly what its name implies.</p><p>Although software development techniques like scrum and kanban have co-opted agile terminology, it’s important to note that they are not the same thing as agile. Rather, both scrum and kanban are agile software development frameworks. They use agile as a general foundation to paint a more specific picture of what good software development should look like.</p><h3>Agile Transformations</h3><p>As the name suggests, an “agile transformation” is any shift that leads to an organization adopting the principles of the agile movement. In order to be successful, agile transformations must involve changes in three domains: people, processes, and tools.</p><ol><li><strong>People:</strong> As the old truism goes, organizations are made up of individuals. Moving to an agile workplace means that your employees must adopt a new mindset, acquiring new skills and knowledge that will change the way they work, communicate, and collaborate.</li><li><strong>Processes:</strong> Agile transformations require new strategies and techniques to be implemented across teams, departments, and the entire organization.</li><li><strong>Tools:</strong> Switching to agile will mean adopting new tools and systems, and abandoning old ones, in order to make your workforce sleeker, speedier, and more limber.</li></ol><h3>Organizations Making the Shift</h3><h3>Cisco</h3><p>By now, countless organizations have used agile practices to improve their software development workflow. Tech giant Cisco, for example, has <a href="http://www.cisco.com/c/en/us/solutions/collateral/enterprise/cisco-on-cisco/cs-boit-06172016-agile-development.html">written</a> about how it used agile software development on its Subscription Billing Platform (SBP) project. Originally, the SBP team used the waterfall model of development, meaning that the software was created incrementally. Developers could start work only when the designers had finished, and testers could begin testing the software only when the last line of code had been written.</p><p>The SBP team first tested using agile practices to make minor enhancements. Team members worked in three “trains” that each had separate responsibilities: defects, capabilities, and projects. Designers, developers, and testers all worked together within the same train.</p><p>After adopting this new agile perspective, the team released the next version of SBP on time with all of the expected features included. What’s more, critical and major issues plunged by 40%, while the team’s productivity increased by 14%.</p><h3>Comcast</h3><p>Similarly, Comcast started by rolling out agile DevOps processes to small hand-picked teams before having the engineering organization adopt the methodologies as a whole. Once those small teams saw an increase in productivity and reliability, the buy-in from the rest of the organization was easy.</p><p>They also <a href="http://www.telcotransformation.com/author.asp?section_id=422&amp;doc_id=723953">point out</a> just how different the new processes are from their traditional ways and the impact it has on individual team members. Rather than the scope of work for an individual being small, they’re able to interact with all aspects of the project. This organically broadens the skill sets of each individual, and in turn makes the entire team (and final product!) that much stronger.</p><h3>NPR</h3><p>Businesses far outside the software industry have also had major successes implementing agile project management within their organization. Consider the case of National Public Radio. Traditionally, new NPR shows were rolled out slowly, and only after millions of dollars had been spent. After the <a href="http://www.niemanlab.org/2012/04/agile-social-cheap-the-new-way-npr-is-trying-to-make-radio/">Bryant Park Project</a> show was cancelled in 2007 (with a $2 million yearly budget), NPR didn’t create any new programming for five years.</p><p>In 2012, however, NPR launched a new round of programs using a more agile approach. The shows were developed at a third of the typical cost, put on the air quicker, and intended right from the start to accommodate listeners’ feedback.</p><p>NPR’s digital media team figured out how to apply the agile concepts of iterative development (changing shows based on audience opinions) and simplicity (adapting existing shows into new ones) within their organization. According to Eric Nuzum, NPR’s vice president of programming, switching to an agile mindset has led to “<a href="http://www.computerworld.com/article/2505876/app-development/npr-adopts-agile-like-method-for-program-development.html">a tremendous amount of success</a>.”</p><p>These are just a few organizations adopting agile practices. There are <a href="http://www.mckinsey.com/industries/financial-services/our-insights/ings-agile-transformation">many</a>, <a href="https://www2.deloitte.com/content/dam/Deloitte/global/Documents/About-Deloitte/gx-about-deloitte-agile-deloitte-agile-transformation-approach.pdf">many</a> <a href="http://www.scaledagileframework.com/john-deere-case-study-part-1/">more</a> <a href="https://www.ebayinc.com/stories/news/expert-joshua-kerievsky-discusses-modern-agile-at-ebay/">examples</a> taking place around the world.</p><h3>What to Consider When Making the Shift</h3><p>Has your organization already begun their agile transformation, or are you thinking about bringing it to the table? Here are a few things to keep in mind before you step on the gas.</p><ul><li><strong>Change isn’t easy.</strong> Remember that you’re modifying the way that every single person in your enterprise carries out their work. Agile transformations can’t happen overnight. Moving to a wholly agile mindset will require a change in your organizational culture, which will require months or years of effort.</li><li><strong>Start small.</strong> Companies like Cisco and Comcast tested agile development on individual projects or teams before they adopted it wholesale. Just as you can’t change your workplace culture by waving a magic wand, replacing your processes and methodologies will take strategic implementation, so experiment and see what works best for you.</li><li><strong>Measure what matters.</strong> Becoming an agile organization means that you now prioritize agility. Instead of tracking traditional key performance indicators (KPIs), pay attention to how well your organization can adapt in a constantly shifting business landscape. This means emphasizing factors like customer satisfaction and employee morale.</li></ul><p>Hopefully the above thoughts were helpful, whether you’re completely new to agile or this was a refresher. ZenHub is helping some of the world’s largest organizations integrate agile best practices into their workflows. Learn more about our <a href="https://www.zenhub.com/enterprise?utm_source=blog&amp;utm_campaign=agile_transformations">on-premise project management</a> software built natively inside of GitHub Enterprise.</p><p><em>Originally published on </em><a href="https://www.zenhub.com/blog/the-rise-of-agile-transformations-and-what-organizations-should-consider/"><em>The ZenHub Blog</em></a><em> on April 18, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7740f8e08e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axiomzenteam/the-rise-of-agile-transformations-and-what-organizations-should-consider-f7740f8e08e">The Rise of Agile Transformations and What Organizations Should Consider</a> was originally published in <a href="https://medium.com/axiomzenteam">Axiom Zen Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Become a Productive, Distraction-Free Developer]]></title>
            <link>https://medium.com/axiomzenteam/become-a-productive-distraction-free-developer-ea885c656959?source=rss-1d8c444e0857------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea885c656959</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[developer-productivity]]></category>
            <category><![CDATA[general]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Zenhub]]></dc:creator>
            <pubDate>Tue, 04 Apr 2017 17:17:40 GMT</pubDate>
            <atom:updated>2017-04-10T23:28:43.985Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M4qhSiyWO_TwkY81LLrXSA.jpeg" /></figure><p>Most work environments are filled with distractions. Whether you’re in an office or even working remotely from home (arguably worse), distractions are everywhere, and they’re non-stop. Even something seemingly simple like a text message can really throw you out of focus. For a developer, that focus is critical when you’re writing code — which is where you spend the majority of your time.</p><p>Aside from text messages and such (more on those distractions later), there’s a specific little-known form of distraction we like to call out, known as ‘context switching’.</p><h3>Context switching explained</h3><p>In the simplest terms, ‘context switching’ is one way to describe moving from one task to another.</p><p>Minimizing your current browser window to check a new email, being poked on the shoulder by a teammate with a question, or leaving GitHub to update a ticket in JIRA, are all great examples of that distracting context switch.</p><p>When you jump from one task to another, there’s a cost. That cost is due to context switching. It’s mentally draining, and it wastes way more time than you’d expect.</p><h3>The true cost of context switching</h3><p>It turns out that people are actually pretty bad at multitasking. A study by the Journal of Experimental Psychology demonstrated that multitasking slows productivity by up to 40%. When interrupted, it takes about <a href="http://www.fastcompany.com/944128/worker-interrupted-cost-task-switching">20–30 minutes</a> to get back on task (for example, jumping from GitHub into another tool to update a task board). Exact numbers vary, but the takeaway is the same: shipping software quickly requires complete focus.</p><p>Even what you think are short interruptions slow you down.</p><p>Switching between low-performance tasks — say, texting a friend and watching TV — isn’t so difficult. It takes nearly no time to get back to “where you were” (zoning out in front of Netflix) prior to the interruption. When tasks are complicated, context switching becomes much more expensive.</p><p>Consider a developer who’s working on a new feature — an incredibly complex task with high mental overhead. Here, a five-minute interruption takes many multiples more than just five minutes. <a href="https://www.stevefenton.co.uk/2012/06/Context-Switching-Comes-At-The-Price-Of-Delivery/">Steve Fenton</a>, author and Development Director at Geronimo Web, describes it this way:</p><blockquote>If a developer is interrupted with a question, it could put their work back by hours for each interruption. This is because of the amount of stuff they are holding in their immediate memory while they are working on a feature. They will have parsed lots of code in the area they will be working on and will have projected their changes in their mind before they start coding and the interruption will impact their focus on this information.</blockquote><blockquote>Additionally, once interrupted the developer may decide to batch other interruptions like email into the break — but this elongates the gap and makes it more likely that the information will be squirrelled away into harder to access places.</blockquote><h3>Eliminate the context switching</h3><p>Agile teams have known this for a while — it’s the same reason many teams impose work-in-progress (WIP) limits when allocating tasks. They know giving developers two tasks to do “at once” takes more time in aggregate than doing one thing at a time.</p><p>It’s not enough to tell our teammates not to get distracted. Even your tool set should reflect your commitment to keeping developers focused. That’s why we built ZenHub inside GitHub — not close to, not integrated with, but <em>inside</em>. When your project management process is right there next to the code, using it becomes almost automatic. The cost of context switching — the time it takes to jump from GitHub, refocus, jump back to GitHub, and refocus yet again — is essentially eliminated.</p><p>(Unconvinced? This well-known <a href="https://www.crisp.se/gratis-material-och-guider/multitasking-name-game">multitasking simulation</a> does a good job of spelling out just how terrible we are at switching tasks.)</p><p>It isn’t only engineers that lose focus when they context switch. Staying on a single task is equally important for managers. Centralizing in one place means:</p><ul><li><strong>More accurate metrics.</strong> Third-party project tools result in silos of information. By making GitHub a single source of truth, your data is always up-to-date.</li><li><strong>More focus on the product.</strong> Project managers shouldn’t spend their day reminding their team to update tickets. When everything is centralized, project managers spend more time worrying about the product, and less time worrying about the people building it.</li><li><strong>Fertile ground for collaboration.</strong> GitHub issues were built for collaboration. Collaboration not only helps reduce error and technical debt, it actually keeps teams happier. In one study, enterprise companies that identified collaboration as the top priority significantly improved employee satisfaction, customer retention, and productivity (Aberdeen Group, 2013).</li></ul><h3>Minimize other distractions too</h3><p>We’ve touched on text messages as an example of unwanted distractions, but they aren’t alone. There are a few simple steps you can take to eliminate, or at least <em>minimize</em>, these distractions.</p><p>Nearly all mobile phones and computers today have handy little notification settings that let you to customize the way you receive them. In a society where it may sound impossible to turn off notifications completely, you will be pleasantly surprised to experience just how much less distracted and more focused you become. If you still want notifications to come through while you’re not at work, you can often create a specific schedule (say 9am to 5pm only) when you want notifications disabled.</p><p>Email is another great example of a common distraction that can be avoided. Many of us have the habit of checking our email several times per day, or even have it open as a browser tab 100% of the time! Similar to your notification schedule, build yourself an email-specific schedule. Add events to your calendar at the beginning and end of every day to create that dedicated time for checking email. When not popping over to an email tab 10 times throughout the day, a developer will write an awful lot more code.</p><p>These simple tips, in combination with no longer having to context switch (because you’re staying in GitHub), will make you the most productive developer on your team. But obviously we think your entire team should use ZenHub too, so you shouldn’t rely on this alone if you’re looking to outpace your teammates during your next sprint.</p><p><strong>Have you read our book on GitHub Project Management? Learn to build better software and a more collaborative team. </strong><a href="https://www.zenhub.com/book/github-project-management"><strong>Get your free copy</strong></a><strong>.</strong></p><p><em>Do you have questions about ZenHub? We’d be more than happy to help on </em><a href="http://www.twitter.com/zenhubhq"><em>Twitter @ZenHubHQ</em></a><em> or </em><a href="/service/mailto:support@zenhub.com"><em>email us directly</em></a><em>.</em></p><p><em>Originally published on </em><a href="https://www.zenhub.com/blog/become-a-productive-distraction-free-developer/"><em>The ZenHub Blog</em></a><em> on April 4, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea885c656959" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axiomzenteam/become-a-productive-distraction-free-developer-ea885c656959">Become a Productive, Distraction-Free Developer</a> was originally published in <a href="https://medium.com/axiomzenteam">Axiom Zen Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>