Welcome to episode 24 of the Why Didn’t You Test That? Podcast. In this episode, Rich Jordan and Huw Price are joined by Marcel Mersie, Technical Lead - Test, and Executive Advisor to the Dutch Tax Administration. Together, they discuss how effective communication and collaboration are crucial for managing knowledge transfer.

Organisations face significant challenges when employees retire, as this often leads to knowledge leakage. To mitigate this, modelling and documentation can effectively capture and transfer critical knowledge before it’s lost. Effective communication and collaboration between teams are also crucial for seamless knowledge sharing and addressing these challenges systematically is essential.

In government organisations, implementing AI and modernising technology can be particularly difficult due to the fear of making large decisions and the complexity of legacy systems. Additionally, a lack of resources and skilled personnel often poses significant obstacles. Resistance to change and comfort with existing processes further hinder progress. Therefore, improving communication and collaboration between teams is vital for the successful implementation of new technologies.

Also, refactoring and addressing technical debt are important strategies to maintain efficiency and prevent future problems. Intelligent use of technology can enhance testing processes and overall organisational efficiency. At which point it's the visionary leaders who can drive essential changes for successful transformation.

By adopting a systematic approach and fostering an environment of open communication and collaboration, organisations can better manage knowledge transfer and technological advancement. This ensures that critical knowledge is retained, efficiency is maintained, and future challenges are proactively addressed.

The Curiosity Software Podcast, hosted by Rich Jordan, Huw Price and the Curiosity team! Together with guests, they share their insight and expertise in driving software design and development in test. Learn how you can improve your journey to quality software delivery, by considering how much do you really understand about your systems, and when things inevitably go wrong, why didn’t you test that?

Welcome to episode 23 of the Why Didn’t You Test That? Podcast. In this episode, Rich Jordan and Huw Price are joined by Adam Sandman, CEO & Founder of Inflectra. Together, they explore the continuous evolution of quality engineering, highlighting critical aspects like traceability, auditability, risk-based testing and regulatory compliance.

The conversation stars with Adam Sandman tracing the evolution of Inflectra, which he founded to offer affordable quality assurance and test management solutions. Continuing on, Adam highlights how merely investing in cybersecurity solutions is insufficient, and only robust software development practices and thorough testing can prevent breaches. While, compliance and traceability can play key roles in verifying security measures and demonstrating adherence to regulators and stakeholders.

Huw Price states that organisations should be mapping their entire software ecosystem, identifying critical failure points, and adopting best practices in software development and quality assurance in order to mitigate data breach risks. This kind of proactive approach should also involve regular audits and continuous monitoring to protect sensitive information.

Rounding out the discussion, Huw, Rich and Adam discuss the challenges of system integrations and migrations, with Huw highlighting the importance of understanding legacy systems and maintaining integrity during transitions.

The Curiosity Software Podcast, hosted by Rich Jordan, Huw Price and the Curiosity team! Together with guests, they share their insight and expertise in driving software design and development in test. Learn how you can improve your journey to quality software delivery, by considering how much do you really understand about your systems, and when things inevitably go wrong, why didn’t you test that?

The "Why Don't You Test That" podcast, hosted by James Walker and Ben Riley from Curiosity Software talk about the importance of decoding the software development life cycle to foster a holistic approach to quality.

In the concept of core inner loop developer activity and essential outer loop organisational processes, this helps address root causes of inefficiencies rather than relies quick fixes. Quick fixes like automation can exacerbate issues if not coupled with a deep understanding of root causes. Also as the Curiosity team are in preparations for a marathon, they use this to shed light on the importance of early preparation in software development.

James Walker refers back to his well received LinkedIn blog post about dissecting the SDLC related to requirements not being good enough. The team also touches on why automation recieves a bad rap, that it’s better to make early actions over reactive measures to shore up quality and to avoid silver bullet fixes.

Referring to their training for a marathon they talk about the need to overcoming challenges and painpoints, and liken this to success in software development. Assuring quality is not about speed just to look productive but about laying the foundation for long-term success. Committing to the challenge in the software development journey is about aligning your core developer activity with essential organisations processes.

The Curiosity Software Podcast featuring Rich Jordan, Huw Price, James Walker and Ben Riley! Get insight and expertise into what’s driving software design and development. Learn how you can improve your journey to quality software delivery, by considering how much do you really understand about your systems, and when things inevitably go wrong, why didn’t you test that? Spotify | YouTube | iTunes | Google Podcasts | Amazon Music | Deezer | RSS Feed

Welcome to episode 21 of the Why Didn’t You Test That? Podcast. In this episode, the Curiosity team, Ben Riley, Rich Jordan, and Mantas Dvareckas, discuss the value of different methods of testing, community-driven quality and continuous learning.

Ben Riley starts the conversation on the “early access” model which many game developers have started to increasingly use, and how it can help improve the quality of software. Early access allows developers to gather feedback, identify issues early and reduce costly post-release fixes, by getting the end user in front of the product as early as possible. Mantas Dvareckas highlights how getting in front of your end user, gathering feedback, and providing software that they actually want, is key to success.

As someone new to the software testing and quality space, Mantas shares some of his insights on how skills from other fields, like marketing, can be transferable. These transferable skills can bring fresh perspectives and innovative approaches to testing, enhancing the overall quality. The recommendation to new testers is to look for existing best practices and resources. This continuous learning helps testers stay updated with the latest techniques, improving their effectiveness.

The conversation rounds out to discuss various methods of testing software, comparing the structured approaches in traditional industries with the more community-driven methods in gaming. Community-driven feedback ensures the software meets user expectations and improves satisfaction. Mantas mentions Tekken 8, and how he participated in their alpha and beta testing, which asked players worldwide to provide feedback by playing the game and filling in surveys on their experience, which helped refine the product and improve quality.

The team concludes with encouragement for listeners to be curious and proactive in their testing approaches, while not forgetting to apply continuous development principles to our own learning. Oh, and is a muffin a cake?

The Curiosity Software Podcast featuring Rich Jordan, Huw Price, James Walker and colleagues! Get insight and expertise into what’s driving software design and development. Learn how you can improve your journey to quality software delivery, by considering how much do you really understand about your systems, and when things inevitably go wrong, why didn’t you test that? Spotify | YouTube | iTunes | Google Podcasts | Amazon Music | Deezer | RSS Feed

Welcome to episode 20 of the Why Didn’t You Test That? Podcast. In this episode, Curiosity Software's Rich Jordan and James Walker, are joined by Tom Riglar, Co-Founder & CEO at Moropo. Together, they discuss the quality, automation and artificial intelligence challenges enterprises are facing, and their potential solutions.

To kick off the conversation, our guest, Tom Riglar, highlights one major pain point, the complexity of mobile app testing and automation. Tom and James share their frustrations with tools like Appium and UI Automation, which often lead to high complexity and frequent failures. To address this, they advocate for a more streamlined and user-friendly approach to mobile automation tools. Additionally, they stress the importance of having clear requirements, good test cases, and robust regression test packs.

Rich Jordan points out another significant pain point is organizational resistance to change, with many teams reluctant to adopt new testing methodologies. The suggested solution involves fostering a culture that embraces change and emphasizes the importance of quality assurance from the start. This includes educating teams on the benefits of early quality activities, such as static code checking and snapshot testing, which can catch issues earlier in the development cycle.

Our hosts also discuss the evolving role of developers, who are increasingly required to balance coding with quality assurance tasks. The proposed solution is to redefine the developers' role to focus more on orchestrating quality activities. This shift can be facilitated by hiring quality engineers who specialize in complex testing tasks, allowing developers to concentrate on delivering business value.

Lastly, James highlights the impact of AI on software quality, with the fear that the focus on productivity might compromise standards. To mitigate this, James and Tom propose a balanced approach that incorporates AI tools without neglecting essential quality assurance, ensuring that software meets high standards of reliability and performance.

The Curiosity Software Podcast featuring Rich Jordan, Huw Price, James Walker and colleagues! Get insight and expertise into what’s driving software design and development. Learn how you can improve your journey to quality software delivery, by considering how much do you really understand about your systems, and when things inevitably go wrong, why didn’t you test that? Spotify | YouTube | iTunes | Google Podcasts | Amazon Music | Deezer | RSS Feed

Welcome to episode 19 of the Why Didn’t You Test That? podcast. In this episode, Curiosity Software's Rich Jordan and Huw Price are joined by John Matthews, a leading purchasing consultant and director at Arish Consulting Together they discuss the impact of quality, speed, and cost in software delivery and the organisational challenges of IT procurement.

John Matthews opens the conversation with a focus on the use of open-ended questions in RFP processes, and how they're a great way for organisations to consider smaller innovative vendors who provide more focused solutions than the behemoth-sized providers.

Matthews further emphasizes the need for procurement to add value and be influential, while also recognizing that they are not in control of the budget. Matthews also highlights the importance of identifying strategic stakeholders, high impact stakeholders, and core stakeholders in IT projects.

One big issue is that people think procurement controls decisions. Matthews says that's not quite right. Instead, procurement should influence decisions positively by showing its value. When this isn't understood, it can slow down projects and make them lower quality.

Another problem is identifying and talking to the important people who make big decisions. Huw Price says it's crucial to understand their needs clearly and talk to them in simple terms. This helps everyone be on the same page and work towards the same goals.

Huw continues by describing the vague requests for IT services that often cause delays and extra costs. Matthews suggests having clear talks about all the costs involved from the start. This way, everyone knows what to expect and can plan better.

Additionally, performance-based fees are proposed as an alternative payment model to incentivize timely and efficient project delivery. This approach shifts the focus from time and materials to outcomes, encouraging vendors to prioritize performance and value creation.

To sum up, by fixing these issues through better communication, talking to the right people, and trying new buying methods, companies can make buying IT services for software smoother and more effective.

The Curiosity Software Podcast featuring Rich Jordan, Huw Price, James Walker and colleagues! Get insight and expertise into what’s driving software design and development. Learn how you can improve your journey to quality software delivery, by considering how much do you really understand about your systems, and when things inevitably go wrong, why didn’t you test that? Spotify | YouTube | iTunes | Google Podcasts | Amazon Music | Deezer | RSS Feed

Welcome to episode 18 of the Why Didn’t You Test That? podcast. In this episode, Curiosity Software's Rich Jordan and CEO James Walker are joined by Chris Harbert, an industry executive and host of the Developers Who Test but also founder and CEO of Testery. Together they discuss the organizational challenges in defining quality.

So, quality is essential in software delivery. But, who actually owns quality? if that’s a reasonable question to ask. Collaboration between developers and testers is crucial for achieving quality and a mutual respect and involvement in bug fixes can bridge the gap between the two roles and improve overall product quality. But can this lead to the ‘bystander effect’? in which no one seems to be responsible for quality.

Increasingly due to legacy systems organizations need to address their technical debt and complexity to improve quality, so saving a clear plan, architectural overview, and leveraging test automation can help untangle legacy systems and pave the way for better quality practices. This can enhance testability and reduce toil during sprints.

And what of metrics which play a crucial role in measuring quality? Key metrics include bug discovery rates, test coverage, customer satisfaction scores, and support team efforts. These metrics provide insights into the effectiveness of quality initiatives and highlight areas for improvement.

Finally, as with any episode of Why Didn’t You Test That? we consider AIs impact your testing effort. Generative AI and non-deterministic behaviour may complicate testing, so requiring skilled testers is paramount to ensure you’re leveraging in line with organizational quality objectives in meeting customer expectations, but also providing a good user experience.

The Curiosity Software Podcast featuring Rich Jordan, Huw Price, James Walker and colleagues! Get insight and expertise into what’s driving software design and development. Learn how you can improve your journey to quality software delivery, by considering how much do you really understand about your systems, and when things inevitably go wrong, why didn’t you test that? Spotify | YouTube | iTunes | Google Podcasts | Amazon Music | Deezer | RSS Feed

Welcome to episode 17 of the Why Didn’t You Test That? podcast. In this episode, Curiosity Software's Rich Jordan and CEO James Walker are joined by Colin Hammond, CEO of ScopeMaster who discusses the importance of how requirements analysis and sizing lends well to predicting project schedules and assessment of scope in software development.

The neglect of skills and training in requirements elicitation and documentation leads to poor requirements quality and project issues. Hammond emphasises how sizing software using functional points allows for accurate estimation, better resource planning, and early identification of project issues. This early detection is crucial avoid budget overruns or ultimately to prevent a project from failing.

Agile development should not neglect the importance of high-level requirements and architecture to avoid costly changes later. Functional sizing provides a reliable predictor of effort, aiding in project estimation and scope management.

AI advancements can automate requirements analysis, generate test scenarios, and offer suggestions, but human supervision and context are essential. Organizations are starting to challenge the ownership of quality, recognizing the need for a holistic approach beyond testing.

The shift towards a quality engineering role and new quality-focused positions shows an increasing awareness of requirements and quality in software development.

The Curiosity Software Podcast featuring Rich Jordan, Huw Price, James Walker and colleagues! Get insight and expertise into what’s driving software design and development. Learn how you can improve your journey to quality software delivery, by considering how much do you really understand about your systems, and when things inevitably go wrong, why didn’t you test that? Spotify | YouTube | iTunes | Google Podcasts | Amazon Music | Deezer | RSS Feed