5 Steps to Introduce an Agile Tool


There are tons of agile tools out there. Just have a look at this looooooong list on Mike Cohn’s site. But what is the best way to introduce such a tool in your team or company? I collected the following steps for you.

1. Start with no tool at all

A fool with a tool is still a fool. Before you introduce a highly sophisticated agile tool, you need to know how Scrum, XP, Kanban or any other method are working in your own context. If you use a tool right from the start, you won’t follow the process that best fits your situation, but the process the tool dictates. Every agile tool has it’s own understanding, how to implement Scrum or Kanban.

Read the rest of this article on marcloeffler.eu.

9 thoughts on “5 Steps to Introduce an Agile Tool”

  1. Couldn’t agree more. Try simple things first, experiment and calculate time invested. Weird ideas like having two physical boards and keeping them in sync manually might in the end be more feasible than an electronic solution. Do not underestimate the advantages of a board you happen to pass by, you can’t avoid to see, over one you have to think of opening.

  2. Yes, good article. But in contrast to paragraph 3, we immediately had chosen not simple, but complex Tool. This will allow us not to worry about what this software will limit our ability to project management in the future.
    You can estimate we were right or not by yourself:

  3. You made some good points, but finding the right solution for the right team can often be big problem. We’ve tried TFS, JIRA, SmartBear and are currently running Countersoft Gemini with which we have seen some good results in going all-in with Agile development. It’s really tough finding a good fit!

Leave a Reply

Your email address will not be published. Required fields are marked *


Notify me of followup comments via e-mail. You can also subscribe without commenting.