Agile Is Not Enough

Agile Is Not Enough

By addressing architectural rigidity, closing talent gaps, and adopting a product mindset, leaders can realize agile’s power.

MIT Sloan Management Review,

5 min read
4 take-aways
Audio & text

What's inside?

Agile project management isn’t just for digital natives, but legacy organizations will need to clear a path for it.

auto-generated audio
auto-generated audio

Editorial Rating

8

Qualities

  • Applicable
  • Concrete Examples

Recommendation

For companies that aren’t digital natives, agile approaches often deliver disappointing results. Certain factors in organizations hamper agility and reduce its benefits. Writing for MIT Sloan Management Review, Will Poindexter and Steve Berez – partners in Bain & Company’s Technology and Agile Innovation practices – describe three organizational factors that undermine agility and outline what leaders can do about them.

Take-Aways

  • Leaders need to support agile development by fixing problems that inhibit it.
  • First, remedy rigidity in IT systems.
  • Second, restore and realign internal talent, and rethink accountability.
  • Third, borrow practices from product management.

Summary

Leaders need to support agile development by fixing problems that inhibit it.

Many organizations find agile software development fails to deliver on its promise because existing structures stonewall its effectiveness. For retailer Target, technical debt meant that inflexible architecture was holding the company back. Also, a habit of bringing in third-party contractors had hollowed out in-house expertise. Leaders need to remedy problems like these to unfetter the agile approach and reap its full potential.

First, remedy rigidity in IT systems.

Rigid legacy IT architectures stymie agility. To modernize applications, choose from four approaches: 1) Completely replace the system with a new one; 2) redesign the system, for example, by separating chunks of code so they work independently; 3) “wrap and trap,” that is, move core functions to APIs and build new systems to support new functions; or 4) in the case of low-impact applications, work around them.

Companies have to fix the speed bumps that slow down the rapid progress of agile software development.”

Which solution works best for your firm depends on various factors, including how much the old and the new system will need to interact. Leaders at Target chose to modernize applications that affect customer experience, such as searches on pricing information, while continuing to maintain adequate legacy systems, for example, for processing transactions.

Second, restore and realign internal talent, and rethink accountability.

After years of hiring IT managers for their business acumen rather than tech expertise and turning to external contractors for technical skills, many companies have bankrupted their IT shops of technological skill. Companies have also disconnected accountability from the people who build products. Leaders need to restore the tech orientation of engineering managers, who should take on the challenge of rebuilding the organization’s internal capabilities. To attract engineering talent, Target’s leaders switched to open source and set ambitious goals for the company’s digital initiative.

“Some of the best practices of former years have actually made it more difficult to hire the right people.”

Because agile teams create efficiencies, many people currently serving in “watcher” roles – such as project managers and business analysts – will need to adapt to more active roles. In addition, leaders should make developers accountable. Many companies are merging development, maintenance and support for the sake of streamlined development, speed and reliability.

Third, borrow practices from product management.

Link software development to business goals by organizing work by products rather than projects. Product teams offer stability, responsiveness and accountability. Funding on annual cycles, with quarterly reviews, supports the product model. Continual measurement, which is also associated with product models, offers better consistency in measuring outcomes. At Target, product managers aim to reach specific business goals and receive rewards when they do.

About the Authors

Will Poindexter and Steve Berez are partners with Bain & Company’s Technology and Agile Innovation practices.

This document is restricted to personal use only.

Did you like this summary?

Read the article

This summary has been shared with you by getAbstract.

We find, rate and summarize relevant knowledge to help people make better decisions in business and in their private lives.

For yourself

Discover your next favorite book with getAbstract.

See prices

For your company

Stay up-to-date with emerging trends in less time.

Learn more

Students

We're committed to helping #nextgenleaders.

See prices

Already a customer? Log in here.

Comment on this summary

More on this topic

By the same authors

Related Channels