<?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 Subin Jacob on Medium]]></title>
        <description><![CDATA[Stories by Subin Jacob on Medium]]></description>
        <link>https://medium.com/@subinjacob?source=rss-a7d8a2d98dff------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*c0BwnoSODWSiKg0-.jpg</url>
            <title>Stories by Subin Jacob on Medium</title>
            <link>https://medium.com/@subinjacob?source=rss-a7d8a2d98dff------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 11:37:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@subinjacob/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[Will Agile Fit In A Non-IT Environment]]></title>
            <link>https://medium.com/@subinjacob/will-agile-fit-in-a-non-it-environment-988ae411fd33?source=rss-a7d8a2d98dff------2</link>
            <guid isPermaLink="false">https://medium.com/p/988ae411fd33</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Subin Jacob]]></dc:creator>
            <pubDate>Thu, 03 Sep 2015 12:43:00 GMT</pubDate>
            <atom:updated>2015-09-03T12:43:00.005Z</atom:updated>
            <content:encoded><![CDATA[<p>Ever since its inception in 2001, the <a href="http://agilemanifesto.org/">Agile manifesto</a> and the Agile project management methodology has been primarily thought of, as a tool for software companies to drive productivity But what about non-IT, non software companies? Don’t they deserve to be productive and gain efficiency using the best practices available? Of course they do — there are several examples of best practices shared across industries and industries getting benefited. One of the most famous is the Lean methodology of startups and software development that was taken from the manufacturing industry.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*rcGOVm9PcfZCqYoE.jpe" /></figure><p>Photo by <a href="https://unsplash.com/alexjones">Alex Jones</a></p><p>On similar lines, Agile methodology can do wonders for non software companies too — after all there are several common activities that can be managed using Agile tools. Armed with this thesis, <a href="http://www.softwareadvice.com/">Software Advice</a>, conducted a study to understand how far is adoption of Agile tools in non IT sector and how do the decision makers in non IT sector perceive Agile tools. There are several other interesting findings. The key points among them are:</p><ul><li>Surprising yet true — 48% of project managers use Agile software for non IT related projects.</li><li>The most useful feature in an Agile tool for non IT projects -</li><li>Workflow tracking (90% respondents).Story mapping and analytics are close second at 89%.Scrum boards and activity streams are the third with 85% people’s votes.</li><li>Biggest challenge for about half of the users is to train others about using Agile tools.</li></ul><p>Nearly half of the respondents already used Agile tools for non IT projects — This is really surprising, because deep down I had assumed that Agile is a property of software domain. But the news that there are several companies who are already reaping the benefits of Agile methodology in their own fields is intriguing. How do they do it? What features they use?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/675/0*rFJV9k0zes8RhE2z.png" /></figure><p>But if you let this sink in, you’d come to agree, Agile methods translate well to any kind of project. For example the activity stream — every manager would love to have a bird’s eye view of what everyone in his team is up to. Another example, workflow management, is applicable to any project you can think, almost all types of projects are now multi-location</p><p>These are the following 10 ways that agile can improve <em>any</em> team :</p><h3>1. Break things down</h3><p>What’s the saying, “How do you eat an elephant? One bite at a time…” Like many aspects of agile, this one seems like a no-brainier. Break large tasks up into smaller, more manageable ones. Prioritize them, and work on the most important ones first. Deliver the smallest, most valuable thing as soon as possible. Get feedback on it and adjust your plans as needed.</p><h3>2. Focus on outcomes instead of output</h3><p>The idea is that we intuitively think about our work in terms of output. How many cases did we close? How many features did we release? How many emails, phone calls, etc. did we make? We think about our work in terms of output because it is easy to measure, but it’s not what <em>really</em> matters. What matters is the impact or outcome of our work. We should focus on minimizing our output while maximizing the outcomes. Which things can we do to have the biggest impact in our customer’s lives?</p><h3>3. Make your work visible and transparent</h3><p>Consider using a physical task board to make your team’s work more visible. Almost everyone has a tough time with this at first. Create columns for things to do, work in progress, and completed tasks. This can do wonders for your team’s communication and collaboration on projects. It is simple but there is something inherently satisfying about moving a task across the board. Try it out!</p><h3>4. Track your progress</h3><p>Set goals for your team and measure the progress towards them. The simpler, the better but make sure that it is highly visible. Post it in a public team space where people will see it often.</p><h3>5. Embrace change</h3><p>Planning is great, but don’t get so tied to your plans that you aren’t willing to change them when you have more information or circumstances change. Be very cautious about making detailed long term plans that are costly to change. If you do this, you’ll be much more willing to steer the ship around the iceberg that just emerged instead of trying to knock it out of the way.</p><h3>6. Daily stand up meetings</h3><p>Have a quick, daily meeting that allows each team member to share what they accomplished since the last meeting, what they are planning to accomplish next, and any obstacles that are preventing them from making progress. Make sure everyone is standing during the meeting to help keep the meeting short and sweet. Mornings are a good time for these since they can help the team get in sync early.</p><h3>7. Eliminate waste</h3><p>One of the <a href="http://agilemanifesto.org/principles.html">agile principles</a> is around the idea of simplicity. Maximizing the amount of work <em>not</em> done, is essential. Are you and your team empowered to question the value of your work? Be willing to ask if and why something is valuable. If it is no longer valuable, be willing to see what happens if you stop doing it. Look for things that are wasteful and eliminate them. This will free you and your team up to focus on the things that drive outcomes. You know — the things that matter!</p><h3>8. Self organizing teams produce the best results</h3><p>Teams should be trusted and empowered to focus on doing whatever is necessary to deliver results. Encourage teams to swarm on tasks that need to be completed even if it puts them out of their comfort zone. Trust the individuals <em>closest</em> to the work being performed to make decisions on <em>how</em> to do the work.</p><h3>9. Inspect &amp; adapt</h3><p>Continuous improvement is one of the most valuable and important principles of agile in my opinion. Encourage your team to constantly look at how they are working and ask, “What can we do to improve?” or “How can we be more effective?”. Agile teams do this in regular meetings called <a href="http://www.mountaingoatsoftware.com/scrum/sprint-retrospective/">retrospectives</a>. These meetings happen regularly (usually every 2 weeks) and the team is encouraged to talk candidly about their work and how things are going on the team. Positive things are reinforced, negative issues are discussed openly, and ideas for changes are considered and planned.</p><h3>10. Have fun!</h3><p>Remember, there is no “one size fits all” version of these agile ideas and techniques. Feel free to experiment and make adjustments and tweaks to these ideas to fit your specific team’s context and needs. Most importantly, remember to have fun and enjoy what you are doing!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=988ae411fd33" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>