Bain uses cookies to improve functionality and performance of this site. More information can be found in our Privacy Policy. By continuing to browse this site, you consent to the use of cookies.

We have limited Spanish content available. View Spanish content.

MIT Sloan Management Review

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.

  • marzo 11, 2019
  • min read

Article

Agile Is Not Enough

This article originally appeared on MIT Sloan Management Review.

Agility is critical for companies trying to keep up with customer expectations and emerging business trends. By adopting an agile approach, software development teams can create new products and services rapidly, transform processes, and even help reinvent the organization. But agile teams can stumble as they interact with and depend on others, so it becomes a matter of anticipating and mitigating these choke points in the organization.

Consider a credit card company that wants to update its mobile app so customers can easily check and redeem their reward points. The company creates an agile team of developers, designers, and an initiative owner who understands customer behavior and can make decisions about focus and priorities. This team updates the app in a few weeks, but it takes months for another part of the organization to provide the data feeds from the rewards system, and longer still for another part to integrate these changes into the app, delaying the rollout of the new functionality.

Bain Partner Will Poindexter addresses how to overcome three major impediments to rapid innovation.

Customers like the new feature, but now they also want to see recent points activity when they log in. The members of the original agile team have moved on, and since everyone is busy, it takes a few months to pull together a new team. This team makes the changes but overlooks a defect that causes the update to fail vulnerability testing. Once fixed, the operations team refuses to release the code to customers without more thorough testing. Disagreements between the development and operations teams about the extent of that testing further delay the new update.

This kind of story is all too common for many companies, even those with a strong technological focus. Several years ago, this was the case at Target. The company suffered from significant technical debt built up from years and years of growth. Critical parts of the business were supported by monolithic architecture that limited how rapidly it could innovate and introduce change. This growth also meant a rapid increase in demand for technology resources—demand that Target met by significantly augmenting its staff with third-party contractors.

The obstacles that Target and other organizations have encountered in their transformation narratives lead us to an important lesson: Agile is powerful, but it is not enough. To have a truly effective digital organization, companies have to fix the speed bumps that slow down the rapid progress of agile software development. Three impediments in particular work against agile in most organizations: rigid architecture, poor talent management, and lack of a product mindset. In this article, we’ll explore each of these and introduce ways organizations can overcome them.

Read the full article at MIT SMR. 

Will Poindexter and Steve Berez are partners with Bain & Co.’s Technology and Agile Innovation practices. Poindexter leads the practices in the Americas, and Berez is a founding member of both. They are based in Chicago and Boston, respectively.

Tags

Want to continue the conversation

We help global leaders with their organization's most critical issues and opportunities. Together, we create enduring change and results