Definitely, Maybe Agile (Peter Maddison and Dave Sharrock)

Send us a text

What do you think of our services, and has it had the impact you were hoping to see? In today's episode of the Definitely Maybe Agile podcast, Peter and Dave talk about the importance of asking for feedback from our customers to prevent business agility from failing.

This week takeaways:

• Validate emergent needs with your customers
• Build a system that can respond to that.

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com

Send us a text

In this episode of the Definitely, Maybe Agile podcast, Dave and Peter have a special guest, Rob Hirschfeld, co-founder, and CEO of RackN, a collaborative platform for teams automating infrastructure as code. This time we'll have a slightly longer episode than normal as we dive into different aspects of complexity. This isn't one you'll want to miss. We had a lot of fun recording it and really liked the end result. We hope you do too.

This week takeaways:

• Stop trying to eliminate complexity and figure out how to manage it.
• Build systems focused on system effectiveness.
• Complexity problems are collaboration problems.

We love to hear feedback. If you have questions, want to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com. 

Send us a text

We're so happy to have made it to episode 52! This year has been full of guests and conversations about agility. We've also had the opportunity to share our expertise, so thank you for joining us on these journeys together—it's not going unnoticed.
This week's episode is about addressing your team's needs and not just forcing agile processes on them. You'll learn what happens when an organization doesn't put people first.

This week takeaways:

• The hiring process is our first impression. If we make a mess there, we're always going to be on our back foot.
• Talk about what's happening. Don't lie.
• Lead by example.

References in this episode:
Leaders Eat Last- Simon Sinek https://www.goodreads.com/book/show/16144853-leaders-eat-last.

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com

Send us a text

 Learning from failure is an essential part of building your resilience. In this week's episode, Peter and Dave discuss how failure gives us the ability to improve and continually create more resilient systems.

This week's takeaways:

• The importance of understanding the resiliency of each part of our system in context of the whole system.
• Failure allows us to learn, and then we can rebuild stronger.
• Recognize that we need to persevere through failures to gain the benefits.

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

Some projects never seem to end. Big upfront design results in long execution phases and eventually it becomes difficult to believe it will ever be delivered. This week, Peter and Dave discuss how to approach these seemingly never-ending projects once they are well underway. Having started this way, how can you bring it under control and apply what we know of business agility to move forwards again? 

 This week's takeaways:

• Stakeholder communication.
• Identify and prioritize
• Do one thing at a time.
• Work on the thing that will help us create stability and move forward.
•  Meanwhile, have everybody else focus on improving the integrations, fixing defects, and removing technical debt. 

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

This week Peter and Dave will deconstruct a quote from Tom DeMarco. "Quality takes time and reduces the quantity, so it makes you, in a sense, less efficient. The organization that optimizes efficiency recognizes quality as its enemy. That's why many corporate quality programs are actually quality reduction programs in disguise."

This week's takeaways:

• Technology is cheap today, but the impact is expensive. 
• Organizations that test at the end reinforce the loop. 
• We now have more integration abilities between systems. 

Resources:
The machine that changed the world- https://www.amazon.com/Machine-That-Changed-World-Revolutionizing/dp/0743299795

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

If all you care about is rushing around, you'll miss learning opportunities that might make you more effective in your delivery. This week Peter and Dave talk about the impacts of innovation as a department.

This week's takeaways:

• Think of innovation as a culture across the organization.
• Innovation is everywhere.
• The psychological safety of making mistakes and learning from them is a foundational block in any learning organization.

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

This week Peter and Dave debate about constantly evolving technology and what that means for the business.

This week's takeaways:

• Let IT take care of it (it's part of your cost)
• Nothing is as permanent as a temporary change.
• Systems, assumptions, and changes cost more than you think
• Challenge your assumptions around TCO (e.g., depreciation)

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

In this week's episode, Dave Sharrock and Peter Maddison share their insights about the decisions within an organization with technology and how we spend money from a technology perspective.

 This week's takeaways:

• Cost of doing business in a VUCA world.
• The unintended consequence of strategy.
• Technology is a strategic partner of the organization.

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com

Send us a text

In episode 59 of the Definitely, Maybe Agile podcast, Peter and Dave discuss the different models of governing delivery. They talk about how project management offices and value management offices approach the same problem of transparency and governance differently.

This week's takeaways:

• Differences between models for governing delivery
• When and why a central office would be valuable
• Intensifying short cycle delivery of customer value

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

This week on the Definitely, Maybe Agile podcast, Peter and Dave talk about VMO/ Product Office ways of working. They share their thoughts on the importance of understanding how the ways of working around a Value Management Office differ from those that we might associate with a project management office.

This week's takeaways:

• Shift to dedicated teams (no need for resource management)
• Outcomes over activity- specifically short timelines
• Start small and iterate. Continually deliver increments of value.

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

The Definitely, Maybe Agile podcast is back this week with an episode all about plans. In today's episode, Peter and Dave continue their series on the Value Management Office by talking about the importance of planning. They discuss how planning is critical to successfully executing a project and how having a structure rather than starting from a blank sheet of paper can aid the planning process. They also explain why it is essential to understand the framework of a plan before creating one.

This week's takeaways:

• Coordinate over short distances.
• Having a frame to drop work into can be valuable.
• Avoid blank sheets of paper
• Priorities over the medium term, decisions at the team level in the short term.

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com

Send us a text

In episode 62 of the Definitely, Maybe Agile podcast, Peter and Dave uncover what they mean by value streams.

 This week's takeaways:

• Understand how your organization does things, so you can learn how to improve.
• Identify where to focus and how to prioritize by identifying constraints in your value streams.
• Optimize your organization to be able to deliver more effectively and faster.

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

In this week's episode of the Definitely, Maybe Agile podcast, Peter and Dave talk about Nested Value Streams. They explain how to take a value stream concept that works well with a single product or service, and scale it up to an organization with hundreds of teams working on multiple products and services.

This week's takeaways:

• How value stream thinking helps to scale up our development capability from one team to many teams
• The boundaries between value streams do not have to be a physical handoff
• Value streams can be technically distinct
• Understand how to make priority trade-offs between value streams

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

Nowadays, training in the Agile space, in some ways, has had a bad rep. It has left a bit of a stigma around what training we need. However, people generally agree there is significant value, so can we change how we approach training? When is training valuable? In this week's episode of the Definitely, Maybe Agile podcast, Peter and Dave discuss how to make your training program effective.

 This week's takeaways: 

• Need training that provides a common lexicon
• Train principles and values over process and practices
• Learn through play
• Facilitates rapid organizational change and speed change
• Training can be made more powerful with coaching elements like follow-on support to reinforce learning

 We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

In this week's episode of the Definitely, Maybe Agile podcast, Peter and Dave talk about the Governance of software delivery value streams. In particular, how to take into account organizational concerns like regulation and architecture while increasing your ability to delivery software faster.

This week's takeaways:

• Governance of delivery in terms of in-process requirements.
• TACO: Traceability, Accessibility, Compliance, and Operations.
• Also need to govern out of process requirements, architecture, data, privacy, security, and regulation.
• The out-of-the-process is often the brakes or the foils that will slow down the delivery.

Resources:
Securing Your Pipes with a TACO - https://youtu.be/E7UjGd7ZRo0

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

It's been a couple of years since people started working from home, and now the situation is leading companies to make changes again. How we're dealing with the challenge of returning to the office is the big question. This week Peter and Dave dive into the implications of returning to work.

 This week's takeaways:

• Mandatory returns are not psychologically safe.
• Be transparent about why things happen.
• Make it attractive

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

 We recently talked about the mandated Return to Work policies. This week, Peter and Dave discuss the implication of that mandated approach to psychological safety.

This week's takeaways:

• Shouldn't be a tick box issue
• Isn't one size fits all
• Stepped back and put yourself in the other person's shoes

Resources:
David Rock's Scarf Model-  http://web.archive.org/web/20100705024057/http://www.your-brain-at-work.com/files/NLJ_SCARFUS.pdf

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

In this episode of the Definitely, Maybe Agile podcast, Peter and Dave will dive into some workshop techniques for facilitation.  They outline key elements that will help you and your stakeholders get to the outcome you are looking for.

This week's takeaways:

•  Preparation is essential
•  Small groups facilitate conversation
•  A clear understanding of the workshop's purpose is key to guiding conversation
•  Have fun with it

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

In this episode of the Definitely, Maybe Agile podcast Dave and Peter discuss a barrier to your workshop's success. Dominant personalities can affect group participation and limit ideas from other participants in a discussion or meeting, but don't worry because there are techniques to ensure everyone's participation. You can learn more about them in this episode.

This week's takeaways:

• Small groups facilitate the conversation
• Need consensus across the group in terms of moving forward
• Use patterns from Liberating Structures 1,2,4, ALL
• Exercise 15 minute photo

Resources:
Liberating Structures- https://www.liberatingstructures.com/
15-minute FOTO- https://www.agendashift.com/resources/15-minute-foto

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com

Send us a text

In this episode of the Definitely, Maybe Agile podcast Dave and Peter dive into executive decision-making. We discuss what can happen when powerful, informed people with a lot of authority and responsibility try to come together to make decisions.

This week's takeaways:

• Pace of change – decision-making is an essential skill
• Emotional intelligence to recognize if we need to step back
• Root of leadership change
• Decision gap (lead time)
• Is the decision being made in the right place?

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

NOTE: This isn't a full episode, just an intro to the next season

We're definitely excited for season 2 of the Definitely, Maybe Agile podcast!

Peter Maddison and Dave Sharrock are ready to tackle the big questions around digital transformation. What does it look like? How can we define it? Why does it all go wrong? These are just some questions they'll be exploring in the upcoming season. But more than just understanding digital transformation, they want to help their listeners recognize where they are in their transformation journey. Is it an agile transformation or a digital transformation? And, of course, no transformation discussion would be complete without challenging some paradigms. So tune in for an exciting season 2 of the Definitely, Maybe Agile podcast!

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

On this episode of the Definitely, Maybe Agile podcast Peter and Dave will talk about the first of the 4 forms of Digital Transformation, Process Transformation. They'll discuss what it is, how to do it, and why it's important.
This week's takeaways:

• Process transformation is probably what most people think of as a "Digital transformation"
• Have a clear understanding of your business outcomes.
• Processes always need to transform.
• Define if your transformation is going to be incremental or not.

 
We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

Previously, Dave and Peter talked about process transformation in the context of digital transformations. This week on the Definitely, Maybe Agile podcast, they discuss the second of the four types of digital transformation, business model transformation.

They will explain some examples of the different types of business model transformation that organizations can experience.

This week's takeaways:

• Bring strategic leaders to the table.
• A shift in how you interact with customers.
• Get good at change.

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

 We've been talking about digital transformation this season. We mentioned the four types of digital transformations: process, business model, domain, and organizational change. Today on the Definitely, Maybe Agile Podcast, Peter & Dave will focus on domain transformation.
What is domain transformation? What differs from business model transformation? Why can it be so difficult for companies to achieve it?

This week's takeaways:

• Success in the new domain often comes from the different approaches and knowledge you bring with you
• Use tools to gather data and understand the risks
• Domain transformation can be challenging to achieve.

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

In this week's podcast, Dave and Peter explore the fourth types of digital transformation: cultural or organizational.

They explain why organizational transformation is tied to any other type of transformation and the role of leadership in those changes.

This week's takeaways:

• Leaders have to be on board with the change.
• Organizational change is always present.
• Intuitive or deliberate. There's a big difference between leaders who intuitively change the culture and those who thoughtfully change a culture.

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

 Dave Sharrock and Peter Maddison explore how an agile transformation is different from a digital transformation in this week's podcast.

This week's takeaways:

• Identify what you need to change first.
• Leadership alone won't make it. They need the participation of the whole organization.
• Understand why you are making the change.

Resource:
Simon Sinek - Golden rule- https://youtu.be/qp0HIF3SfI4

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

In the last couple of weeks, Peter and Dave have shared their thoughts on digital transformations and what constitutes that transformation. In this episode, they will cover the underlying piece or underlying umbrella about this, which is digital change management. They'll talk about how to move forward after implementing change.

 This week's takeaways: 

• Make changes small enough that people can get through them. We want lots of small changes, not one massive one.
• Change is continuous.
• Stop optimizing before you have tested your model.

Resources:
Dave Snowden - How leaders change culture through small actions https://youtu.be/MsLmjoAp_Dg

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

Dave Sharrock and Peter Maddison dive into the topic of bridging the gap in this week's podcast. In recent weeks they've talked a lot about transformation through the eyes of technical digital implementation. Now they will focus on bridging the gap between technology and the business side of the organization.

This week's takeaways:

• Customer-centric versus product-centric
• Close customer decision gap
• There's a greater understanding in general of technology and how it can be applied

Resource:
How Apple Is Organized for Innovation- https://hbr.org/2020/11/how-apple-is-organized-for-innovation

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

 How do you know you are going in the right direction? This is a question that plagues many of us. We set out with a plan and a destination in mind, but somewhere along the way, we lose sight of where we're supposed to be going. If this sounds familiar, don't worry, you're not alone. In this week's episode, Peter and Dave talk about how to measure your progress and keep track of whether or not you're headed in the right direction. We'll also discuss some of the indicators that can help you determine if you're making the desired behavioral change.

This week's takeaways:
- Keep your people on board and reward the change
-Incremental delivery. Take small and measurable steps
-Checking-in regularly
- Establish your Leading vs Lagging Indicators

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

Many businesses are under pressure to undergo digital transformation, but the process is often fraught with difficulties. In this week's episode of the podcast, Peter and Dave discuss what causes digital transformations to run into issues and fail.

This week's takeaways: 

• Focusing on too much change all at once
• Lack of alignment
• Conflicting priorities

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com

Send us a text

On the last episode of the Definitely, Maybe Agile podcast, Peter Maddison and Dave Sharrock had a great discussion about 12 year-end suggestions for a more agile 2023. Let’s take a look at the four main categories they discussed.

This week's takeaways:
A.- Marketplace and change:
   1. Stop thinking things are different right now (change is the new black).
   2. Think holistically
   3. Broaden your information-gathering sources

B.- Pragmatic stuff to remember
   4. Shorter time horizons
   5. Rise to your goals, fall to the level of your systems
   6. Strategic: If you say yes to this, what do you say no to?

C. Don't forget
   7. Quality is probably more important than you think
   8. Don't forget your people
   9. Security

D. End of year
   10. Revisit your objectives
   11. Reflect: Notebook story
   12. Sharpen the saw

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

 In this week's episode, Peter Maddison and David Sharrock discuss how Geoffrey Moore's “chasm” model of market adoption can be used to understand organizational change. They explore the differences between enthusiastic early adopters and more reluctant individuals when it comes to change. The model explains the challenges organizations face when adopting new ideas or technologies and the necessary shift in mindset and approach required to successfully navigate the chasm. They also discuss what behaviors or approaches need to be altered based on the specific context of the organization.

This week's takeaways:

• Understand the different stages of adoption, practices, and people.
• Different methods and techniques are needed for different groups of people, depending on their journey.

 We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com

Send us a text

In the most recent episode, Peter and Dave engage in a thoughtful discussion on Mike Burrows' book "Agendashift". They highlight the book's unique consolidation of practices and experiences that Burrows has accumulated while working with clients. They particularly appreciate the book's straightforwardness and how it almost reads like a how-to guide for those facilitating conversations.

The book focuses on emergent approaches that can be tailored to an individual organization, rather than a one-size-fits-all framework. They appreciate that each chapter includes exercises, underlying principles, and theories. Peter and Dave also acknowledge the book's emphasis on the human behavior side of things, which can be easy to overlook during transformations.

This week's takeaways:

• How do you create outcomes that are relevant?
• Empathy is a change agent super-power
• How to Guide- Facilitator driven

Resources:

• Agendashift- https://www.goodreads.com/book/show/35439273-agendashift?ref=nav_sb_ss_1_11
• OI-SR- https://www.agendashift.com/resources/oi-sdr
• OI-SR Template- https://www.agendashift.com/resources/oi-sr-template 

 We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

 On this week's episode of Definitely Maybe Agile, Peter Maddison and David Sharrock dive into the world of change management through a conversation about the book "Our Iceberg is Melting." This easy-to-read parable offers a unique perspective on change through the lens of a colony of penguins living on a melting iceberg. The book explores the eight-step model of change management from Kotter's perspective, providing an accessible entry point to the topic. The conversation delves into the nuances of change management, highlighting the importance of gaining buy-in across different characters and perspectives within an organization. So come listen to Peter and Dave chat about the complexities of change management and what we can learn from those penguins.

 This week's takeaways:
• Identify influential players in the organization.
• Broadening awareness of complexity and existential threats.
• Look for something to learn from any situation, no matter how difficult.
• Allow team members to act independently.
• Listen for opportunities to contribute and offer feedback.

Resource:
Our Iceberg Is Melting- https://www.goodreads.com/en/book/show/419461 

We are always eager to receive your feedback! If you have any questions, would like to suggest a topic, or even participate in a conversation, please don't hesitate to contact us at feedback@definitelymaybeagile.com. Also, be sure to hit the subscribe button for our podcast to stay updated on our latest episodes. 

Send us a text

 This week Peter and Dave decided to delve into questions that have come up in workshops with senior leaders. Some of the questions they consider are How can we bring senior leadership along on the journey? What are the leaders showing through their actions? How do we measure the success of a leader's contribution?This episode emphasized the crucial role that executive leadership support plays in the success of an agile transformation and encouraged leaders to lead by example and show their commitment to the change.

This week's takeaways:

• A leader's success should also be measured by their availability and response time to team members.
• Growing leaders around them is a sign of a great leader.
• Safety in tough decisions is important for leaders to create a safe conversation.
• It's important for leaders to recognize and grow the people around them to create the next generation of leaders.

We are always eager to receive your feedback! If you have any questions, would like to suggest a topic, or even participate in a conversation, please don't hesitate to contact us at feedback@definitelymaybeagile.com. Also, be sure to hit the subscribe button for our podcast to stay updated on our latest episodes. 

Send us a text

Dave Sharrock and Peter Maddison discuss the challenges of implementing Agile practices when working with a complex legacy system with a monolithic architecture. They stress the importance of working out how to incrementally deliver value and describe some of the patterns and strategies you might take.

 This week's takeaways: 

• Understanding the end-to-end system needs and treating the problem space correctly
• Making small incremental changes to systems can be life-changing and empowering for teams
• Enabling teams to make small changes should be the goal
• The approach to achieving this goal will depend on the systems being worked with and how they need to evolve

Feedback is always welcome, including questions, topic suggestions, or participation in a conversation, by emailing feedback@definitelymaybeagile.com. Don't forget to hit the subscribe button for the podcast to stay updated on the latest episodes. 

Send us a text

In this episode of Definitely Maybe Agile, Peter Maddison and Dave Sharrock delve into a common dilemma faced by many organizations: why should they invest in Agile or digital transformation if their workforce lacks interest in it? They discuss the importance of creating an engaging, fulfilling, and motivating work environment, pointing out that disengagement is often a sign of deeper issues within the organization. Leaders must prioritize their employees' well-being to avoid a downward spiral.

This week's takeaways: 

• Understand the system, don't blame the people
• Environment determines commitment
• Clear and aligned incentive drives behaviour and reinforced by structure

Resources:
The Culture Code: The Secrets of Highly Successful Groups-  https://www.goodreads.com/book/show/33517721-the-culture-code
Nudge: Improving Decisions About Health, Wealth, and Happiness-  https://www.goodreads.com/book/show/3450744-nudge

Feedback is always welcome, including questions, topic suggestions, or participation in a conversation, by emailing feedback@definitelymaybeagile.com. Don't forget to hit the subscribe button for the podcast to stay updated on the latest episodes.

Send us a text

Peter Maddison and David Sharrock discuss the significance of culture in driving organizational change in the “Are we having fun yet?” episode of the Definitely, Maybe Agile podcast. They emphasize that imposing “your method” and “your framework” on others will not bring them on board with the transformation.

A better outcome is happier. Are the actions we are taking removing barriers and resulting in happier employees? When we forget it isn't about “our method,” we start to inflict instead of inviting people. When that happens, people lose agency. People need to feel they can contribute.

This week's takeaways:

•  We should enjoy what we do
• Don't try copying somebody else model
• The focus on the method vs. the outcome

"The principal function of most corporations is not to maximize shareholder value, but to maximize the standard of living and quality of work life of those who manage the corporation"- Russell Ackoff.  Providing the shareholders with a return on their investments is a requirement, not an objective. As Peter Drucker observed, profit is to a corporation as oxygen is to a human being: necessary for existence, not the reason for it. A corporation that fails to provide an adequate return for their investment to its employees and customers is just as likely to fail as one that does not reward its shareholders adequately.

Feedback is always welcome, including questions, topic suggestions, or participation in a conversation, by emailing feedback@definitelymaybeagile.com. Don't forget to hit the subscribe button for the podcast to stay updated on the latest episodes. 

Send us a text

In a recent episode of the Definitely, Maybe Agile podcast, Peter Maddison and Dave Sharrock explore if AI tools can replace Agile coaches. Is there a future where ChatGPT or other AI-powered tools eliminate the need for human interaction in Agile coaching? Discover their insights on how AI can enhance our knowledge and potential pitfalls to avoid.

This week's takeaways:

• AI could be seen as an augmentation of human capabilities rather than a replacement. This can accelerate learning and problem-solving.
• It's important to understand and evaluate the output of AI tools, as they may not always be correct.
• We should start experimenting with AI now, but always be ready to take back control if needed.

Feedback is always welcome, including questions, topic suggestions, or participation in a conversation, by emailing feedback@definitelymaybeagile.com. Hit the subscribe button for the podcast to stay updated on the latest episodes. 

Send us a text

 In this week's episode of Definitely, Maybe Agile, Peter Maddison and Dave Sharrock discuss the challenges and opportunities of scaling agile. It's the age old story. Organization meets Agile, tries it in a small area, has some initial success, and then says "let's do this elsewhere!".  At that point the wheels come off the car.

They argue that there is no one-size-fits-all approach to scaling agile, and that the best approach will vary depending on the specific organization. There's a need to focus on what is the outcome you are looking for? People forget the goal is agility, not more Agile. They also agree that it is essential to avoid simply "scaling" a framework, and that instead, the focus should be on "descaling" the work.


This week's takeaways:
- Involve all stakeholders in the scaling process
- Scaling agile means scaling the work, not the framework
- Use frameworks as a starting point, not a destination
- Transformation is essential for successful scaling

To join the discussion, email us at feedback@definitelymaybeagile.com with your thoughts, questions, or suggestions for future episodes. Don't forget to hit that subscribe button to stay updated on our latest releases.  So, let's dive in! 

Send us a text

In this episode of the Definitely, Maybe Agile podcast, Dave and Peter have a special guest, Mike Freislich, co-founder, coach & Trainer of We Do Change. This time we'll have a slightly longer episode than normal as we dive into different aspects of Kanban Flight Levels framework and how it can be used to help organizations achieve business agility.

This week's takeaways:

• It allows teams to have a concept of strategy for themselves.
• When embarking on an organizational change, do not do it alone.
• Create a culture of inclusion and collaboration to empower employees to take ownership of their work.

Resources:
Mike Freislich  - https://www.linkedin.com/in/mikefreislich/ https://www.wedochange.io/

To join the discussion, email us at feedback@definitelymaybeagile.com with your thoughts, questions, or suggestions for future episodes. Don't forget to hit that subscribe button to stay updated on our latest releases.  So, let's dive in! 

Send us a text

In this episode of Definitely Maybe Agile, Peter Maddison and Dave Sharrock chat with Eric Brook, CTO, Technology & Product Executive, about the importance of ownership in organizations. Brook explains that ownership is not just about control, but about a sense of responsibility and accountability for our work. He offers a number of practices that organizations can use to foster a culture of ownership.

This week's takeaways:

• Ownership is not just about individual employees. It is also about teams and organizations as a whole.
• It doesn't come for free, it takes effort and commitment from everyone involved.
• Creating a culture of ownership is an ongoing journey. It is important to be open to feedback and change.

Resources:

• Eric's new blog post - https://ericbrooke.blog/2023/05/10/ownership-in-small-and-medium-technology-companies-part-1/
• Learning Domain-Driven Design: Aligning Software Architecture and Business Strategy - https://www.goodreads.com/en/book/show/57573212

To join the discussion, email us at feedback@definitelymaybeagile.com with your thoughts, questions, or suggestions for future episodes. Don't forget to hit that subscribe button to stay updated on our latest releases.  So, let's dive in!

Send us a text

 In this episode, Peter Maddison and David Sharrock have a special guest, Jorge Arevalo, CIO, CTO, IT Director, and consultant. The topic of discussion for today's episode revolves around the role of C-level executives and the board in the context of digital transformation. Jorge shares his firsthand experiences with digital transformation projects in the banking sector and sheds light on the challenges C-level executives and boards face during these initiatives.

This week's takeaways:

• Understand the why. Having a clear understanding of the why will help to guide the transformation and ensure that it is successful.
• Create a safe environment. In a safe environment, people feel comfortable enough to speak up resulting in a greater willingness to share ideas and take risks.
• Ensure digital literacy. The board of directors should have a basic understanding of digital technology.  We talk through how to make this happen.

Resources:
Turn Your Ship Around!: A Workbook for Implementing Intent-Based Leadership in Your Organization -https://www.goodreads.com/book/show/22529128-turn-your-ship-around

We would love to hear from you! Share your thoughts, questions, or suggestions for future episodes at feedback@definitelymaybeagile.com. And remember to subscribe to stay updated on our latest releases. 

Send us a text

In this episode of the Definitely, Maybe Agile podcast, Peter Maddison and Dave Sharrock discuss the book "Five Dysfunctions of a Team" by Patrick Lencioni. They talk about how the book provides a natural description of the challenges faced by teams and emphasize that the book focuses on the team's dysfunction at the top of the organization and how it affects the entire business.

This week's takeaways:

• The value of taking time out as a leadership team. Stepping away from the daily grind can help leadership teams address dysfunctions.
• The benefit of investing in teams. When teams are allowed to work together, they surpass expectations and progress faster. 
• The importance of fostering an environment for collaboration. Investing in teams and enabling effective collaboration leads to greater value creation and faster progress.

Resources: 

• The Tuckman Model: A Roadmap for Team Development and Success- https://medium.com/@williammeller/the-tuckman-model-of-team-development-c0b3fbdce0de
• The Five Dysfunctions of a Team: A Leadership Fable- https://www.goodreads.com/book/show/21343.The_Five_Dysfunctions_of_a_Team

We would love to hear from you! Share your thoughts, questions, or suggestions for future episodes at feedback@definitelymaybeagile.com. And remember to subscribe to stay updated on our latest releases.

Send us a text

Peter and Dave explore strategy creation in this episode, specifically focusing on product development, discovery, and management. Drawing from their own experiences, they discuss the challenge of balancing creating a product and actively listening to customers when venturing into a new marketplace. They raise important questions, such as determining when a product is ready for the market and identifying the differentiators that will enable organizational success in a competitive landscape.

This week's takeaways:

• It's essential to understand the customer's needs and motivations.
• Emphasizing an emergent strategy allows you to rapidly iterate, improve, and build upon your product based on customer feedback and market insights.
• Find the balance between exploration (observing, listening, empathizing) and exploitation (accelerating product delivery).

We would love to hear from you! Share your thoughts, questions, or suggestions for future episodes at feedback@definitelymaybeagile.com. And remember to subscribe to stay updated on our latest releases. 

Send us a text

 In this episode of the Definitely, Maybe Agile podcast, Dave and Peter talk to Marius de Beer, Senior Director of Digital Product Delivery at Aritzia, about the challenges and evolution of agile practices. After years of working on transformations at different organizations, Marius has distilled agile transformation down to four things: How you are measured, recognized, rewarded, and supported. This is an episode you won't want to miss!

This week's takeaways:

• Change itself has changed: Making change a natural part of learning, responding, and growing helps remove the fear and resistance associated with it.
• Applying the four principles at each organizational layer: It's important to consider the needs and recognition of the organization as a whole, not just individuals or teams.
• Instead of forcefully pushing tools and practices onto individuals or teams, providing support and focusing on how people are measured, recognized, and rewarded is more effective.

To join the discussion, email us at feedback@definitelymaybeagile.com with your thoughts, questions, or suggestions for future episodes. Don't forget to hit that subscribe button to stay updated on our latest releases. 

Send us a text

Erin Leslie, a leadership coach, and career strategist, joins the Definitely Maybe Agile podcast to discuss the importance of vulnerable leadership and emotional intelligence in agile transformations.

Erin shares her experience leading agile teams in the public sector, and discusses the challenges and opportunities of working in this environment. She emphasizes the importance of creating a safe space for creativity and risk-taking and of being able to relate to team members on a human level.

This week's takeaways:

• Allow space for emotions and feelings to be expressed in conversations and listen for the answer rather than coming in with preconceived ideas.
• New roles in government. The public sector is increasingly adopting new roles, such as product owner. These roles allow public servants to take on more responsibility and ownership of their work.
• Compassion is essential in both public and private sector leadership.

To join the discussion, email us at feedback@definitelymaybeagile.com with your thoughts, questions, or suggestions for future episodes. Remember to hit that subscribe button to stay updated on our latest releases. 

Send us a text

 Join Peter Maddison and David Sharrock on the latest episode of Definitely, Maybe Agile as they sit down with Pia Wendelbo, change agent and CEO of Scandinavian Change Agents. Together, they delve into the crucial topic of holistic thinking in change management. Pia highlights the often overlooked impact on people during a transformation, emphasizing the importance of considering culture, staff happiness, and the structures and processes affected by the change. This insightful conversation highlights the need for a more comprehensive approach to change management that fully embraces human aspects of organizational transformation.
 
This week's takeaways:

• Recognize that individuals are at the core of any transformation effort.
• Incorporating "slack" into work life can bring balance and productivity.
• Continuous learning and improvement are crucial in transformation.

To join the discussion, email us at feedback@definitelymaybeagile.com with your thoughts, questions, or suggestions for future episodes. Remember to hit that subscribe button to stay updated on our latest releases. 

Send us a text

Are you ready to shatter the glass ceiling of traditional management methods? We promise this episode will equip you with the tools to achieve just that! Join us, Peter Madison and David Sharrock, as we journey into the realm of OKRs (Objectives and Key Results). Learn about their power in fueling organizational alignment and goal-setting and how they stand apart from other management frameworks like MBOs, balanced scorecards, and KPIs. Discover why they are indispensable in setting long-term objectives and milestones that can pivot with the ever-changing landscapes of your business operations.

This week's takeaways:

•  OKRs are a goal-setting framework are effective at creating alignment and, though simple on the surface, they take practice to get right.
• They are not meant to be static but rather should be updated and adjusted as new information becomes available.
• It should not be tied to performance reviews or bonuses. Instead, they should be used as a tool for setting ambitious goals and tracking progress.

To join the discussion, email us at feedback@definitelymaybeagile.com with your thoughts, questions, or suggestions for future episodes. Remember to hit that subscribe button to stay updated on our latest releases.   Tune in, and let us help you revolutionize the way your organization marches towards achieving its goals. 

Send us a text

 Are you ready to challenge conventional wisdom about traditional architecture and Agile practices? This week, Peter Maddison and Dave Sharrock steer us through the labyrinth of Agile Architecture, revealing how it can become a strategic partner rather than just a service function. We examine the potential barriers old-school architecture can pose, and how Agile principles can reshape the layers of your organization's system architecture.

This week's takeaways:

• Ensure architects are actively involved in specific business domains or architecture, rather than being temporary consultants.
• Remember that architecture is not solely the responsibility of a select few; it permeates all levels of the organization.
• Avoid relying too heavily on Architectural Review Boards (ARBs) as they can impede decision-making and hinder innovation. Instead, prioritize empowering architects to make informed decisions and collaborate regularly with relevant stakeholders.

Join the conversation by contacting us at feedback@definitelymaybeagile.com with your thoughts, questions, or suggestions for future episodes. Don't forget to subscribe to stay updated on our latest releases. Let us uncover the potential of Agile Architecture together! 

Send us a text

In this episode of the Definitely, Maybe Agile podcast, we'll discuss how to make the most of your time at conferences. Discover the power of tribe-finding, uncover a range of learning opportunities, and unlock the potential for networking with like-minded individuals. From informal exchanges to roundtable discussions with industry experts, there's something for everyone.

This week's takeaways: 

• Find your tribe.
• Prepare in advance.
• Embrace informal networking opportunities.
• Don't be afraid to leave if it's not serving your goals.

 Join the conversation by contacting us at feedback@definitelymaybeagile.com with your thoughts, questions, or suggestions for future episodes. Don't forget to subscribe to stay updated on our latest releases. And remember, conferences can be an absolute blast and an enriching learning experience rolled into one!

Send us a text

Curious about how validation works in agile development? By this, we mean the process of verifying the product does what it is supposed to. Join Peter Maddison and David Sharrock as we unravel the nuances of this crucial process. We'll dive headfirst into the technological and business aspects of validation, discussing everything from automated deployment processes to system monitoring and the importance of telemetry data. We'll also show how business validation ensures your product behaves as planned, giving you the confidence to move forward. We’ll also talk about how validation differs across types of business. 

 This week's takeaways:

• Try to predict what customers will do with your new functionality.
• Think of the many ways you might measure the impact of your new functionality.
• Involve all stakeholders in the validation process.

 Contact us at feedback@definitelymaybeagile.com with your thoughts, questions, or suggestions for future episodes. Remember to subscribe to stay updated on our latest releases.

Send us a text

Tune in to the newest episode of Definitely Maybe Agile as Peter Maddison and Dave Sharrock challenge the notion of using a single solution for all problems. They explain the importance of having a diverse, agile methods and practices toolkit. Peter and Dave highlight the need to consider the context of each problem before deciding on a solution. They stress the value of tailoring the approach to fit the unique circumstances, emphasizing the necessity of fully understanding the problem.

This week's takeaways:

• Have a toolkit of different frameworks and models.
• Measure the right thing.
• Context is King.

Contact us at feedback@definitelymaybeagile.com with your thoughts, questions, or suggestions for future episodes. Hit subscribe to stay updated on our latest releases. Don't miss out on this insightful discussion on effective problem-solving strategies in the agile world. Expand your toolkit and enhance your problem-solving skills with the expert advice featured in this episode.

Send us a text

Are you drowning in work? Learning to streamline your team's processes but can’t find the time? Don't panic; Peter Maddison and David Sharrock have covered you with simplistic yet powerful strategies! In this episode, they talk through the 'two-out, one-in process. It's a methodology that ensures the focus is on finishing tasks rather than continually adding to the work pipeline. Expect discussion of work-in-progress limits and empowering your teams to take control of their work.

 This week's takeaways:

•  Try “two-out, one-in," as it can be a valuable technique for teams overwhelmed with too much work in progress.
• Make sure everything is captured as work. Visibility is a key first step.
• Sharing the visibility of the team's workload and its capacity with stakeholders can lead to a better understanding of the team's constraints and workload.

Resources: Video Lucy and the Chocolate Factory: https://youtu.be/NkQ58I53mjk

Join the conversation by contacting us at feedback@definitelymaybeagile.com with your thoughts, questions, or suggestions for future episodes. Don't forget to subscribe to stay updated on our latest releases. So, brace yourself for an insightful conversation as Peter and David showcase how to navigate the complexities of adopting new working methods while managing work overload.

Send us a text

Are you ready to challenge conventional wisdom and reexamine your understanding of product development? This episode promises to do just that, as we unravel the misconceptions highlighted in the Harvard Business Review article, 'Six Myths of Product Development.' We'll share insights on how these myths, often carried over from physical manufacturing to the digital sphere, can lead to a misallocation of resources and stifle innovation.

This week's takeaways:

• The economics of cost saving and optimization can have a detrimental effect on digital product development. 
• The mindset of "plan to create options" is essential for digital product development. 
• The lessons learned from digital product development can be applied to other areas of the business, such as operations.

Resources:
Six Myths of Product Development- https://hbr.org/2012/05/six-myths-of-product-development

Contact us at feedback@definitelymaybeagile.com with your thoughts, questions, or suggestions for future episodes. Hit subscribe to stay updated on our latest releases. Join us in this captivating exploration of product development myths, and gain fresh insights into crafting effective strategies for the digital era. 

Send us a text

What causes collaboration to break down in organizations? We often hear talk of collaboration breaking down in command and control style hub-and-spoke structures, but more agile modern structures can also cause issues. Using a 2021 MIT article on collaboration and organizational network design (ONA) as a base, Dave and Peter explore these different models and their impact on collaboration. Expect lots of discussion on Agile and DevOps.

This week's takeaways:

• Centralized decision-making and hub and spoke models can hinder teamwork and cause confusion.
• Collaboration goes beyond breaking down silos; it requires a shared purpose and aligned goals across teams and units.
• Addressing bottlenecks, maintaining work transparency, and considering the entire system are crucial to avoid overload and disenfranchisement.
• It's important to consider structural and behavioral aspects to foster effective collaboration. 

Resources: 

Sloan Management Review: When Collaboration Fails and How to Fix It- https://corporateinnovation.mit.edu/2021/05/18/sloan-management-review-when-collaboration-fails-and-how-to-fix-it/

Ready to revolutionize your workplace collaboration? Don't miss this insightful episode! Be sure to listen to Definitely Maybe Agile on your favorite platform, and remember to subscribe. For additional resources and to join the conversation, visit our website and contact us at feedback@definitelymaybeagile.com with your thoughts, questions, or suggestions for future episodes. Click that subscribe button and stay tuned for more exciting content!

Send us a text

Have you ever pondered upon the intricacies of business resilience? Do you fully grasp the importance of non-functional requirements for your business? Peter Maddison and David Sharrock promise to demystify these topics on the Definitely, Maybe Agile podcast. We guide you through the nuances of scenario planning, business continuity, and disaster recovery processes that are pivotal for preparing against potential disruptions. Events like pandemics, environmental issues, and economic changes have underscored how essential it is to comprehend the key parts of your business and the resources necessary for recovery.

Furthermore, we'll spotlight non-functional requirements and their vital role in business resilience. We'll show you why it's crucial for your teams to be autonomous and how to manage system changes without triggering unanticipated impacts. We'll also touch on the rising observability movement and its role in making non-functional requirements more conspicuous. From discussing design and architecture to system latency and changes, we hope to provide valuable insights into non-functional requirements. 

This week's takeaways:

• Don't overlook non-functional requirements - they're crucial for the resilience of your business.
• Understand the impact of changes on your system with observability at the forefront.
• Take a comprehensive approach to business resilience planning, considering all aspects of your business.
• Make sure everyone is aware of the business resilience plan and knows their role in executing it.

So, buckle up for an enlightening journey through the nitty-gritty details of business resilience! Be sure to listen to Definitely Maybe Agile on your favorite platform, and remember to subscribe. For additional resources and to join the conversation, visit our website and contact us at feedback@definitelymaybeagile.com with your thoughts, questions, or suggestions for future episodes. Stay tuned for more exciting content! 

Send us a text

Imagine facing colossal challenges and complex problems and not knowing where or how to start solving them. In this episode, we wrestle with the complexities of problem-solving within Agile organizations, particularly when adopting new methodologies at scale. We dissect various problem management strategies - from the well-established ITIL to the Lean and A3 methods- providing you with a toolkit for identifying root causes and understanding the factors contributing to your problems.

We delve into the intricacies of problem management within a microservices environment. We discuss the power of predictive problem management and the tools you can leverage to solve problems. We also explore the realm of complex systems and the strategies that can help identify probable causes of problems, specifically focusing on the Safety 1 and Safety 2 models. All this is aimed at equipping you and your teams with a systematic approach to problem-solving, reducing chances of catastrophic failure through proper service contracts, smaller batches, and fast releases. 

This week's takeaways:

• Problems are ubiquitous: Problems exist everywhere, but organizations often lack a formal approach to addressing them.
• Take the time to understand problems: Instead of reacting to problems instinctively, organizations should create a space for thoughtful, data-driven problem-solving. 
• Establish a common understanding of problems: Having a common agreement and language within the organization is crucial regarding what constitutes a problem. 

As we navigate these complex topics, we ensure that you come away with a deeper understanding and practical solutions you can implement in your organization. Tune in! Be sure to listen to Definitely Maybe Agile on your favorite platform, and remember to subscribe. For additional resources and to join the conversation, contact us at feedback@definitelymaybeagile.com with your thoughts, questions, or suggestions for future episodes. Stay tuned for more exciting content!

Send us a text

This week, Peter Maddison and David Sharrock promise to provide insights that will revolutionize your understanding of fixed processes. Join them to explore how these systems impact business operations. This episode will empower you with the knowledge you need to navigate tricky financial processes, highlighting the importance of agility and adaptability and illuminating the pitfalls of over-reliance on fixed systems. We uncover how the right balance of formal and informal processes ensures consistency and credibility and facilitates scalability within your organization.

This week's takeaways:

• Processes can range from fixed and unchanging to flexible and subject to continuous review.
• Find the right balance between creativity and risk when determining whether to keep, modify, or challenge processes.
• The nature of the problem space and context should influence how processes are approached and managed.

 By the end of the episode, you'll have the tools to tailor processes to your specific needs and the understanding necessary to implement large-scale changes. Don't forget to subscribe and share your feedback! For additional resources and to join the conversation, contact us at feedback@definitelymaybeagile.com with your thoughts, questions, or suggestions for future episodes. Stay tuned for more exciting content!

Send us a text

Feeling stuck when it comes to aligning IT with your business goals? Wondering why bridging the gap between tech and business is so important? Get ready to change the way you think about IT as we explore the value of IT as a strategic partner. In this episode, we'll share insights to help you maximize your organization's capabilities.

But our conversation doesn't stop there. We'll also delve into effective communication and building a strong partnership between IT and business. Discover the importance of speaking a common language, respecting each other, and building trust.

This week's takeaways:

• Effective Communication: Speak in a way your audience understands, especially when discussing complex topics like technology and business.
• Shift to a Strategic Partnership: Understand the challenges faced by the business and show how technology can be leveraged strategically.
• Collaborate in Both Directions: Success requires a two-way dialogue between IT and the business, with both sides contributing their insights and needs.

If you're ready to transform your organization's integration of IT and business, this episode is your guide. Join us on this enlightening journey, and don't forget to subscribe and give us your feedback! To learn more and be part of the conversation, contact us at feedback@definitelymaybeagile.com. Stay tuned for more exciting content! 

Send us a text

Struggling to juggle multiple tasks and maintain focus? Join Peter Madison and David Sharrock as they shed light on the significant consequences of context switching on work productivity. From exploring the complexities of our thinking processes to the negative effects of constant notifications on our devices, we uncover the toll that switching between initiatives can have on our productivity.

But we don't stop at uncovering the problem; we provide practical strategies for managing cognitive load and reducing context switching. Learn about time blocking, a method that allows you to allocate dedicated time for deep, meaningful work. Discover the power of making work visible and contributing purposefully in meetings. We also emphasize the importance of clear meeting agendas and being mindful of the tasks we take on. By implementing these strategies, team members can work more effectively, minimizing unnecessary interruptions.

This week's takeaways:

• Context Switching is a Hidden Productivity Killer.
• Make work visible and prioritize tasks.
• Recognize that it takes time to transition between different tasks and thinking modes.

Join us in this episode as we navigate through the challenges of context-switching and explore ways to build a more productive work environment.  Don't forget to subscribe and share your feedback! For additional resources and to join the conversation, contact us at feedback@definitelymaybeagile.com with your thoughts, questions, or suggestions for future episodes. Stay tuned for more exciting content!

Send us a text

Join us for an exciting episode of "Definitely, Maybe Agile" as David Sharrock shares his firsthand experience of a successful business transformation in the competitive world of e-retail. Get ready for valuable insights on the real-world impact of agile transformations and what it takes to make them happen.

This week's takeaways:

• Leadership Matters: Open, experimental, and engaged leadership is essential for successful agile transformations.
• Collaboration: Combining bottom-up team initiatives with top-down support is crucial for lasting change.
• Business-Tech Alignment: Aligning technology with business objectives and adapting to market changes yields significant advantages in agile transformations.

Resources:
- Hudson Bay Start- https://derivadow.com/2007/11/08/hudson-bay-start-reducing-project-risk/

If you're interested in helping edit or provide feedback for their upcoming ebook, you can reach out to them at feedback@definitelymaybeagile.com. Don't forget to subscribe to the podcast for more insightful episodes. 

Send us a text

Are you ready to build a culture that values quality and embraces design thinking? We'll show you how to foster collaboration, encourage idea-sharing, and establish feedback loops for data within your organization. Learn how to establish consistency, manage system risks, and make informed decisions for future scalability. Rest assured, creating a culture of design thinking goes beyond simply following a process - it's about making quality a core value of your organization.

This week's takeaways:

• Design Thinking as a Habit: Make it a continual practice, not a one-time exercise.
• Transparency and Collaboration: Encourage everyone to challenge and share ideas, fostering a culture of innovation and problem-solving.
• Aligning Ideas with Objectives: Evaluate how feasible ideas contribute to strategic goals and adapt as necessary.
• Managing Conflicts and Respecting Ideas: Foster a comfortable environment for disagreement when important decisions need to be made.

If you're interested in editing or providing feedback for their upcoming ebook, please contact them at feedback@definitelymaybeagile.com. And don't forget to subscribe to the podcast for more insightful episodes.

Send us a text

Join us as we welcome David Adeoye, an esteemed guest and expert in Agile and Project Management. Discover how these two strategies can work together to maximize business value. Learn tips on adopting new ways of working and navigating complexities. Explore the role of biases in decision-making and the connection between culture and cybersecurity. Gain insights on Agile Cybersecurity and its benefits.

This week's takeaways:
- Use agile methodologies to improve efficiency in cybersecurity projects.
- Adopt feature-based thinking with versioned cybersecurity plans tied to budgets.
- Understand the problem-solving approaches of project management and agility.
- Focus on delivering value efficiently based on project context.
- Foster a culture of reporting cybersecurity issues.
- Conduct simulated exercises to improve cybersecurity mindset and incident reporting.

For collaboration or feedback on their ebook, contact them at feedback@definitelymaybeagile.com. Don't forget to subscribe to the podcast for more insights

Send us a text

Ever tried to untangle the stubborn knot of capacity planning in Agile teams? Brace yourself as we, Peter Maddison and David Sharrock, take you on an enlightening journey to decipher the complexities of this aspect. We shed light on the importance of crafting robust, dedicated, and cross-functional teams and how they become a reliable gauge for capacity planning. We acknowledge the uphill battle many organizations are fighting, leading to wavering predictability and dwindling trust. Traditional resource planning methods are out, and the focus on team consistency is in.

This week's takeaways:

• Shift from Work-Centric to Customer-Centric View.
• Trust and empower agile teams to manage their capacities for better performance and adaptability.
• Identify critical skill sets and shared services beyond agile teams.
• Recognize potential bottlenecks in compliance, UX, or infrastructure for strategic capacity planning.

If you're interested in editing or providing feedback for their upcoming ebook, please contact us at feedback@definitelymaybeagile.com. And don't forget to subscribe to the podcast for more insightful episodes.

Send us a text

Following on from episode 115, today's episode, Peter and Dave delve into the complexities of capacity planning in organizations undergoing transitions, emphasizing the need for a balanced approach that incorporates agile principles and traditional project management practices. They stress the importance of due diligence, the interface between different methodologies, and the necessity of prioritizing improvements to achieve a more agile and efficient workflow.

This week's takeaways:

• Emphasize the importance of due diligence in capacity planning, especially in transitional states where agile practices are not fully established.
• Acknowledge the interface between traditional project management and agile methodologies, recognizing that both have valuable contributions.
• Prioritize work based on a common understanding of organizational problems and goals.
• Communicate the idea that focusing on specific improvements doesn't mean discarding other initiatives but rather sequencing them for continuous enhancement.

For collaboration or feedback on our ebook, contact us at feedback@definitelymaybeagile.com. Be sure to subscribe, spread the word to a friend, and join our engaging conversations. Who knows? You might just be our next podcast guest as we continue to explore the rich tapestry of agile transformation

Send us a text

Scaling Agile to fit your world! Peter & Dave explore the nuances of customizing agile frameworks for diverse organizational needs. They delve into practical applications of the 80-20 rule and discuss the pivotal role of agile coaching in facilitating effective change. Tune in for a clear and engaging discussion on how to adapt agile methods to suit your specific organizational needs, making your work processes smoother and more efficient.

This week's takeaways:

• Context-specific scaling: the need to tailor agile scaling efforts to the unique context and culture of each organization, acknowledging that a one-size-fits-all approach doesn't work.
• Framework agnosticism:  the importance of not being overly reliant on a single agile framework. Instead, understanding and choosing from various frameworks and patterns to best fit your organization's specific needs is crucial.
• The 80-20 rule in scaling: identify the critical 20% of agile practices that are most relevant and impactful for your organization, while recognizing that 80% might be generally applicable.
• Organizational change as problem-solving:  scaling agile as an organizational change challenge, requiring a problem-solving mindset to identify specific issues and apply targeted agile practices effectively.

If you're interested in editing or providing feedback for their upcoming ebook, please contact us at feedback@definitelymaybeagile.com. And don't forget to subscribe to the podcast for more insightful episodes.

Send us a text

On the last episode of the Definitely, Maybe Agile podcast, Peter & Dave had a great discussion about 12 year-end suggestions for a more agile 2023. Let’s take a look at the four main categories they discussed.

This week's takeaways:
A. Marketplace and change:
   1. Do more with less
   2. AI in our work
   3. Shorter time horizons (in times of uncertainty)

B. Pragmatic stuff to remember
   4. Two out one in (manage WIP)
   5. High uncertainty means continuous learning and validation
   6. Estimates are just guesses

C. Don't forget
   7. The Agile/DevOps mindset
   8. Risks and contingency
  9. Don't forget to measure

D. End of year
   10. Check your progress/direction
   11. Take time to review/learn
   12. Recognize the people that got you (t)here

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com 

Send us a text

Discover the future of agile roles in organizations with the insights of Brock Argue, co-founder of Superheroes Academy. Our latest episode unravels the real-world implications of economic pressures on the agile transformation journey, with a keen focus on the delicate interplay between team support and hands-on product development. As heavyweights like Spotify and Capital One pivot towards leaner structures, we question the longevity of specialized coaching positions and how these changes might reshape the agile landscape.

This week's takeaways:

• Invest in Skill Development: Explore the untapped potential in skill development.
• Embrace Agility and Flexibility: Dive into the world of agility and flexibility demanded by the hybrid work model and shifting economic tides.
• Focus on Productivity and Delivery: Whether in-person or remote, the secret sauce lies in unwavering focus on productivity and delivery.

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com

Send us a text

Ever wondered how to bridge the gap between grand strategy and on-the-ground execution in today's Agile and DevOps-driven world? We're Peter Madison and David Sharrock, and in our latest episode, we crack this code, sharing our experiences and the occasional humorous tale, such as the Austrian airport mix-up meme. We dissect the importance of aligning every cog in the organizational machine, with a special focus on the mental models that guide decision-making. By introducing cutting-edge technologies, we illuminate how enhanced visibility can transform the way your teams operate, ensuring that those crucial organizational handoffs are as smooth as silk.

This week's takeaways:

• Connecting Strategy to Execution.
• Shift in Language and Terminology.
• People-Centric Focus.

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com

Send us a text

Embark on an enlightening journey with Peter Madison and David Sharrock as they tackle the ever-evolving world of service delivery. From the bustling crossroads of Agile, DevOps, and ITSM, they dissect the common confusions that arise from industry jargon, ensuring that when they speak of 'service', everyone is nodding in agreement. Promises of clarity in this tangled web of terminologies are fulfilled as they lay bare the distinctions between product and service delivery – a must-hear for those navigating the intricate paths of modern organizational structures.

As the episode unfolds, Peter and Dave navigate the critical processes of incident response, problem management, and change management. They consider how these elements, integral to the IT service framework, come into play with Agile and DevOps methodologies. The dialogue weaves through the importance of maintaining system stability while managing risk, and the role of context in understanding the various perspectives and terminologies that often lead to confusion.

This week's takeaways:

• Context-Driven Application of Frameworks
• Recognition of Overlapping Intersections
• Holistic Thinking for Organizational Change

We love to hear feedback! If you have questions, would like to propose a topic, or even join us for a conversation, contact us here: feedback@definitelymaybeagile.com

Send us a text

Has the agile shine worn off in the sprawling corridors of big business? In this episode, we unpack the startling findings from Digital AI's latest state of agile survey that show people's satisfaction with their organization's agile practices. Join us as we scrutinize the complexities that have dulled the luster of agile methodologies and debate the crucial adjustments needed to reignite its promise. From the necessity of strong leadership advocacy to the bespoke tailoring of agile for the multifaceted needs of large organizations, we lay bare the pivotal elements in crafting a triumphant agile metamorphosis.

This week's takeaways:

• Technical Adoption Curve: Expect a decline in satisfaction as Agile reaches a broader audience, particularly the late majority, causing discomfort and peaking expectations.
• Organizational Size Matters: Satisfaction correlates with organizational size. Agile is a significant improvement in smaller organizations, but in larger ones, it becomes one tool among many, increasing the risk of misapplication.
• Not All or Nothing: Agile is not an all-or-nothing solution. In larger organizations, it coexists with different methodologies, challenging the idea of a universal fix and emphasizing the need for tailored solutions based on context.

Resources:
Agile development is fading in popularity at large enterprises - and developer burnout is a key factor- https://www.itpro.com/software/agile-development-is-fading-in-popularity-at-large-enterprises-and-developer-burnout-is-a-key-factor

Join us for an episode that will broaden your understanding of how large enterprises can adapt and embrace a more efficient and fulfilling agile culture. We love to hear your feedback! If you have questions or would like to suggest a topic, please feel free to contact us at feedback@definitelymaybeagile.com.

Send us a text

Could Agile methodologies be the villain behind developer burnout, or is it time to put the blame elsewhere? Strap in as Peter Maddison and David Sharrock pull back the curtain on the true antagonists in the saga of developer fatigue. This episode isn't about finger-pointing; it's about unveiling the systemic issues that lead to overworked teams and debunking the myth that Agile practices are inherently at fault. We're on a mission to shift the focus from flawed productivity metrics to the lived experiences of developers, advocating for a workplace ecosystem that values well-being as much as it does output.

This week's takeaways:

• System Over Agile: Burnout in developers isn't caused by Agile itself but by systemic issues within the organization.
• Curiosity Beats Assumptions: Prioritize curiosity over jumping to conclusions, as it leads to a deeper understanding of complex problems.
• Experience Matters: Consider both developer productivity and experience, as focusing solely on productivity metrics may miss important qualitative aspects of developer well-being.

Join us on a thought-provoking journey as we dissect the nuanced relationship between leadership, incentives, and workplace behaviors. Far from a one-sided debate, we consider how effective leadership and the right organizational incentives can create an environment that not only encourages productivity but also ensures the sustainability of its workforce. Peter and David don't just skim the surface; they dig deep into the complexities that drive developer burnout and explore the intricate dance of factors that can make or break the health of a tech team. Tune in and gain insight into crafting a more supportive and resilient work culture. 

 We love to hear your feedback! If you have questions or would like to suggest a topic, please feel free to contact us at feedback@definitelymaybeagile.com.

Send us a text

Unlock the power of data in shaping your organization's future as we tear down the myths surrounding data-driven decision-making. We dissect the essential cultural shift necessary for integrating data analytics into the heart of business strategy, steering clear of reliance on gut feelings or misleading numbers. We dive into practical applications, from planning poker to interpreting customer experience metrics. We provide the knowledge to avoid common data interpretation pitfalls, such as those exemplified by the beer game in supply chain management.

For those striving to guide intuition-driven leaders towards a more data-informed approach, our dialogue offers inventive tactics for leveraging trusted allies and fostering a climate of persistent, creative persuasion. 

This week's takeaways:

• Data-driven vs. number-driven decision making: Data alone isn't enough. Context and understanding of statistical deviations are crucial for sound judgments.
• Overcoming resistance to data-driven decisions: Inflexible leaders pose a challenge. Directly challenging their intuition might be ineffective. 
• Empowering teams and managing technical debt: Create short feedback cycles to enable rapid decision-making and results demonstration.

Resources:

Algorithms to Live By: The Computer Science of Human Decisions - https://a.co/d/dzojO5k

Jeff Bezos- https://www.youtube.com/watch?v=Ub585Pn4yro

Tune in to transform how you harness data for smart, insightful leadership decisions. We love to hear your feedback! If you have questions or would like to suggest a topic, please feel free to contact us at feedback@definitelymaybeagile.com.

Send us a text

Navigating through the murky waters of system bottlenecks and feedback loops can be daunting. In this episode, we scrutinize how these bottlenecks can strangle a system's potential and discuss methods for their identification and alleviation. We also highlight the importance of acknowledging long-cycle feedback and confronting resistance to change, underscored by the vital role of those who adeptly bridge the gap between systemic understanding and practical application. Join us as we provide strategies to transform challenges into opportunities for triumph, crucial for anyone invested in organizational optimization.

This week's takeaways:

• Bridging the perspective gap
• Behavioral Influences on Organizational Dynamics
• Beware of Resistance and Long-Term Challenges
• Non-believers in change or the system

 Subscribe and tune in for an enlightening journey that extends beyond theories, equipping you with the tools necessary to steer your organization through the transformative tides of digital, agile, and DevOps methodologies. If you have questions or would like to suggest a topic, please feel free to contact us at feedback@definitelymaybeagile.com.

Send us a text

This week, we explore the surprising shift away from dedicated teams, a cornerstone of traditional agile practices. Our hosts, Peter and Dave, unpack the challenges organizations face, including resistance to change, disruptive reorganizations, and the ever-present struggle to secure buy-in. We'll also discuss practical strategies to navigate these challenges, emphasizing the importance of incremental steps, clear communication, and building trust.

This week's takeaways:

• Dedicated teams are no longer a guaranteed starting point.
• Build trust, use clear language, and focus on small.
• Prioritize creating value over disruptive reorganizations

Join us as we explore how to embrace agile principles and achieve success, even in the face of resistance. We love to hear your feedback! If you have questions or would like to suggest a topic, please feel free to contact us at feedback@definitelymaybeagile.com.

Send us a text

Need help communicating Agile and DevOps to Executives? This episode of Definitely Maybe Agile is for you! Peter Maddison and David Sharrock unpack the challenges of getting leadership on board with new ways of working. Learn best practices for clear, concise communication, tailoring your message to your company culture, and effectively socializing agile and DevOps initiatives.

This week's takeaways:

• Prepare like a pro and "socialize" your ideas beforehand.
• Keep it short, clear, and data-driven.
• Adapt your language to the audience.

Join the conversation and share your insights with us at feedback@definitelymaybeagile.com – your input could shape our next big topic. Tune in, and let's take this journey towards exceptional executive communication together.

Send us a text

How can organizations create the necessary space for leadership to flourish amidst complexity and pressure? In this episode of Definitely Maybe Agile, Peter Maddison and David Sharrock delve into the intricate world of leadership in complex environments. Opening with a warm exchange, they explore an insightful article by John Cutler, examining the indispensable soft skills essential for leaders navigating complexity.

Reflecting on Cutler's piece, Peter and David dissect various facets of leadership, from self-awareness to patience and self-repair. They highlight leaders' need to create space for diverse perspectives, fostering an environment where multiple possibilities can thrive. Amidst organizations' pressures, they ponder the challenge of finding time for such introspection amidst the relentless demand for results.

This week's takeaways:

• Leaders must cultivate self-awareness
• Encourage the blending of diverse perspectives
• Practice Patience and Self-Repair

Resources:
How Capable Leaders Navigate Uncertainty and Ambiguity- https://cutlefish.substack.com/p/tbm-274-how-capable-leaders-navigate?utm_source=activity_item

Join the conversation and share your insights at feedback@definitelymaybeagile.com – your input could shape our next big topic. Subscribe today and equip yourself to navigate the beautiful mess of leadership!

Send us a text

In this episode, Peter and Dave discuss an article by Steve Denning published in Forbes titled "Why the World's Most Valuable Firms Are so Agile." They explore Denning's observations about the agile mindset and characteristics exhibited by highly successful companies. The discussion revolves around the relationship between adopting an agile approach and organizational performance, as well as the potential correlation or causation between agile ways of working and the exceptional valuations of these firms.

This week's takeaways:

• Keep an eye on Steve Denning's work.
• Focus on financial performance.
• Avoid using the term "agile" and focus on the outcome you are trying to achieve.

Resources:
Why The World’s Most Valuable Firms Are So Agile- https://www.forbes.com/sites/stevedenning/2024/02/26/why-the-worlds-most-valuable-firms-are-so-agile/?sh=1094bb1d794c

Have your own take on whether an agile mindset truly powers the world's most valuable firms? Let us know at feedback@definitelymaybeagile.com.  Subscribe today to gain a fresher outlook on embracing organizational agility without the buzzwords.

Send us a text

How do you know you have a great agile team? This episode reveals the secret sauce that makes high-performing Agile teams tick. From the power of predictable delivery to the pursuit of relentless quality, we dissect the various elements that contribute to a team's success. We go beyond the typical metrics to understand what it takes for a team to own their processes and evolve their work environment to reach new heights of excellence.

This week's takeaways:

• Top agile teams measure their performance, enabling transparency and continuous improvement.
• Focus on continuous learning and quality.
• Cultivate a collaborative, blame-free culture focused on the work while maintaining a balanced, fun, and supportive team environment.

Join the conversation and share your insights at feedback@definitelymaybeagile.com – your input could shape our next big topic. Subscribe today and learn more about agile teams

Send us a text

In this episode, Peter and Dave discuss the importance of building robust systems and processes to achieve goals, drawing insights from the book "Atomic Habits" by James Clear. They explore the notion that simply setting objectives is not enough - sustained success requires developing the right habits, practices, and systems to support those objectives. The conversation touches on OKRs (Objectives and Key Results), KPIs (Key Performance Indicators), and the need to take small, incremental steps towards larger goals.

This week's takeaways:

• "You do not rise to the level of your goals. You fall to the level of your systems."
• OKRs provide the roadmap, and KPIs gauge how well the core operations run.
• Identify the next incremental habit or process you can implement to move forward.

Join the conversation and share your insights at feedback@definitelymaybeagile.com – your input could shape our next big topic. Subscribe today and learn more about agile teams.

Send us a text

In this episode, Peter and Dave discuss the importance of effective organizational change management in digital transformations. They highlight that simply implementing new processes and systems is not enough - organizations must also carefully manage the human aspect of change. This includes understanding the intangible factors and behaviors that can derail well-designed transformations. They emphasize the need to get close to the actual end-users, observe their behaviors, and adapt accordingly instead of relying solely on high-level communications.

This week's takeaways:

• Organizational change management is essential, not optional, for successful digital transformation.
• Go beyond just communications - understand real end-user behaviors and intangible adoption factors.
• Build capabilities to collect user feedback/telemetry, learn from it, and adapt the change process accordingly.

Join the conversation and share your insights at feedback@definitelymaybeagile.com. Your input could shape our next big topic. Subscribe today to learn more about organizational change. 

Send us a text

Unlock the secrets to a thriving developer experience as we dissect the critical balance between productivity and fulfillment in the tech world. Prepare to have your perspective on developer metrics as we dive deep into the implications of AI advancements and economic shifts on the roles and recognition of software engineers. This episode is a treasure trove for anyone seeking to understand the nuanced landscape of the tech industry, where the intangible aspects of job satisfaction go hand-in-hand with tangible outputs.

We challenge the traditional yardsticks of developer output, advocating for a collaborative approach to productivity that values the system over the individual. You'll discover the art of using metrics responsibly in a way that empowers and informs developers rather than policing them. Drawing on our expertise, we leave you with actionable insights into fostering an agile environment where collective progress is king and where developers feel secure, autonomous, and integral to their organization's success.

This week's takeaways:

• There is no single metric to measure developer productivity effectively. Look at correlations across multiple qualitative and quantitative metrics.
• Focus on development productivity metrics for the overall system/team rather than individual developer productivity numbers.
• Make productivity metrics transparently available to developers, allowing them to self-regulate performance rather than being managed top-down.

Resource:  

Measuring Developer Productivity: Real-World Examples -
https://newsletter.pragmaticengineer.com/p/measuring-developer-productivity-bae

Tune in for a thought-provoking conversation that reshapes how we perceive and enhance the developer experience in an ever-evolving industry. Subscribe to learn more insights around leadership, agile, and DevOps transformation at scale.

Send us a text

In this episode, Peter Maddison and David Sharrock discuss the complexities and misconceptions surrounding estimation in software development and agile project management. They explore the differences between bottom-up and top-down estimation approaches, emphasizing the importance of continuous conversations and feedback loops throughout the process.

This week's takeaways:

• Bottom-up estimation, where every task is estimated and summed up, is highly inefficient and inaccurate, especially for long-term projects or when requirements are likely to change.
• Top-down estimation, which involves breaking down work into relatable chunks and understanding the journey, is more effective and allows for adaptability as the project progresses.
• Estimation should be an ongoing conversation between teams, stakeholders, and decision-makers, focusing on problem-solving, progress tracking, and continuous feedback rather than rigid timelines.

Tune in for a riveting discussion that challenges traditional notches around estimation in agile software development. Subscribe to absorb invaluable insights on nurturing continuous conversations, embracing top-down estimation techniques, and fostering an environment primed for delivery excellence at scale.

Send us a text

In this episode, Peter Maddison and David Sharrock are joined by Melissa Boggs, a leadership coach, consultant, and keynote speaker for Agile 2024. They discuss Melissa's experience as the co-CEO and chief scrum master of Scrum Alliance during the challenging times of the COVID-19 pandemic. The conversation dives into the topics of employee experience design, non-hierarchical organizations, and the importance of co-creating buy-in for organizational change.

Key Takeaways:

• Delegating authority and distributing power within an organization requires providing context, setting boundaries, and preparing employees for decision-making responsibilities.
• Leaders often avoid change due to a fear of losing authority, power, or performance. Coaching and empathy are essential to help leaders move from a state of caution to curiosity and eventually courage.
• Co-creating buy-in through collaboration and involving employees in decision-making processes leads to organic, natural buy-in and better solutions, as opposed to top-down directives.

Discount Information: Melissa provided a discount code for listeners interested in attending Agile 2024 in Dallas, where she will be the closing keynote speaker. The code "A24-podcast" will give you $100 off your registration-  https://www.agilealliance.org/agile2024/

We love to hear your feedback! If you have questions or would like to suggest a topic, please feel free to contact us at feedback@definitelymaybeagile.com.

Send us a text

In this episode, Peter Maddison and David Sharrock discuss how to integrate threat modeling into the secure development lifecycle (SDLC) at scale. They cover the importance of shifting security practices left, and how to establish communication channels between development teams and security experts.

Key takeaways:

• Threat modeling is a security practice that involves identifying and mitigating potential threats to an organization's assets.
• Threat models should be created and maintained early in the SDLC, but don't need to be updated for every minor change.
• A mechanism for ongoing communication between developers and security professionals is essential for effective threat modeling.

Resources:

• Sooner Safer Happier   by Jonathan Smart - https://www.goodreads.com/en/book/show/50343488
• Larry Maccherone https://www.youtube.com/watch?v=EyS1kmmlA5Y
• Martin Fowler blog  https://martinfowler.com/articles/scaling-architecture-conversationally.html

 Whether you're diving into DevSecOps or just looking to get a handle on threat modeling at scale, this episode is a must-listen. Tune in now as Dave and Peter discuss how to future-proof your organization! 

Send us a text

In this episode, Peter Maddison and David Sharrock discuss the qualities to look for when recruiting and selecting the perfect Product Owner (PO). They delve into the nuances between a Product Owner and a Product Manager role, emphasizing the importance of defining the authority and accountability the PO will have. The conversation explores the essential attributes of an excellent PO, including domain knowledge, understanding business models, data-driven decision-making, effective communication skills, and the ability to navigate various stakeholder demands. They also highlight the significance of storytelling and sharing real-life experiences during the interview process as a strong indicator of a high-caliber PO.

This week´s takeaways:

• Clearly outline the level of authority and accountability the PO will have over the product's success, profitability, and decision-making. 
• Look for candidates with relevant domain experience, an understanding of the business models, and the capability to analyze the product's impact on the organization's ecosystem, including costs, revenue, and customer satisfaction.
• During the interview process, pay attention to candidates who naturally share stories and narratives about their experiences, challenges they overcame, and lessons learned. These stories often provide insights into their problem-solving abilities and deep understanding of product ownership.

We love to hear your feedback! If you have questions or would like to suggest a topic related to nurturing exceptional product ownership, feel free to contact us at feedback@definitelymaybeagile.com. 

Send us a text

In this episode, Peter and David dive into the complexities of organizational change, exploring how agile transformations sometimes discard valuable lessons from past change management practices. They discuss blending systems thinking, behavioral economics, and incremental change approaches to create truly adaptive organizations. The conversation spans concepts like organizational immune systems, the human element in change, and the importance of clear strategy and communication.

This week's takeaways:

• Blindly following capital-A "Agile" transformations can lead to throwing out valuable organizational change management wisdom accumulated over decades.
• Organizations are complex systems, and sustainable change requires understanding human behaviors and making changes at a rate the organizational "immune system" can absorb rather than big disruptive shifts.
• Clear strategic direction combined with empowering teams for continuous bottom-up improvement is critical. Frequent communication and recognizing people as adaptive beings, not just mechanical components, is crucial for effective change.

 We love to hear your feedback! If you have questions or would like to suggest a topic related to organizational change management and creating truly adaptive systems, please get in touch with us at feedback@definitelymaybeagile.com.

Send us a text

In this episode, Peter and Dave explore the complexities of accountability and leadership in organizations. They delve into how systems can often constrain agency and foster "learned helplessness," even when leaders claim to have an open-door policy. The conversation touches on the importance of empathetic listening, inclusive language, and creating environments that empower teams to make decisions closer to the issues they face.

This week´s takeaways: 

• Organizational systems are often designed to produce repetitive, constrained behavior, making it difficult for individuals to break out of engrained patterns, even when change is needed.
• True accountability requires not just assigning responsibility, but providing the authority, support and incentives for people to exercise that accountability.
• Leaders must be intentional about using inclusive language that creates psychological safety and invites open dialogue, rather than language that shuts down discourse.

Resources:

• The Unaccountability Machine by Dan Davis- https://www.goodreads.com/book/show/211161687-the-unaccountability-machine
• Leadership is Language: The Hidden Power of What You Say -- and What You Don't by David Marquet - https://www.goodreads.com/book/show/42774083-leadership-is-language?ref=nav_sb_ss_1_39

 We love to hear your feedback! If you have questions or would like to suggest a topic please contact us at feedback@definitelymaybeagile.com.

Send us a text

In this episode, Peter Maddison and David Sharrock tackle the often polarizing topic of "hybrid" agile approaches.
They break down why mindlessly blending practices like waterfall and agile is rarely the solution, as it creates an unsatisfactory middle ground that fails to maximize either approach's strengths. Instead, they suggest that organizations should aim to comprehensively understand the problems they're solving, and then purposefully apply the methodology best suited for that context - whether it's agile, waterfall, lean, or something else entirely.

This week´s takeaways:

• Avoid defaulting to a watered-down "hybrid" methodology that dilutes best practices.
• Deeply analyze problems to determine the optimal approach - don't blindly apply one-size-fits-all.
• Promote peer-to-peer cooperation and mutual understanding across boundaries between different practices rather than hierarchical control.
• Strive for an integrated enterprise where distinct methodologies complement each other fluidly.

We love to hear your feedback! If you have questions or would like to suggest a topic please contact us at feedback@definitelymaybeagile.com.

Send us a text

In this episode, Peter Maddison and David Sharrock discuss when not to use Scrum, the popular agile framework for software development. They explore scenarios where Scrum may not be the best fit, such as when an organization is resistant to change, lacks collaborative work, or operates in a highly complex environment with many dependencies and high failure costs. The conversation highlights the importance of understanding the problem, organizational context, and underlying assumptions before adopting any framework.

This week's takeaways:

• Assess the organization's readiness and openness to change before adopting Scrum, especially if past attempts have failed or if it is seen as a quick fix.
• Scrum thrives in collaborative environments; if the work is highly individualistic, Scrum may not be suitable.
• A cautious approach is required in complex and high-risk environments, potentially adapting Scrum or considering other frameworks.

Tune in to gain a nuanced understanding of how to navigate agile frameworks in complex environments and make informed decisions for your teams.

Send us a text

In this podcast episode, Peter Maddison and David Sharrock discuss the concept of designing an organization for continuous learning and improvement. They explore the leadership mindset and behaviors required to foster an environment that values and prioritizes continuous learning, as well as the need for leaders to relinquish control and empower data-driven decision-making. They emphasize the importance of creating capacity for learning by prioritizing work and saying no to non-essential tasks, as well as the role of leadership in modeling the desired behaviors.

This week´s takeaways:

• Leadership must prioritize and role model continuous learning through expectations and behaviors
• Create capacity by prioritizing work, saying no to non-essentials, and reducing overload
• Align organizational design (teams, feedback loops, tech) and strategy to enable learning

We love to hear your feedback! If you have questions or would like to suggest a topic please contact us at feedback@definitelymaybeagile.com.

Send us a text

In this episode, Peter Maddison and David Sharrock explore the nuanced topic of assigning user stories to individual team members. They discuss the pros and cons of this practice, discussing when it might be appropriate and when it could potentially harm team dynamics and productivity. The conversation touches on the importance of collaboration, team autonomy, and the challenges of balancing urgent work with long-term team development.

This week´s takeaways:

• Avoid individual assignments; encourage team members to pull tasks collaboratively.
• Individual assignments may be necessary for specialized skills or simple tasks, but use sparingly.
• Frequent individual assignments can reduce team autonomy, engagement, and skill development.

We love to hear your feedback! If you have questions or would like to suggest a topic, please contact us at feedback@definitelymaybeagile.com.

Send us a text

In this episode of Definitely, Maybe Agile, Peter Maddison and David Sharrock explore the critical aspects of creating a compelling business case for agile transformation. They discuss the importance of understanding an organization's current state, setting clear goals, and implementing change incrementally. The conversation delves into the challenges of organizational change, the value of external help, and the need for effective communication across all company levels during transformation efforts.

This week´s takeaways:

• Before embarking on any transformation, it's crucial to understand where your organization currently stands.
• Successful transformations require buy-in and participation from all parts of the organization.
• Rather than attempting large-scale changes simultaneously, focus on implementing transformations in small, manageable increments.

Join us as we navigate the complexities of organizational transformation with practical advice on achieving smooth, well-communicated change. 

Send us a text

In this podcast episode, Peter and Dave discuss strategies for overcoming procrastination and getting started on important tasks. They explore various factors that contribute to procrastination, including energy levels, prioritization, and the importance of managing one's schedule effectively. The conversation touches on productivity techniques like the Pomodoro method and the value of self-compassion when dealing with procrastination. They emphasize the importance of understanding personal energy patterns and creating a balanced approach to task management.

This week´s takeaways:

• Recognizing and working with your natural energy patterns throughout the day can significantly impact productivity. Tackle complex tasks when you're most alert, and incorporate breaks to maintain energy levels.
• Organize tasks based on priority and context (e.g., grouping similar activities together). This approach can help create a more efficient workflow and reduce the mental burden of constantly switching between different types of tasks.
• Be kind to yourself when facing productivity challenges. Techniques like the Pomodoro method, breaking large tasks into smaller steps, and planning your week in advance can help overcome procrastination and increase overall productivity.

Tune in to elevate your productivity game and achieve a harmonious work-life integration.

Send us a text

In this episode of Definitely, Maybe Agile, Peter Maddison and David Sharrock explore the role of agile coaches in organizations. They discuss the evolution of coaching in business, drawing parallels with sports coaching, and examine the value coaches bring to modern organizations. The conversation delves into the challenges faced by agile coaches, the importance of objectivity, and the future of coaching in the business world.

This week´s takeaways:

• Organizational coaches provide valuable objectivity by observing the system from the outside, offering insights that those within the system might miss.
• While the term "agile coach" may evolve, the need for nurturing support to help organizations improve and adapt remains crucial in today's business landscape.
• There are strong parallels between coaching in high-performing sports teams and successful businesses, with coached organizations generally outperforming those without coaching support.

Don’t miss this conversation about the enduring necessity and transformative potential of Agile coaching

Send us a text

In this episode of Definitely Maybe Agile, hosts Peter Maddison and David Sharrock explore the complex dynamics between rational and emotional decision-making in organizations, particularly when implementing new ways of working at scale. They discuss the challenges of presenting data-driven solutions and the often unexpected emotional responses these can trigger. The conversation delves into the psychological aspects of decision-making, including the impact of past experiences, and the importance of recognizing and addressing emotional responses in professional settings. Peter and Dave offer insights on effective communication strategies, the significance of timing and presentation methods, and the need to understand hidden incentives that may influence reactions to proposed changes.

This week´s takeaways:

• Recognize when a discussion is becoming unproductive due to emotional responses, and be willing to step back, listen, and allow time for tensions to dissipate before proceeding.
• Tailor your presentation of data and information to your audience, keeping it simple and clear.
• Be aware of hidden incentives or underlying factors that may be influencing someone's response to a proposed change. Listen actively to understand their perspective and concerns beyond the surface-level reaction.

Don't miss this episode brimming with practical advice and actionable strategies for navigating the intricate landscape of organizational decision-making.

Send us a text

In this episode of Definitely Maybe Agile, Peter Maddison and David Sharrock dive into the often misunderstood concept of "Definition of Done" and its crucial role in measuring and maintaining quality in agile teams. They explore how this simple yet powerful tool can significantly impact team discipline, product quality, and overall project success. The hosts discuss common challenges teams face in adhering to their Definition of Done and offer insights on effectively implementing and maintaining this practice.

This week´s takeaways:

• The true value lies in developing team discipline to consistently meet the agreed-upon criteria, not just in creating the list itself.
• Should be viewed as a "tax on delivery" - a necessary investment in quality that may slightly reduce immediate output but prevents future rework and technical debt.
• The implementation requires buy-in from the entire team, including product owners, and should be kept to a manageable 5-10 items to ensure consistent adherence.

Whether you're a seasoned agile practitioner or new to the concept, this episode offers valuable lessons on the balance between quality and commitment, ensuring your team's work stands the test of time.

Send us a text

In this episode of the Definitely, Maybe Agile podcast, hosts Peter Maddison and Dave Sharrock are joined by special guest Kate Megaw to explore the evolving landscape of leadership in the age of remote and hybrid work. The trio delves into the challenges leaders face in transitioning from traditional management styles to more adaptive, trust-based approaches. They discuss the importance of empathy, outcome-focused leadership, and the need for organizations to invest in developing leadership skills at all levels. The conversation touches on the complexities of maintaining team engagement, the value of in-person interactions, and strategies for effective remote leadership.

This week´s takeaways:

• Leaders must shift from managing work to leading people, focusing on coaching and building trust rather than micromanaging tasks, especially in remote and hybrid environments.
• Effective leadership, particularly in remote settings, requires increased emphasis on empathy, regular check-ins, and building relationships with team members beyond work-related discussions.
• Companies need to invest more in leadership training and development, recognizing that leadership is a skill set that requires ongoing support and education, not just a title or promotion.

Don't miss this episode! Tune in now to discover how leaders can adapt and thrive in the modern work environment. Listen to it today!