Many mid-scale companies feel they are in the dilemma that LeSS is insufficient while SAFe feels like too much. Many decide to use the SAFe program increment planning event but are left with little guidance on product management. SAFe”s intriguing because it provides many good insights – MVPs, MMFs, Solutions, and more. But many of these are discussed mostly at the portfolio level or above. Continue reading “How Midscale Companies Can Use a Lightweight Version of SAFe – #SAFeSummit 13”
The purpose of Agile@scale is business agility- the quick realization of value predictably, sustainably & with high quality. We know we want to realize value in increments, but what do we call these increments? I say “realize” not “deliver” because the mere delivery of software often has no value- it usually requires non-software aspects to be useful. Continue reading “Focus on Realization of Value, Not Delivery of Software – #SAFeSummit 14”
We suggest our clients focus on:
- Systems thinking
- Quarterly business planning or shorter
- Small business chunks so you can release quickly
- Creating the right environment for teams to work in
- Acceptance Test-Driven Development
- A flow-based mindset
In over a decade of doing Agile at scale, we’ve found the most important concept to be that of the smallest realizable chunk of business value (hashtag14’s topic). But why small? Continue reading “The Case for Small When You Are @Scale – #SAFeSummit 15”
There are three types of ‘scaling Agile’:
- Spreading team Agility across the organization. In most mid-large organizations this does not address the root of their challenges which are not at the team level
- Increasing the size of the projects – almost never a good idea
- Having the entire value stream be Agile – the right thing to do
In Countdown #17, I discussed the essence of SAFe – those principles that are essential regardless of how large your org is. If your dev group’s just a team, Scrum’s sprint planning can be the intake control process you need. If you org is larger with multiple stakeholders, product management is likely required. Large organizations likely have multiple portfolio and more is needed. Continue reading “What does scaling mean? Countdown #SAFeSummit #16”
17 days until I’ll be at the SAFe Summit (10/2-4). This begins a series of daily posts about SAFe & how Targetprocess & Net Objectives provides a complete solution for mid-scale companies both using (& not) using SAFe.
SAFe is not intended to be followed dogmatically, although that often happens. Understanding the essence of what SAFe is attempting to accomplish will enable you to use it better. Continue reading “The Essence of SAFe – countdown #17”
I tweeted the following
If you saw a new engineer designing a long suspension bridge without attending to the wind would you say “let him figure it out, we’re Agile and that means we trust people”? why is it different in software which is even more complex?
The definition of ‘value stream’ changed a bit in SAFe 4.0 to 4.5
Here’s the current definition of a value stream from the SAFe site: Continue reading “Value Streams in SAFe”
First, let’s get clear. All organizations are complex. So if you’re doing software dev you are in a complex system. Aspects of it also have the possibility for chaotic events (such as the Martian Lander disaster).
But let’s consider something necessary to consider in even simple situations. Continue reading “Why the difference between “necessary” and “sufficient” is even more important in complex systems”
From the moment Scrum became more popular than XP, the software dev community has been focusing on frameworks more than Lean-Agile principles. It’s not surprising this has happened. It’s a lot easier to understand a framework than the principles underneath them.
The challenge that occurs is when the framework becomes the goal. Continue reading “Frameworks, proxies and Lean-Agile Principles”