Engineering Practices for Establishing Quality – PwP Episode 24

Challenges

  • Aligning engineering practices with quality goals in software development.
  • Ensuring consistency across teams in applying quality standards.
  • Balancing speed of delivery with maintaining high-quality outcomes.

Solutions

  • Adopting a comprehensive set of engineering practices focused on quality.
  • Providing clear guidance and training for consistent team implementation.
  • Regularly reviewing and refining practices to adapt to project needs.

Benefits

  • Improved software reliability and reduced defect rates.
  • Enhanced team efficiency with clear and consistent practices.
  • Stronger alignment with project and organizational quality objectives.

In this episode, Jeffrey discusses quality and the engineering practices that support it. Not at all a comprehensive list of possible practices, this list contains the practices that should be considered essential. Without these, any team would find it difficult to establish a high-quality piece of software. Establishing quality is one of the pillars of the Clear Measure Way.

Without first establishing quality, software developers end up spending time finding, diagnosing, and fixing bugs that pop up. This robs the team of much-needed capacity for new features and enhancements. Trying to add features without first establishing quality is like budgeting based on a credit card rather than income. There is no way the budget will balance, and it’s only a matter of time before the situation comes crumbling down.

  • An automated (private) build
  • Test-driven development
  • Onion architecture (dependency management & proper factoring)
  • Static analysis
  • Pull request checklists
  • Continuous integration
  • Automated full-system acceptance tests

Sample repository: https://github.com/ClearMeasureLabs/onion-architecture-dotnet-7-container-apps