The Scrum Guide tells us that its roles, events, artifacts, and rules are immutable. This is fine if you want to ensure you are doing Scrum. But this can force you to use practices that aren’t appropriate for you as well. Scrum is based on the philosophy that following its roles, events, artifacts, and rules will facilitate Agile. While this is often true, doing so sometimes either cannot be done economically or at all. Cross-functional teams and being able to plan ahead is not something that can always be accomplished. Just as important, sometimes Scrum’s roles, events, artifacts, or rules are not appropriate for a particular situation.

Amplio@Teams avoids this problem by specifying not practices, but rather objectives to me met. When a particular practice doesn’t seem appropriate or is too hard to implement, you don’t abandon it, instead you find another one that can meet the objective and which is both more appropriate and likely easier to implement. There is a reason (objective) for the roles, events, artifacts, and rules. While it may be advisable to change one, the new practice must achieve the original intended objective.

Making a change can be accomplished with this four-step process:

  1. Are you having challenges with the practice because it is being done poorly? If Yes, then inspect and adapt and see if you can do it better. If No, continue.
  2. Is there something else in the organization that is causing us this problem? If Yes, then see how to fix that or at least influence the fixing of it. If No, then continue.
  3. Is the ecosystem that the team finds itself in causing the problem? That is, are people not collocated when they need to be or are required skills missing? Can you improve on this? If yes, do so. If No, continue to see if another practice that works within this ecosystem will work better (see next step).
  4. What else can we do that meets the same objective of the practice? If there is something else you can do, then try that. If not stick with the practice until you learn more.

There is no definitive set of alternative practices to Scrum. You can find several in any number of places. Or you can make up your own as long as they align with first principles

How to tell if a change is better

There is a set of underlying principles that can provide an indication if a change will improve things. This is always in theory to some extent, because even if a change will improve things if made, there are often side effects caused by people not adopting the change that work against it. We therefore must always be diligent and validate any change we make.

The measure to use is the value stream impedance scorecard (VSIS). In a nutshell, the VSIS indicates how much resistance the system will impose on work being attempted. It is based on what improves the total value manifested. Lowering this resistance usually results in more value manifested.

So What If It’s Not Scrum?

Of course, following the procedures may take you out of the arena of what Scrum defines. But you should be more concerned about being effective than if you’re doing Scrum.  

Go to Amplio@Teams: The Path to Effective Lean-Agile Teams

Go to Being a Professional Coach

New Workshop

More Info >>

Upcoming Events

None