Podcast appearances and mentions of david sharrock

Send us a textIn this episode of Definitely, Maybe Agile, hosts Peter Maddison and David Sharrock welcome Steven Puri, Founder and CEO of The Sukha Company. Drawing from his unique background spanning Hollywood film production and tech startups, Steven shares fascinating insights about achieving flow states in remote and hybrid work environments.Steven's journey from IBM software engineer to Hollywood executive (where he helped manage franchises like Die Hard and Wolverine at studios including DreamWorks and 20th Century Fox) provides a refreshing perspective on team productivity and creative collaboration. He explains how the film industry has long mastered the transitions between remote, hybrid, and in-person work—knowledge that proved invaluable when the pandemic forced tech teams into distributed environments. The conversation explores the neuroscience of creativity, practical leadership approaches to foster flow states, and how Steven's experiences led him to create a platform specifically designed to help remote workers overcome procrastination while maintaining wellbeing. This is one not to miss!  Key Takeaways: Leaders can create environments where flow happens - Establishing boundaries like protected focus time (e.g., 9 AM to noon) allows team members to accomplish meaningful work before daily meetings begin.The "two-problem" approach to creativity - Having more than one challenge to work on simultaneously can unlock creative solutions, as your subconscious mind works on one problem while you actively engage with another.Remote work requires different "colors on your palette" - Different work modes (remote, hybrid, in-office) excel at different tasks, with in-person collaboration being particularly valuable for creative ideation and whiteboarding sessions.Books Mentioned:"Flow" by Mihaly Csikszentmihalyi - https://www.goodreads.com/es/book/show/66354.Flow"The Net and the Butterfly" by Olivia Fox - https://www.goodreads.com/book/show/30024684-the-net-and-the-butterfly"Atomic Habits" by James Clear - https://www.goodreads.com/book/show/40121378-atomic-habits

Send us a textEvery technical system harbors its share of quick fixes and band-aids – those temporary solutions we implement with the best intentions of returning to fix properly "someday." But what happens when that day never comes?Peter Maddison and David Sharrock dive deep into what they call "longstanding risks" – the accumulated technical debt that results from prioritizing expediency over completeness. Through a relatable example of a memory-leaking service that gets automatically restarted rather than properly fixed, they unpack the hidden costs of these decisions. The conversation reveals how seemingly minor shortcuts can gradually transform robust systems into fragile, unmaintainable messes.The hosts share a compelling analogy about a utility company that saved money by skipping tree trimming around power lines for just one year – only to face significantly higher costs from the resulting infrastructure damage. This perfectly illustrates how short-term thinking about technical maintenance creates expensive long-term consequences. They offer practical recommendations including proper documentation of temporary fixes, avoiding team overload, and maintaining good system hygiene.What makes this episode particularly valuable is the mindset shift it advocates: moving from attempting to prevent all possible failures to building systems that remain resilient when inevitable problems occur. As Sharrock references from safety expert Sidney Decker's work, sometimes the best approach is focusing on what makes your system work well rather than obsessively eliminating every risk. Whether you're managing complex technical systems or leading transformation efforts, these insights will help you balance pragmatic solutions with long-term system health.

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

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.

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.

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

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.

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. 

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!

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!

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! 

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.

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/NkQ58I53mjkJoin 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. 

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. 

 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. 

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

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 doDon't try copying somebody else modelThe 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. 

 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. 

 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

In this episode we are going to strike at the heart of what it takes to develop a successful business. My guest is David Sharrock. Through his long career as a suburban solicitor, David has helped thousands of small business owners. He knows what works and what doesn’t. He has seen everything. From the woefully unsuccessful to the booming enterprise, and everything in between. And, of course, he’s learned a bunch of lessons about what separates the good from the bad. The winners from the losers. I love his calm wisdom. And the genuine care he has for people who run businesses. Because, he knows, the success or otherwise of small and medium business affects lives. It can set people up for a happy, fulfilled, secure life . Or it can plunge them into a spiral of worry and anxiety.

David Sharrock is the Managing Principal of Sharrock Pitman Legal, a thriving boutique Melbourne based commercial law practice where the credo is: ‘on your side’. David has over 40 years extensive business experience and provides business consulting to the owners and managers of small to medium enterprises. He also works with the executive and board members of not for profit organisations, advising on practical matters relevant to running their enterprises. A nationally accredited and experienced mediator and dispute resolution expert, David’s aim is to work with his clients on practical solutions to avoid the need for costly court proceedings. David is also an accomplished author, writing the book: Fighting for Enterprise Success: Through the Eye of the Tiger.  It’s a practical workbook comprising a 440-page journey through 44 years of personal and enterprise experience, with 68 self-assessment tools, samples and templates. Episode highlights include: David’s first leadership role and the challenges associated with this Servant leadership and why it is a leadership philosophy that David follows Leaving full time employment and starting your own business The challenges that the legal profession will face in the coming years Links David's LinkedIn Profile Sharrock Pitman Website Purchase Fighting For Enterprise Success  

In this fourth episode of Horror Hill (http://www.simplyscarypodcast.com/shows/horror-hill/) , we bring you two spine-tingling tales from David Sharrock (http://www.simplyscarypodcast.com/authors/david-sharrock/)  and Soren Narnia (http://www.simplyscarypodcast.com/authors/soren-narnia/) , performed by host and narrator Jason Hill (http://www.simplyscarypodcast.com/performers/jason-hill/) , one a a meditation on the power of the written work and the cruel things that lurk within the dusty pages of forgotten tomes, the second concerning visitors in the dark night from places even darker still. Stories featured in this episode “Mummer Man (https://www.reddit.com/r/nosleep/comments/1x4kk6/mummer_man/) ” by David Sharrock – more info about this author (http://www.simplyscarypodcast.com/authors/david-sharrock/) “Visitation” by Soren Narnia – more info about this author (http://www.simplyscarypodcast.com/authors/soren-narnia/) See full episode details, including the text of the featured stories, here:  http://www.simplyscarypodcast.com/series/horror-hill/s1e04-hh/ Podcast executive produced and directed by: Craig Groshek (http://simplyscarypodcast.com/staff/craig-groshek/) Podcast produced by: Craig Groshek (http://simplyscarypodcast.com/staff/craig-groshek/) Podcast hosted by: Jason Hill (https://www.simplyscarypodcast.com/performers/jason-hill/) Stories performed by: Jason Hill (https://www.simplyscarypodcast.com/performers/jason-hill/) Sound design by: Luke Hodgkinson (https://www.simplyscarypodcast.com/staff/luke-hodgkinson/) Script by: Craig Groshek (http://simplyscarypodcast.com/staff/craig-groshek/)  & Jason Hill (https://www.simplyscarypodcast.com/performers/jason-hill/) (http://simplyscarypodcast.com/staff/craig-groshek/) Original artwork by: Jason Hill (https://www.simplyscarypodcast.com/performers/jason-hill/) Audio program © 2018 Chilling Entertainment, LLC (http://chilling-entertainment.com/)  – All Rights Reserved. No reproduction or use of this content is permitted without the express written consent of Chilling Entertainment, LLC (http://chilling-entertainment.com/) . The copyrights for each story are held by the respective authors.

In this fourth episode of Horror Hill (http://www.simplyscarypodcast.com/shows/horror-hill/) , we bring you two spine-tingling tales from David Sharrock (http://www.simplyscarypodcast.com/authors/david-sharrock/)  and Soren Narnia (http://www.simplyscarypodcast.com/authors/soren-narnia/) , performed by host and narrator Jason Hill (http://www.simplyscarypodcast.com/performers/jason-hill/) , one a a meditation on the power of the written work and the cruel things that lurk within the dusty pages of forgotten tomes, the second concerning visitors in the dark night from places even darker still. Stories featured in this episode “Mummer Man (https://www.reddit.com/r/nosleep/comments/1x4kk6/mummer_man/) ” by David Sharrock – more info about this author (http://www.simplyscarypodcast.com/authors/david-sharrock/) “Visitation” by Soren Narnia – more info about this author (http://www.simplyscarypodcast.com/authors/soren-narnia/) See full episode details, including the text of the featured stories, here:  http://www.simplyscarypodcast.com/series/horror-hill/s1e04-hh/ Podcast executive produced and directed by: Craig Groshek (http://simplyscarypodcast.com/staff/craig-groshek/) Podcast produced by: Craig Groshek (http://simplyscarypodcast.com/staff/craig-groshek/) Podcast hosted by: Jason Hill (https://www.simplyscarypodcast.com/performers/jason-hill/) Stories performed by: Jason Hill (https://www.simplyscarypodcast.com/performers/jason-hill/) Sound design by: Luke Hodgkinson (https://www.simplyscarypodcast.com/staff/luke-hodgkinson/) Script by: Craig Groshek (http://simplyscarypodcast.com/staff/craig-groshek/)  & Jason Hill (https://www.simplyscarypodcast.com/performers/jason-hill/) (http://simplyscarypodcast.com/staff/craig-groshek/) Original artwork by: Jason Hill (https://www.simplyscarypodcast.com/performers/jason-hill/) Audio program © 2018 Chilling Entertainment, LLC (http://chilling-entertainment.com/)  – All Rights Reserved. No reproduction or use of this content is permitted without the express written consent of Chilling Entertainment, LLC (http://chilling-entertainment.com/) . The copyrights for each story are held by the respective authors.

This episode we sit down with David Sharrock, the Producer of Battlestar Galactica Deadlock, the upcoming PC, XBOX and PS4 strategy game.  We also catch up on a few other projects he's working on.   Special shout out to David Sharrock, Black Lab Games and Slitherine for making this amazing game!

This is a quick HIGHLIGHTS episode.  For the FULL interview return to the Podcast page. This episode we sit down with David Sharrock, the Producer of Battlestar Galactica Deadlock, the upcoming PC, XBOX and PS4 strategy game.  We also catch up on a few other projects he's working on.   Special shout out to David Sharrock, Black Lab Games and Slitherine for making this amazing game!

It's episode 4 of Season 5. We have five tales this week featuring stories about compelling creatures, callous cuisine, and creepy communications. The full episode features the following stories. The free version features only the first two tales. "Scarecrow" written by Liam Hogan and read by David Ault. (Story starts at 00:04:40) "Mummer Man" written by David Sharrock and read by Peter Lewis. (Story starts at 00:18:35) "Long Pig" written by Jack Blakeslee and read by James Cleveland. (Story starts at 00:43:40) "My Name is Jennifer and I Live Alone" written by J. Chastel and read by Corinne Sanders. (Story starts at 01:01:10) "Flight 370" written by M.N. Malone and read by David Cummings. (Story starts at 01:11:45) Click here to discover more about Brandon Boone's music Click here to learn more about Liam Hogan Podcast produced by: David Cummings Music & Sound Design by: Brandon Boone & David Cummings "Scarecrow" illustration courtesy of Lukasz Godlewski This podcast is licensed under a Creative Commons License 2015.