Shiny Objects and SAFe

Recently, while I was teaching new teams how SCRUM fits in a larger SAFeTM structure, the question kept

Recently, while I was teaching new teams how SCRUM fits in a larger SAFeTM structure, the question kept coming up from a Product Owner. “Yes, all this new SCRUM stuff is great, BUT how do I juggle multiple requests from multiple stakeholders?” “My customers keep asking for more and more without taking anything off the plate.” I often refer to this as stakeholders chasing “The Next Shiny Object.” Or, I want it all and I want it now.

Our business customers often fall into this mode due to the delivery nature of the waterfall projects we have been running for 40 years, where we deliver late, we do not deliver all they want, and it is not the best quality. As a result, I think they ask for everything they think they might need, which results in some of the difficulties of delivering what they REALLY need.

So the answer led me to explain how, not only the SCRUM teams deliver work, but each of the teams is part of a larger ecosystem of project, program and portfolio control that helps define work and priorities from original stakeholder requests to the work dispatched to the individual team members.

Walking the team through the SAFe Big Picture was exciting, and I’m not sure everyone took it all in a short time, but the questions kept coming: “Where do we fit in?” “What happens if I get buttonholed in the hallway and asked to do something by one of my customers, do I promise to deliver what they want?” and (well, you get the idea), new practices, new ways of acting and reacting to old situations. As team members they were afraid to tell a customer “No, we cannot do that” or “I don’t know we have the staff to cover that request.”

In a recent engagement, the CIO never refused a request. We needed a way to corral her “Can’t say no” responses with SAFe. And we did. I’ll explain further a little later. The end result of these problems is a book of work that continues to expand, priorities that are not met, pet projects that take precedence and generally, queued work that gets out of balance with priority requests.

SAFe has some of the answers. We need to look to adding a strong helping of simple discipline and rigor following the SAFe principles and practices. But in my opinion, SAFe adoption alone is not enough – you need the Circle of Life in an IT shop: People, Practices and Tools. All three combined are a recipe for success.

SAFe BigPic

SAFe Big Pic -Scaled Agile Framework & SAFe are registered trademarks of Scaled Agile, Inc.

 

People – SAFe does give us governance structures, roles that staff needs to play and definitions of how they interact. This is highly valuable as it gives substance to the various roles in SAFe, while being flexible enough to add or revise, as needed. After all, it is a framework.

Process – With the introduction of SCRUM and Product Owners, all the Inspect and Adapt cycles, potential added capabilities with Portfolio management to direct traffic, the picture looks a lot better from the standpoint of someone driving and managing those priorities. Now we actually have a framework to customize and make “our own” to manage a book of work for a medium to large shop (say 500 – 10,000 staff). New versions of “Essential SAFe” are available for smaller shops as well.

Tools – They give us the necessary discipline and rigor to carry through with the often complex dance of delivering systems and features to production. We need a single global collection point as a repository of the work to be delivered, a means of dispatching the work to various teams, a collection of metrics to report our current state, past efforts, future capabilities, compliance with practices, and so on. Tools provide us with the ability to do this. Strengthening the back end delivery through DevOps is also a great capability to deliver.

Still, Stakeholders of Systems want LOTS of features

So, our business customers are still going to come at us from many different directions with a ton of Features, which can often be identified as “The Next Shiny Object.” What work may already be in stream or in construction can get impacted as the “next shiny object” can now be added to the list.

Shiny objects occur with amazing regularity as a result of:

  • A competitor introduces a new function – keeping up with the Joneses.
  • Some stakeholder gets impatient for the delivery of a feature and becomes focused on that current shiny object.
  • That simple request in an email, which you mistakenly agree to do, goes from being a small paper airplane to a B-2 Stealth Bomber-sized project or program.

The results of stakeholders repeatedly chasing Shiny Objects tends to distract teams from delivery. Stakeholders can change their minds about what is important based on what is happening in the business world – which is often disconnected from our IT delivery world. Unless we have a strong commitment to the SAFe processes and practices, we are unlikely to actually combat the Shiny Object syndrome.

SAFe practices corral, organize, prioritize and deliver whole categories of Shiny Objects based on the Needs and Priorities of the stakeholders.

At the Portfolio level:

  • We corral, organize and prioritize (and even set the value of) Shiny Objects.
  • We use Kanban capabilities to organize and prioritize objects.
  • We use Value Streams to align work and fund the work (unfunded work like those B-2 stealth projects die at this point).
  • We make strategic level decisions for the good of the enterprise.

Remember that errant CIO who promised everyone who asked whatever they asked for? We gave her a sheet that became an input form to the portfolio screening process.

So what happens when that commitment starts to backslide or fail? How can we make sure a complex system of systems like this keeps on working?

SAFe is based upon a set of key Lean and Agile principles:

# 1-Take an economic view

#2-Apply systems thinking

#3-Assume variability; preserve options

#4-Build incrementally with fast, integrated learning cycles

#5-Base milestones on objective evaluation of working systems

#6-Visualize and limit WIP, reduce batch sizes, and manage queue lengths

#7-Apply cadence; synchronize with cross-domain planning

#8-Unlock the intrinsic motivation of knowledge workers

#9-Decentralize decision-making

Also of critical importance are the Core Values of SAFe:

SAFe Core Values

For organizations to effectively implement SAFe, we also need a significant amount of individual and team based capabilities of Rigor and Discipline. In addition, we need some mechanism to keep us on track, and monitor speed, delivery, quality and compliance, plus deliveries in a priority cadence that is driven by the stakeholders.

Rigor and Discipline of this type comes in the form of using a global mechanized capability (such as VersionOne) as a key to providing work dispatch capabilities:

  1. Planning capabilities at various levels for various roles
  2. Metrics gathering
  3. Quick methods of prioritizing
  4. Globally distributed capabilities of defining and managing work

In my own experience working with large and globally distributed organizations, performing SAFe planning and execution and utilizing technology with enterprise-wide capabilities of the caliber of VersionOne, provides them with the rigor and discipline to successfully be SAFe!

 

Leave a Comment