What Is “LEAN” or "AGILE" Business Analysis?
4.2 (69 ratings)
Course Ratings are calculated from individual students’ ratings and a variety of other signals, like age of rating and reliability, to ensure that they reflect course quality fairly and accurately.
2,655 students enrolled

What Is “LEAN” or "AGILE" Business Analysis?

Understanding How Lean Principles Affect Your Requirements Discovery Process in Agile Software Development
4.2 (69 ratings)
Course Ratings are calculated from individual students’ ratings and a variety of other signals, like age of rating and reliability, to ensure that they reflect course quality fairly and accurately.
2,655 students enrolled
Last updated 3/2019
English [Auto-generated]
Current price: $9.99 Original price: $19.99 Discount: 50% off
30-Day Money-Back Guarantee
This course includes
  • 44 mins on-demand video
  • 1 article
  • Full lifetime access
  • Access on mobile and TV
  • Certificate of Completion
Training 5 or more people?

Get your team access to Udemy's top 3,000+ courses anytime, anywhere.

Try Udemy for Business
What you'll learn
  • Understand how lean principles affect business analysis and the requirements definition process
  • Explain what lean requirements such as Features, User Stories, Epics, Scenarios, etc. look like in a lean and agile world

  • Apply lean principles to known business analysis techniques

Course content
Expand all 20 lectures 47:51
+ How Do Lean Principles Affect the Business Analysis Process?
5 lectures 13:56

Get to know your instructor and learn what topics will be covered in this overview.

Preview 02:06

A brief look at modern software development methods, their primary focus and methodologies.

Preview 03:31

Traditional Business Analysis contains a lot of waste. The lecture will show you the 9 most common wastes.

Preview 03:17

Lean or Agile Business Analysis is about combating waste. After this lecture you know which changes are necessary for your to your current Business Analysis Process to eliminate waste and optimally support new software development methods.

Preview 03:38

The importance of understanding the difference between project and product is at the heart of understanding how business analysis must change to support Lean and Agile software development.

The Shift Focus from Project to Product in Lean and Agile
+ Lean Requirements Are the Prime Deliverable of Lean Business Analysis
4 lectures 12:56

Software developers need requirements differently than in the past. This lecture explains the new forms that IT requirements have in a lean and agile environment?

Requirements Constructs in an Agile, Lean Environment

To communicate requirements to software developers, we still need to document them somehow and somewhere. However, the “traditional BRD" does not work in the lean and agile world. You probably know what I mean with "traditional BRD": Pages and Pages of documents with lots of sections which scream “Fill me or the document isn’t complete!”. This lecture shows what requirements repositories look like in a lean and  agile world. 

Product Backlogs and Other Requirements Repositories and Kanban Boards

A Product Backlog needs grooming. What does this mean and what tools and techniques can you use to do it?

Managing or Grooming, and Seeding Product Backlogs

The biggest difference between lean and traditional business analysis is the timing of the activities. Whereas conventionally business analysis has been primarily conducted at the start of a project, it is now an ongoing process throughout the product life cycle.

Knowing When to Do What in a Lean and Agile World
+ What Lean Techniques Does the One Wearing the BA Hat Need?
9 lectures 16:20

Learn the five fundamental questions that a Product Vision Statement answers.

Creating and Using a Product Vision (Next Big Thing)

One critical component to the success of agile, continuous integration, and continuous delivery software development is defining a Minimum Viable Product.

Defining a Minimum Viable (Buyable) Product

Learn how to make the best use of other people's time as well as your own.

Lean Requirements Communication Techniques

What differentiates great business analysts is an artistic ability to comprehend a problem that has not yet been solved and guide stakeholders to define the right solution that would provide significant value to the end customer.

Lean Problem Analysis Reveals Business Needs

Apply the SMART acronym to lean and agile software requirements constructs.

Writing SMART Features, Requirements, User Stories, and Epics

Cynefin is an amazing new technique that belongs in every business analyst's tool box. The Cynefin framework exists to help us realize that all requirements are not created equal and to help us understand that different situations might require different responses to successfully navigate them. 

Using Cynefin to Manage Uncertainty

In today's software development environment, good User Stories tend to be small. They typically represent at a few person-weeks worth of work.  Typically, a Product Owner or the business side teams will make Features, Epics, and User Stories ready for developers.

Right-Sizing Epics, Features, User Stories, and Requirements

A picture still says more than a thousand words. But for the models to be "lean", they need the right level of detail for a given target audience.

Developing, Presenting, and Analyzing Visual Models

Acceptance Test Driven Development (ATDD) and Behavior Driven Development (BDD) are increasingly popular development methods for agile teams. Automating Acceptance Testing is a prerequisite for successful implementation of Continuous Delivery.

Acceptance or Business-Facing Testing
+ Wrap-up
2 lectures 04:53
What Should You Do Now
Bonus Lecture: Mastering the Learning Curve
  • No tools or knowledge required
  • Interest in Business Analysis for Information Technology (IT) and Software Requirements Definition / Analysis

Take the Path to LEAN Business Analysis (as it relates to Information Technology)

In today’s world, you and your organization must be responsive, flexible, and make things happen quickly. You must do more with less – and faster. You no longer have business as usual, so why do business analysis as usual?


With the widespread adoption of Agile, software development has gone through some serious remodeling. Agile teams build robust products incrementally and iteratively, requiring fast feedback from the business community to define ongoing work.  As a result, the process of defining IT requirements is evolving rapidly. Backlogs replace requirements definition documents. User Stories, Epics and Features replace requirement statements. Scenarios and Examples replace test cases. The timing of business analysis activities is shifting like sand.


This course is a brief overview of how you can reduce waste in Business Analysis practices to optimally support the new lean and agile software development world. You will learn about topics such as:

·         The purpose of a product roadmap and a prioritized product backlog

·         The concept of a Minimum Viable Product (MVP)

·         Agile and Lean thinking applied to requirements discovery, analysis, and acceptance testing

·         Lean requirement constructs such as Features, User Stories, Epics, Scenarios, Examples, etc.

·         The importance of feedback from your customers to improve the product

Who this course is for:
  • Business Analysts
  • Product Owners
  • Subject Matter Experts
  • Project Managers
  • Managers of all levels
  • Business Architects
  • CIO
  • Anyone interested in Business Analysis for IT projects