https://engineering-leadership.hinshelwood.com/tags/engineering-practices/ Recent content in Engineering Practices 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/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/videos/how-to-tackle-technical-debt-without-halting-progress-smarter-ways-to-keep-your-team-moving-forward/ Mon, 26 May 2025 06:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/how-to-tackle-technical-debt-without-halting-progress-smarter-ways-to-keep-your-team-moving-forward/ Technical debt slows teams down and hurts morale, but stopping all work to fix it is unrealistic. The most effective approach is to make technical debt visible, prioritize high-impact improvements, and embed continuous improvement into daily workflows. Development managers should focus on changing team practices and decision-making so that managing technical debt becomes a natural, ongoing part of delivering value. https://engineering-leadership.hinshelwood.com/articles/your-evolving-definition-of-done/ Mon, 31 Mar 2025 09:00:00 +0100 https://engineering-leadership.hinshelwood.com/articles/your-evolving-definition-of-done/ The Definition of Done should evolve as teams mature, starting with basic quality standards and expanding to include automation, security, and business-level requirements that align with organisational goals. A strong, consistently applied DoD reduces risk, rework, and delays, ensuring every increment is truly releasable and delivers real value. Development managers should regularly review and raise the DoD, embedding it into team practices to protect quality and support strategic objectives. https://engineering-leadership.hinshelwood.com/signals/velocity-isn-t-how-many-story-points-a-team-burns-down/ Mon, 10 Mar 2025 16:30:02 +0000 https://engineering-leadership.hinshelwood.com/signals/velocity-isn-t-how-many-story-points-a-team-burns-down/ Velocity is about how quickly your team delivers value, not just story points completed. Focus on measuring time to build, self-test, deploy, and learn from user feedback, as these are actionable and within your control. Start tracking these metrics to improve your delivery speed and effectiveness. 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/videos/stop-paying-the-hidden-costs-of-weak-delivery-why-a-strong-definition-of-done-transforms-your-team-s-results/ Wed, 21 May 2025 06:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/stop-paying-the-hidden-costs-of-weak-delivery-why-a-strong-definition-of-done-transforms-your-team-s-results/ Cutting corners on quality and having a weak definition of done leads to hidden costs like rework, production risks, and lost trust. A clear, shared, and enforceable definition of done ensures every increment is truly usable, reliable, and aligned with business goals. Make your definition of done visible, evidence-based, and strictly enforced to improve delivery outcomes and build stakeholder confidence. https://engineering-leadership.hinshelwood.com/signals/there-no-such-thing-as-good-technical-debt/ Sat, 19 Apr 2025 15:30:34 +0100 https://engineering-leadership.hinshelwood.com/signals/there-no-such-thing-as-good-technical-debt/ Technical debt is always harmful and should not be considered acceptable; it slows onboarding, increases errors, and creates inefficiency. It accumulates quickly and can suddenly halt delivery, as seen in Microsoft’s experience before they overhauled their processes and addressed their debt. Development managers should prioritize identifying and reducing technical debt now rather than accepting it as normal. 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/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/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/videos/navigating-technical-debt-how-to-transform-challenges-into-opportunities-for-quality-and-efficiency/ Thu, 19 Dec 2024 06:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/navigating-technical-debt-how-to-transform-challenges-into-opportunities-for-quality-and-efficiency/ Technical debt is the cost of future rework from prioritising speed over good design, and it is distinct from poor quality, which often causes bigger productivity losses. Long release cycles and mislabeling poor quality as technical debt can lead to unsustainable practices and higher costs. Development managers should set clear quality standards, encourage regular refactoring, and adopt continuous improvement to reduce technical debt, improve efficiency, and deliver better products. https://engineering-leadership.hinshelwood.com/articles/work-can-flow-across-the-sprint-boundary/ Tue, 30 Jan 2018 20:12:00 +0000 https://engineering-leadership.hinshelwood.com/articles/work-can-flow-across-the-sprint-boundary/ Allowing work to flow across Sprint boundaries is permitted in Scrum and can improve delivery speed, responsiveness, and value, as long as teams maintain clear, outcome-focused Sprint Goals and consistently deliver Done increments. Adopting practices like Continuous Delivery, feature toggles, and frequent feedback helps teams validate work early and adapt quickly. Development managers should encourage flow principles and robust engineering practices to maximize throughput and support better business decisions. 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/the-crucible-of-learning-transforming-organizational-effectiveness-through-devops/ Wed, 21 Aug 2024 07:00:19 +0000 https://engineering-leadership.hinshelwood.com/videos/the-crucible-of-learning-transforming-organizational-effectiveness-through-devops/ DevOps transformation delivers major benefits when organizations address technical debt, simplify systems, and empower teams to take ownership of change. Key outcomes include faster delivery, lower costs, and happier, more effective teams, but success requires upskilling and active participation rather than outsourcing the work. Development managers should prioritize regular refactoring and foster a culture of continuous improvement to achieve lasting results. 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/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/articles/fragile-by-design-the-cost-of-pretending-to-be-resilient/ Mon, 12 May 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/fragile-by-design-the-cost-of-pretending-to-be-resilient/ Most systems fail under real pressure because resilience is often treated as a checkbox or afterthought rather than a core product capability that is engineered, tested, and verified in real-world conditions. High-profile outages at Spain’s grid, Oracle, and Heathrow show that bad engineering, shallow product thinking, and leadership denial lead to systemic fragility. To avoid costly failures, development managers must make resilience a disciplined, ongoing practice by designing for failure, testing recovery regularly, and confronting weaknesses head-on. 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/mastering-site-reliability-insights-from-azure-devops-on-building-a-resilient-live-site-culture/ Thu, 04 Jun 2020 02:05:28 +0000 https://engineering-leadership.hinshelwood.com/videos/mastering-site-reliability-insights-from-azure-devops-on-building-a-resilient-live-site-culture/ The Azure DevOps team at Microsoft has built a resilient live site culture by prioritising transparency with customers, investing in comprehensive telemetry, and automating deployment processes. Cross-functional teams and structured incident response drive continuous improvement and reliability at scale. Development managers should focus on these practices to boost both agility and system robustness while maintaining customer trust. 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/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/stop-firefighting-bugs-why-shifting-left-saves-time-money-and-your-reputation/ Wed, 04 Jun 2025 06:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/stop-firefighting-bugs-why-shifting-left-saves-time-money-and-your-reputation/ Catching bugs late in the process wastes time, increases costs, and damages your reputation, while most issues could be prevented much earlier. Shifting left by embedding quality checks, early validation, and security into every stage of development leads to faster fixes, fewer production surprises, and greater stakeholder trust. Start building quality in from the beginning to avoid last-minute firefighting and deliver more reliable software. 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/articles/professional-scrum-teams-build-software-that-works/ Thu, 03 Dec 2020 00:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/professional-scrum-teams-build-software-that-works/ Professional Scrum teams must deliver high-quality, working software every sprint, prioritizing quality over speed or feature quantity to build trust and protect the organization’s reputation. Developers are accountable for quality and should use automation, DevOps practices, and continuous improvement to avoid technical debt and defects. Managers should empower teams to focus on quality, address technical debt in retrospectives, and consider upskilling developers through professional training. 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/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/devops-the-practical-path-to-modernising-legacy-systems-without-starting-over/ Mon, 02 Jun 2025 06:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/devops-the-practical-path-to-modernising-legacy-systems-without-starting-over/ DevOps enables organisations to modernise legacy systems without starting from scratch by introducing automation, continuous integration and deployment, and observability, which make change safer and more routine. These practices reduce bottlenecks, lower the cost of change, and help teams deliver improvements continuously. Development managers should focus on identifying friction points and adopting DevOps practices to make ongoing system improvements achievable and sustainable. https://engineering-leadership.hinshelwood.com/signals/rethinking-dev-test-staging-production-pipelines-for-safety/ Fri, 21 Feb 2025 16:30:30 +0000 https://engineering-leadership.hinshelwood.com/signals/rethinking-dev-test-staging-production-pipelines-for-safety/ Traditional Dev-Test-Staging-Production pipelines give a false sense of security because staging environments do not truly reflect production, leading to missed issues and wasted resources. Modern teams should focus on releasing to small user groups in production and using real feedback to guide rollouts. Consider shifting from heavy pre-release testing to faster, data-driven feedback in production to improve safety and efficiency. https://engineering-leadership.hinshelwood.com/videos/unlocking-engineering-excellence-how-azure-devops-transforms-traceability-transparency-and-the-developer-experience/ Mon, 28 Jul 2025 07:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/unlocking-engineering-excellence-how-azure-devops-transforms-traceability-transparency-and-the-developer-experience/ Azure DevOps is a comprehensive platform that enhances engineering excellence by providing end-to-end traceability, transparency, and an integrated developer experience across planning, code, builds, and testing. Key benefits include instant visibility into what is deployed where, streamlined audit and compliance processes, and reduced friction between developers and testers. Development managers should ensure their teams fully leverage Azure DevOps’ capabilities to improve collaboration, accountability, and product quality. 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/signals/why-engineering-teams-use-staging-environments-for-risk-reduction/ Fri, 14 Feb 2025 16:30:01 +0000 https://engineering-leadership.hinshelwood.com/signals/why-engineering-teams-use-staging-environments-for-risk-reduction/ Staging environments are intended to reduce risk but often lead to wasted time, delayed feedback, and extra costs without truly preventing failures. Modern practices like feature flags, progressive rollouts, and real-time monitoring can help teams deploy safely to production while reducing waste. Consider whether maintaining staging environments is actually benefiting your team or just adding unnecessary overhead. 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-insufficiency-of-scrum-is-a-fallacy/ Sat, 23 Mar 2013 17:37:31 +0000 https://engineering-leadership.hinshelwood.com/articles/the-insufficiency-of-scrum-is-a-fallacy/ Scrum alone does not cause project failure; lacking strong engineering practices and effective retrospectives leads to technical debt and poor Agile outcomes. 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/signals/executives-want-predictability/ Mon, 31 Mar 2025 15:30:08 +0100 https://engineering-leadership.hinshelwood.com/signals/executives-want-predictability/ If your teams do not have a clear, enforced Definition of Done, you are creating hidden risks and unreliable forecasts, which leads to missed deadlines and frustrated customers. Treating “Done” as negotiable means you are not delivering real value or predictability. Make sure your teams only mark work as done when it meets objective, enforceable standards to ensure true progress and trustworthy commitments. 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/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/signals/there-a-common-belief-that-rollback-is-the-ultimate-safety-net/ Thu, 13 Feb 2025 15:53:38 +0000 https://engineering-leadership.hinshelwood.com/signals/there-a-common-belief-that-rollback-is-the-ultimate-safety-net/ Relying on rollback as a safety net is risky, especially for stateful applications where it can cause data issues and failures. Safer approaches include progressive delivery methods like feature flags and canary releases, which help detect and limit problems early. Teams should focus on making deployments safe to fail rather than assuming rollback will fix mistakes. https://engineering-leadership.hinshelwood.com/signals/branch-promotion-is-a-relic-of-slow-manual-software-delivery/ Sat, 08 Feb 2025 16:30:00 +0000 https://engineering-leadership.hinshelwood.com/signals/branch-promotion-is-a-relic-of-slow-manual-software-delivery/ Branch promotion slows down delivery and adds risk, while modern teams merge changes into the main branch as soon as they are ready and use feature flags to separate deployment from release. Testing in production-like environments and instant rollbacks improve speed and safety. Focus on managing the flow of work, not branches, to streamline delivery. 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/articles/getting-started-with-a-definition-of-done-dod/ Mon, 14 Dec 2020 13:03:00 +0000 https://engineering-leadership.hinshelwood.com/articles/getting-started-with-a-definition-of-done-dod/ A clear Definition of Done (DoD) is essential for ensuring software quality and predictable delivery, as it sets shared criteria for what “done” means for every increment. Involve the whole Scrum Team and relevant experts to create a short, measurable checklist that covers code quality, testing, security, and usability, and review it regularly to keep raising the quality bar. Before starting sprints, make sure your current increment meets the DoD, and continuously improve both your software and your DoD to maintain a working, shippable product. 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/signals/staging-environments-do-not-prevent-production-failures/ Fri, 28 Feb 2025 16:30:01 +0000 https://engineering-leadership.hinshelwood.com/signals/staging-environments-do-not-prevent-production-failures/ Staging environments do not truly prevent production failures because they cannot fully replicate real-world conditions, often giving teams a false sense of security. Leading teams now deploy changes incrementally to real users in production, using monitoring and automated safeguards to catch issues early. Consider shifting focus from pre-production testing to safer, controlled releases in production to reduce risk and respond faster to problems. 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/engineering-notes/convert-legacy-projects-and-asp-net-mvc-apps-to-sdk-style-with-confidence/ Thu, 29 May 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/engineering-notes/convert-legacy-projects-and-asp-net-mvc-apps-to-sdk-style-with-confidence/ Upgrading legacy .NET projects to SDK-style makes your codebase easier to maintain, improves build and CI/CD integration, and prepares you for future .NET upgrades. Converting class libraries is straightforward and highly recommended, while web apps require more care and are best handled with the MSBuild.SDK.SystemWeb package if you want SDK-style; otherwise, you can leave them in the old format. Start by converting class libraries now to simplify your engineering system and reduce technical debt. 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-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/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/agentic-engineering/ Tue, 22 Jul 2025 15:58:00 +0000 https://engineering-leadership.hinshelwood.com/tags/agentic-engineering/ Agentic Engineering is the deliberate design and practice of software development that maximises the agency of both humans and intelligent systems. It integrates engineering excellence, DevOps ethos, and ethical autonomy to create environments where decisions are decentralised, feedback is fast, and value delivery is continuous. It’s characterised by Developer Agency, Systemic Observability, DevOps-Infused Craft, Ethical AI Integration, and Feedback-Driven Adaptation. Agentic Engineering is not a job title, role, or method, it’s a philosophy of engineering in which the ability to act with clarity, intent, and impact is engineered into the way we build, learn, and evolve. 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/definition-of-done/ Mon, 05 May 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/tags/definition-of-done/ The Definition of Done (DoD) is a critical framework that establishes a shared understanding of what constitutes a completed and releasable product increment within agile and DevOps environments. Originating from the need for clarity in product development, the DoD serves as an organisational standard that all teams must adhere to, ensuring that every increment meets minimum quality criteria before it can be considered complete. This framework is vital for fostering transparency and consistency across teams, enabling empirical decision-making based on real-world feedback. By defining specific criteria, such as deployment in production, telemetry collection, and validation of initial hypotheses, the DoD helps mitigate risks associated with incomplete or subpar work, thereby reducing technical debt and enhancing the overall quality of deliverables. Furthermore, it facilitates faster feedback loops and iterative learning, allowing teams to adapt their processes based on actual performance data. The DoD not only clarifies expectations for stakeholders but also protects the integrity of the product, ensuring that increments are valuable, verifiable, and ready for real-world use. In essence, the Definition of Done is foundational to maintaining high standards in product development, promoting alignment among teams, and ultimately driving successful outcomes in organisational design and delivery. https://engineering-leadership.hinshelwood.com/tags/github/ Thu, 10 Apr 2025 10:16:54 +0000 https://engineering-leadership.hinshelwood.com/tags/github/ GitHub is a comprehensive platform that facilitates version control, collaboration, and integration within software development. Originating as a hosting service for Git repositories, it has evolved to include features such as GitHub Actions for automating continuous integration and continuous delivery workflows, and GitHub Projects for task management and progress tracking. Its significance lies in its ability to enhance collaboration among development teams, reduce friction in development cycles, and support the efficient delivery of value. GitHub is essential for organisations seeking to maintain transparency and integrate workflows between development and operations teams, as its integration with CI/CD practices allows for the automation of testing, builds, and deployments, ensuring continuous validation and delivery of code changes. The platform’s features, including issues, pull requests, and discussions, foster effective communication and alignment on project goals. Additionally, GitHub’s compatibility with a variety of third-party tools and services further amplifies its effectiveness in modern DevOps environments. By utilising GitHub’s extensive toolset, organisations can enhance team collaboration, streamline development processes, and improve software delivery outcomes. 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/continuous-delivery/ Fri, 21 Mar 2025 13:37:32 +0000 https://engineering-leadership.hinshelwood.com/tags/continuous-delivery/ Continuous Delivery is a software delivery practice that focuses on producing software in short, reliable cycles, enabling teams to release updates at any time. Originating from the need for more efficient and responsive software development processes, it involves delivering small, incremental improvements directly to users from the initial stages of development. This approach, as defined by Jez Humble, emphasises the ability to safely and quickly implement changes, such as new features, configuration adjustments, and bug fixes, into production. The importance of Continuous Delivery lies in its capacity to facilitate rapid validation of assumptions and collection of user feedback, which are crucial for refining products and achieving valuable outcomes. By automating essential processes like testing, integration, and deployment, Continuous Delivery not only mitigates the risk of errors but also enhances software quality and accelerates the time it takes to deliver value to users. Teams that adopt this practice can more effectively respond to market demands and stakeholder input, thereby fostering a culture of continuous learning, innovation, and adaptability within their organisations. https://engineering-leadership.hinshelwood.com/tags/shift-left-strategy/ Mon, 17 Mar 2025 14:46:11 +0000 https://engineering-leadership.hinshelwood.com/tags/shift-left-strategy/ The Shift-Left Strategy is a proactive approach in modern software development that emphasises the integration of testing, security, and compliance activities early in the development lifecycle, rather than deferring them to the end. Originating from the need to mitigate risks associated with late-stage defect detection, this strategy allows teams to identify and address issues sooner, thereby reducing the amount of rework required and accelerating feedback loops. By implementing practices such as automated testing, security as code, and continuous integration, organisations can enhance software quality and reliability from the outset. This approach is particularly valuable in agile and DevOps environments, where rapid delivery and high performance are critical. Ultimately, the Shift-Left Strategy fosters a culture of quality and efficiency, ensuring that products are not only delivered faster but also meet the necessary standards for security and compliance, making it an essential component of effective organisational design and product development. https://engineering-leadership.hinshelwood.com/tags/internal-developer-platform/ Mon, 24 Feb 2025 13:04:45 +0000 https://engineering-leadership.hinshelwood.com/tags/internal-developer-platform/ An Internal Developer Platform (IDP) is a unified environment designed to enhance the development lifecycle by enabling teams to efficiently build, test, and deploy applications. Originating from the need to simplify infrastructure management and application dependencies, an IDP allows developers to concentrate on delivering value rather than dealing with operational challenges. This platform cultivates a collaborative and innovative culture, empowering teams to experiment and iterate quickly within a structured framework. By embedding best practices into the development process, an IDP promotes reliability and predictability in software delivery. It also facilitates continuous integration and continuous delivery (CI/CD) practices, which are vital for maintaining competitiveness in rapidly evolving markets. By automating repetitive tasks and standardising workflows, an IDP boosts productivity and shortens lead times, enabling organisations to swiftly adapt to changing customer demands. Ultimately, the long-term advantages of an Internal Developer Platform lie in its capacity to foster a sustainable development ecosystem that aligns with organisational objectives, thereby driving innovation and operational excellence. This alignment is essential for nurturing a resilient and adaptive organisational culture focused on continuous improvement and value delivery. 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/behaviour-driven-development/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/behaviour-driven-development/ Behaviour Driven Development (BDD) is a collaborative methodology that aligns software development with business objectives by promoting clear communication among all stakeholders involved. Originating from the need to bridge the gap between technical and non-technical participants, BDD utilises natural language to articulate the desired behaviour of a system, fostering a shared understanding of requirements that are both testable and comprehensible. This approach is crucial in agile and DevOps environments, as it encourages teams to focus on user-centric outcomes, thereby enhancing collaboration and minimising ambiguity in requirements. By reducing misunderstandings and the need for rework, BDD enables teams to deliver features that more accurately meet user needs, resulting in a more predictable and sustainable development process. Furthermore, BDD supports continuous improvement by integrating with automated testing and continuous delivery practices, ensuring that teams remain aligned with user value as they iterate on their products. This emphasis on behaviour over mere functionality cultivates a culture of shared ownership and accountability, empowering teams to innovate while maintaining a clear focus on business goals, ultimately driving a deeper understanding of user needs and enhancing overall product quality. 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-debt/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/technical-debt/ Technical debt is the concept that encapsulates the hidden costs associated with opting for quick, suboptimal solutions in software development rather than investing time in more effective, long-term strategies. It often emerges from factors such as hurried development processes, insufficient documentation, or reliance on outdated technologies. Recognising and managing technical debt is essential for teams striving to deliver consistent and sustainable value, as its accumulation can impede innovation and responsiveness to market changes, ultimately compromising product quality and delivery timelines. Addressing technical debt requires a commitment to refactoring, enhancing code quality, and adopting superior tools and practices, which not only boosts team efficiency but also cultivates a culture of continuous improvement. By systematically tackling technical debt, organisations can sustain a healthy development pace, ensuring competitiveness and responsiveness to customer demands. This strategic focus on technical debt is crucial for fostering organisational agility, as it directly impacts the ability to innovate and adapt in a fast-evolving landscape. 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.