Toggle Menu

Insights / Agile Transformation / Introducing the Agile Extension to the BABOK® Guide version 2

August 23, 2017

Introducing the Agile Extension to the BABOK® Guide version 2

2 mins read

This summer, the International Institute of Business Analysis (IIBA) partnered with the Agile Alliance to update its Agile Extension to the Business Analysis Body of Knowledge (BABOK) Guide.

While Agile and analysis practices have advanced, the Agile Extension had not. Thus, a core team of seven contributors joined together to update this guide. The goal of the guide is to demonstrate the link between Agile and analysis.

Why Does Agile Matter for Analysis?

Agile is a mindset, not a framework or set of activities. It is about collaboration, putting the customer first, and learning from each other to deliver value.

Agile isn’t about delivering everything you want, and it’s not about delivering it faster. It’s about delivering the most important, highest value items in short cycles to engage customers early and shorten feedback loops.

Analysis is critical to this process to understand what are those high value, high return, high importance items. Analysis is also critical to decompose large items into small ones to enable those short delivery cycles.

So, analysis is Agile.

Seven Principles of Agile Business Analysis

The first Agile Extension introduced the Seven Principles of Agile Business Analysis, and the core team found these are still relevant today.

  1. See the Whole
  2. Think as a Customer
  3. Analyze to Determine What is Valuable
  4. Get Real Using Examples
  5. Understand What is Doable
  6. Stimulate Collaboration and Continuous Improvement
  7. Avoid Waste

The principles give us a common language to understand and describe agile business analysis.


The Agile Extension version 2 introduces the concept of a multi-level, rolling planning horizons. These horizons bring together the big picture with a narrow view. In Agile business analysis, we balance seeing the whole picture with diving into specific aspects to understand what is doable and avoid waste.

The Agile Extension defines three horizons: Strategy, Initiative, and Delivery. This framework has some fluidity, but the core team found these levels consistently across Agile business analysis practices. Most importantly, there is a critical feedback loop between these three horizons which ensures the success of an initiative.


Thanks to the partnership between IIBA and Agile Alliance, this document will be available at no charge on their websites for members. Go to IIBA or Agile Alliance to access the document.

You Might Also Like


Human Centered Design: The What, Why, and How

Have you ever been on a website and felt that it was made for you?...

Excellian Spotlights

Mahreen Rashid Announced as a 2023 WashingtonExec’s HR Executive of the Year Finalist

“It is vital that we create and enable opportunities for anyone looking to pursue a...


Software Lifecycle Development: Day 0 vs. Day 2 DevSecOps

Improving the software development lifecycle has benefits both internally and externally, particularly when security is...