Lean Agile

Lean Agile supports the continuous delivery of business value for less complex work that generally impacts fewer systems and teams. It bridges the gap between traditional developments and fully scaled agile by delivering business value faster by following appropriate Lean and Scaled Agile principles.

Use Lean Agile when...

· Less complexity, typically impacting fewer systems/apps/teams (1-3 Agile teams)

· Business Partners are committed to working differently and remain actively involved

· The work has a continuously prioritized program-level backlog

· Work has quarterly, capacity-based funding. Capacity Funding is established at the beginning of the engagement, usually in partnership with business client finance and technology portfolio teams

Three paths, different criteria

Scaled Agile Framework® , Lean Agile, Traditional (project-based Waterfall/Blended/Agile)

Lean Agile is for experienced Agile teams that are stable (less than 20% turnover of team members). These teams are ready to increase their productivity by adding scaled agile practices to their toolkit.

Once multiple Agile Teams are working together to deliver a common goal – they may need the rigor of Scaled Agile Framework® (SAFe®). SAFe aligns teams into Agile Release Trains (ARTs). SAFe requires certain roles (for example, Release Train Engineer/RTE) and ceremonies (such as in-person PI Planning) that Lean Agile does not.

Example Scenarios

I hope this information has been useful to you and good luck!