InfoQ Homepage Scaling Agile Content on InfoQ
-
The Right Way to Scale Agile: Scaling Value Delivery over Process
There is no one way to scale agile. In order to find the right way for you organizations you need to understand what you are trying to achieve and create a process that works to deliver that outcome. This article shows how organizations can help teams remain true to agility and deliver value as they scale Agile — whether from top-down or bottom-up — without following a one-size-fits-all process.
-
Q&A with Bas Vodde on the LeSS Framework: Principles, Practices and Core Concepts
Bas Vodde and Craig Larman framed and introduced Large Scale Scrum (LeSS), the scaling model. Large-Scale Scrum (LeSS) is Scrum applied to many teams working together on one product. InfoQ interviewed Bas Vodde to discuss more about LeSS framework.
-
Book Review and Author Q&A on Scaling Agile: A Lean JumpStart
Sanjiv Augustine is the author of Scaling Agile: A Lean JumpStart, a short and informative book about scaling Agile methods. It covers an essential set of Lean building blocks as a starting foundation for larger Agile scaling frameworks, including the Scaled Agile Framework (SAFe), Large-Scale Scrum (LeSS), and Disciplined Agile Delivery (DAD).
-
Q&A on the Scrumban [R]Evolution
In the book “The Scrumban [R]Evolution: Getting the Most Out of Agile, Scrum, and Lean Kanban" Ajay Reddy describes what Scrumban is, explores the principles and theories on which it is based, and shows how Scrumban can be deployed in organizations.
-
Four Must-Have Rules for Scaling Enterprise Agile
Agile methodologies long ago proved their efficiency with small co-located teams. But when it comes to moving past team level to organizational scale, Agile practices are up against enterprise development realities like distributed teams, multi-component projects and traditional resource management. No organization is too big, complex or distributed, but they must follow these simple rules
-
Scaling Mobile at XING: Platform, Framework and Domain Teams
This article describes learning from XING on how to scale mobile development such that as many teams as necessary can contribute to the development of mobile apps (on both iOS and Android platforms) and at the same time keep the apps consistent, stable and shiny. It summarizes the key decisions and structural changes they made in order to enable scaling mobile from 2 to 10 teams.
-
Gunther Verheyen on Scaled Professional Scrum – Nexus Framework
The Scaled Professional Scrum framework of Scrum.org provides guidance to organizations engaging in efforts to scale their product development done through Scrum. InfoQ interviewed Verheyen about the Nexus framework.
-
Q&A with Ron Jeffries on The Nature of Software Development.
The book "the nature of software development" intents to help people to organize their thoughts about value and find ways to deliver value in software development. It's a book of questions, not of answers, says author Ron Jeffries, for readers to discover the natural way to develop software, the simple way, inside themselves.
-
From a Project to a Product Approach Using LeSS at Agfa Healthcare
By changing the inner workings from a project perspective to a product perspective Agfa Healthcare established a less complicated process using a single backlog for the entire organisation. Main advice is to try to avoid setting up silos where they do not belong. When applying LeSS it is important to stick to its basic rules even though they are, in most organisations, very disruptive.
-
Q&A with Dean Leffingwell on Leading SAFe LiveLessons
Dean Leffingwell’s “Leading SAFe LiveLessons” - training videos are based on Lean-Agile transformation concepts at enterprise level. The Scaled Agile Framework (SAFe) provides practices, roles, activities and artifacts for applying Lean and Agile development at enterprise scale.
-
Using Large-Scale Scrum (LeSS) with Feature Teams to Ship Your Product Every Sprint
An interview with Larman about LeSS and what makes it different from other scaling frameworks and using empirical process control to increase organizational agility. Larman also explained how organizations can work with feature teams, and gave examples of how teams and stakeholders can be in direct contact with their customers and users and can work together to ship their product every sprint.
-
Inviting over Imposing Agile
We are at a crossroads in the agile-adoption narrative. Early in the story teams were the “bottom-up” vector for agile spread. Next the way agile spread started to shift away from teams to executives and “management”. Recent developments move us towards consultancy for bring agile to larger enterprises that struggle with change. Which way is agile going to go next?