profile

Agile Circle

Innovation or stability? 21 questions to strike a balance in agile strategies

Published 3 months ago • 4 min read

Hey Reader,

As we set sail into a new year, how about an attempt to navigate the waters of "Balancing Innovation and Stability." The ability to strike this delicate balance is the key to sustained success in the ever-evolving landscape of agility.

Why Balancing Innovation and Stability is Crucial

Too many people read the book 📘 Lean Startup and think that the reality of companies are supposed to be like that. While that book is an awesome read, it’s more likely your organization is well established and not as carefree as a company whose sole focus is to innovate and generate funding externally.

You are probably worried about effectiveness, and people don’t like to admit that it includes efficiency (using just enough of resources to get to the desired results): saving money, being smart on how to use people’s time, that sort of thing. It’s not a sin to care for it.

It’s always important to keep bandwidth for innovation though. If anything, the last 3 years have been… interesting! First, COVID, then AI… thinking on our feet not only to respond to the market, but to actually utilize current trends and opportunities for the benefit of the organization is a necessity.

When asked “Innovation or stability?” you answer “Yes.”

And that is not incompatible with agility in any way, my friend.

You know what to do, just ask questions

Whether you are a manager of a big team or a coach of many small teams, chances are you are the one communicating the vision, or at least helping it come to light. You’ll be asking senior leadership to define a clear vision.

And as such, you can be the one reminding other leaders of the need to strike a balance between innovation and stability, and in turn making sure it takes place for the sake of the teams.

For the sake of the teams?

Yep. Happy teams, happy businesses.

You see, many VPs are sometimes so far removed that they might consider changing direction is about making a simple decision. But they are no longer the ones in the reality of branching out thousands of lines of code or maintaining a pristine support environment.

So your role is to get the maximum clarity from all possible leaders and make the information flow to your teams in a way that allow for teams to proactively accommodate. Self-organization, anyone? It’s as simple as knowing where we are going.

In the grand tradition of agile coaching, asking is queen.

Here are 21 questions for you to ask to ensure that a clear vision encompasses both innovation and maintenance aspects in the agile context:

  1. Strategic Alignment:
    • How does the envisioned future align with the organization's overall strategy?
    • Are there specific innovation goals outlined in the vision, and how do they contribute to strategic objectives?
    • How does the vision address the need for stability and predictability in our products or services?
  2. Balancing Priorities:
    • What is the balance between driving innovation and maintaining stability in the vision?
    • How do we prioritize efforts between introducing new features and ensuring the reliability of existing ones?
    • Are there explicit goals related to both innovation and stability in the vision statement?
  3. Customer-Centric Approach:
    • How does the vision address the evolving needs and expectations of our customers?
    • In what ways does the vision incorporate feedback loops to drive continuous improvement in both innovation and stability aspects?
  4. Adaptability and Flexibility:
    • Does the vision promote a culture of adaptability and flexibility to respond to changing market conditions and emerging technologies?
    • How are teams encouraged to experiment and iterate to foster innovation while maintaining a stable core?
  5. Cross-Functional Collaboration:
    • How does the vision encourage collaboration between teams focused on innovation and those responsible for stability?
    • Are there mechanisms in place to facilitate knowledge sharing and cross-functional communication?
  6. Measurable Outcomes:
    • What key performance indicators (KPIs) are defined to measure success in both innovation and stability?
    • How do these metrics align with the goals outlined in the vision, ensuring a balanced and holistic approach to success?
  7. Risk Management:
    • How does the vision address risk management in both innovative initiatives and the maintenance of existing systems?
    • Are there strategies in place to mitigate risks associated with innovation without compromising stability?
  8. Continuous Improvement:
    • How is the vision promoting a culture of continuous improvement in both innovative practices and stable processes?
    • Are there mechanisms for regular reflection and adaptation based on lessons learned from both successful innovations and challenges in maintaining stability?
  9. Employee Engagement:
    • How does the vision consider the engagement and motivation of team members involved in both innovation and maintenance activities?
    • Are there opportunities for recognition and growth in both areas to ensure a balanced and fulfilling work environment?
  10. Long-Term Sustainability:
    • How does the vision contribute to the long-term sustainability of the organization, considering the need for both innovation to stay competitive and stability to build customer trust?

From PI planning to coffee break with leaders, these questions aim to guide the development of a vision that embraces both innovation and maintenance aspects, fostering a balanced and resilient approach to agile practices.

Even if you are the VP in this story, your focus isn't on having all the answers; it's on asking the right questions. Surprisingly, answers often emerge through conversations with those around you, shaping the vision for the next quarter collaboratively.

While some seek definitive answers, the power lies in harnessing collective wisdom. Yet, there's merit in a leader with a clear path and readiness to address questions. The key is avoiding isolation, ensuring leadership remains engaged and communicative, steering organizations toward success.

Is there a question in this mix you are already itching to ask? Or one you wouldn’t dare? 💣🙊

Those are clues…


From the blog

In the recent blog posts, I've delved into what’s evolving in the agile landscape. I even initiated a discussion on the distinct aspects of seeking opportunities as Agile Coaches or Scrum Masters in the year 2024. Curious to know what's changed? Take a moment to explore more on the blog.


Mini-Class Live in February

Starting next month you can count on your calendar for the first Wednesday of the month live with me. The topic for this one, on February 7th will be "Carry over activities from sprints". Is it bad? Why? And what to do?

I'll show you how most people look at this common situation under the wrong lenses and help you make the most of it actually.

Like any of my master and mini-clasess, it's fast-paced and based on real life experience and practical advice.

Pick your favorite channel (YouTube, Instagram, LinkedIn) and join me at 11:30 EST!

You'll obviously be able to catch a replay on YouTube, but chances to get your question answered happen for when you're live, so...

Meet you there!


I hope you are having a wonderful day!

Cheers,

P


Are you on socials? Let's Connect!

Check out the allthingsagile.co blog

unsubscribe here or manage your profile

All Things Agile Canada | 360 21E Avenue, Deux-Montagnes, QC J7R 4H1

Agile Circle

All things agile directly into your inbox

Specialized in Agile coaching and training. Visit us at http://allthingsagile.co

Read more from Agile Circle

Hey Reader, Today, I want to bring you perspective on something we all face: problems. Should we solve every problem that comes our team’s way? It might surprise you, but the answer isn’t always yes. Some issues are better left alone, at least for a while. Not every problem needs a solution. Sometimes, they just need time. Choosing Your Battles: not every problem is a problem. I can think of at least two types of problems that benefit from our waiting before acting: Temporary Issues: Like a...

20 days ago • 2 min read

Hey Reader Sometimes it gets annoying how people polarize agility so much. But it’s also an easy way out to just say “it depends” or “the answer is in the middle”. I think one particularly unhelpful polarization in agile has been the output vs outcome one. And I must admit I was there advocating for outcomes for some time, as an early scrum master some 12 years ago and many more years after that. That being said, we should all learn. The world adapts, we adapt. And today I’m here to tell you...

about 2 months ago • 3 min read

Hey Reader, Today’s edition is about an insight for maximizing your effectiveness as an agile coach or consultant. True, Start With Why, Simon Sinek’s book is very famous and very inspiring. Yet what I learned in the business and coaching world is that the single most important thing for results is uncovering what the very next step forward is. And in order to move forward you need to know where to. And this is defined either by desire (towards something) or by pain (away from something). And...

2 months ago • 4 min read
Share this post