Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

How Not to Fail an Agile Transformation

DZone's Guide to

How Not to Fail an Agile Transformation

Avoiding the temptation to backtrack on your Agile transformation is difficult, but there are ways to keep the spirit alive.

· Agile Zone ·
Free Resource

You've been hearing a lot about agile software development, get started with the eBook: Agile Product Development from 321 Gang

It's all too easy for teams to drop their Agile-related efforts after a little while since their initial training. Don't we all have a natural tendency to want to go back to how things used to be?

But doing so does, obviously, render all improvement and change efforts useless. What do you do then?

Culture Check

It's a truism by now, that any organizational changes need to match the existing organizational culture and needs. It is then crucial to keep in mind that even the best applied and executed Agile practices will never work when they are not the answer to what a company needs, and to what it can work with. Start with checking how this looks for your Agile implementation — does it answer real needs and does so in manageable ways? Agile is a means of achieving greater productivity and better results; it's not a goal in itself.

Injected Interest

If the standard practices seem to fail, it's worth considering injecting a general inspiration and interest in Agile through your delegated Agile ambassadors. All this involves is selling an influential employee on Agile values, so that they implement it themselves and start to generate interest within the team. Then, this team's approach becomes something other teams want to strive for etc. The reason why it should work is that the interest gets generated in the most natural way — by seeing a working example.

At kanbantool.com we see this all the time — a small team starts to use the online Kanban boards and applying Agile practices, other teams in their organization see it work, and ask for own boards for themselves, as a start. Nothing is forced, but change is fueled by just wanting to have it as good as the other team does.

Leadership

It's rare for team members to follow a new paradigm or practice when it clearly has no approval with leadership. Even more so true, when leaders only see the new thing as something they just have to agree with, rather than appreciate its merit. Ideally then, you could attempt to make your leaders your Agile ambassadors and kill two birds with one stone.

It's also worth mentioning that bringing enthusiasm and examples to the team needn't come from named leaders only. Anyone can bring a change about if their implementation creates enough interest (or envy) among others.

Follow Through

In any Kanban and Agile system, there should be a schedule in place, indicating when your current process should be reviewed for faults and potential improvement spaces. It's the key element to keeping your Agile truly agile, isn’t it?

Perform regular process reviews in order for the process to be always evolving; otherwise, you're just set with one, non-stale-proof, formerly Agile process.


Download the free agile tools checklist from 321 Gang. This guide will help you choose the right agile tools to position your team for success. 

Topics:
agile ,agile transformation ,agile adoption ,leadership ,organizational culture ,tutorial

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}