A question often arises of how to connect strategies, which are long term thinking, with the shorter event horizon of small increments of delivery. The first part of the answer is to shift our thinking from project thinking to product/service thinking. This means that we think of the offerings we provide and consider how we consistently improve them instead of doing a series of one-off projects.
We manage these improvements by creating initiatives based on our strategies and then consider the business increments we want to release on a regular basis. Continue reading “Implementing Strategies with Small Pieces of Work- 8 days to #SAFeSummit”
Frameworks in and of themselves are not the goal. This is sometimes forgotten when Scrum is conflated with Agile. Scrum is a means to Agile, but it is not Agile in the same way a recipe is not the meal. Recipes have ingredients, an order to cook, how to cook, etc. Frameworks provide us with roles, rules, events, structure (of the people) and events. These are all required for effective work. Continue reading “What is the purpose of a framework? 9 days to #SAFeSummit”
Essential SAFe is intended for when a group of teams working together using SAFe. It presumes that a backlog has been created for the train(s) to work on. Most groups starting SAFe at the program level have done so, however, because they can’t get product management involved or believe the higher levels of SAFe are too complicated. Continue reading “What to do when prod management won’t provide MBIs to a program – SAFe countdown #10”
Many dev groups in large companies start with Essential SAFe because they are the only group starting SAFe. This is not a bad way to start. However, many of the concepts needed for such groups are described at levels above the Essential SAFe level. This can be confusing.
We suggest adding the MBI concept as we discussed in the earlier post. In this situation, as epics comes in, the dev group can break them into MBIs by collaborating with product managers & asking them the following questions: Continue reading “Essential SAFe for Large-Scale Companies – Countdown #11”
Essential SAFe was intended for large orgs adopting SAFe at the program level. But many mid-scale companies have adopted it as well.
Mostly they’ve done this because of: Continue reading “Essential SAFe for Mid-Scale Companies – #SAFeSummit 12”
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”