Adaptive Software Development (ASD)

What is Adaptive Software Development (ASD)?

Adaptive Software Development (ASD) is a direct outgrowth of an earlier agile framework, Rapid Application Development (RAD). Moreover, it aims to enable teams to quickly and effectively adapt to changing requirements or market needs by evolving their products with lightweight planning and continuous learning. Lastly, The ability to adapt allows teams to align with organizational goals. The ASD approach encourages teams to develop according to a three-phase process: speculate, collaborate, learn.

What’s the history of Adaptive Software Development (ASD)

Project managers John Highsmith and Sam Bayer are credited with inventing the Adaptive Software Development methodology in the early 1990s. Moreover, they developed ASD as a more iterative and shorter-interval version of the Rapid Application Development (RAD) agile framework.

Highsmith and Bayer used their new project management approach, designed around one-month projects with one-week iteration periods, to complete more than 100 real-world commercial software projects across many industries. That is to say, they wrote about their new approach in Highsmith’s 2000 book, Adaptive Software Development.
Download the Product Planning Guide ➜

What are the Strengths and Weakness of Adaptive Software Development?

ASD’s strengths include:

  • Focused on the end users, which can lead to better and more intuitive products
  • Allows for on-time and even early delivery
  • Encourages more transparency between developers and clients

ASD’s weaknesses include:

  • Demands extensive user involvement, which can be difficult to facilitate
  • Integrates testing into every stage, which can add to a project’s costs
  • Emphasis on rapid iterating and continuous feedback can lead to scope creep

Should you use ADS?

Adaptive Software Development can be a viable methodology if your organization prioritizes rapid delivery of products and sees value in continuously evolving your offerings. However, if you do not believe it would be feasible to secure deep involvement from your users, or you are not willing to add costly continuous testing throughout your development process, this might not be the right agile framework for you.