Here is part 5 of the presentation to the IIBA® (International Institute of Business Analysis TM) Cincinnati Chapter and the Bluegrass IIBA® Chapter.

NEW workshop: Lean Business Analysis for Lean Requirements – Simply Put!

Helping Product Owners and Business-side Teams Discover and Write Requirements, User Stories, Features, Acceptance Tests, Scenarios, and Examples

About Part 5: In Lean and Agile software development environments, all levels of Business Analysis are strictly done on an as-needed basis. This video introduces typical business analysis activities at each stage of a Lean / Agile development life cycle and correlates the respective business analysis techniques.

If you are interested in learning the presented business analysis techniques, check out our self-paced, online course Getting and Writing IT Requirements in a Lean and Agile World.

Fundamentally, Agile software development depends on Just-In-Time (JIT) analysis. The timing of Strategic, Tactical, and Operational Business Analysis in an Agile environment is different than in traditional environments. However, every software development life-cycle (yes, even Lean and Agile, or let me say ESPECIALLY Lean and Agile approaches) needs some degree of up-front definition of business vision, goals, objectives, and high-level stakeholder requirements. This is accomplished during Strategic Business Analysis. This is followed by the Tactical Business Analysis stage where developer and business teams flush out User Stories and Acceptance Tests. This stage often starts with a Sprint 0 or requirements discovery workshop. During the release planning stages or, at the latest, during the sprint, developer and business teams flush out the solution requirement level often referred to as the Operational Business Analysis stage.

Read the overview of the 6-part Presentation presented to the IIBA® (International Institute of Business Analysis TM) Cincinnati Chapter and the Bluegrass IIBA® Chapter.