I work with many organizations that are fairly chaotic and far from Agile. While I’ve led fairly involved transformations, there are four actions a development group that’s 50-300 in size can take, mostly on their own, that can have a great impact. These are:
- Use Minimum Business Increments (MBIs) to identify enhancements to make to the system
- Have an intake product backlog (even better to add service classes) where all work in the system can be seen
- Organize around product teams. These are teams that can develop the MBIs defined. You can then create Scrum-Kanban teams (8-12 people) if the product teams are too big.
- Do DevOps phase 1- create visibility between dev and ops so ops knows what coming and dev understands what ops needs. Work together even if you don’t take steps towards continuous integration and continuous deployment.
These straightforward steps can be done quickly. Even if you are planning on using an Agile at scale approach, taking these steps early will help prepare for that.
As a metaphor for stages of learning it’s not bad. But even then it’s not a great metaphor. Let’s consider in the martial arts we’re trying to suppress our mind and learn certain moves. A collection of methods will let us chose the right moves from our repertoire. In knowledge work, we’re doing different things and wanting to engage our minds. I prefer to teach by:
Continue reading “I am not a big fan of Shu Ha Ri”
Scrum org defines “ScrumBut” as “that Scrum has exposed a dysfunction that is contributing to the problem, but is too hard to fix. A ScrumBut retains the problem while modifying Scrum to make it invisible so that the dysfunction is no longer a thorn in the side of the team.”
Scrum assumes that people doing Scrum stay within the confines of Scrum’s immutable artifacts, roles, events, and rules. However, when problems arise there are times that they can be solved with methods outside of Scrum. Sometimes, the cost of accommodating them is lower than the cost of fixing them. If you want to be doing Scrum you can’t do the first and Scrum gives no guidance on the second.
Continue reading “Why I hate the term ScrumBut”
Self-organizing, cross-functional teams are good when it is possible and advisable to achieve them.
The question is how do you create them? I tend to look at the edge conditions because I believe that when you learn to handle difficult cases you also learn how to manage and teach the easier cases even better.
Continue reading “Getting to cross-functional teams”
Our Agile at scale methods are often like driving on the wrong side of the road in reverse during a rainstorm. While the driver’s are well intended, and may even appreciate that at least they’re in a car, that are better ways. Here’s a list of things we must do that are usually not done when attempting Agile at scale.
Continue reading “We shouldn’t be surprised by Dark Agile. We should be surprised it works as well as it does”
Originally posted October 3, 2010
It is seductive to think about scaling Agile up from teams to the enterprise. It seems the correct path to take because you can almost always find a team or two where Agile methods lead to great improvements over Waterfall methods. But what works for a few teams at the local level often obscures the bigger picture: creating enterprise agility. Enterprise agility is the ability of an organization to deliver value quickly when needed. Sadly, I have seen many organizations achieve many successes locally – team agility – and move even further away from enterprise agility.
Continue reading “How Successful Pilots Often Actually Hurt an Organization”
Consider how your organization is currently developing products and/or services. As a thought experiment, consider how to make things worse. For example, have people work on too many things, don’t have a process where you resolve multiple requests, have product managers create requirements
for the team and just hand them off in written form, have developers and testers be in separate organizations, have managers makeup schedules and then berate developers when they are not met, … You get the idea.
I’m pretty sure you can see that things will get worse. Now, consider where in your organization you are doing some of these ineffective things. Could you stop doing some of them? Even partially? If it became worse when you started doing these wouldn’t it get better if you just stopped doing them? Sometimes improvements are easier to achieve just by stopping doing things incorrectly.
Of course, making these changes is no guarantee of improving your process, but generally, improvement will occur if you do them. As always, you must run any improvement as a hypothesis of it being a better way and validate that it is.
Learn more at Understand Your Options.
There are several concepts needed to do this:
- The items to be sequenced must be both the smallest batch of work that can be realized by the customer. They must also include all the work items required for the realization. Note that epics are too large, MVPs are about discovery of what’s of value and features often do not realize value on their own.
- A vision on what we’re trying to achieve that the owners of the work being prioritized can agree one. This has to take place at the leadership level.
- A way of comparing two items based on cost-of-delay and time to complete.
- Being able to implement the items quickly in the order they are sequenced. This provides motivation for the other two. This requires working on smaller sub-batches of this work. Having 3 months of work will not get us to attend to the delays between teams.
Whenever I see people having problems with prioritization, I know one or more of these items are missing.
#developer. When you finish something look for something else to help folks finish. See Manage Work-in-Process (WIP) by Focusing on Finishing
I tag each insight with one or more roles that it will relate to. I will provide a link when more information is available.
You can see the accumulated insights here.
The best way to get these as I add to the list is to subscribe (see upper right of this page).
#everyone. Working on too many things creates both multi-tasking and delays in our workflow. The causes of this include: interruptions, a lack of focus on finishing, have too large work items, product managers focusing on getting things started instead of finishing them and poor organizational structure.
Continue reading “What’s Obvious or Quickly Learned As It’s Pointed Out #1”