Whitepaper Whitepaper

Harvard Business Review: Why agile goes awry and how to fix it

Read the article

You must provide your contact details to receive this content. This means that we’ll occasionally invite you to Optimizely events and webinars and send you industry insights and product news.

Optimizely will store and process your personal data as described in our Privacy Policy. You can opt out at any time.

As organizations strive to become more adaptive and nimble, they are adopting agile software development. While Agile can have tremendous benefits such as better collaboration between teams, improved responses to change, and greater learning, it can end up hurting teams when implemented incorrectly.

Many engineering and product teams are deeply focused on understanding what customers want and what will motivate them to buy. The best teams focus on maximizing their “speed to truth.” To do this, teams need to experiment and iterate quickly.

Read this Harvard Business Review article to learn why experimentation can help you better focus on customers, how to prevent the Agile process from going awry, and more:

  • Deliver what customers want through experimentation
  • Develop a customer-centric process to business software development
  • Organize teams to emphasize collaboration
  • Question current processes