https://engineering-leadership.hinshelwood.com/tags/technical-excellence/ Recent content in Technical Excellence on Engineering Leadership in AI & Software Hugo en Tue, 16 Jun 2026 17:40:35 +0000 https://engineering-leadership.hinshelwood.com/articles/stop-building-silos-start-building-systems/ Mon, 07 Jul 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/stop-building-silos-start-building-systems/ Fragmented automation and tool silos slow delivery, increase risk, and create confusion, while a unified engineering system enables speed, safety, and clarity. Standardising on a single platform like Azure Pipelines, with shared processes and guardrails, empowers teams to focus on delivering value instead of managing complexity. To scale effectively, consolidate your toolchain, define clear boundaries, and invest in platform engineering so teams can work autonomously within a reliable system. https://engineering-leadership.hinshelwood.com/articles/is-agile-really-just-a-mindset/ Mon, 11 Aug 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/is-agile-really-just-a-mindset/ Agile is not just a mindset or set of behaviours; it is a disciplined system of work rooted in engineering excellence, technical leadership, and empirical delivery. True agility requires robust engineering practices like CI/CD, automated testing, and observability, not just ceremonies or coaching. To achieve real Agile outcomes, focus on building systems that enable frequent, reliable delivery and hold both teams and leadership accountable for technical and organisational change. https://engineering-leadership.hinshelwood.com/articles/why-topic-branches-drive-high-quality-delivery/ Mon, 14 Jul 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/why-topic-branches-drive-high-quality-delivery/ Short-lived topic branches help teams deliver high-quality software by making integration easier, reducing merge conflicts, and supporting modular, continuous delivery. Adopting models like GitHub Flow or Release Flow keeps work focused and feedback fast, while long-lived branches increase risk and slow down delivery. Development managers should enforce small, short-lived branches and regularly review branching strategies to maintain flow, agility, and quality. https://engineering-leadership.hinshelwood.com/videos/why-outsourcing-devops-fails-and-how-real-engineering-excellence-starts-with-your-team/ Mon, 15 Sep 2025 06:30:00 +0000 https://engineering-leadership.hinshelwood.com/videos/why-outsourcing-devops-fails-and-how-real-engineering-excellence-starts-with-your-team/ Outsourcing DevOps often leads to vendor lock-in, legacy systems, and teams that cannot maintain or evolve their own tools. Real engineering excellence comes from building internal capability through partnership, where experts mentor and guide your team to modernize workflows and systems themselves. Invest in developing your engineers’ skills and mindset so your organization can achieve sustainable progress and avoid costly dependencies. https://engineering-leadership.hinshelwood.com/articles/the-definition-of-done-is-a-commitment-to-quality/ Mon, 28 Jul 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/the-definition-of-done-is-a-commitment-to-quality/ A clear, shared Definition of Done is essential for delivering quality, releasable software in Scrum and aligns teams on what “complete” means. It ensures transparency, predictability, and accountability, protects your product’s reputation, and must be created, automated, and regularly improved by all teams working on a product. Development managers should prioritise running DoD workshops, making standards visible, automating checks, and reviewing the DoD every sprint to maintain quality and reduce risk. https://engineering-leadership.hinshelwood.com/articles/stop-hiding-behind-complexity-and-start-delivering-continuously/ Mon, 24 Feb 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/stop-hiding-behind-complexity-and-start-delivering-continuously/ Complexity is not a valid reason to avoid continuous delivery; organisations like Azure DevOps and Starbucks have proven that even large, complex systems can achieve frequent, reliable releases with the right investment in automation, process improvement, and culture change. Key actions include automating everything, adopting trunk-based development, using feature flags, shifting quality left, and iterating on pain points. Development managers should focus on measuring and improving flow metrics and value delivery, prioritising organisational commitment to overcome resistance and realise the benefits of continuous delivery. https://engineering-leadership.hinshelwood.com/signals/scrum-masters-are-not-glorified-meeting-schedulers/ Sun, 09 Mar 2025 16:30:01 +0000 https://engineering-leadership.hinshelwood.com/signals/scrum-masters-are-not-glorified-meeting-schedulers/ Scrum Masters must have strong technical and business skills, including coding knowledge and expertise in modern engineering practices, to effectively lead software teams. They should be able to challenge teams, identify technical debt, and promote quality, not just schedule meetings. Ensure your Scrum Master can engage with developers on technical topics to achieve real agility. https://engineering-leadership.hinshelwood.com/signals/engineering-can-fix-technical-debt-but-leadership-has-to-invest-in-it/ Mon, 03 Mar 2025 16:30:35 +0000 https://engineering-leadership.hinshelwood.com/signals/engineering-can-fix-technical-debt-but-leadership-has-to-invest-in-it/ Fixing technical debt requires leadership investment, not just harder work from engineers. Success comes from funding automation, better testing, and empowering teams to address issues directly. If continuous delivery is not happening, leaders should reconsider their priorities and support the necessary improvements. https://engineering-leadership.hinshelwood.com/articles/there-is-no-such-thing-as-a-junior-scrum-master/ Mon, 17 Feb 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/there-is-no-such-thing-as-a-junior-scrum-master/ The Scrum Master role requires deep technical, business, and organisational expertise and should not be treated as an entry-level or “junior” position. The most effective Scrum Masters emerge from within high-performing teams, having already demonstrated real-world competence and leadership, not just certification. To ensure team effectiveness and delivery, select Scrum Masters based on proven experience and peer respect, not on cost savings or minimal qualifications. https://engineering-leadership.hinshelwood.com/videos/from-legacy-pain-to-modern-devops-my-proven-roadmap-for-real-engineering-transformation/ Mon, 04 Aug 2025 07:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/from-legacy-pain-to-modern-devops-my-proven-roadmap-for-real-engineering-transformation/ Transforming legacy engineering to modern DevOps requires a flexible, evidence-based approach focused on testing hypotheses, starting with the most challenging products, and automating every step from code commit to production. Involve all stakeholders to define essential requirements, automate approvals and deployments, and use phased rollouts with real-time feedback to minimize risk. Focus on one improvement at a time, build a culture of continuous learning, and scale successful practices across the organization. https://engineering-leadership.hinshelwood.com/articles/testing-in-production-maximises-quality-and-value/ Thu, 13 Feb 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/testing-in-production-maximises-quality-and-value/ Testing in production using audience-based deployment enables faster feedback, safer incremental releases, and better alignment with real user needs compared to traditional Dev-Test-Staging pipelines. Microsoft’s shift to this model, driven by feature flags, progressive rollouts, and real-time monitoring, has improved quality and innovation while reducing risk and overhead. Development managers should consider moving away from environment-based branching and invest in automation, observability, and team upskilling to maximise value and responsiveness. https://engineering-leadership.hinshelwood.com/articles/definition-of-done-objective-vs-subjective/ Fri, 03 Jan 2025 00:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/definition-of-done-objective-vs-subjective/ The Definition of Done (DoD) in Scrum is an objective, measurable checklist that sets the minimum quality standard for every product increment, distinct from the more subjective Product and Sprint Goals. Teams should ensure their DoD is clear, comprehensive, regularly reviewed, and as automated as possible, avoiding subjective approval steps. Development managers should treat the DoD as a non-negotiable baseline for quality, not a ceiling, and keep it updated to reflect evolving standards and business needs. https://engineering-leadership.hinshelwood.com/articles/are-we-still-pretending-coding-was-the-bottleneck/ Mon, 01 Sep 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/are-we-still-pretending-coding-was-the-bottleneck/ AI writing code is not the real game-changer; coding was never the main bottleneck in software delivery. The real constraints are in poor system design, handoffs, unclear requirements, and lack of built-in quality, which AI will only make more visible. To benefit from AI, focus on improving flow, building quality in from the start, and making teams accountable for outcomes rather than output. https://engineering-leadership.hinshelwood.com/videos/engineering-excellence-isn-t-perfection-how-continuous-improvement-and-fast-feedback-drive-real-agile-and-devops-success/ Mon, 21 Jul 2025 06:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/engineering-excellence-isn-t-perfection-how-continuous-improvement-and-fast-feedback-drive-real-agile-and-devops-success/ Engineering excellence is not about achieving perfection or creating exhaustive plans, but about building systems that continuously adapt and improve through fast feedback and incremental change. Key practices include clean code, observability, automated testing, and CI/CD, which together enable teams to deliver high-quality software quickly and respond to real-world needs. Development managers should focus on removing manual bottlenecks and technical debt to shorten feedback loops, as this is the foundation of true Agile and DevOps success. https://engineering-leadership.hinshelwood.com/articles/resilience-is-part-of-the-product-not-an-afterthought/ Mon, 09 Jun 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/resilience-is-part-of-the-product-not-an-afterthought/ Resilience must be designed into your product from the start, not added later or left to individual heroics. Building resilience means engineering for failure containment, rapid recovery, and continuous improvement, using tools like telemetry, feature flags, and safe deployment practices. Make resilience a core part of your development process and culture, treating it as a critical feature to avoid costly outages and business risks. https://engineering-leadership.hinshelwood.com/videos/stop-testing-quality-in-how-shifting-left-builds-better-software-faster/ Mon, 18 Aug 2025 06:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/stop-testing-quality-in-how-shifting-left-builds-better-software-faster/ Relying on testers to catch issues late in the process increases costs, slows feedback, and undermines product trust; instead, quality should be built in from the start by moving tests and feedback as close to the engineer as possible. Key practices include automating builds and tests, adopting continuous integration and delivery, using test-driven development, and incrementally improving code quality. Development managers should focus on empowering engineers to own quality, relentlessly shortening feedback loops, and making incremental improvements to achieve faster, more reliable releases. https://engineering-leadership.hinshelwood.com/signals/do-more-staging-environments-really-reduce-deployment-risk/ Wed, 26 Feb 2025 16:30:31 +0000 https://engineering-leadership.hinshelwood.com/signals/do-more-staging-environments-really-reduce-deployment-risk/ Adding more staging environments does not actually reduce deployment risk; it only delays issue discovery and creates a false sense of security. Real risk reduction comes from investing in automated testing, continuous integration, and quality practices built into the development process. To minimize downtime and deployment risk, focus on modern engineering practices rather than adding more pre-production gates. https://engineering-leadership.hinshelwood.com/videos/the-power-of-technical-excellence-in-agile-development/ Thu, 27 Jun 2024 06:45:00 +0000 https://engineering-leadership.hinshelwood.com/videos/the-power-of-technical-excellence-in-agile-development/ Technical excellence is essential for delivering a usable, high-quality product at the end of every iteration, which reduces risk and enables faster, more valuable feature delivery. The Azure DevOps team at Microsoft dramatically increased their output by focusing on paying down technical debt and establishing a strong Definition of Done. Development managers should prioritize technical excellence, avoid sacrificing quality for speed, and ensure their teams have a clear Definition of Done to maximize value and stay competitive. https://engineering-leadership.hinshelwood.com/videos/why-your-definition-of-done-is-holding-back-quality-agility-and-trust-and-how-to-raise-the-bar/ Wed, 09 Jul 2025 06:45:00 +0000 https://engineering-leadership.hinshelwood.com/videos/why-your-definition-of-done-is-holding-back-quality-agility-and-trust-and-how-to-raise-the-bar/ Treating “done” as a vague checklist limits quality, agility, and stakeholder trust; instead, teams should define “done” as delivering thoroughly tested, production-ready, and valuable increments that work in the real world. Clear, objective standards for “done” reduce defects, speed up learning, and build confidence with stakeholders. Development managers should work with their teams to set and uphold a robust definition of “done” to drive better outcomes and long-term success. https://engineering-leadership.hinshelwood.com/articles/how-to-build-for-business-resilience-and-continuity/ Mon, 26 May 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/how-to-build-for-business-resilience-and-continuity/ Building business resilience requires intentional design, strong observability, and aggressive decoupling so failures do not cascade across systems. Empower teams to act quickly, treat deployments as routine, and design for fast recovery using practices like chaos engineering and circuit breakers. Make resilience a core part of your culture and operations, not a one-time project, and use real metrics to guide continuous improvement. https://engineering-leadership.hinshelwood.com/videos/building-a-culture-of-quality/ Fri, 22 Nov 2024 07:00:08 +0000 https://engineering-leadership.hinshelwood.com/videos/building-a-culture-of-quality/ A culture of quality cannot be built by one person; it requires everyone in the organization to demonstrate and model technical excellence and leadership. Focusing only on revenue, as seen in Boeing’s decline, undermines quality and can lead to dangerous outcomes, while a strong culture of quality leads to better, safer products. Development managers should prioritize building and reinforcing engineering excellence and technical leadership across teams, using frameworks and tools as enablers rather than solutions. https://engineering-leadership.hinshelwood.com/videos/how-to-evolve-your-definition-of-done-start-small-grow-smarter-and-build-lasting-momentum/ Wed, 25 Jun 2025 06:45:00 +0000 https://engineering-leadership.hinshelwood.com/videos/how-to-evolve-your-definition-of-done-start-small-grow-smarter-and-build-lasting-momentum/ You do not need a perfect Definition of Done from the start; begin with what is usable, then gradually add quality, testing, and compliance standards as your team grows more capable. Trying to do everything at once can stall progress, so evolve your standards step by step to build momentum and resilience. Focus on essential requirements now and raise the bar as your team is ready. https://engineering-leadership.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/ Sun, 25 May 2025 15:30:23 +0100 https://engineering-leadership.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/ Scrum allows you to optimise workflow as long as you maintain accountability through a Sprint Goal and a Done Increment. If your team already delivers quality software continuously and meets these standards, you do not need to force all work to finish within strict Sprint timelines. Focus on outcomes and professionalism rather than rigid rules, and let work flow naturally if your processes support it. https://engineering-leadership.hinshelwood.com/signals/technical-debt-isn-t-just-messy-code/ Thu, 13 Mar 2025 16:30:02 +0000 https://engineering-leadership.hinshelwood.com/signals/technical-debt-isn-t-just-messy-code/ Technical debt goes beyond messy code and includes slow feedback, fragile systems, and manual processes that hinder progress. It results from choices like delaying refactoring or skipping automation, and it compounds over time. To avoid bigger problems later, prioritize paying down technical debt now by automating, testing early, and streamlining delivery pipelines. https://engineering-leadership.hinshelwood.com/videos/transforming-chaos-into-clarity-how-optimising-systems-fuels-engineering-excellence/ Mon, 16 Dec 2024 06:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/transforming-chaos-into-clarity-how-optimising-systems-fuels-engineering-excellence/ Unmanaged chaos in software delivery leads to poor quality, technical debt, and wasted resources. Optimising systems and processes, as shown by Microsoft’s transformation of their DevOps team, enables faster delivery, higher productivity, and better products by reducing technical debt and improving testing practices. Development managers should prioritise system optimisation and technical leadership to empower teams and drive sustainable engineering excellence. https://engineering-leadership.hinshelwood.com/articles/a-better-way-than-staggered-iterations-for-delivery/ Thu, 10 Dec 2020 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/a-better-way-than-staggered-iterations-for-delivery/ Staggered iterations slow feedback, increase technical debt, and reduce software quality, making delivery less agile and more expensive. Instead, form cross-functional teams that deliver working software every iteration, integrate all required work including testing into each sprint, and automate as much as possible. Shift away from staged handoffs to continuous, team-owned delivery to improve value and quality. https://engineering-leadership.hinshelwood.com/videos/still-deploying-manually-why-automation-is-the-bare-minimum-for-modern-engineering-and-your-business-survival/ Mon, 11 Aug 2025 07:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/still-deploying-manually-why-automation-is-the-bare-minimum-for-modern-engineering-and-your-business-survival/ Manual deployments put your business at serious risk due to inevitable human error, as shown by real-world failures that have caused massive financial losses. Automation of builds, deployments, tests, and quality checks is now the minimum standard for professional software development, enabling faster, safer, and more reliable releases. To protect your business and deliver value consistently, eliminate manual steps and automate every part of your delivery pipeline as soon as possible. https://engineering-leadership.hinshelwood.com/videos/the-hidden-costs-of-poor-quality-code-and-how-to-turn-it-into-a-superpower/ Tue, 19 Nov 2024 09:58:28 +0000 https://engineering-leadership.hinshelwood.com/videos/the-hidden-costs-of-poor-quality-code-and-how-to-turn-it-into-a-superpower/ Poor-quality code leads to escalating costs, lost productivity, and damage to team morale and brand reputation, while also causing missed opportunities for innovation. Simplifying branching, limiting supported versions, and investing in engineering excellence and security can dramatically boost productivity and customer satisfaction. Development managers should prioritize code quality improvements now to unlock greater efficiency and long-term organizational success. https://engineering-leadership.hinshelwood.com/videos/stop-hoping-for-quality-why-automated-pipelines-are-the-only-way-to-deliver-with-confidence/ Wed, 28 May 2025 07:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/stop-hoping-for-quality-why-automated-pipelines-are-the-only-way-to-deliver-with-confidence/ Relying on manual quality checks leads to inconsistency and risk because people inevitably forget or make mistakes, no matter their intentions. Embedding automated quality gates like security scans, static analysis, linting, and automated tests directly into your delivery pipeline ensures that nothing is missed and quality becomes the default. To deliver reliably and protect your team and customers, make all critical checks automatic and non-optional in your pipeline. https://engineering-leadership.hinshelwood.com/signals/why-organisations-believe-their-software-is-too-complex-for-cd/ Mon, 24 Feb 2025 10:51:31 +0000 https://engineering-leadership.hinshelwood.com/signals/why-organisations-believe-their-software-is-too-complex-for-cd/ Software complexity is often used as an excuse to avoid continuous delivery, but real-world examples like Microsoft’s Azure DevOps team show that even large, complex systems can achieve frequent releases by investing in quality practices and addressing technical debt. The main barrier is not complexity but the willingness to make necessary improvements. Development managers should focus on fixing underlying issues rather than blaming complexity. https://engineering-leadership.hinshelwood.com/videos/nkd-agility-your-partner-in-developing-engineering-excellence/ Sat, 23 Nov 2024 07:00:12 +0000 https://engineering-leadership.hinshelwood.com/videos/nkd-agility-your-partner-in-developing-engineering-excellence/ NKD Agility helps organizations build engineering excellence and technical leadership by shifting key practices like testing, security, and architecture closer to development teams and actively addressing technical debt. This approach reduces the high costs of poor-quality products and supports a culture of quality and value creation. Development managers looking to improve software quality and team capability can partner with NKD Agility for modern engineering practices and support. https://engineering-leadership.hinshelwood.com/articles/avoid-the-pick-n-mix-branching-anti-pattern/ Mon, 14 Jul 2014 15:35:35 +0000 https://engineering-leadership.hinshelwood.com/articles/avoid-the-pick-n-mix-branching-anti-pattern/ Explains the risks of the pick-n-mix branching anti-pattern in source control, its impact on code quality, and recommends feature branching and toggles for stability. https://engineering-leadership.hinshelwood.com/videos/maximising-deployment-frequency-the-key-to-faster-time-to-market-and-business-success/ Wed, 22 Jan 2025 14:16:54 +0000 https://engineering-leadership.hinshelwood.com/videos/maximising-deployment-frequency-the-key-to-faster-time-to-market-and-business-success/ Increasing deployment frequency is key to reducing time to market and driving business success, but it only adds value if deployments reach production and enable fast learning from real user feedback. Focus on stable environments, end-to-end pipeline analysis, and shortening the time to learn so you can iterate quickly and align with business needs. Prioritise building trust with stakeholders, collecting actionable data, and enabling continuous delivery to respond rapidly to opportunities and deliver the right features at the right time. https://engineering-leadership.hinshelwood.com/signals/evolving-engineering-practices-to-improve-sprint-workflow-in-scrum/ Thu, 29 May 2025 15:30:45 +0100 https://engineering-leadership.hinshelwood.com/signals/evolving-engineering-practices-to-improve-sprint-workflow-in-scrum/ To improve sprint workflow in Scrum without sacrificing quality, teams need to adopt practices like Feature Flags, TDD, and regular refactoring to enable safe, continuous flow of work. These practices help ship incomplete features safely, ensure code reliability, and maintain system health. Development managers should prioritize evolving engineering practices and consider Continuous Delivery essential for sustainable progress. https://engineering-leadership.hinshelwood.com/articles/getting-started-with-a-modern-source-control-system-and-devops/ Mon, 13 Jul 2020 18:41:59 +0000 https://engineering-leadership.hinshelwood.com/articles/getting-started-with-a-modern-source-control-system-and-devops/ Modern source control systems are essential for managing not just code but the entire software development lifecycle, supporting DevOps practices and providing critical metadata for process visibility. Key practices include always using source control, automating release pipelines, minimizing branches with feature flags, moving to Git, and ensuring regular feedback and testing. To stay competitive, development managers should ensure all code is in source control, automate releases, and adopt integrated platforms like VSTS that support any technology and enable continuous delivery. https://engineering-leadership.hinshelwood.com/articles/the-sprint-is-a-container-for-planning-and-not-necessarily-for-delivery/ Tue, 29 Nov 2011 04:36:22 +0000 https://engineering-leadership.hinshelwood.com/articles/the-sprint-is-a-container-for-planning-and-not-necessarily-for-delivery/ Explains how Scrum Sprints are primarily for planning, not fixed delivery, and discusses aligning delivery schedules, continuous deployment, and improving software quality. https://engineering-leadership.hinshelwood.com/videos/shifting-left-quality-from-the-start/ Wed, 20 Nov 2024 07:00:26 +0000 https://engineering-leadership.hinshelwood.com/videos/shifting-left-quality-from-the-start/ Automating code reviews and quality checks as early as possible in the development process reduces defects and speeds up delivery by minimizing manual bottlenecks. Manual code reviews should be a safety net, not the primary method for ensuring quality, and no code should reach the main branch without passing automated checks. Development managers should invest in robust automation for code validation to improve quality and accelerate value delivery. https://engineering-leadership.hinshelwood.com/articles/stop-writing-business-logic-in-stored-procedures/ Mon, 23 Jun 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/stop-writing-business-logic-in-stored-procedures/ Stop adding business logic to stored procedures and refactor existing logic into application code as you make changes, rather than rewriting everything at once. Keeping business logic in stored procedures makes testing, deployment, version control, scalability, and maintainability much harder, increasing technical debt and risk. Adopt a gradual, pay-as-you-go approach to modernize your codebase, improve engineering practices, and enable faster, more reliable delivery. https://engineering-leadership.hinshelwood.com/videos/technical-debt-management-for-long-term-quality/ Thu, 21 Nov 2024 07:00:11 +0000 https://engineering-leadership.hinshelwood.com/videos/technical-debt-management-for-long-term-quality/ Technical debt results from choosing quick fixes over long-term solutions and can be both intentional and unintentional, eventually limiting your team’s ability to deliver value. The Azure DevOps team dramatically increased their feature delivery by prioritizing and paying down technical debt, showing that addressing it leads to faster delivery and higher product quality. Development managers should actively identify and pay back technical debt to maximize long-term productivity and value. https://engineering-leadership.hinshelwood.com/videos/embrace-simplicity-how-to-transform-complexity-into-continuous-delivery-success/ Thu, 27 Feb 2025 07:00:10 +0000 https://engineering-leadership.hinshelwood.com/videos/embrace-simplicity-how-to-transform-complexity-into-continuous-delivery-success/ Complexity is not a valid excuse for avoiding continuous delivery; with organisational commitment and a willingness to modernise, even legacy systems can be transformed for faster, more reliable releases. Key steps include honestly assessing your product, investing in ongoing improvement, and addressing technical debt rather than ignoring warning signs. Leaders should prioritise resources and foster a culture that values continuous improvement to avoid costly failures and achieve lasting delivery success. https://engineering-leadership.hinshelwood.com/engineering-notes/building-a-resilient-token-server-engineering-for-flow-fault-tolerance-and-speed/ Thu, 08 May 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/engineering-notes/building-a-resilient-token-server-engineering-for-flow-fault-tolerance-and-speed/ Aiming for a resilient, fast, and fault-tolerant token counting system, the author replaced fragile server restarts with a batch-wide server lifecycle, added retry logic for transient failures, and implemented a local fallback to ensure uninterrupted processing. These changes improved reliability, reduced downtime, and provided clear logs for troubleshooting. Development managers should focus on building systems that handle real-world failures gracefully, prioritize flow, and include observability and fallback mechanisms from the start. https://engineering-leadership.hinshelwood.com/videos/rethinking-continuous-delivery-why-best-practices-don't-exist-in-complex-environments/ Thu, 23 Jan 2025 06:30:03 +0000 https://engineering-leadership.hinshelwood.com/videos/rethinking-continuous-delivery-why-best-practices-don't-exist-in-complex-environments/ There are no universal best practices for continuous delivery in complex environments; instead, teams should adopt flexible, situation-specific approaches. Key strategies include audience-based delivery for rapid feedback, testing in production to validate real-world performance, and a commitment to quickly finding and fixing issues. Development managers should focus on continuous improvement and adaptability rather than rigid processes. https://engineering-leadership.hinshelwood.com/videos/transform-your-software-architecture-the-game-changing-impact-of-tdd-and-pair-programming/ Tue, 19 Nov 2024 16:55:41 +0000 https://engineering-leadership.hinshelwood.com/videos/transform-your-software-architecture-the-game-changing-impact-of-tdd-and-pair-programming/ Test-driven development and pair programming lead to cleaner, more maintainable software architectures by focusing on essential functionality and fostering collaboration. While pair programming may seem slower at first, it improves code quality, reduces costly bugs, and enhances team skills, resulting in long-term productivity gains. Development managers should consider adopting these practices to build more resilient and scalable systems that align with business goals. https://engineering-leadership.hinshelwood.com/videos/embracing-automation-the-key-to-transforming-your-development-process-and-boosting-confidence/ Tue, 14 Jan 2025 06:45:00 +0000 https://engineering-leadership.hinshelwood.com/videos/embracing-automation-the-key-to-transforming-your-development-process-and-boosting-confidence/ Embracing automation in testing, deployment, and validation is essential for faster, more reliable software delivery and increased team confidence. The Azure DevOps team drastically reduced feedback loops and technical debt by shifting to automated, efficient testing and empowering developers with local testing tools. Prioritizing automation and quality builds trust both within teams and with customers, so development managers should focus on automating as much as possible to enable continuous delivery and rapid improvement. https://engineering-leadership.hinshelwood.com/videos/unlocking-code-quality-the-transformative-power-of-frequent-deployments/ Mon, 13 Jan 2025 06:45:00 +0000 https://engineering-leadership.hinshelwood.com/videos/unlocking-code-quality-the-transformative-power-of-frequent-deployments/ Frequent deployments lead to higher code quality, faster feedback, and better alignment with user needs, while infrequent deployments cause larger, riskier changes and more technical debt. Breaking work into smaller pieces and deploying regularly encourages maintainable code and enables quick pivots based on real user data. Development managers should focus on reducing batch sizes, increasing deployment frequency, and investing in observability to improve both product quality and team performance. https://engineering-leadership.hinshelwood.com/videos/from-chaos-to-clarity-my-journey-through-devops-and-the-three-key-challenges-to-overcome/ Thu, 04 Apr 2024 11:34:59 +0000 https://engineering-leadership.hinshelwood.com/videos/from-chaos-to-clarity-my-journey-through-devops-and-the-three-key-challenges-to-overcome/ The author describes moving from chaotic, manual development practices to adopting DevOps, highlighting three main challenges: shifting culture and collaboration, integrating and automating toolchains, and fostering continuous learning. Success requires systems thinking, strong feedback loops, and a culture of experimentation. Development managers should focus on supporting people, streamlining processes, and encouraging ongoing learning to deliver better products faster. https://engineering-leadership.hinshelwood.com/articles/building-a-release-pipeline-with-release-management-with-visual-studio-2013/ Tue, 18 Feb 2014 16:30:59 +0000 https://engineering-leadership.hinshelwood.com/articles/building-a-release-pipeline-with-release-management-with-visual-studio-2013/ Explains how to set up a scalable release pipeline using Release Management in Visual Studio 2013, covering continuous release, feedback environments, and DevOps practices. https://engineering-leadership.hinshelwood.com/articles/quality-enablement-to-achieve-predictable-delivery/ Wed, 24 Jul 2013 09:46:22 +0000 https://engineering-leadership.hinshelwood.com/articles/quality-enablement-to-achieve-predictable-delivery/ Explains how defining quality standards, acceptance criteria, and automation in software delivery leads to predictable outcomes, fewer bugs, and improved team performance. https://engineering-leadership.hinshelwood.com/articles/release-management-with-team-foundation-server-2012/ Wed, 24 Apr 2013 17:38:24 +0000 https://engineering-leadership.hinshelwood.com/articles/release-management-with-team-foundation-server-2012/ Explains how to automate and streamline software release management using Team Foundation Server 2012, Lab Management, and Octopus, focusing on build, deployment, and quality. https://engineering-leadership.hinshelwood.com/articles/professional-scrum-developer-net-training-in-london/ Fri, 18 Jun 2010 15:53:27 +0000 https://engineering-leadership.hinshelwood.com/articles/professional-scrum-developer-net-training-in-london/ Intensive five-day course for software developers covering Scrum, Visual Studio 2010, .NET, and Agile practices through hands-on team sprints and real-world case studies. https://engineering-leadership.hinshelwood.com/videos/unlocking-the-true-power-of-continuous-delivery-how-automation-transforms-software-development/ Fri, 06 Dec 2024 06:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/unlocking-the-true-power-of-continuous-delivery-how-automation-transforms-software-development/ The main benefit of continuous delivery is the automation it brings, which increases consistency, reliability, and risk mitigation in software deployments. Real-world examples like Azure DevOps and Windows teams show that automation shortens feedback loops, reduces errors, and enables faster, higher-quality releases without increasing team size. Development managers should focus on embedding automation throughout their delivery process to protect the business and empower teams to deliver better software more efficiently. https://engineering-leadership.hinshelwood.com/articles/you-are-doing-it-wrong-if-you-are-not-using-test-first/ Mon, 07 Dec 2020 12:00:58 +0000 https://engineering-leadership.hinshelwood.com/articles/you-are-doing-it-wrong-if-you-are-not-using-test-first/ Using test-first approaches like Test Driven Development helps teams deliver software that meets customer needs, reduces maintenance costs, and prevents bugs from reaching production. Writing tests before coding ensures validation at every step, shortens feedback loops, and makes it easier and cheaper to fix issues early. To improve quality and enable confident continuous delivery, development managers should encourage their teams to adopt test-first practices. https://engineering-leadership.hinshelwood.com/videos/unlocking-continuous-delivery-how-feature-flags-transform-software-development/ Thu, 16 Jan 2025 06:45:00 +0000 https://engineering-leadership.hinshelwood.com/videos/unlocking-continuous-delivery-how-feature-flags-transform-software-development/ Feature flags enable teams to release new features incrementally, gather user feedback early, and quickly respond to issues, supporting safer and more frequent deployments. Real-world examples like Azure DevOps show that this approach allows for controlled rollouts, continuous monitoring, and ongoing improvements based on user input. Development managers should consider adopting feature flags to improve delivery speed, reduce risk, and ensure features better meet user needs. https://engineering-leadership.hinshelwood.com/videos/unlocking-the-future-of-software-development-why-automation-is-your-key-to-success/ Wed, 15 Jan 2025 06:45:00 +0000 https://engineering-leadership.hinshelwood.com/videos/unlocking-the-future-of-software-development-why-automation-is-your-key-to-success/ Automation is essential for faster, more reliable software development, reducing human error and enabling consistent, rapid deployments. Real-world failures like Knight Capital show the high cost of manual processes, while leading teams achieve quick, high-quality releases by building automation into every step. Development managers should prioritize automating all possible tasks to improve quality, speed, and adaptability. https://engineering-leadership.hinshelwood.com/articles/create-a-release-management-pipeline-for-professional-developers/ Thu, 04 Dec 2014 12:15:56 +0000 https://engineering-leadership.hinshelwood.com/articles/create-a-release-management-pipeline-for-professional-developers/ This guide walks through setting up an automated release management pipeline using TFS/VSO and Azure, showing how to build, deploy, and parameterize a legacy web app across multiple feedback environments. Key takeaways include the importance of automating builds and releases, using environment-specific parameters, and streamlining approvals for smoother deployments. Development managers should consider investing time upfront to automate and parameterize their pipelines, as this reduces manual errors and accelerates feedback cycles. https://engineering-leadership.hinshelwood.com/articles/quality-enablement-with-visual-studio-2012/ Wed, 15 May 2013 03:13:20 +0000 https://engineering-leadership.hinshelwood.com/articles/quality-enablement-with-visual-studio-2012/ Explores how Visual Studio 2012 supports continuous quality enablement, automated testing, and rapid delivery in modern software development for higher user satisfaction. https://engineering-leadership.hinshelwood.com/videos/why-embracing-automation-is-essential-for-reducing-human-error-in-software-development/ Wed, 18 Dec 2024 06:45:00 +0000 https://engineering-leadership.hinshelwood.com/videos/why-embracing-automation-is-essential-for-reducing-human-error-in-software-development/ Automation is essential in software development because it reduces human error, speeds up feedback, and creates more reliable processes. Relying on manual steps leads to costly mistakes and unsustainable workloads, while automation enables faster, higher-quality releases and happier customers. Development managers should prioritise automating repetitive tasks and rearchitecting processes that cannot be automated to improve quality and efficiency. https://engineering-leadership.hinshelwood.com/articles/standard-environments-for-automated-deployment-and-testing/ Sun, 17 Mar 2013 06:23:45 +0000 https://engineering-leadership.hinshelwood.com/articles/standard-environments-for-automated-deployment-and-testing/ Explains how to set up and use Standard Environments in Visual Studio 2012 TFS for automated software deployment and testing, enabling consistent, repeatable pipelines. https://engineering-leadership.hinshelwood.com/articles/automated-testing-in-a-modern-application-lifecycle/ Tue, 25 Sep 2012 04:33:30 +0000 https://engineering-leadership.hinshelwood.com/articles/automated-testing-in-a-modern-application-lifecycle/ Explains the role of automated testing in modern software development, covering types, integration, benefits, challenges, and tools for maintaining code quality. https://engineering-leadership.hinshelwood.com/articles/unit-testing-against-the-team-foundation-server-2012-api/ Mon, 02 Apr 2012 03:52:55 +0000 https://engineering-leadership.hinshelwood.com/articles/unit-testing-against-the-team-foundation-server-2012-api/ Explains how to unit test applications against the Team Foundation Server 2012 API, focusing on handling authentication for automated and unattended test scenarios. https://engineering-leadership.hinshelwood.com/articles/solution-testing-web-services-with-mstest-on-team-foundation-build-services-2010/ Thu, 04 Mar 2010 13:15:31 +0000 https://engineering-leadership.hinshelwood.com/articles/solution-testing-web-services-with-mstest-on-team-foundation-build-services-2010/ Explains how to configure MSTest for automated testing of web services on Team Foundation Build Services 2010, including handling dynamic server ports and build environments. https://engineering-leadership.hinshelwood.com/articles/does-test-driven-development-speed-up-development/ Mon, 15 Dec 2008 14:55:51 +0000 https://engineering-leadership.hinshelwood.com/articles/does-test-driven-development-speed-up-development/ Explores whether test-driven development (TDD) accelerates software delivery by reducing complexity, rework, and design flaws, and improving adaptability and productivity. https://engineering-leadership.hinshelwood.com/tags/site-reliability-engineering/ Mon, 05 May 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/site-reliability-engineering/ Site Reliability Engineering (SRE) is a discipline that utilises software engineering principles to develop scalable and reliable systems, effectively bridging the gap between development and operations. Originating from the need to embed reliability within the software development lifecycle, SRE ensures that systems maintain functionality and resilience under diverse conditions. This methodology prioritises automation, monitoring, and incident response, which allows teams to deliver consistent value in a sustainable manner. SRE teams establish service level objectives (SLOs) and service level indicators (SLIs) to create clear performance and reliability metrics, fostering a culture of accountability and continuous improvement. This proactive approach to problem-solving and engineering solutions to operational challenges enhances overall system performance, distinguishing SRE from traditional operations roles. By promoting shared responsibility for reliability across teams, SRE encourages collaboration and knowledge sharing, which not only improves user satisfaction but also drives positive business outcomes. Ultimately, the integration of reliability into the development process supports organisational strategic goals and enhances competitive advantage, making SRE a vital component in agile, DevOps, and product development frameworks. https://engineering-leadership.hinshelwood.com/tags/test-first-development/ Tue, 25 Mar 2025 07:40:33 +0000 https://engineering-leadership.hinshelwood.com/tags/test-first-development/ Test First Development is a contemporary engineering practice that emphasises the importance of defining success criteria before the actual implementation of software begins. Originating from the need for clarity and quality in software delivery, this approach involves establishing tests, whether through examples, specifications, or executable tests, prior to coding. This shift-left strategy enhances collaboration among developers, testers, designers, and product owners by ensuring a shared understanding of what constitutes a successful outcome. Test First encompasses both manual and automated validation methods, with a preference for automation due to its ability to facilitate rapid feedback, support continuous integration, and mitigate regression risks. While manual testing serves a role in exploratory validation, automated practices like Test-Driven Development (TDD) and Acceptance Test-Driven Development (ATDD) are more effective in driving design and exposing ambiguities. Importantly, Test First transcends traditional testing; it is fundamentally a design, collaboration, and feedback practice that streamlines workflows by aligning expectations early and grounding development efforts in actual customer needs. By adopting Test First, teams can significantly reduce rework and enhance the overall quality of their software products, making it a valuable methodology in agile, DevOps, and product development contexts. https://engineering-leadership.hinshelwood.com/tags/acceptance-test-driven-development/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/acceptance-test-driven-development/ Acceptance Test Driven Development (ATDD) is a collaborative methodology that prioritises the establishment of clear, testable acceptance criteria prior to feature implementation. Originating from the need for alignment among stakeholders, such as product owners, developers, and testers, ATDD ensures a shared understanding of success metrics for features, thereby minimising miscommunication and the potential for rework. This approach enhances the predictability and sustainability of value delivery by integrating quality assurance early in the development process, promoting a shift-left mindset that allows teams to identify and resolve issues proactively. The emphasis on early testing not only improves software quality but also nurtures a culture of collaboration and shared accountability within teams. Furthermore, the long-term advantages of ATDD extend beyond immediate project results; it fosters a systematic working method that encourages continuous improvement and adaptability to evolving requirements. By consistently implementing ATDD, organisations can enhance their agility and efficiency in delivering higher value to customers, making it a fundamental practice that reinforces the overall development process and keeps teams focused on what is essential for the business and its users. https://engineering-leadership.hinshelwood.com/tags/automated-testing/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/automated-testing/ Automated Testing is a vital practice in software development that utilises automation tools to execute tests systematically, thereby enhancing the quality and reliability of software products. Originating from the need to streamline the testing process, this approach allows development teams to identify and address issues early, significantly minimising manual testing efforts and expediting the delivery of high-quality software. The significance of Automated Testing lies in its capacity to facilitate predictable and sustainable value delivery, fostering a culture of continuous improvement through shortened feedback loops. This practice aligns with Agile and DevOps principles by promoting a shift-left strategy, which encourages earlier testing in the development cycle, enhancing collaboration among cross-functional teams. Furthermore, Automated Testing serves as a long-term enabler of organisational agility, embedding quality assurance within the development workflow. This integration leads to increased throughput and a sustained focus on customer value, ultimately resulting in improved customer satisfaction and retention. By adopting this proactive approach, organisations empower their teams to innovate and adapt, ensuring competitiveness in a fast-paced market environment. https://engineering-leadership.hinshelwood.com/tags/azure-pipelines/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/azure-pipelines/ Azure Pipelines is a cloud-based service designed to automate the processes of building, testing, and deploying applications, thereby enabling teams to deliver value in a predictable and sustainable manner. Originating from the need for efficient software development practices, it integrates seamlessly with various version control systems to facilitate continuous integration and continuous delivery (CI/CD). This capability allows teams to implement code changes frequently and reliably, significantly reducing manual errors and accelerating feedback loops while enhancing collaboration among cross-functional teams. The importance of Azure Pipelines lies in its ability to streamline workflows and improve overall efficiency throughout the software development lifecycle, supporting a diverse array of programming languages and platforms to meet varied project needs. By offering a consistent framework for managing builds and releases, it promotes a culture of continuous improvement and innovation. Furthermore, its integration with Azure DevOps tools, such as Azure Boards and Azure Repos, fosters a cohesive project management environment that enhances visibility into the development process and aligns teams towards shared objectives. This systemic approach ultimately drives organisational agility and resilience, with long-term benefits including increased deployment frequency, reduced lead times, and a heightened focus on delivering high-quality software that aligns with customer requirements. https://engineering-leadership.hinshelwood.com/tags/continuous-integration/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/continuous-integration/ Continuous Integration (CI) is a software development practice that focuses on the frequent merging of code changes into a shared repository, facilitating early detection of errors and prompt resolution of integration issues. Originating from the need for more efficient collaboration in software teams, CI automates the build and testing processes, allowing developers to concentrate on delivering value rather than troubleshooting. Its importance lies in fostering a culture of continuous improvement and collaboration, enabling teams to iterate quickly and adapt to evolving requirements. By promoting regular communication and feedback, CI helps maintain a consistent development pace, resulting in more predictable and sustainable feature delivery. Additionally, CI significantly reduces technical debt by encouraging developers to address issues as they arise, which not only enhances code quality but also boosts team morale through a smoother workflow. Ultimately, CI serves as a foundational element that empowers teams to innovate and effectively respond to customer needs, contributing to long-term success in product development. https://engineering-leadership.hinshelwood.com/tags/deployment-strategies/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/deployment-strategies/ Deployment strategies are systematic approaches that organisations utilise to release software into production, balancing the need for speed with risk management. These strategies are essential for enabling teams to deliver value in a predictable and sustainable manner, facilitating rapid iterations and continuous feedback. Techniques such as blue-green deployments, canary releases, and rolling updates help mitigate the impact of potential failures, allowing teams to address issues swiftly without causing significant disruption to users. The effectiveness of deployment strategies lies in their capacity to cultivate a culture of experimentation and learning, encouraging continuous improvement where each deployment provides insights for refining processes. This approach enhances operational efficiency and aligns with Agile and DevOps principles, fostering collaboration and shared responsibility among cross-functional teams. Furthermore, well-defined deployment strategies contribute to a resilient organisational structure, enabling teams to adapt to evolving market demands and technological changes. By prioritising safe and efficient releases, organisations can maintain a competitive advantage while ensuring customer satisfaction remains central to their product development efforts. Ultimately, the integration of deployment strategies into the broader organisational framework supports sustainable growth and reinforces the importance of delivering value through strategic software releases. https://engineering-leadership.hinshelwood.com/tags/engineering-practices/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/engineering-practices/ Engineering Practices refer to a collection of essential techniques and methodologies aimed at delivering high-quality software within an Agile framework. Originating from the need for reliable and maintainable software, these practices include principles such as clean code, automation, and test-first development, which are integrated into the software development lifecycle to ensure a consistent flow of value to customers. Their importance lies in fostering a culture of technical excellence and continuous improvement, enabling teams to adapt quickly to changing requirements while minimising technical debt, thereby maintaining the software’s robustness over time. This holistic approach enhances collaboration among cross-functional teams and aligns technical initiatives with business goals, promoting overall organisational agility. Additionally, Engineering Practices facilitate the establishment of Continuous Integration and Continuous Delivery pipelines, which optimise the deployment process and shorten lead times. By emphasising quality throughout development, these practices empower teams to innovate with confidence, ensuring that each software release meets customer expectations and contributes to sustained success. The incorporation of these practices into everyday workflows nurtures an environment conducive to learning and experimentation, ultimately boosting team motivation and performance. https://engineering-leadership.hinshelwood.com/tags/technical-mastery/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/technical-mastery/ Technical Mastery is the pursuit of excellence in software craftsmanship, architecture, and engineering practices, characterised by a profound understanding of relevant technologies, methodologies, and tools. It is essential for teams aiming to deliver high-quality products efficiently and sustainably, as it directly influences their ability to provide predictable value. By fostering Technical Mastery, organisations enable their teams to confidently address complex challenges, ensuring that solutions are both effective and maintainable over time. This focus on quality and skill development not only reduces technical debt but also enhances collaboration and responsiveness to market changes. Furthermore, Technical Mastery aligns with the principles of Agile and DevOps by encouraging a shared understanding of best practices and nurturing a culture of experimentation and learning. It facilitates the implementation of robust engineering practices, such as automated testing and continuous integration, which are vital for maintaining a consistent flow of value delivery. As teams refine their skills, they can better align their efforts with organisational objectives, ultimately contributing to greater success and resilience in a rapidly changing environment. https://engineering-leadership.hinshelwood.com/tags/test-automation/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/test-automation/ Test automation is the practice of employing software tools to execute pre-scripted tests on applications prior to their production release. Originating from the need to enhance software quality and expedite feedback loops, this approach allows development teams to automate repetitive testing tasks, thereby enabling them to concentrate on more intricate scenarios that necessitate human insight. The significance of test automation lies in its capacity to provide predictable and sustainable value, facilitating continuous integration and continuous delivery practices. This enables teams to release software updates more frequently and with increased confidence, as automated tests yield immediate feedback on code changes, allowing for swift identification and resolution of defects. Consequently, this reduces the risk of errors in production and promotes collaboration among cross-functional teams by ensuring access to reliable testing results. Furthermore, test automation nurtures a culture of continuous improvement, empowering teams to measure and refine their testing processes over time. By integrating testing into the development lifecycle rather than treating it as a separate phase, organisations can achieve higher quality products and a more resilient development process, equipping teams to respond effectively to evolving market demands and customer requirements. https://engineering-leadership.hinshelwood.com/tags/test-driven-development/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/test-driven-development/ Test Driven Development (TDD) is a software development methodology that prioritises the creation of automated tests prior to writing the actual code. Originating from the need for a structured approach to software design, TDD ensures that development is guided by the requirements specified in the tests, which clarifies the intended functionality of the software. This practice is crucial in the context of Agile and DevOps as it promotes a culture of quality and accountability, allowing teams to deliver consistent and sustainable value. By embedding testing into the development lifecycle from the beginning, TDD significantly reduces the risk of defects and simplifies the process of refactoring, with tests acting as a safety net. The long-term advantages of TDD extend beyond immediate improvements in code quality; it fosters a mindset of continuous improvement and adaptability among team members. This approach aligns seamlessly with Agile principles, enhancing collaboration and responsiveness to change while supporting technical excellence. By focusing on test coverage, teams can confidently introduce new features and enhancements, ensuring that existing functionalities remain intact. Ultimately, TDD not only improves individual projects but also cultivates a culture of reliability and trust within the organisation, leading to better outcomes for stakeholders and customers. https://engineering-leadership.hinshelwood.com/tags/technical-excellence/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership.hinshelwood.com/tags/technical-excellence/ Technical Excellence encompasses the quality of engineering practices that facilitate high-quality software delivery, enhanced agility, and ongoing improvement within development teams. Originating from methodologies that prioritise best practices, it empowers teams to create maintainable, scalable, and resilient software. In the context of Agile, Technical Excellence is vital as it allows teams to swiftly adapt to changing requirements and market demands while ensuring product quality and sustainability. Key practices such as Test-Driven Development (TDD) and Continuous Integration and Continuous Delivery (CI/CD) play a significant role in maintaining high standards by automating testing and deployment processes, thus enabling more frequent and reliable software releases. Additionally, modular architecture supports scalability and responsiveness to new requirements, while emergent design principles promote flexibility in adapting software designs as understanding evolves. By fostering a culture of continuous improvement, Technical Excellence encourages teams to regularly evaluate and refine their practices, ensuring they can maintain quality and responsiveness to change. Embedding this capability within an organisation’s culture not only addresses immediate customer needs but also establishes a sustainable foundation for long-term success, allowing organisations to consistently deliver high-quality software while remaining adaptable and efficient in their development processes.