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

Agile Transformation: Steps, Statistics, and a Case Study

DZone's Guide to

Agile Transformation: Steps, Statistics, and a Case Study

Is your company considering a switch to Agile. Read on to get some great tips on how to achieve your goal, and to see how one company achieved something similar.

Free Resource

See how three solutions work together to help your teams have the tools they need to deliver quality software quickly. Brought to you in partnership with CA Technologies

Many companies are stuck in old ways of operating, and that negatively affects an organization’s speed and adaptability to change. Nowadays, to be competitive in the digital age, businesses need to achieve agility.

But many leading companies struggle to be efficient, and data-driven, which then makes them less productive. Agile transformation isn’t just about technology. It’s about a new way of thinking. It’s more collaborative, more open, more creative, and much more efficient than other business models. And it’s something that can be implemented across a company, not just in one or two departments.

Actually, evidence indicates that Agile project management results in a higher success. High quality, reduced costs, greater levels of customer satisfaction, shortened time-to-market, improved flexibility, faster feedback, and ROI. With so many great advantages, I am sure you have noticed that the popularity of Agile has skyrocketed in recent years, and we are not talking only about software development industry. Now, Agile is adopted across different projects, departments, and companies. To tell you the truth, I truly believe that Agile transformation is essential in changing your company into a truly innovative business. It is all about changing your culture, your processes, improving your quality, and business results. 

It’s interesting, if you ask talented young people to name their dream company from an employment perspective, they’ll almost always name companies like Facebook, Google, Netflix, Spotify, Uber, etc. Why? The thing is that none of these companies operate in the same industry, but what they all have in common is a particular way of working and a distinctive culture. They work in small teams that are united following Agile methodology.

Agile Transformation

To start with an Agile transformation, you should definitely hire an Agile Coach. Even if you are familiar with Agile methodologies and you believe you manage an Agile project for a long period of time, it doesn’t mean you can transform the whole organization. Agile transformation means that all people and all processes in a company should be agile. Imagine the scale of this change in huge companies with thousands of employees. It is extremely difficult and in the best case scenario, you will need nearly 1 year to implement your Agile transformation. So, my recommendation would be to go for an Agile Coach, they know how and when to start. An Agile Coach normally speaks with management and with employees to better understand why the organization wants to go through an Agile transformation, to understand the current situation of the company, their main goals and priorities, etc. And then, based on organizational feedback, the coach will select the right tools and practices for the company. 

But wait, the Agile transformation itself, what is that? Simply put, it is the transformation of an organization to one that is able to embrace and thrive in a flexible, collaborative, self-organizing, fast changing environment.

An Agile Transformation Is Made Up of the Following 3 Key Areas

1. Structure: this is how your organization will form teams at all levels of the company.

2. Governance: the way in which your organization intakes work, makes decisions about priorities, and balances work capacity with demand, as well as coordination across teams. 

3. Metrics and Tools: ;how you are going to measure organizational performance. This is about gathering the metrics, showing improvement, and communicating those metrics to the appropriate stakeholders. Just to give you an example, a typical KPI is delivery time, measured from the moment a customer request is accepted until the moment it’s delivered to production.

First of all, you need to think about the end results, about your goals. A good example would be to cut the lead-time for project delivery. Agile approaches are just your path to your goals, to your desired results. Here, it is important to answer the following questions: What is failure for you? What is your current performance level? What performance level do you want to achieve? Then, you need to plan and execute incremental improvements. After identifying your goals, you need to make incremental progress toward them, iteratively. Normally teams work with 2 weeks Sprints following an Agile transformation roadmap. As every organization or team has their own unique challenges, culture, processes, and goals that must be taken into consideration when creating an Agile transformation roadmap, a high-level plan that helps to communicate the vision and the steps an organization wishes to take towards their Agile transformation is necessary. 

Agile Transformation: Steps to Consider

1. Describe What Is Changing
This is perhaps the most important step that the leadership team should consider when beginning the Agile transformation. Leaders should clearly set the vision for change and how the business would benefit from that change. 

2. Create the Implementation Team
Once the transformational vision is identified, leadership should also identify the right set of people to own, plan, and run the transformation agenda. This team should include senior members of the organization. It is a good idea to include members who have experience in Agile project management. The leadership should also assign specific roles and responsibilities to the Agile implementation team members. 

3. Identify Quick Benefits
Now the implementation team should make sure that stakeholders see some quick benefits through the Agile ways of working. For example, they could identify a couple of projects where they deliver a set of critical functionalities to production faster using the Agile methods. 

4. Brand and Socialize 
The team should create a brand or a tagline for the transition to Agile ways of working. The tagline should be catchy and easy to remember, so it can stick for a long time. Agile transformation is a mindset change. Continuous communication is necessary to reinforce the need for Agile and its benefits to different teams. 

5. Train, Experiment, and Make Corrections
A Definition of Done, Sprint planning, and several other Agile methods should be practiced and analyzed. 

Continuous improvement is key here; leadership should get feedback from the stakeholders, on a continuous basis to validate that the business is, in fact, benefiting from Agile practices.

Time for Agile Transformation Statistics

Let’s look at numbers and facts to be sure that Agile transformation is a good strategy.

Project failure rates: Agile vs Waterfall 

  • Small projects: Waterfall 11% vs Agile 4%
  • Medium projects: Waterfall 25% vs Agile 11%
  • Large projects: Waterfall 42% vs Agile 23%

Key motivators for Agile transformation.
Why have so many organizations moved to Agile? Here's what 403 organizations, which already went through an Agile transformation, had to say.

  • 54% – enhances collaboration between teams that don’t usually work together.
  • 52% – increases the level of software quality in organizations.
  • 49% – increases customer satisfaction.
  • 43% – shortens time to market.
  • 42% – reduces cost of development.

Agile Transformation Case Study: ING

To start an Agile transformation, it is good to know how others did it and what it actually gave them. Let’s look at how and why a leading bank, ING, went through it and what it achieved.

In 2015, the Dutch banking group ING started its Agile transformation. ING was inspired by companies such as Google, Netflix, and Spotify and wanted to increase efficiency just like they did. And just by consolidating about 350 nine-person squads in 13 groups, they improved their time to market, boosted employee engagement, and increased productivity.

Actually, when they introduced an Agile way of working in June 2015, customer behavior was rapidly changing due to new digital distribution channels, and customer expectations were influenced by digital leaders, not just banks. And ING wanted to stop thinking traditionally about product marketing.

And Agile transformation was a must to be able to achieve that goal, as well as achieve flexibility and the ability to rapidly adapt to the changing circumstances. 

Also, ING had a goal to build stronger, more rounded professionals out of all their people. 
The idea was to work in multidisciplinary teams: a mix of marketing specialists, product and commercial specialists, UX designers, data analysts, IT engineers, etc. All of them should be focused on solving the client’s needs from their perspective, but at the same time, they should be united by common goals and a definition of success. 

Of course, bettering their organizational structure was considered as well. ING worked on creating clarity around the new roles and governance. 

As for the IT department, ING invested a lot in DevOps and continuous delivery. Their aspiration was to go live with new software releases on a much more frequent basis – every two weeks rather than having five to six “big launches” a year. The integration of product development and IT operations has enabled them to develop innovative new product features and position themselves as the number-one mobile bank in the Netherlands.

Discover how TDM Is Essential To Achieving Quality At Speed For Agile, DevOps, And Continuous Delivery. Brought to you in partnership with CA Technologies

Topics:
agile transformation

Published at DZone with permission of Ekaterina Novoseltseva. See the original article here.

Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}