LeSS
Within a LeSS product, the Product Owner and the one Product Backlog decide; aangine works beside them at the portfolio level, where the organization funds several products, sizes their teams and plans everything that doesn’t run on LeSS.
Outside the backlog
LeSS is precise: one product has one Product Owner, one Product Backlog, one Definition of Done and one shared Sprint, however many teams work on it. Priorities inside the product are the Product Owner’s call. That restraint is why it works. It is also why the questions LeSS deliberately leaves to the wider organization deserve evidence of their own.
Most organizations run more than one product, plus operations, compliance work and parts of the business that don’t use LeSS. Someone still decides how many teams each product gets, what happens when a new product is proposed and where a budget change lands. In LeSS Huge, the Product Owner decides which teams work in which Requirement Area, a capacity decision that shapes what every area can deliver for months.
Change itself creates planning work. Defining products broadly turns several small backlogs into one, but the roadmaps, budget lines and commitments each former group carried don’t merge on their own. Moving from project funding to product funding rarely happens in a single step either; finance often still reports by project while teams already work from one Product Backlog.
How aangine works with LeSS
Products and Requirement Areas are planned as portfolio items or capacity pools, with stable teams as the capacity, and funding and team-allocation scenarios are compared before they are decided. The Product Backlog and Sprints are not managed in aangine.
Plan each product with its stable teams as capacity, next to operations and other work that doesn’t run on LeSS. Add a product, move a team or change a budget, and one click replans the portfolio to show what each product can still deliver and where the gaps are.
Plan each Requirement Area as a capacity pool, with its large roadmap items, dependencies and any fixed dates. Compare the current team split with a proposed move side by side: what lands when, which area runs short, which dates hold.
Keep projects and products in one plan against the same teams while finance still reports by project. Move budget lines to products, with cost rates attached to teams, and compare both funding views as scenarios before changing the books.
When product groups merge under a broader definition, bring their plans together. Shared teams are counted once, dependencies are kept, and the combined demand is replanned to show what still fits and what has to move.
In practice
In LeSS Huge, the Product Owner decides which teams work in which Requirement Area. Here is that decision with a live plan, while the Product Backlog stays with the Product Owner.
Each Requirement Area becomes a capacity pool with its stable teams and the large items it is expected to deliver, including any dates customers were told about.
Keep the teams where they are and replan. See what each area delivers, period by period, and which dates hold.
Move teams from one area to another and replan. Compare both scenarios side by side on timing, capacity and cost.
The Product Owner chooses, with the trade-offs visible to every Area Product Owner. The approved plan goes back to the tools the teams use.
How aangine works
aangine is the decision layer above the tools you already use. No rip & replace: it imports your plans, replans them in one click and pushes the approved plan back.
The result: faster, clearer decisions when it matters most.
What our customers report in their case studies. Read the customer results
Keep exploring
LeSS and Large-Scale Scrum are trademarks of their respective owner. Framework and method names are used to identify them only. aangine and Continuous Software are not affiliated with, or endorsed by, the owners of these frameworks and methods.
Book a demo
Book a demo and bring your products, their stable teams and the funding or team-allocation question you face next. We’ll show it as scenarios, with the Product Backlog left where it belongs.
