How to make your organization Agile in seven easy steps

(common Agile transition antipatterns exposed)

(High Crap Factor warning!)

So, you want to become Agile… everyone is on that track already, and you feel that you are lagging behind. Do not worry! Agile is not hard, it is not magic. There is so much information out there, it can be overwhelming. Let me help you. Here is how to become Agile – fast.

1. Announce to everyone that from now on, you are Agile. Communicate it to your employees, put the ads in the relevant newspapers, underline that you are doing (whatever you are doing) – The Agile Way!

 becomingagilebyyelling1

2. You do not need to dive into all those Agile methods. There are too many around. You may get confused.

Pick Scrum. Enlighten everyone that for you Agile = Scrum. Everyone modern is using Scrum anyway. Get yourself informed – google a bit about it, so you get some idea what the hype around it is. Get familiar with the buzzwords.

3. Send all of your project managers to a Scrum Master course. Yes, it will cost you some money, but it is a safe bet – none ever failed the course, and you will have a bunch of certified experts within only two days!

Now, we all now that Scrum rocks, but why don’t you take it a step further and do it your way! Here is how to optimize and improve Scrum:

4. Daily meetings are a waste of time. Calculate how much time it takes away from your resources and mail everyone about the result! They will be shocked with your revelation, and praise you for saving the money and preserving their precious time (after all, it is a well known fact that no one likes meetings and frequent interruptions). So, the daily Scrum meetings should be scoped out.

5. Now, this is a huge flaw in Scrum – the planning meetings are just too short. That is what Scrum does wrong!

We should perform a careful planning to avoid any mistakes. If we use 60% of our time for detailed planning, it will be easy to just implement our solutions once we are done with the planning phase, since we took everything into account!

6. The Retrospectives – those are a bit unnecessary, you’ll agree. We should focus on the future, not dwell on the past! The time we save by scoping these out can be used for our planning activities!

7. The Artifacts. Scrum incorporates several artifacts: Product Backlog, Sprint Backlog, Burn Down Chart. Artifacts are good, keep them. Add even more!

The value of artifacts and documentation is great. It is very important to have a well documented overview of what every team member is doing. Transparency is what we value! Create a document where people write down what they did every day, in details. Assign someone who checks whether they did it and send reminder mails regularly to the ones that did not.

This is just a start. Soon you will be ready to improve your Modified Scrum with even more of your own modifications! Good luck on your way to success!

***

This post is dedicated to all the Modified Agile practitioners I met that inspired me to compile this wonderful list.

***

Please check out these two posts: Why would anyone want to become Agile? and Two steps to become agile written by Joakim and Daniel, respectively. Those are two guys that (more often than not) have the same values like I do. No crap warning there, I promise.

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to Ma.gnoliaAdd to TechnoratiAdd to FurlAdd to Newsvine

Advertisements

6 Responses to How to make your organization Agile in seven easy steps

  1. Shane says:

    What do you mean planning should be longer??? It should be shorter!!!

    We should be more agile, and plan as we go. This means that we just meet at the beginning of the Sprint to show the list of items to do. We will figure out what they are exactly during the Sprint.

    That is true agile!

  2. Jelena says:

    Shane,

    Of course, you are right. We are on the same team. The whole post has “High Crap Factor warning!” at the very start, it is meant to be ironic.

  3. Shane says:

    I meant to be ironic too, but I guess I was not very successful. Cheers

  4. Jelena says:

    Ah! You meant the other extreme – to optimize the planning session by removing all the planning, in order to save the precious time! I’ve never experienced that “improvement”, the usual ones I encountered are those I listed. But good to know! 😉 I am sure the list could be much longer…

  5. Jelena says:

    Today I added a subtitle to this post: “common Agile transition antipatterns exposed”.

    Antipatterns were here to start with. I will blog about Agile transition patterns soon.

  6. […] another post, I addressed some commonly used antipatterns, when one wants to get Agile just because it is cool, […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: