Traditional software delivery is broken

Traditional software delivery (many times referred to as Waterfall), only works in very specific applications and is no longer the choice for most organizations trying to improve their software delivery.

By the time most organizations get through the process of scoping the requirements, cost and schedule of a software initiative, the landscape of the solution has changed. Processes change, people leave, organization goals shift, etc.

On average, Agile Projects have a 42% success rate compared to 26% success rate for traditional/waterfall projects from 2013-2017.
— Jim Johnson, Standish Group, Chaos Report, 2018

What is agile / scrum?

Scrum, as originally outlined in the Scrum Guide, is a framework for developing, delivering, and sustaining complex products by a single team. Since its inception, its usage has extended to the creation of products, processes, services, and systems that require the efforts of multiple teams. Scrum@Scale was created to efficiently coordinate this new ecosystem of teams in a way that optimizes the overall strategy of the organization. It achieves this goal through setting up a “minimum viable bureaucracy” via a scale-free architecture, which naturally extends the way a single Scrum team functions across the organization.

Scrum_Inc_Sprint.jpg

How Spotify utilizes Agile & Scrum

Spotify improved their software delivery by implementing their own brand of Agile/Scrum, customizing it to meet their needs.

Agile and Scrum are analogous to making a salad. There are myriad ways to make a salad (amounts, ingredients, dressings, etc), and everyone’s sald turns out different; although, everyone has a general idea about what a salad is. Using this analogy, Agile and Scrum provide a framework, and you finesse it to your liking.


What is Scrum@Scale?

Scrum, as described above, was designed for a single team to be able to work at its optimal capacity while maintaining a sustainable pace.

Scrum@Scale allows numerous sprint teams (and potentially the entire organization), to work in an agile fashion. In the field, it was found that as the number of Scrum teams within an organization grew, the output (working product) and velocity of those teams began to fall (due to issues like cross-team dependencies and duplication of work). It became obvious that a framework for effectively coordinating those teams was needed in order to achieve linear scalability. Scrum@Scale is designed to accomplish this goal via its scale-free architecture.

By utilizing a scale-free architecture, your organization is not constrained to grow in a particular way determined by a set of arbitrary rules; rather it can grow organically based on its unique needs and at a sustainable pace of change that can be accepted by the groups of individuals that make up the organization. The simplicity of the Scrum@Scale model is essential to a scale-free architecture and carefully avoids introducing extra complexity that will cause productivity per team to decrease as more teams are created.

Scrum@Scale is designed to scale across the organization as a whole: all departments, products and services. It can be applied across multiple domains in all types of organizations in industry, government, or academia.

How Toyota utilizes Scrum@scale


Why choose Annadel Consulting to help with your Scrum@Scale implementation?

Since the early 90’s, our team members have been passionate about improving the software delivery process for small, medium, and large enterprise organizations. We’ve seen many software projects succeed (and have seen some fail), and therefore we understand how to best implement delivery processes that will work for you.

We’ve worn almost every possible hat a software delivery team member can hold, from programmer up to leading a software company with dozens of software delivery teams.