Send us a text

In 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

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

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.