Taking the risk out of software experimentation

"Learn strategies to reduce risk in software experimentation, break down "done" into manageable pieces, and discover how companies successfully balance innovation with quality and security."

Key takeaways
  • Emphasize the importance of reducing risk in software experimentation, and provide strategies for doing so.
  • Break down the concept of “done” into smaller, more manageable pieces, such as code quality, security, and unit test coverage.
  • Highlight the value of providing education and tooling to developers, rather than simply mandating certain practices.
  • Emphasize the importance of flexibility and autonomy in software development, particularly in small teams.
  • Provide examples of companies that have successfully used experimentation and risk-taking to drive innovation.
  • Discuss the importance of codifying decision-making processes and providing guidance for developers, rather than relying solely on informal agreements.
  • Emphasize the need to balance experimentation with quality and security concerns, and to ensure that all stakeholders are aligned and informed.
  • Highlight the benefits of using technology radar to guide technology choices, and of providing training and support to developers.
  • Discuss the importance of acknowledging and learning from mistakes, and of maintaining a positive and iterative approach to experimentation.
  • Summarize the importance of upskilling and up-training developers to ensure they have the skills needed to successfully experiment and take risks in software development.