Engineering Practices encompass a set of foundational techniques and methodologies that ensure the delivery of high-quality software in an Agile environment. These practices include clean code principles, automation, and test-first development, which collectively enhance the reliability and maintainability of software products. By embedding these practices into the development lifecycle, teams can achieve a predictable and sustainable flow of value to customers.
The significance of Engineering Practices lies in their ability to foster a culture of technical excellence and continuous improvement. They enable teams to respond swiftly to changing requirements while minimising technical debt, thus ensuring that the software remains adaptable and robust over time. This systemic approach not only enhances collaboration among cross-functional teams but also aligns technical efforts with business objectives, driving overall organisational agility.
Moreover, Engineering Practices support the implementation of Continuous Integration and Continuous Delivery (CI/CD) pipelines, which streamline the deployment process and reduce lead times. By prioritising quality at every stage of development, these practices empower teams to innovate confidently, ensuring that each release meets customer expectations and contributes to long-term success. The integration of these practices into daily workflows cultivates an environment where learning and experimentation thrive, ultimately leading to higher levels of team motivation and performance.
The strongest work on Engineering Practices — ranked by substance, not recency. How this is ranked
AI Agents Lie About Being Done
My agent reported every task complete when half the tests were missing. Call that a lie if you like. The engineering problem is that the …
Is Agile Really Just a Mindset?
Explores Agile as a disciplined system of delivery, emphasizing engineering excellence, CI/CD, observability, and system design over mindset …
Stop Building Silos. Start Building Systems
Explains how fragmented automation and tool silos harm software delivery, and advocates for unified engineering systems and platform …
How to Build for Business Resilience and Continuity
Learn key strategies for building business resilience and continuity, including observability, system decoupling, routine deployments, team …
Stop Hiding Behind Complexity and Start Delivering Continuously
Continuous delivery is achievable for any software, regardless of complexity. Success depends on investment in automation, quality, and …
Delivery is the only Measure of Progress in Scrum
Scrum teams must deliver working software to real users every Sprint; true progress is measured by delivery to production, not just by …
From Legacy Pain to Modern DevOps: My Proven Roadmap for Real Engineering Transformation
Transform legacy engineering with a proven, step-by-step approach, learn how to automate, adapt, and build a resilient, modern DevOps …
Engineering Excellence Isn’t Perfection: How Continuous Improvement and Fast Feedback Drive Real Agile and DevOps Success
Engineering excellence isn’t perfection, it’s continuous improvement, clean code, and fast feedback. Unlock true agility with modern Agile …
Resilience is Part of the Product, Not an Afterthought
Resilience must be designed into products from the start, not added later. Build systems to detect, contain, and recover from failures, …
AI Agents Lie About Being Done
My agent reported every task complete when half the tests were missing. Call that a lie if you like. The engineering problem is that the …
Is Agile Really Just a Mindset?
Explores Agile as a disciplined system of delivery, emphasizing engineering excellence, CI/CD, observability, and system design over mindset …
Stop Building Silos. Start Building Systems
Explains how fragmented automation and tool silos harm software delivery, and advocates for unified engineering systems and platform …
Are We Still Pretending Coding Was the Bottleneck?
AI exposes that coding was never the main bottleneck in software delivery; real constraints are in system flow, team practices, and …
The Definition of Done is a Commitment to Quality
Defines the Definition of Done in Scrum as a clear, shared standard for quality, ensuring increments are releasable, transparent, and …
Why Topic Branches Drive High-Quality Delivery
Explains how short-lived topic branches in source control improve software quality, enable modularity, speed up integration, and support …
Stop Writing Business Logic in Stored Procedures
Explains why business logic should not be written in stored procedures, highlighting testability, maintainability, scalability, and …
Resilience is Part of the Product, Not an Afterthought
Resilience must be designed into products from the start, not added later. Build systems to detect, contain, and recover from failures, …
How to Build for Business Resilience and Continuity
Learn key strategies for building business resilience and continuity, including observability, system decoupling, routine deployments, team …
From Legacy Pain to Modern DevOps: My Proven Roadmap for Real Engineering Transformation
Transform legacy engineering with a proven, step-by-step approach, learn how to automate, adapt, and build a resilient, modern DevOps …
Engineering Excellence Isn’t Perfection: How Continuous Improvement and Fast Feedback Drive Real Agile and DevOps Success
Engineering excellence isn’t perfection, it’s continuous improvement, clean code, and fast feedback. Unlock true agility with modern Agile …
Stop Testing Quality In: How Shifting Left Builds Better Software, Faster
Stop testing quality in, start building it in. Learn how shifting left, automation, and fast feedback loops drive engineering excellence in …
Why Big Bang Rewrites Fail: How Sustainable Change and Engineering Excellence Transform Legacy Systems
Ditch the Big Bang rewrite. Discover why sustainable, in-place change drives true engineering excellence and lasting transformation in your …
Still Deploying Manually? Why Automation Is the Bare Minimum for Modern Engineering (and Your Business Survival)
Still deploying manually? Discover why automation isn’t optional, protect your business, avoid disaster, and deliver value with modern …
Unlocking Engineering Excellence: How Azure DevOps Transforms Traceability, Transparency, and the Developer Experience
Unlock engineering excellence with Azure DevOps, boost traceability, transparency, and developer experience for agile, high-performing …
Why Your Definition of “Done” Is Holding Back Quality, Agility, and Trust, And How to Raise the Bar
Is your team’s “done” really done? Discover how a clear, objective definition of done boosts quality, agility, and trust in product …
Acceptance Criteria vs Definition of Done: Why Getting This Right Builds Trust and Delivers Quality Faster
Stop confusing acceptance criteria with definition of done, learn the crucial difference to boost quality, speed, and trust in your agile …
Stop Flying Blind: Why Telemetry Belongs in Your Definition of Done
Stop flying blind after release, learn why telemetry is vital to your Definition of Done and how real feedback drives better software, …
Building a Resilient Token Server: Engineering for Flow, Fault Tolerance, and Speed
Explains how to engineer a robust, fault-tolerant token counting server using FastAPI and PowerShell, covering error handling, retries, …
Convert Legacy Projects and ASP.NET MVC Apps to SDK-Style with Confidence
Learn how to upgrade legacy .NET and ASP.NET MVC projects to SDK-style for easier builds, modern tooling, and future readiness, including …
81 resources, newest first
AI Agents Lie About Being Done
My agent reported every task complete when half the tests were missing. Call that a lie if you like. The engineering problem is that the …
Engineering Excellence: The Quiet Discipline Behind Great Teams
A weekly one-hour mentorship for engineering teams to improve code quality, delivery predictability, and team culture through practical, …
Why Big Bang Rewrites Fail: How Sustainable Change and Engineering Excellence Transform Legacy Systems
Ditch the Big Bang rewrite. Discover why sustainable, in-place change drives true engineering excellence and lasting transformation in your …
Are We Still Pretending Coding Was the Bottleneck?
AI exposes that coding was never the main bottleneck in software delivery; real constraints are in system flow, team practices, and …
Stop Testing Quality In: How Shifting Left Builds Better Software, Faster
Stop testing quality in, start building it in. Learn how shifting left, automation, and fast feedback loops drive engineering excellence in …
Is Agile Really Just a Mindset?
Explores Agile as a disciplined system of delivery, emphasizing engineering excellence, CI/CD, observability, and system design over mindset …
Still Deploying Manually? Why Automation Is the Bare Minimum for Modern Engineering (and Your Business Survival)
Still deploying manually? Discover why automation isn’t optional, protect your business, avoid disaster, and deliver value with modern …
From Legacy Pain to Modern DevOps: My Proven Roadmap for Real Engineering Transformation
Transform legacy engineering with a proven, step-by-step approach, learn how to automate, adapt, and build a resilient, modern DevOps …
The Definition of Done is a Commitment to Quality
Defines the Definition of Done in Scrum as a clear, shared standard for quality, ensuring increments are releasable, transparent, and …
Unlocking Engineering Excellence: How Azure DevOps Transforms Traceability, Transparency, and the Developer Experience
Unlock engineering excellence with Azure DevOps, boost traceability, transparency, and developer experience for agile, high-performing …
Engineering Excellence Isn’t Perfection: How Continuous Improvement and Fast Feedback Drive Real Agile and DevOps Success
Engineering excellence isn’t perfection, it’s continuous improvement, clean code, and fast feedback. Unlock true agility with modern Agile …
Break organisational silos and stop tolerating bad branching models
Explains how technical leaders can break down organisational silos and enforce better branching, team structures, and architecture to …
Why Topic Branches Drive High-Quality Delivery
Explains how short-lived topic branches in source control improve software quality, enable modularity, speed up integration, and support …
Why Your Definition of “Done” Is Holding Back Quality, Agility, and Trust, And How to Raise the Bar
Is your team’s “done” really done? Discover how a clear, objective definition of done boosts quality, agility, and trust in product …
Stop Building Silos. Start Building Systems
Explains how fragmented automation and tool silos harm software delivery, and advocates for unified engineering systems and platform …
Acceptance Criteria vs Definition of Done: Why Getting This Right Builds Trust and Delivers Quality Faster
Stop confusing acceptance criteria with definition of done, learn the crucial difference to boost quality, speed, and trust in your agile …
Stop Writing Business Logic in Stored Procedures
Explains why business logic should not be written in stored procedures, highlighting testability, maintainability, scalability, and …
Stop Flying Blind: Why Telemetry Belongs in Your Definition of Done
Stop flying blind after release, learn why telemetry is vital to your Definition of Done and how real feedback drives better software, …
Resilience is Part of the Product, Not an Afterthought
Resilience must be designed into products from the start, not added later. Build systems to detect, contain, and recover from failures, …
Stop Firefighting Bugs: Why Shifting Left Saves Time, Money, and Your Reputation
Stop firefighting late-stage bugs, discover how shifting left saves time, money, and reputation by building quality in from the start. Learn …
DevOps: The Practical Path to Modernising Legacy Systems Without Starting Over
Unlock legacy system agility, discover how DevOps transforms slow, brittle tech into fast, scalable, and change-ready platforms without …
Evolving Engineering Practices to Improve Sprint Workflow in Scrum
Learn how evolving engineering practices like Feature Flags, TDD, and refactoring enable smoother Sprint workflows and reduce technical debt …
Convert Legacy Projects and ASP.NET MVC Apps to SDK-Style with Confidence
Learn how to upgrade legacy .NET and ASP.NET MVC projects to SDK-style for easier builds, modern tooling, and future readiness, including …
Stop Hoping for Quality: Why Automated Pipelines Are the Only Way to Deliver with Confidence
Stop relying on memory for quality. Discover why automated pipelines beat manual checks, and how embedding quality gates ensures trust, …
How to Build for Business Resilience and Continuity
Learn key strategies for building business resilience and continuity, including observability, system decoupling, routine deployments, team …
Scrum doesn’t stop you from optimising flow
Explains how Scrum supports continuous flow and agility by prioritising Sprint Goals, Done increments, CI/CD practices, and outcomes over …
Building a Resilient Token Server: Engineering for Flow, Fault Tolerance, and Speed
Explains how to engineer a robust, fault-tolerant token counting server using FastAPI and PowerShell, covering error handling, retries, …
There no such thing as "good" technical debt
Technical debt always harms productivity and system stability. Ignoring it leads to inefficiency and risk, making it essential to address …
Executives want predictability
Lack of a clear, enforced Definition of Done leads to hidden risks, unreliable forecasts, and eroded trust in delivery, undermining …
Your Evolving Definition of Done
Explains how the Definition of Done evolves in Scrum, aligning team practices with organisational standards to ensure consistent quality, …
Great Scrum Masters Need Technical, Business, and Organisational Mastery
Scrum Masters are most effective when they combine leadership skills with technical, business, and organisational mastery to support teams, …
Technical debt isn’t just messy code
Technical debt includes slow feedback, fragile systems, and manual processes that hinder progress. Addressing it early with automation and …
Velocity isn’t how many story points a team burns down
Velocity measures how quickly teams turn ideas into value, using build, test, deploy, and feedback times, not just story points, to track …
Scrum Masters are not glorified meeting schedulers
Scrum Masters must have technical and business expertise to guide teams, improve code quality, and drive real agility, not just schedule …
Engineering can fix technical debt, but leadership has to invest in it
Technical debt requires leadership investment to resolve; without support for automation and quality improvements, continuous delivery is …
Staging Environments Do Not Prevent Production Failures
Staging environments can’t fully replicate production, often leading to false confidence. Real risk reduction comes from safe, incremental …
Do More Staging Environments Really Reduce Deployment Risk
Adding more staging environments does not reduce deployment risk; true safety comes from automated testing, continuous integration, and …
Why Organisations Believe Their Software Is Too Complex for CD
Many organisations cite software complexity as a barrier to continuous delivery, but real obstacles are technical debt and lack of …
Stop Hiding Behind Complexity and Start Delivering Continuously
Continuous delivery is achievable for any software, regardless of complexity. Success depends on investment in automation, quality, and …
Rethinking Dev-Test-Staging-Production Pipelines for Safety
Explores why traditional Dev-Test-Staging-Production pipelines fall short and highlights audience-based deployment for safer, faster …
Why Engineering Teams Use Staging Environments for Risk Reduction
Explores how staging environments aim to reduce risk in software development, their hidden costs, and modern alternatives like feature flags …
There a common belief that rollback is the ultimate safety net
Rollback is often riskier than rolling forward, especially for stateful apps. Safer deployment relies on progressive delivery and …
Testing in Production Maximises Quality and Value
Explains how audience-based deployment and testing in production enable faster feedback, safer rollouts, and higher software quality by …
Branch promotion is a relic of slow, manual software delivery
Explains why modern software teams avoid branch promotion, using continuous integration, feature flags, and production-like testing to …
Stop Promoting Branches
Explains why promoting code through multiple branches slows delivery, increases risk, and suggests GitHub Flow or Release Flow as simpler, …
Delivery is the only Measure of Progress in Scrum
Scrum teams must deliver working software to real users every Sprint; true progress is measured by delivery to production, not just by …
Unlocking the Future of Software Development: Why Automation is Your Key to Success
Explores how automation boosts software development by reducing errors, speeding up deployments, and ensuring consistent, high-quality …
Embracing Automation: The Key to Transforming Your Development Process and Boosting Confidence
Explores how automation in testing, deployment, and validation streamlines development, reduces technical debt, and builds confidence for …
Unlocking Code Quality: The Transformative Power of Frequent Deployments
Explores how frequent code deployments improve code quality, reduce technical debt, enable faster feedback, and support iterative, …
Why Handoffs Are Killing Your Agility
Excessive handoffs in software development create delays, reduce quality, and harm team morale. Learn how eliminating handoffs boosts …