Skip to content
LB Consulting Group
← All cases

Visma Commerce

One planning rhythm for a whole product portfolio

Industry
Commercial software, R&D
Period
2014–2015
Where
Sweden, Lithuania and Romania

60+

people trained in Leading SAFe in the first phase

Day 2

of a quarterly plan, teams could say with confidence whether the scope was realistic

3

countries working on one planning cadence

The challenge

Visma Commerce’s development teams already worked in Scrum and Kanban. The hard part was everything above the team: product management and executives couldn’t see collective progress, quality and health across interdependent teams and products. Expectations, estimates and measurements weren’t aligned between the people funding the work and the people doing it.

What we did

Starting in autumn 2014, Visma Commerce adopted the Scaled Agile Framework® across its product portfolio, with LB Consulting Group as trainer, coach and tool mentor.

  • Shared foundation. Everyone in R&D, product management and targeted executives took a two-day Leading SAFe course, so the whole organisation started from the same picture.
  • Economics-driven backlog. Product management ranked features with Weighted Shortest Job First and prepared them before each joint planning.
  • Bottom-up quarterly planning. All teams and product management planned one quarter ahead together, in five to six two-week sprints, and set business objectives jointly.
  • Inspect & Adapt. Every quarter ended with a system demo and a review of objectives, defect trends and business value, for all teams at once.
  • Tooling and engineering. Jira set up for planning and dependency tracking across all levels, build pipelines for on-demand builds, and test automation from unit to acceptance level.

Results after one year

  • Teams could say with confidence on day two of the quarterly plan whether the expected scope was realistic, so customer expectations were set earlier.
  • Dependencies between teams were mapped and visible on dashboards from the first day of planning, so they were resolved faster.
  • Smaller, more frequent releases. Marketing, once a step ahead, had to work to keep up.
  • Feature priority followed a documented method instead of who shouted loudest.
  • Less parallel work and context switching in teams, and faster throughput as a result.

Based on the original write-up.

Thirty minutes, no slides: tell us where it's stuck.