So, we talked about predictive systems. When we cannot use a predictive system, an adaptive one is a great replacement. Adaptive systems are those commonly called “Agile”.

This system is used when we have a result in mind, but we cannot be sure what kind of product can create it, and therefore “prediction” is not possible. This is the case when the market changes dramatically (thing of IT), or it’s not possible to really understand the market or the client. 

In this case, we will have a number of cycles. In each cycle, a subset of the product is designed, planned, built, tested, and made ready for deployment. We provide it to the customer or end user and receive feedback. We’ll “adapt” based on the feedback; we understand what should be the output of the next cycle.

The cycles are run, until enough value is created in the latest product and we’re close enough to the expected result. This is adaptation; this is Agility.

Let’s start talking about the Scrum framework, shall we? We’ll start it tomorrow by discussing how a Scrum project is started.


- Nader

P.S. the best case for Agility is software development. That’s why all the explanations and examples in this course are based on software development. It’s possible to use Agile for some other projects, but not all of them.