Living Agility: A journey to an agile organization

The original impetus for the agile movement was that IT projects were obsolete before their completion. Either the client’s business requirements had changed or, worse, the project had gaps or misconceptions that they did not discuss up until the delivery of final product.

This experience is the same in multiple industries. One organization described the need to change its products every two years. But with development taking 18 months, the newest product was obsolete almost from the day it was delivered.

Project management - traditional vs agile

The traditional waterfall project management approach decides on the end product right at the start, then executes it step by step in a linear fashion, until release to the customer. It has little space for changes, iterations, learning as you go and pivoting as new needs emerge.

Agile, on the other hand, involves continuous iteration and testing. The organization divide the large project into smaller pieces, which the small teams handle, and delivers working modules along the way. The original concept may change significantly during the development process. Apparent failures become immediate learnings, which accelerate and reduce the cost of the final product. The premise is that quality is better if they resolve the defects early on. It is most valuable where there are real and complex problems, where the solutions are not clear at the start and where innovation is required.

Agile organizations are faster than their competition, and measure in weeks and months rather than years.

Agile philosophies and principles

At its most simple, you can see the agile approach in

• Obsession with innovating and delivering customer value
• Work being delivered by small, self-organizing teams
• Collaboration in an interactive network

The top strategic priority in an agile organization is innovation and thinking that delivers customer value. They question any activity that does not add customer value. The focus is on outcomes (like profitability or customer loyalty), not outputs (like lines of code or the number of new products).

The team is the primary unit of the organization. There is free flow of ideas and feedback internally, collaboration with other networked teams and close contact with customers, without the traditional barriers of hierarchies and silos.

Cycle times or sprints are short, there are regular super-short scrum meetings or events and they track the progress on Kanban or status boards, so teams can quickly fix errors or change direction. Team members evaluate each other during retro meetings or use apps to do this. They expect teams to have entrepreneurial approach, to learn quickly and to have role flexibility.

Having direction and strategy from the top of the organization is crucial. A clear vision and shared purpose create stability. The executive role also is to give attention to flexible allocation of resources, identification of new opportunities and building organizational capability.

They don't see new technologies as disruptive. They use new technologies as enablers and facilitate collaboration, transparency and quick and continuous decision-making.

However, there's a big BUT to all of this: It is clearly a tall order to expect teams to manage themselves and managers to give up control, while seamlessly introducing new processes and technologies.

Moreover, bringing in an outside expert may help to make it happen.

Unless you are a Netflix or Spotify that were born as agile organizations, agile transformation is a journey that will require patience, risk tolerance and commitment.

Basically, the trick is to apply agile principles to achieve agility. This means having a clear vision of the end goal, breaking down the overall plan into smaller manageable parts, experimenting and adjusting, aligning processes and monitoring outcomes. This also means testing the early teams for any prototype, to show the way for the ones that follow.

Some routine functions such as accounting and plant maintenance may not need the whole approach, but they too must develop agile mindsets and give high priority to the requests of agile teams.

All of this will not be plain sailing. There is a need for experienced and talented agile practitioners who will guide new teams and set up contingency plans for unexpected breakdowns. This may be the place for experienced freelance consultants to train, coach and embed new ways of working.

The problem with agile, as with any relatively new approach, is that everyone is suddenly an expert! Anyone who has read a few books or applied a few techniques in scrums, sprints or stand-up meetings is now in the online consulting marketplace, offering agile coaching services.

Now, this is definitely a time when you should be checking credentials and getting references from previous clients.

One of the major benefits of using a freelance platform like Consultport is that this step has been done for you. Consultants are pre-screened to establish who they are and what they really can do. Clients are also pre-screened, so consultants have some protection too. Then the two are matched. Clients can choose the consultant that best suits them, and consultants can choose the work that they can best deliver.

As a bonus, a freelance platform like Consultport also undertakes quality assurance, project management and administration tasks, thus freeing up the client and the consultant to get on with the task at hand.

But, is agile transformation worth the effort required to achieve it? Agility sounds like an obvious goal. It isn’t easy to achieve, but there is an online consultant marketplace with people who can help.

Now, The question is whether it is worth the effort?

Well, if research findings are correct, agile organizations achieve accelerated time to market, with better quality and lower risk. They have faster responses to changing conditions and customer demands as well as higher team productivity and morale. And they score highly for achieving strategic goals - this is a predictor of long-term performance.