Definitely, Maybe Agile

Send us a textIn this episode of Definitely Maybe Agile, Peter Maddison and David Sharrock explore the critical question: "How do we know when work is ready to start developing?" They discuss the challenges of translating business requirements into technical implementation, the importance of having the right people in collaborative discussions, and practical approaches to defining "ready" work. Peter shares recent experiences with organizations struggling with this exact problem, while Dave highlights how trust between business and technology teams impacts the handoff process. They explore visual collaboration techniques, the concept of "full kit," and practical ways to determine if work is truly ready to begin.This week´s takeaways:Revisit and reinforce your work definition process regularly, as changing roles and organizational shifts can erode even the most robust systems over time.Use the "full kit" concept as part of your definition of ready, and be willing to say no to work that doesn't meet these criteria.Work is ready to start when it's the team's top priority, has a clearly defined problem to solve, and the team can confidently estimate it within their typical delivery range.

Send us a textIn this insightful conversation with Suzanne El-Moursi, co-founder and CEO of BrightHive, Peter and Dave explore how organizations are addressing the growing gap between data volume and analytical capacity. Suzanne reveals that while 90% of the world's data was created in just the last two years, only about 3% of enterprise employees are data professionals, creating a massive bottleneck where business teams must wait in line for insights from central data teams.BrightHive's solution is an "agentic data team in a box" – seven AI agents that work in unison to handle the entire data lifecycle from ingestion to governance to analytics. Unlike typical AI solutions, these agents operate at the metadata layer to ensure quality, compliance, and meaningful insights without replacing human expertise.The conversation covers compelling use cases across industries – from helping resource-constrained organizations extend their analytical capacity to unifying fragmented data landscapes resulting from mergers and acquisitions. Perhaps most striking is Suzanne's vision for measuring AI's impact through what she calls the "delight KPI" – are employees finding their work more fulfilling when augmented by these tools?Key Takeaways:Data fragmentation persists - Organizations struggle with siloed data across systems, especially after mergers, blocking comprehensive analysis.AI augments human intelligence - "A doctor with AI will displace a doctor without AI" - the goal is removing grunt work so humans tackle higher-value analysis.Measure the "delight KPI" - Track how AI improves job satisfaction by enabling more data-informed work without technical bottlenecks.Cultural shift needs technical solutions AND organizational buy-in to overcome skepticism about AI in the workplace.

Send us a textIn this episode of Definitely Maybe Agile, Peter Maddison and David Sharrock explore how increasing technological capabilities—particularly AI and modern development tools—are changing the landscape of organizational change management. They discuss the implications of newly created capacity, the value of team autonomy, and the importance of balancing efficiency with innovation.This week´s takeaways:Creating capacity through new technologies doesn't mean downsizing teams—it means enabling organizations to address previously neglected but valuable work while maintaining knowledge pipelines.Team autonomy is crucial for effective change management—when teams have both direction and freedom to make decisions about their workspace, they can respond more effectively to urgent needs in the system.Organizations must recognize and protect "slack time" as a valuable resource rather than inefficiency—this time for maintenance, innovation, and thinking is essential for sustainable systems.

Send us a textIn this episode of Definitely Maybe Agile, hosts Peter Maddison and David Sharrock tackle an often overlooked but critical topic: career progression for Scrum Masters and Product Owners. They explore how organizations initiate these crucial Agile roles but frequently fail to consider their long-term evolution within the company structure.The discussion contrasts the divergent career trajectories of these two roles. For Product Owners, a clearer path exists from managing individual products to becoming Chief Product Owners and potentially Line of Business managers, though challenges arise when the role lacks proper autonomy or is treated as a part-time responsibility. Meanwhile, Scrum Masters face a more ambiguous journey, with traditional progression into Agile coaching roles becoming increasingly limited in many organizations despite the valuable skills they develop.Peter and Dave highlight the critical importance of demonstrating value and making contributions visible, particularly for Scrum Masters whose impact often remains behind the scenes. They also discuss how understanding financial aspects of the business becomes increasingly crucial as professionals advance in either career path.Key Takeaways:Product Owners have clearer progression paths toward leadership positions, but organizations must properly position and empower the role from the beginning to enable this growth.Scrum Masters develop highly valuable skills in facilitating delivery and optimizing organizational flow, but need to actively demonstrate their impact to create career advancement opportunities.Both roles require increasingly strategic thinking about business value and financial outcomes to progress into higher leadership positions within organizations.

Send us a textIn this episode of Definitely Maybe Agile, hosts Peter Maddison and David Sharrock dive into the world of Objectives and Key Results (OKRs). They explore how this increasingly popular framework helps organizations create alignment, measure progress, and foster autonomy while moving away from traditional KPIs. From the origins at Intel in the 70s to widespread adoption by tech giants like Google, Peter and David discuss the nuances of implementing OKRs effectively and why they're particularly well-suited for organizations operating in rapidly changing environments.This week´s takeaways:Unlike KPIs which measure performance, OKRs measure progress and alignment to strategy. They should never be tied to individual performance metrics as this undermines their exploratory nature.Successful OKR implementation requires ongoing conversations, regular reviews, and a cultural shift. Many organizations underestimate the effort needed to maintain OKRs effectively.Effective OKRs should be limited in number (3-5 objectives with 3-5 key results each), represent stretch goals beyond business-as-usual, and serve as a prioritization mechanism for the organization.

Send us a textWhen was the last time raising risk in your organization led to anything other than slowing down? Join hosts Peter Maddison and David Sharrock as they challenge conventional thinking about risk management in the age of rapid technological change. This episode reveals why traditional approaches might be putting your organization in greater danger.Drawing from their battle-tested experience working with financial and technology organizations, Peter and David crack open the uncomfortable truth: many companies still treat risk management as a checkbox exercise rather than a competitive advantage. They reveal how the explosion of data analytics capabilities has rendered old "rule of thumb" approaches obsolete while simultaneously creating entirely new risk landscapes that most organizations are woefully unprepared to navigate.This week's takeaways :Risk management begins with identifying vulnerabilities, understanding potential impacts, and making informed decisions about how to handle them—whether through acceptance, avoidance, transfer, or reduction.Effective risk management isn't just about frameworks and committees—it requires a cultural environment of psychological safety where risks can be openly discussed without fear.The most effective approaches position oversight functions like architecture as service providers rather than gatekeepers, helping teams move forward safely rather than simply blocking progress.Subscribe to "Definitely Maybe Agile" to transform how your organization approaches risk, digital transformation, and DevOps at scale.

Send us a textIn this insightful episode of "Definitely Maybe Agile," hosts Peter Maddison and Dave Sharrock welcome David Hirschfeld, founder and CEO of Tekyz Inc, to discuss the complexities of effective product management. A 35-year software development veteran and former physics student from UCLA, David brings a unique perspective shaped by leadership roles at tech giants like Computer Associates, Texas Instruments, Intel, and Motorola.The conversation explores the critical balance between product market fit and product solution fit, with David emphasizing why focusing on customer problems rather than product features leads to greater success. Whether you're a startup founder, product manager, or development team leader, this episode with the host of the Scaling Smarter Podcast provides actionable insights for creating products that truly solve customer problems and generate sustainable revenue.This week´s takeaways:The most valuable customer conversations happen when you ask about their problems, not your product features.Successful product management requires understanding both the perceived impact of a problem and its actual cost to customers.Successful founders and product managers are those who love understanding customer problems and spend their time learning about customer challenges.

Send us a textIn this engaging episode of "Definitely Maybe Agile," hosts Peter Maddison and David Sharrock welcome Marcelo Calbucci, author of "The PR FAQ Framework." Marcelo shares his expertise from 25+ years at companies like Amazon and Microsoft, plus his extensive startup experience.The conversation explores the Press Release and Frequently Asked Questions (PR FAQ) framework developed at Amazon around 2004. This approach helps teams clarify vision and strategy before jumping into execution, addressing a common problem in software projects. Unlike PowerPoint presentations that can create an "illusion of clarity," the PR FAQ document promotes alignment and ownership through collaborative creation.This week´s takeaways:Why most PR FAQs actually lead to "no" decisions (which is valuable)How the framework balances strategic thinking with practical considerationsThe importance of involving multiple stakeholders (sometimes 20+ people)How PR FAQs can be used at different product lifecycle stagesThe hosts draw parallels to lean startup methodology, while Marcelo explains why PR FAQ encourages "thinking before shooting" rather than the "build first, learn later" approach. The discussion highlights how clear, collaborative documentation can prevent misalignment and create shared ownership of initiatives.

Send us a textIn this episode of Definitely Maybe Agile, Peter Maddison and Dave Sharrock dive into the nuances of intake funnels and definitions of ready—key concepts for ensuring work progresses effectively. They explore how traditional project delivery mindsets differ from product-driven approaches, emphasizing the need for adaptability, continuous learning, and decision points that prevent wasted effort.From setting clear entry criteria to measuring throughput and pivoting when needed, they break down how teams can structure their workflows to prioritize value-driven outcomes. Whether you're refining your backlog, managing stakeholder expectations, or optimizing delivery processes, this episode provides practical insights to help you navigate uncertainty while keeping momentum.This week´s takeaways: Clear intake process – Define criteria to assess idea readiness before execution.Product vs. project mindset – Embrace uncertainty and pivot as needed.Measure progress – Use checkpoints and throughput tracking to prioritize work.Tune in to learn how to balance discipline with flexibility and ensure your work moves forward with intention!

Send us a text In this episode of Definitely Maybe Agile, Peter Maddison and David Sharrock explore the evolution of Agile methodologies. They discuss how Agile represents solutions to persistent problems that may be rebranded but address fundamental needs. The hosts examine why Agile has faced criticism, drawing parallels to Lean's journey from buzzword to established methodology, while exploring the challenges organizations face in implementation.This week´s takeaways: The fundamental problems Agile addresses remain constant, even as attitudes toward the methodology evolve.Organizations often struggle with Agile implementation due to legacy architecture, leadership buy-in, and organizational context.Like Lean before it, Agile is transitioning from a hyped methodology to becoming part of a broader toolkit.Ready for more insights?  Follow Definitely Maybe Agile on your favorite podcast platform and join Peter and David as they tackle the complexities of digital transformation at scale. New episodes drop regularly!

Send us a textIn this episode of Definitely Maybe Agile, Peter Maddison and David Sharrock explore the critical role of documentation, terminology, and process definition in scaling organizational success. They discuss how leading companies like Netflix build strong cultures through well-defined terms and principles rather than rigid processes. The hosts dive deep into how architectural decisions, cultural transformation, and team empowerment all stem from having a shared organizational language. Through real-world examples and references to modern practices, they examine the balance between principle-based leadership and necessary process documentation in creating high-performing organizations.This week´s takeaways:Shared terminology drives better communication and decision-making across teams and departments.Principles empower teams more effectively than rigid processes and controls.Leading with principles while maintaining essential process documentation creates the right organizational balance.

Send us a textIn this episode of Definitely Maybe Agile, Peter Maddison and David Sharrock explore the evolution of quarterly planning from traditional PI planning events to more streamlined modern approaches. They discuss how effective quarterly planning reveals organizational dependencies, aligns priorities across teams, and helps maintain focus on delivering value. The hosts share insights on avoiding common pitfalls like over-planning future work and emphasize the importance of maintaining flexibility while ensuring clear direction for immediate execution.This week´s takeaways:Clear, sequenced priorities shared across teams - focus on completing initiatives before starting new onesDetailed planning for immediate work (1-2 months), with less detail for future monthsActive dependency management to identify and address bottlenecks early

Send us a text In this thought-provoking episode of Definitely Maybe Agile, hosts Peter Maddison and David Sharrock dive into PMI's groundbreaking shift beyond the iron triangle. Discover why successful project delivery now demands both traditional metrics and tangible business value. The hosts explore the crucial differences between ordered and unordered problem spaces, revealing when to apply Agile versus traditional project management approaches. Learn practical insights about balancing execution with outcomes, and why the most successful organizations master both methodologies. Essential listening for project managers, Agile practitioners, and technology leaders navigating modern delivery challenges. 

Send us a textIn this episode of Definitely Maybe Agile, Peter Maddison and David Sharrock explore the nuances of product backlogs in agile environments. They discuss the tension between emergent backlogs and fixed feature sets, the importance of backlog management, and various prioritization techniques, including "buy a feature" and impact-effort matrices.This week's takeaways:Separate tactical (near-term) and strategic backlogs to reduce psychological pressure and maintain focus - avoid creating extensive long-term backlogs that will likely become irrelevant.Stakeholder prioritization must be balanced with technical constraints and team capabilities - product owners should communicate changes in delivery order transparently to maintain trust.Regular backlog refinement should include archiving rejected items instead of deleting them, helping teams avoid repeatedly addressing the same requests while keeping the active backlog manageable.Ready to scale your agile practices? Tune in to more episodes on your favorite platform.

Send us a textJoin Peter Maddison and David Sharrock in this thought-provoking episode of Definitely Maybe Agile as they explore the evolution of leadership decision-making in modern organizations. They dive deep into how traditional leadership models are being challenged by today's business environment and discuss the crucial shift from control-based to collaborative decision-making approaches.This week´s takeaways:  Executive decision-making challenges often stem from two distinct factors: emotional intelligence issues (dealing with unprepared stakeholders) and critical thinking problems (legitimate exploration of complex issues).  The traditional "highest paid person's opinion" (HiPPO) approach to decision-making is becoming increasingly dangerous in today's rapidly changing business environment, where the speed of market changes demands faster and more distributed decision-making processes.  Modern leadership requires a fundamental shift from centralized control to distributed authority, with leaders focusing on creating frameworks that enable lower-level decision-making while maintaining visibility of outcomes. 

Send us a textIn this episode of Definitely Maybe Agile,  Peter Maddison and David Sharrock explore the evolving complexities of calculating the total cost of ownership (TCO) in modern software development and delivery.This week´s takeaways:TCO fundamentals remain unchanged, but the environment for calculating and applying TCO has become more complex.Organizations must distinguish between strategic proprietary development and commoditized solutions, using tools like Wardley mapping to identify where to invest versus reduce costs.Understanding and defining system boundaries is crucial for accurate TCO calculation - using approaches like value chain mapping, value stream mapping, or domain-driven design helps identify hidden costs and dependencies.Subscribe to Definitely Maybe Agile on your favourite platform and join Peter and David as they unpack the challenges of digital transformation at scale.

Send us a textIn this thought-provoking episode of the Definitely, Maybe Agile podcast,  Peter Maddison and David Sharrock dive deep into the evolving world of enterprise data management and its impact on modern organizations. From data hygiene to governance, discover how the definition of corporate data has dramatically shifted in recent years and what it means for your business.This week´s takeaways:The evolution from "data is the new oil" to strategic data stewardshipWhy Chief Data Officers (CDOs) struggle to maintain long-term positionsHow regulatory compliance is reshaping data management practicesThe critical balance between quantitative and qualitative data in decision-makingThe impact of AI and LLMs on data analysis and sentiment trackingWhether you're a technology leader, data professional, or business executive, this episode provides insights into navigating the complex intersection of data governance, team structure, and business value. Learn why traditional approaches to data management may be insufficient for today's challenges and what successful organizations are doing differently.

Send us a textIn this episode of "Definitely Maybe Agile," Peter Maddison and David Sharrock explore the application of generative AI in the Software Development Lifecycle (SDLC). While many organizations focus solely on using AI tools like GitHub Copilot for coding, the hosts discuss a broader vision of how AI can enhance the entire development process, from ideation to maintenance. They delve into innovative concepts like organizational knowledge agents and AI-assisted work prioritization systems.This week´s takeaways:SDLC optimization  - A key value creation area that continues to evolve through new approaches and technologies.AI applications extend beyond developer tools - Moving past coding assistance to improve productivity across multiple roles and touchpoints.AI as an organizational assistant - Understanding company knowledge, refining ideas, and improving prioritization and decision-making processes.Want to join the conversation about AI in SDLC and digital transformation at scale? Share your thoughts and feedback at feedback@definitelymaybeagile.com, and don't forget to subscribe to the podcast to stay updated on future discussions about agile and DevOps practices.

Send us a textIn this episode of the Definitely, Maybe Agile podcast, Peter Maddison and David Sharrock explore the critical challenges they've encountered when working on agile transformations. From superficial leadership support to misdiagnosed organizational problems, these seasoned consultants share their insights on navigating the complex obstacles that can undermine transformation efforts. They also discuss the dynamics of working with strong-willed leaders, managing shifting priorities, and the importance of dedicated teams - all while highlighting the fundamental role of effective leadership in driving successful change. This episode offers valuable lessons for any organization embarking on an agile journey at scale.This week's takeaways:Lack of leadership buy-in and support can doom an agile transformation effort, as the change agents lack the authority and credibility to drive the necessary changes.Fixing the wrong problem or focusing on ineffective solutions like training can waste time and resources, highlighting the importance of accurately diagnosing the root causes.Challenges with strong-willed leaders, constantly shifting priorities, and non-dedicated teams all require skilled navigation and a focus on addressing the underlying leadership and organizational issues.By the end of this discussion, you'll understand why identifying the right problem is crucial for meaningful transformation and how organizations can avoid these common traps to achieve genuine progress.

Send us a textIn this episode of Definitely Maybe Agile, Peter Maddison and David Sharrock tackle the delicate balance between work transparency and micromanagement, particularly in hybrid work environments. They explore how breaking down work effectively, building trust between leaders and teams, and maintaining healthy communication patterns can create a more productive workplace. The hosts discuss why detailed task breakdowns aren't about control but rather about creating clarity and confidence for all stakeholders involved.This week´s takeaways:  Effective work relationships require trust flowing both ways between leadership and teams.Breaking down work into smaller, measurable pieces isn't about micromanagement – it's about creating clarity, enabling better learning, and building confidence in progress.Leaders need to be mindful of how they request updates and information. Listen in for actionable ideas and engaging perspectives that will help you build stronger, more accountable teams.

Send us a textWhy do even successful agile teams struggle to maintain their improvement momentum?In this compelling episode, Peter Maddison and David Sharrock answer this question and challenge the myth that continuous improvement is "just a mindset." Drawing from both scientific research and hands-on experience, they reveal why sustaining improvement is physically and mentally taxing, and why the journey becomes increasingly difficult after the initial quick wins. Through insights from sports coaching and real-world software delivery, they offer a fresh perspective on making continuous improvement truly sustainable.This week´s takeaways: Continuous Improvement Needs Constant NurturingSmall Steps Lead to Big ChangesMake Progress Visible and Achievable Want more practical insights on scaling agile and DevOps practices? Join Peter and Dave as they unpack the complexities of modern software delivery and organizational transformation. Subscribe to Definitely Maybe Agile wherever you get your podcasts, and share your thoughts at feedback@definitelymaybeagile.com.

Send us a textIn this episode, hosts Peter Maddison and David Sharrock delve into onboarding in organizations. They explore the challenges and best practices of integrating new team members, discussing everything from formal training methods to hands-on learning approaches. The conversation covers the importance of providing context, the value of apprenticeship-style learning, and the role of DevOps practices in facilitating smooth onboarding processes.This week´s takeaways:Provide comprehensive organizational context to new hiresImplement apprenticeship-style, hands-on learningCreate easily digestible, on-demand learning contentDevelop robust DevOps practices for early engagementBalance formal training with informal learning opportunitiesRegularly validate learning progress and understandingTailor onboarding approaches to different roles and experience levelsDon't miss this episode if you're looking to enhance your organization's onboarding processes and create a more agile and efficient workplace environment.

Send us a textIn this episode of "Definitely Maybe Agile," hosts Peter Maddison and David Sharrock discuss the evolution of agile methodologies beyond software development. They explore how agile principles can be applied to business processes, such as budgeting, and delve into the challenges of implementing cultural change within organizations. The conversation touches on the importance of collaboration, facilitated workshops, and the need to move beyond rigid frameworks to focus on outcomes and ways of working that drive value. This week's takeaways:Organizations should focus on the benefits and mindset of agile rather than getting caught up in terminology or strict processes.Continued efforts to drive cultural shifts are important, even as the initial momentum for change may wane in some environments.Instead of fixating on agile terminology or frameworks, organizations should concentrate on fostering collaboration, cross-functional teamwork, and achieving tangible business outcomes to deliver better value sooner safer happier.Tune in for actionable strategies to foster perseverance and continuous improvement. Don't miss out—subscribe and share with your friends to keep the insights flowing!

Send us a textIn this episode of the Definitely, Maybe Agile podcast, Peter Maddison and David Sharrock discuss a fascinating case study of Nike's digital transformation gone awry, resulting in a $25 billion loss and 32% market share decline over three years. They explore the pitfalls of over-relying on data-driven decision-making while neglecting other crucial aspects of business strategy and customer engagement.This week´s takeaways:Data-driven decision-making is valuable, but you need the right data. Companies need to balance quantitative data with qualitative insights and intuition.Optimizing for existing customers isn't enough for growth. Businesses must also focus on attracting new customers and exploring adjacent markets.Organizational culture plays a critical role in transformation efforts. Companies need to foster an environment where employees feel empowered to speak up and challenge prevailing narratives.Not everything that matters can be easily measured. Organizations should find ways to understand and manage important factors, even if they are difficult to quantify, rather than ignoring them in favor of easily measurable metrics.Resources_ Nike's $25B blunder shows us the limits of “data-driven-  https://uxdesign.cc/nikes-25b-blunder-shows-us-the-limits-of-data-driven-ad30b6e3d938

Send us a textIn this episode of Definitely Maybe Agile, hosts Peter Maddison and David Sharrock dive into the challenging world of agile practices in regulated environments. They explore the tension between modern agile methodologies and traditional audit requirements, offering insights on how organizations can bridge this gap. The discussion covers the importance of understanding compliance needs, automating evidence collection, and transforming the audit process to align with agile principles.This week´s takeaways:Organizations must understand what they need to comply with and set up systems and practices that make evidence easily obtainable without disrupting workflow.Implement automation in the delivery system to capture and expose evidence of compliance, making it easier to demonstrate adherence to regulations without slowing down agile processes.Shift the audit focus from document checking and stage gates to validating system behavior. This approach can make audits more meaningful and engage development teams in solving compliance challenges creatively.

Send us a Text Message.In this thought-provoking episode of Definitely Maybe Agile, Peter Maddison and David Sharrock dive into the complex relationship between quality, productivity, and organizational culture. They explore how external market pressures and a focus on short-term productivity can undermine long-term success. The hosts discuss the importance of building quality into processes, the challenges of cultural change, and the enduring relevance of Deming's principles in today's business world. This conversation offers valuable insights for leaders and teams striving to balance market demands with sustainable, quality-focused practices.This week´s takeaways:Quality is cultural, not mechanical. Sustainable improvement comes from fostering a culture of quality rather than simply implementing mechanical processes.Building quality in is more effective than inspecting for quality at the end. Organizations that integrate quality throughout their development process tend to perform better than those relying on final quality checks.Cultural change is slow to build but quick to lose. While it takes time and effort to cultivate a quality-focused culture, it can be rapidly undermined by leadership changes, mergers, or short-term thinking.Don't miss out on this deep dive into aligning leadership and processes to create an environment where quality and innovation can truly thrive.

Send us a Text Message.In this episode of Definitely Maybe Agile, hosts Peter Maddison and David Sharrock dive into the complex world of developer experience and its impact on organizational productivity. They explore the various methods of measuring developer experience, from telemetry and flow metrics to impact metrics and qualitative data. The conversation touches on the challenges of interpreting this data, the importance of trust in the workplace, and the long-term implications of focusing on developer experience, including employee retention and engagement.This week´s takeaways:Developer experience is becoming a crucial focus for organizations, driven by factors such as the adoption of AI tools like GitHub Copilot and the need to improve productivity and retention.Measuring developer experience requires a multifaceted approach, including telemetry, flow metrics, impact metrics, and qualitative data gathered through surveys and direct conversations with employees.Long-term considerations, such as employee retention and engagement, are essential aspects of developer experience that require careful attention and cannot be addressed solely through short-term productivity metrics.Tune in, and rethink how you measure and optimize developer experience for sustained innovation and long-term organizational growth.

Send us a Text Message.In this episode of "Definitely Maybe Agile," hosts Peter Maddison and David Sharrock dive deep into the critical skill of understanding and communicating with customers. They explore common pitfalls in messaging, the importance of tailoring communication to different audiences, and strategies for effectively conveying your value proposition. Whether you're a product owner, marketer, or anyone looking to improve their communication skills, this episode offers valuable insights on crafting messages that resonate with your target audience.This week´s takeaways: Understanding your customer is crucial for effective communication, both externally and within organizations.There isn't a single perfect message; successful communication often requires multiple tailored approaches.Focus on solving one specific problem for your customer rather than trying to address everything at once.Stay tuned for more episodes that promise continued insights into effective agile and DevOps strategies. Your feedback and subscription are pivotal to our journey, so join us and become part of our growing community.

Send us a Text Message.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!

Send us a Text Message.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 Message.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 Message.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 Message.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 Message.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 Message.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 Message.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 behaviorsCreate capacity by prioritizing work, saying no to non-essentials, and reducing overloadAlign organizational design (teams, feedback loops, tech) and strategy to enable learningWe 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 Message.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 Message.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 Message.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-machineLeadership 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 Message.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 Message.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 Message.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/50343488Larry Maccherone https://www.youtube.com/watch?v=EyS1kmmlA5YMartin 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! 

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.

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.