Why your organization isn’t agile?

I have found this through talking with my network, job ads, events, etc. For example: using Trello, Jira or any other project management software doesn’t make you agile. If you think that it does you are wildly in the wrong.

Being agile as an organization or a team is far more complex than implementing a singular project management software.

Luckily it isn’t also overly complex to get you on your way towards being agile. It is a journey without an end after all.

Biggest reason preventing the change is time

Time. How often have you heard somebody say they don’t have time to do something? I think everyone has heard it.

“We are so busy pushing the cart that we don’t want to spend time attaching wheels to it”

Being busy or working insane hours doesn’t make you effective. (Feel free to argue with me about this)

What is agile?

In my experience and understanding it is quite simple.

1.    Being agile means doing the things which have the biggest impact for your business.

2.    Make sure you are committed to constant improvement. It often means slowing down and looking at things you have done – Retrospective and sprint review session is used for this in software development.

3.    Plan what you are doing in the next few weeks. This is called sprint and involves planning for it which would be sprint planning.

4.    Sticking to the plan is also agile. To get sh*t done. Being agile doesn’t mean you are changing what you are doing constantly and not getting anything done with quality.

Steps to make you agile:

What could be the first steps to make you agile? Where to start? There is a hint of irony here: start using a project management software or post its in a Kanban board-type of way. Main thing here is to track the progress of your activities.

  1. Plan and fill requirement of actions that need to be done within a week or two
  2. Create a Kanban board with planned activities with lanes named as backlog, progress, in review, done (just examples to get you started)
  3. Move them along as they progress
  4. Retrospective session: have once a week or every second week. Type of workshop with the team where you go over in turns with sticky notes on the wall (or softwares) what was good and what was bad.
    1. Why? To know where you need to improve and know what went well
    2. Get feedback and general feelings from everyone so nothing gets bottled up
Share on facebook
Share on Facebook
Share on twitter
Share on Twitter
Share on pinterest
Share on Pinterest
Share on whatsapp
Share on WhatsApp