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

Få tilgang nå!

Read the article

Du må oppgi kontaktinformasjonen din for å få tilgang til dette innholdet. Dette betyr at vi av og til inviterer deg til Optimizely-arrangementer og webinarer og sender deg bransjeinnsikt og produktnyheter.

Optimizely lagrer og behandler dine personlige data slik vi har beskrevet det i vår Personvernerklæring. Du kan trekke samtykket ditt når som helst.

Optimizely lagrer og behandler dine personlige data slik vi har beskrevet det i vår Personvernerklæring. Du kan trekke samtykket ditt når som helst.

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