Great! You want to work Agile!

Agile will help your company grow by better Time, Cost, Resources management.

Taking the first Steps


Would you be a Product Manager, a Developer or a C-level, the first question to ask yourself is :

How can Agile help us attain product excellence and deliver more value to the company?

Ideally, you should have a sub-goal for switching to Agile. It could be something like:

We want to use Agile to develop a better product giving us more than one USP (Unique Selling Proposition) to get ahead of the competition.

If you reached this page, you probably read quite a lot about Agile already. We want to help you to make the right call on this. Note that Agile is not magic, it’s just a smarter way to work. Keep in mind that it won’t work if your team does not make any effort to facilitate the change to Agile.

So what now?

Step 1: Focus on a Purpose

Define Goals to achieve by switching to Agile

Step 2: Inform people and gather intel

Set up a meeting and announce that you would like to switch to Agile and that it’s gonna happen.

Ask your team what they think about it, if they are against it, ask why. Basically, this is a qualitative study and you should listen to and write down every negative pre-feedback so you are aware of the potential issues and remove the blocks before the actual problems occur.


Step 3: Select your Agile Framework

Check alignment of Purpose with Team’s feedback, make changes if needed. Once refined and clearly defined, you should be able to select the most suitable Agile Framework for your Team or your company.

Step 4: Select your Agile Tool(s)

Meet again with the Team and Key Stakeholders to determine the best tool for your unique use.

We recommend you follow these 5 principles to select your tool. The right tool should :

1. Facilitate Collaboration and Communication 

2. Track History and Accountability

3. Have a Searchable Central Storage 

4. Have good Ability to Scale

5. Provide Analytics

We recommend you write a list of the requirements for this tool. Note that requirements are functions and not features. Features are what you find in the tool, but functions are the activities performed by the features. Think of it as your very first User Story!

May 26 • 5 min read ★


© 2019 by 🐿️

Website developed through ongoing iterative and agile development.