This presentation shares in details how Skandinaviska Enskilda Banken implemented the SAFe agile framework, creating tribes, agile teams, iterations, PI Planning, Review, Backlogs or Kanban portfolio. The presenter adds a “but” to this, as the organization still does not know the priorities, requirements and their roles.
Resources on Scaling Agile frameworks like the Scaling Agile Framework (SAFe), LESS, Nexus, Disciplined Agile Delivery (DAD), Scrums of Scrums, etc.
Are Agile methods appropriate for safety-critical products? This presentation describes how an Agile project in the nuclear industry, has managed to be Agile while maintaining nuclear safety. A related issue is the complex nature of the work, spread over multiple teams in multiple companies, with work projected to continue for over 5 years.
By now most large enterprises are past the experimenting stage with Agile. Many are beginning to realize that simply training teams in Agile techniques like Scrum and Kanban, while useful, is not enough to achieve real business transformation.
Scrum of Scrums is a technique used to scale Agile by dividing the groups into Agile teams of 5-10. Each daily scrum within a sub-team ends by designating one member as representative to participate in a daily meeting with ambassadors from other teams, called the Scrum of Scrums. This article provides some tips on how to succeed with Scrum of Scrums.
In this presentation, Bas Vodde shares the creation of LeSS and within that side-track on explaining better how LeSS works. LeSS is a lightweight (agile) framework for scaling Scrum to more than one team. It was extracted out of the experiences of Bas Vodde and Craig Larman while Scaling Agile development in multiple different types of companies, products and industries over the last ten years.
Agile development starts with small Scrum teams tackling small problems. After some initial successes the organization gets more ambitious, and tries to get more teams tackling bigger problems. At some point these endeavors run headlong into organizational finance and governance structures from a different era, designed with huge projects in mind, and it usually doesn’t end well.
Agile development starts with small Scrum teams tackling small problems. After some initial successes the organization gets more ambitious, and tries to scale Agile, getting more teams tackling bigger problems. At some point these endeavors run headlong into finance and governance structures from a different era, designed with huge projects in mind, and it usually doesn’t end well.