Lesson 02: The Adaptive Approach

Let’s see how the second development approach works…

2020 update notes

A few things have changed in the latest version of the Scrum Guide (2020), and the ASF exam is updated based on those changes. However, our videos are not updated yet; so, please note the following changes:

  • There’s no “development team” anymore, but only Developers.
  • The recommended team size is now “10 people or less” for the whole Scrum Team.
  • It’s now called “self-managing” instead of “self-organizing” (same concept, different name).
  • There’s a Product Goal now, which is part of the Product Backlog, and sets the overall direction for the product.
  • The Sprint Goal is now considered as part of the Sprint Backlog.
  • The concept of commitments is introduced for the artifacts:
    • Product Goal is the commitment for the Product Backlog.
    • Sprint Goal is the commitment for the Sprint Backlog.
    • Definition of Done is the commitment for the Increment.
  • The Definition of Done is created by the whole Scrum Team now, and not only by the Developers.
  • Now, any time you finish an item (based on the Definition of Done), a new Increment is formed. It’s not about having just one Increment at the end of the Sprint.
  • The guide doesn’t suggest 10% as the ceiling for the amount of time Developers spend on Product Backlog refinement.
  • Sprint Planning has three topics now:
    • Why? -> Sprint Goal
    • What? -> Items from the Product Backlog
    • How? -> Tasks created by decomposing the items
  • “Estimating” is now called “sizing”. So, it’s the responsibility of the Developers to size the Product Backlog items.
  • “Value” is no longer one of the mandatory attributes of the Product Backlog items. The mandatory attributes are description, size, and order.
  • Instead of calling the Increments “potentially releasable”, the new guide calls them “usable” (more or less the same concept).

How is planning different in adaptive (Agile) and predictive (Waterfall) systems?

Self Evaluation