Business Analysis + Agile = Lean projects

Description

More and more Agile teams implement lean flow techniques to reduce the time to take a User Story from implementation to deployment. When we reduce implementation, test and deployment cycle time, we respond faster to our customers and deliver value sooner. But if it takes us a long time to get that story written or if our backlog is large, the total cycle time seen by the customer is still larger than necessary.

Can we apply lean and flow techniques to speed up what happens before development? Which techniques can we use to write better User Stories in less time? How can we estimate and validate the almost mythical "Business Value" to be sure that we work on what brings the most value to our customers? How can we "lean out" our backlog so that our Product Owner can spend more time on value-adding work?

Where do we find the people, processes and techniques that allow us to do all this? We think that business analysts have known the answers to these questions for years. We just forgot to ask them to join the Agile party.

Practical Information

Schedule