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.

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-baeTune 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.

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.

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.

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

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=1094bb1d794cHave 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.

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-awarenessEncourage the blending of diverse perspectivesPractice Patience and Self-RepairResources: How Capable Leaders Navigate Uncertainty and Ambiguity- https://cutlefish.substack.com/p/tbm-274-how-capable-leaders-navigate?utm_source=activity_itemJoin 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!

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.

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 reorganizationsJoin 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.

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 gapBehavioral Influences on Organizational DynamicsBeware of Resistance and Long-Term ChallengesNon-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.

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/dzojO5kJeff Bezos- https://www.youtube.com/watch?v=Ub585Pn4yroTune 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.

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.

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-factorJoin 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.

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 FrameworksRecognition of Overlapping IntersectionsHolistic Thinking for Organizational ChangeWe 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

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

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

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 guessesC. Don't forget   7. The Agile/DevOps mindset   8. Risks and contingency   9. Don't forget to measureD. End of year   10. Check your progress/direction   11. Take time to review/learn    12. Recognize the people that got you (t)hereWe 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

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.

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

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.