https://engineering-leadership-preview.hinshelwood.com/tags/technical-mastery/ Recent content in Technical Mastery on Engineering Leadership in AI & Software Hugo en Tue, 16 Jun 2026 17:40:35 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/stop-building-silos-start-building-systems/ Mon, 07 Jul 2025 09:00:00 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/is-agile-really-just-a-mindset/ Mon, 11 Aug 2025 09:00:00 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/why-topic-branches-drive-high-quality-delivery/ Mon, 14 Jul 2025 09:00:00 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/videos/why-a-shared-definition-of-done-is-the-secret-to-consistent-predictable-quality-in-agile-teams/ Wed, 14 May 2025 07:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-a-shared-definition-of-done-is-the-secret-to-consistent-predictable-quality-in-agile-teams/ When teams lack a shared definition of done, quality and predictability suffer, leading to confusion, hidden risks, and technical debt. Aligning on a clear, organisation-wide standard ensures consistent delivery, builds trust, and reduces production risks. Development managers should prioritise creating and enforcing a common definition of done to achieve reliable outcomes and true agility. https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/articles/your-evolving-definition-of-done/ Mon, 31 Mar 2025 09:00:00 +0100 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/stop-hiding-behind-complexity-and-start-delivering-continuously/ Mon, 24 Feb 2025 09:00:00 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/signals/scrum-masters-are-not-glorified-meeting-schedulers/ Sun, 09 Mar 2025 16:30:01 +0000 https://engineering-leadership-preview.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-preview.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-preview.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-preview.hinshelwood.com/signals/there-no-such-thing-as-good-technical-debt/ Sat, 19 Apr 2025 15:30:34 +0100 https://engineering-leadership-preview.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-preview.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-preview.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-preview.hinshelwood.com/signals/scrum-teams-don-t-set-the-bar-for-quality-they-meet-it/ Thu, 03 Apr 2025 15:30:01 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/scrum-teams-don-t-set-the-bar-for-quality-they-meet-it/ Scrum teams are responsible for meeting, not setting, the quality standard defined by the Definition of Done, which should be a strict, non-negotiable measure of what is releasable. Weakening or fluctuating the DoD increases risk and technical debt, undermining quality and predictability. Development managers should ensure their teams consistently strengthen the DoD over time rather than lowering it to deliver more features. https://engineering-leadership-preview.hinshelwood.com/articles/testing-in-production-maximises-quality-and-value/ Thu, 13 Feb 2025 09:00:00 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/definition-of-done-objective-vs-subjective/ Fri, 03 Jan 2025 00:00:00 +0000 https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.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-preview.hinshelwood.com/articles/resilience-is-part-of-the-product-not-an-afterthought/ Mon, 09 Jun 2025 09:00:00 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/delivery-is-the-only-measure-of-progress-in-scrum/ Mon, 03 Feb 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/delivery-is-the-only-measure-of-progress-in-scrum/ Progress in Scrum should be measured by delivering working software to real users, not just completing internal work. Teams must deliver increments to production every Sprint, gather user feedback quickly, and adapt based on that feedback. To stay competitive, make delivery the default by automating releases, breaking down silos, and ensuring value reaches users every iteration. https://engineering-leadership-preview.hinshelwood.com/videos/transforming-engineering-excellence-the-power-of-naked-agility-in-quality-and-leadership/ Sat, 30 Nov 2024 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/transforming-engineering-excellence-the-power-of-naked-agility-in-quality-and-leadership/ Prioritising quality from the start is essential to protect your brand and build customer trust, and this requires empowering engineering teams to take ownership, address technical debt openly, and integrate practices like continuous integration, user experience, and security early in development. Fostering a culture of transparency, collaboration, and continuous improvement leads to better products and stronger technical leadership. Invest in your teams’ skills and encourage shared responsibility for quality to drive lasting value for your customers and organisation. https://engineering-leadership-preview.hinshelwood.com/videos/the-crucible-of-learning-transforming-organizational-effectiveness-through-devops/ Wed, 21 Aug 2024 07:00:19 +0000 https://engineering-leadership-preview.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-preview.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-preview.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-preview.hinshelwood.com/signals/do-more-staging-environments-really-reduce-deployment-risk/ Wed, 26 Feb 2025 16:30:31 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/stop-promoting-branches/ Thu, 06 Feb 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/stop-promoting-branches/ Promoting code through multiple environment branches slows delivery, increases risk, and adds unnecessary complexity. Instead, use simple branching models like GitHub Flow for continuous delivery or Release Flow if you must support multiple live versions; avoid outdated models like Git Flow and never rely on reverse integration. Focus on merging changes directly into main, use feature flags for releases, and keep branching lightweight to deliver value faster. https://engineering-leadership-preview.hinshelwood.com/videos/the-power-of-technical-excellence-in-agile-development/ Thu, 27 Jun 2024 06:45:00 +0000 https://engineering-leadership-preview.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-preview.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-preview.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-preview.hinshelwood.com/articles/how-to-build-for-business-resilience-and-continuity/ Mon, 26 May 2025 09:00:00 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/fragile-by-design-the-cost-of-pretending-to-be-resilient/ Mon, 12 May 2025 09:00:00 +0000 https://engineering-leadership-preview.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-preview.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-preview.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-preview.hinshelwood.com/videos/why-big-bang-rewrites-fail-how-sustainable-change-and-engineering-excellence-transform-legacy-systems/ Mon, 08 Sep 2025 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-big-bang-rewrites-fail-how-sustainable-change-and-engineering-excellence-transform-legacy-systems/ Big Bang rewrites of legacy systems usually fail due to high costs, delays, and unchanged team mindsets, while incremental in-place improvements deliver ongoing value and reduce risk. Sustainable change comes from building a culture of continuous improvement and engineering excellence, where teams refactor and modernise systems piece by piece. Development managers should focus on fostering this culture and invest in gradual, disciplined transformation rather than risky all-at-once rewrites. https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/signals/technical-debt-isn-t-just-messy-code/ Thu, 13 Mar 2025 16:30:02 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/videos/transforming-chaos-into-clarity-how-optimising-systems-fuels-engineering-excellence/ Mon, 16 Dec 2024 06:00:00 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/why-handoffs-are-killing-your-agility/ Mon, 13 Jan 2025 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/why-handoffs-are-killing-your-agility/ Excessive handoffs between siloed teams slow delivery, reduce quality, and undermine team morale, making true agility impossible. Key issues include loss of context, increased cycle time, and lower accountability, all of which compound to hurt value delivery. To improve, reorganise into cross-functional teams, automate workflows, limit work in progress, and regularly remove outdated processes to streamline flow and boost team effectiveness. https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.hinshelwood.com/signals/the-hidden-costs-of-supporting-multiple-versions-in-production/ Thu, 06 Feb 2025 16:30:01 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/the-hidden-costs-of-supporting-multiple-versions-in-production/ Supporting multiple versions in production drains engineering resources through increased context-switching, merge conflicts, and bug risks. Back-porting fixes and maintaining separate branches for each customer make things worse, leading to instability and technical debt. To avoid these problems, teams should simplify and standardise their branching strategy. https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/articles/why-most-scrum-masters-are-failing-and-what-they-should-know/ Thu, 05 Sep 2024 11:14:48 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/why-most-scrum-masters-are-failing-and-what-they-should-know/ Most Scrum Masters lack the necessary understanding of Scrum and related technical and business practices, which has led to widespread layoffs and questions about their value. Companies now expect Scrum Masters to demonstrate clear competence in areas like DevOps, engineering practices, agile frameworks, release planning, stakeholder management, and metrics. Development managers should ensure their Scrum Masters have foundational knowledge in these areas and can show measurable impact on team effectiveness. https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-teams-build-software-that-works/ Thu, 03 Dec 2020 00:00:00 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/videos/stop-flying-blind-why-telemetry-belongs-in-your-definition-of-done/ Wed, 11 Jun 2025 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/stop-flying-blind-why-telemetry-belongs-in-your-definition-of-done/ Shipping software without telemetry leaves teams guessing about usage, performance, and user behavior, which prevents learning and improvement. Teams that make telemetry a core part of their Definition of Done catch issues early, validate outcomes with real data, and make better decisions. To deliver real value, define telemetry needs upfront, automate data collection, review feedback regularly, and act on what you learn. https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/articles/can-the-definition-of-done-change-per-sprint/ Mon, 14 Oct 2019 13:55:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/can-the-definition-of-done-change-per-sprint/ The Definition of Done can be improved each Sprint to raise quality but should never be changed to lower standards or to vary by backlog item, as this undermines transparency and product value. Consistency in the Definition of Done ensures everyone understands what a usable increment means and supports reliable delivery. Development managers should encourage teams to strengthen the Definition of Done over time, aiming for a shippable product each Sprint. https://engineering-leadership-preview.hinshelwood.com/signals/why-organisations-believe-their-software-is-too-complex-for-cd/ Mon, 24 Feb 2025 10:51:31 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/videos/mastering-technical-debt-strategies-to-transform-challenges-into-opportunities-for-your-development-team/ Thu, 28 Nov 2024 06:00:11 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/mastering-technical-debt-strategies-to-transform-challenges-into-opportunities-for-your-development-team/ Technical debt results from choosing quick fixes over robust solutions, leading to future costs and risks that can hinder your team’s productivity. Proactively paying down technical debt, as shown by the Azure DevOps team’s shift to agile practices, can dramatically increase feature delivery and product quality. Make refactoring, short feedback loops, and a focus on quality part of your regular process to unlock long-term gains and sustainable success. https://engineering-leadership-preview.hinshelwood.com/videos/nkd-agility-your-partner-in-developing-engineering-excellence/ Sat, 23 Nov 2024 07:00:12 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/avoid-the-pick-n-mix-branching-anti-pattern/ Mon, 14 Jul 2014 15:35:35 +0000 https://engineering-leadership-preview.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-preview.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-preview.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-preview.hinshelwood.com/signals/rethinking-dev-test-staging-production-pipelines-for-safety/ Fri, 21 Feb 2025 16:30:30 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/signals/evolving-engineering-practices-to-improve-sprint-workflow-in-scrum/ Thu, 29 May 2025 15:30:45 +0100 https://engineering-leadership-preview.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-preview.hinshelwood.com/signals/why-engineering-teams-use-staging-environments-for-risk-reduction/ Fri, 14 Feb 2025 16:30:01 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/getting-started-with-a-modern-source-control-system-and-devops/ Mon, 13 Jul 2020 18:41:59 +0000 https://engineering-leadership-preview.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-preview.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-preview.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-preview.hinshelwood.com/signals/executives-want-predictability/ Mon, 31 Mar 2025 15:30:08 +0100 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/stop-writing-business-logic-in-stored-procedures/ Mon, 23 Jun 2025 09:00:00 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/signals/understand-the-true-risk-of-technical-debt-in-your-business/ Thu, 24 Apr 2025 15:30:48 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/understand-the-true-risk-of-technical-debt-in-your-business/ Technical debt is pure risk with no upside, leading to lost time, reduced agility, and missed opportunities. Microsoft’s experience shows that unchecked technical debt can severely slow delivery, but addressing it directly restores speed and flexibility. Development managers should treat technical debt as a critical business issue and take proactive steps to reduce it. https://engineering-leadership-preview.hinshelwood.com/videos/technical-debt-management-for-long-term-quality/ Thu, 21 Nov 2024 07:00:11 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/signals/best-branching-strategies-for-development-teams-explained/ Tue, 25 Feb 2025 16:30:02 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/best-branching-strategies-for-development-teams-explained/ Using separate branches for each environment increases complexity and slows feedback, making it harder to deliver value quickly. Teams should use branches to manage work in progress and rely on feature flags and progressive rollouts to control what users see. Review your current branching approach and consider simplifying it to speed up delivery and reduce risk. https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-rapid-delivery-overcoming-common-devops-challenges-for-agile-success/ Fri, 21 Apr 2023 07:00:06 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-rapid-delivery-overcoming-common-devops-challenges-for-agile-success/ Many teams struggle to deliver products quickly due to slow feedback loops, limited automation, and resistance to change. Key improvements include automating processes, engaging compliance teams early to challenge assumptions, and fostering a culture open to experimentation. Development managers should review their delivery pipelines for bottlenecks and actively involve stakeholders to enable faster, more agile releases. https://engineering-leadership-preview.hinshelwood.com/videos/why-azure-devops-wins-for-governance-security-and-scale-right-out-of-the-box/ Mon, 01 Sep 2025 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-azure-devops-wins-for-governance-security-and-scale-right-out-of-the-box/ Azure DevOps provides integrated governance, security, compliance, and scalability out of the box, eliminating the need for complex tool setups and manual integration. Its seamless traceability, audit trails, and ability to handle thousands of users make it ideal for large-scale, secure software development. Development managers should consider Azure DevOps to reduce operational friction and focus on delivering value rather than managing disparate tools. https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/signals/i-ll-never-understand-teams-that-manage-bugs-instead-of-fixing-them/ Thu, 01 May 2025 15:30:38 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/i-ll-never-understand-teams-that-manage-bugs-instead-of-fixing-them/ Teams should focus on fixing bugs as soon as they are found instead of managing or prioritising them in backlogs or meetings. Delaying bug fixes leads to bigger problems and undermines the goal of delivering working software. Development managers should ensure their teams address defects promptly rather than letting them accumulate. https://engineering-leadership-preview.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-preview.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-preview.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-preview.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-preview.hinshelwood.com/videos/transforming-technical-debt-unlocking-innovation-and-value-through-quality-product-delivery/ Thu, 21 Nov 2024 17:01:52 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/transforming-technical-debt-unlocking-innovation-and-value-through-quality-product-delivery/ Technical debt is more than just a cost; it represents missed opportunities for innovation and value. Allowing technical debt to persist leads to higher maintenance costs, slower delivery, and lower team morale, while prioritising high-quality product delivery enables greater agility, consistent value, and innovation. Development managers should regularly assess and address technical debt, foster a culture of quality, and communicate its impact to stakeholders to unlock their teams’ full potential. https://engineering-leadership-preview.hinshelwood.com/articles/how-lack-of-agency-is-killing-your-devops-initiatives/ Mon, 16 Jun 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/how-lack-of-agency-is-killing-your-devops-initiatives/ DevOps only works when developers have real control over production environments, deployments, and telemetry; without this operational agency, automation just creates fragile systems and blocks learning from real user feedback. Most DevOps efforts fail because they focus on tools instead of empowering developers to deploy, monitor, and adapt in production. To succeed, give your teams full operational ownership so they can deliver value continuously and respond quickly to real-world issues. https://engineering-leadership-preview.hinshelwood.com/signals/branch-promotion-is-a-relic-of-slow-manual-software-delivery/ Sat, 08 Feb 2025 16:30:00 +0000 https://engineering-leadership-preview.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-preview.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-preview.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-preview.hinshelwood.com/signals/too-many-teams-overcomplicate-their-branching-strategies/ Thu, 06 Feb 2025 09:38:01 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/too-many-teams-overcomplicate-their-branching-strategies/ Many teams make branching too complex, which slows delivery and adds risk. Simple models like GitHub Flow or Release Flow help teams move faster and deliver value more consistently. Focus on minimizing branching complexity to improve speed and reliability. https://engineering-leadership-preview.hinshelwood.com/videos/is-your-project-ecosystem-truly-agile/ Wed, 31 Jul 2024 06:45:01 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/is-your-project-ecosystem-truly-agile/ Having Agile development teams is not enough if your deployment processes remain slow and bureaucratic, as this creates delays, reduces value, and frustrates teams. Automating deployment and testing, implementing CI/CD pipelines, and shortening feedback loops are essential to achieving true end-to-end agility and maximizing stakeholder value. Review your current processes for bottlenecks, start automating where possible, and involve stakeholders early and often to ensure your entire project ecosystem is genuinely Agile. https://engineering-leadership-preview.hinshelwood.com/signals/we-don-t-have-time-for-automation-but-manual-testing-slows-releases-and-quality/ Mon, 07 Apr 2025 15:30:01 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/we-don-t-have-time-for-automation-but-manual-testing-slows-releases-and-quality/ Relying on manual testing slows releases, overwhelms testers, and lets bugs slip through, making it impossible to keep up with rapid changes. Automation is essential for maintaining both speed and quality in software development. Teams should prioritize moving to automated testing to avoid bottlenecks and improve release reliability. https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/videos/unlocking-code-quality-the-transformative-power-of-frequent-deployments/ Mon, 13 Jan 2025 06:45:00 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/getting-started-with-a-definition-of-done-dod/ Mon, 14 Dec 2020 13:03:00 +0000 https://engineering-leadership-preview.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-preview.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-preview.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-preview.hinshelwood.com/videos/the-evolution-of-my-journey-with-azure-devops-lessons-and-insights/ Wed, 31 Jul 2024 09:21:03 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/the-evolution-of-my-journey-with-azure-devops-lessons-and-insights/ Azure DevOps has evolved from TFS to a powerful, flexible platform that can transform team workflows, but successful adoption and migration require careful planning and sometimes custom solutions. Key lessons include the importance of assessing your environment, choosing the right migration tools, and leveraging expert guidance for complex needs. Development managers should ensure their teams are trained and consider consulting support to maximize the benefits and scalability of Azure DevOps. https://engineering-leadership-preview.hinshelwood.com/signals/staging-environments-do-not-prevent-production-failures/ Fri, 28 Feb 2025 16:30:01 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/all-technical-debt-is-a-risk-to-the-product-and-to-your-business/ Mon, 25 Jan 2021 14:55:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/all-technical-debt-is-a-risk-to-the-product-and-to-your-business/ Technical debt is a significant risk to your product and business, as it undermines quality, slows delivery, and can accumulate unnoticed until it becomes a major problem. The Microsoft Team Foundation Server example shows that ignoring technical debt leads to reduced productivity and competitiveness, while addressing it through transparency and shorter feedback cycles enables faster, higher-quality delivery. Development managers should prioritize eliminating technical debt and fostering a culture of quality to protect business value and avoid long-term risks. https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-developer-net-training-in-london/ Fri, 18 Jun 2010 15:53:27 +0000 https://engineering-leadership-preview.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-preview.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-preview.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-preview.hinshelwood.com/videos/security-by-design-building-secure-software/ Tue, 26 Nov 2024 13:35:33 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/security-by-design-building-secure-software/ Shifting left means building quality and security into software from the start by making developers responsible for testing, integrating expertise early, and using practices like test-driven development and continuous feedback. Although it may feel slower at first, this approach reduces long-term costs, technical debt, and enables faster, higher-quality delivery as shown by Azure DevOps’ transformation. Development managers should invest in shift-left practices now to empower teams, improve products, and accelerate innovation. https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/articles/testing-in-the-modern-application-lifecycle/ Tue, 25 Sep 2012 02:00:46 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/testing-in-the-modern-application-lifecycle/ Explores challenges and solutions for manual testing in agile software development, focusing on tracking, automation, actionable bugs, and integrated test management tools. https://engineering-leadership-preview.hinshelwood.com/articles/create-a-release-management-pipeline-for-professional-developers/ Thu, 04 Dec 2014 12:15:56 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/engineering-notes/how-i-used-generative-ai-to-transform-site-tagging-and-categories/ Thu, 15 May 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/engineering-notes/how-i-used-generative-ai-to-transform-site-tagging-and-categories/ Migrating a large, legacy blog to Hugo enabled the use of generative AI for automated tagging and categorisation, significantly improving content discoverability and editorial consistency while reducing manual effort. The system combines AI-driven suggestions with human oversight, using multi-factor scoring, penalty logic, and transparent reasoning to ensure quality and accountability. Development managers considering similar automation should maintain human control over final decisions and leverage AI to streamline, not replace, editorial processes. https://engineering-leadership-preview.hinshelwood.com/articles/quality-enablement-with-visual-studio-2012/ Wed, 15 May 2013 03:13:20 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/standard-environments-for-automated-deployment-and-testing/ Sun, 17 Mar 2013 06:23:45 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/automated-testing-in-a-modern-application-lifecycle/ Tue, 25 Sep 2012 04:33:30 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/introducing-kanban-for-professional-scrum-teams/ Mon, 26 Feb 2018 15:00:08 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/introducing-kanban-for-professional-scrum-teams/ A new Professional Scrum with Kanban class and guide now enable Scrum teams to integrate Kanban practices like workflow visualization, limiting work in progress, and flow-based metrics without changing Scrum itself. This approach helps teams focus on value delivery and can replace traditional metrics like velocity with more actionable measures such as throughput and cycle time. Development managers should consider reviewing the Kanban Guide for Scrum Teams and exploring the training to enhance their teams’ effectiveness. https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-superpower-of-software-development-how-shifting-left-transforms-quality-assurance/ Fri, 22 Nov 2024 14:04:14 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-superpower-of-software-development-how-shifting-left-transforms-quality-assurance/ Shifting quality assurance to the start of the development process leads to higher product quality, faster delivery, and lower costs by catching issues early and fostering better collaboration. Teams that adopt this approach see improved morale and stakeholder confidence. To get started, educate your team, involve QA early, encourage collaboration, use automation, and focus on continuous improvement. https://engineering-leadership-preview.hinshelwood.com/articles/unit-testing-against-the-team-foundation-server-2012-api/ Mon, 02 Apr 2012 03:52:55 +0000 https://engineering-leadership-preview.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-preview.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-preview.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-preview.hinshelwood.com/articles/developer-day-scotland/ Sun, 03 May 2009 21:42:33 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/developer-day-scotland/ Summary of sessions from a Glasgow developer event, covering refactoring, dynamic languages in .NET, MVVM for WPF, architecture, and ASP.NET 4.0 insights. https://engineering-leadership-preview.hinshelwood.com/videos/confronting-incompetence-how-to-stop-shipping-bad-code-and-tackle-technical-debt-effectively/ Tue, 26 Nov 2024 13:55:20 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/confronting-incompetence-how-to-stop-shipping-bad-code-and-tackle-technical-debt-effectively/ Shipping bad code is not just technical debt but a sign of deeper issues that teams must address by committing to quality and accountability. Key actions include enforcing thorough code reviews, investing in automated testing, and making regular refactoring a habit, while also actively identifying, prioritising, and allocating time to pay down technical debt. Development managers should ensure their teams distinguish between technical debt and poor practices, and dedicate resources to maintain a healthy, sustainable codebase. https://engineering-leadership-preview.hinshelwood.com/articles/team-foundation-build-2012-issue-the-target-cleanworkspacepackagetempdir-does-not-exist/ Sat, 20 Oct 2012 17:30:11 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/team-foundation-build-2012-issue-the-target-cleanworkspacepackagetempdir-does-not-exist/ Explains how to resolve the “CleanWorkspacePackageTempDir does not exist” build error in Team Foundation Build 2012 for upgraded ASP.NET MVC projects by updating project targets. https://engineering-leadership-preview.hinshelwood.com/articles/log-elmah-errors-in-team-foundation-server/ Sun, 26 Jul 2009 22:30:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/log-elmah-errors-in-team-foundation-server/ Explains how to log Elmah error reports as work items in Team Foundation Server, including attaching error logs, using templates, and retrieving error details. https://engineering-leadership-preview.hinshelwood.com/articles/in-place-upgrade-of-tfs-2008-to-tfs-2010-with-move-to-new-domain/ Tue, 19 Apr 2011 17:57:41 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/in-place-upgrade-of-tfs-2008-to-tfs-2010-with-move-to-new-domain/ Step-by-step guide to upgrading Team Foundation Server 2008 to 2010, including in-place upgrade, build server update, and migrating to a new domain with key troubleshooting tips. https://engineering-leadership-preview.hinshelwood.com/engineering-notes/leveraging-ai-embeddings-for-related-content-classification/ Wed, 04 Jun 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/engineering-notes/leveraging-ai-embeddings-for-related-content-classification/ Switching from Hugo’s basic related content feature to an AI embeddings-based approach enabled much more accurate and meaningful content recommendations, improving both user navigation and AI discoverability. The solution was cost-effective, scalable, and reduced computational overhead by caching similarity scores and storing embeddings for reuse. Development managers can consider using AI embeddings for smarter content linking, which can enhance user experience and support future automation or classification needs. https://engineering-leadership-preview.hinshelwood.com/articles/creating-a-wit-adapter-for-the-tfs-integration-platform-for-a-source-with-no-history/ Thu, 02 Jun 2011 11:25:32 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/creating-a-wit-adapter-for-the-tfs-integration-platform-for-a-source-with-no-history/ Explains how to build a TFS Integration Platform Work Item Tracking (WIT) adapter for a source system without history, covering versioning, field mapping, and error handling. https://engineering-leadership-preview.hinshelwood.com/articles/reserve-an-agent-for-a-special-build-in-team-foundation-server-2012/ Thu, 04 Apr 2013 01:37:57 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/reserve-an-agent-for-a-special-build-in-team-foundation-server-2012/ Explains how to reserve a build agent in Team Foundation Server 2012 using custom activities, agent tagging, and workflow changes to ensure reliable, isolated build execution. https://engineering-leadership-preview.hinshelwood.com/articles/migrating-data-from-fogbugz-to-tfs-2012-using-the-tfs-integration-platform/ Tue, 17 Jul 2012 00:54:29 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/migrating-data-from-fogbugz-to-tfs-2012-using-the-tfs-integration-platform/ Step-by-step guide to migrating FogBugz data to TFS 2012 using a custom CSV adapter with the TFS Integration Platform, including setup, mapping, and import tips. https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-from-tfs-2008-and-wss-v3-0-with-sftsv2-to-tfs-2010-and-sf-2010-with-sftsv3/ Thu, 30 Jun 2011 15:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-from-tfs-2008-and-wss-v3-0-with-sftsv2-to-tfs-2010-and-sf-2010-with-sftsv3/ Step-by-step guide to upgrading TFS 2008 and WSS v3.0 with SfTSv2 to TFS 2010 and SharePoint 2010, including process template migration and data handling. https://engineering-leadership-preview.hinshelwood.com/articles/configuring-a-dc-in-azure-for-aad-integrated-release-management/ Fri, 14 Nov 2014 15:24:52 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/configuring-a-dc-in-azure-for-aad-integrated-release-management/ Setting up a domain controller in Azure for Azure Active Directory integrated release management enables realistic cloud-based demos and infrastructure. The process involves creating a virtual machine, installing Active Directory and DNS roles, configuring a static IP, and promoting the VM to a domain controller, after which you can scale down resources to save costs. This approach provides a practical, cost-effective way to build and manage cloud-based environments for development and training; consider adopting similar steps for your own cloud infrastructure needs. https://engineering-leadership-preview.hinshelwood.com/articles/team-foundation-server-2010-event-handling-with-subscribers/ Thu, 16 Sep 2010 14:28:20 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/team-foundation-server-2010-event-handling-with-subscribers/ Explains how to create and deploy server-side event subscribers in Team Foundation Server 2010 using the ISubscriber interface to handle and process TFS events. https://engineering-leadership-preview.hinshelwood.com/articles/solution-seo-permanent-redirects-for-old-url-s/ Mon, 04 Jan 2010 02:34:55 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/solution-seo-permanent-redirects-for-old-url-s/ Explains how to set up SEO-friendly permanent redirects for old URLs to new ones in ASP.NET, covering best practices and code examples for preserving search rankings. https://engineering-leadership-preview.hinshelwood.com/articles/wpf-ninject-dojo-the-data-provider/ Tue, 25 Aug 2009 14:43:35 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/wpf-ninject-dojo-the-data-provider/ Explains how to use a custom NinjectDataProvider in WPF to enable dependency injection for ViewModels, improving flexibility and design-time support in MVVM projects. https://engineering-leadership-preview.hinshelwood.com/articles/creating-a-data-access-layer-using-unity/ Thu, 30 Jul 2009 04:57:53 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/creating-a-data-access-layer-using-unity/ Learn how to build a flexible data access layer in .NET using Unity for dependency injection, interface mapping, and factory patterns with configuration support. https://engineering-leadership-preview.hinshelwood.com/articles/creating-a-wpf-work-item-control/ Fri, 19 Sep 2008 12:14:21 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/creating-a-wpf-work-item-control/ Learn how to build a custom WPF work item control for Visual Studio Team System, enabling WPF UI integration in work item forms using a generic wrapper and IWorkItemControl. https://engineering-leadership-preview.hinshelwood.com/articles/creating-wcf-service-host-programmatically/ Wed, 30 May 2007 00:23:24 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/creating-wcf-service-host-programmatically/ Explains how to programmatically create and configure a WCF Service Host in .NET, including base addresses, endpoints, bindings, and service behaviours for secure hosting. https://engineering-leadership-preview.hinshelwood.com/tags/agentic-engineering/ Tue, 22 Jul 2025 15:58:00 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/site-reliability-engineering/ Mon, 05 May 2025 10:17:24 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/definition-of-done/ Mon, 05 May 2025 09:00:00 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/system-configuration/ Wed, 09 Apr 2025 13:08:13 +0100 https://engineering-leadership-preview.hinshelwood.com/tags/system-configuration/ System Configuration encompasses the technical setup and optimisation of software, hardware, and systems to ensure efficient and reliable operation. It is essential in Agile and DevOps environments, where the need for speed, efficiency, and flexibility is critical. This process establishes a robust foundation for operational performance, allowing teams to deliver high-quality products in a predictable and sustainable manner. Central to System Configuration are tools that automate and manage the integration of system components, such as Ansible, Chef, Puppet, and Terraform, which facilitate infrastructure as code and ensure consistent configurations across various environments. By optimising hardware and software components to work seamlessly together, System Configuration minimises bottlenecks and supports continuous integration and continuous delivery by automating testing, deployment, and monitoring. Its importance lies in enhancing workflow efficiency, fostering collaboration among teams, and reducing time spent on manual tasks, thereby allowing teams to concentrate on innovation and value creation. Furthermore, effective System Configuration is crucial for scaling Agile practices within larger organisations, as it ensures that systems are properly configured from the beginning, leading to efficient scaling with minimal disruption. Ultimately, System Configuration provides the tools and processes necessary for organisations to improve performance, reduce operational overhead, and maintain adaptable and scalable systems in a rapidly evolving landscape. https://engineering-leadership-preview.hinshelwood.com/tags/test-first-development/ Tue, 25 Mar 2025 07:40:33 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/categories/devops/ Thu, 20 Mar 2025 11:04:38 +0000 https://engineering-leadership-preview.hinshelwood.com/categories/devops/ DevOps is a philosophy that integrates people, processes, and technology to facilitate continuous value delivery in software development. Originating from the need to bridge the gap between development and operations, it emphasises collaboration and automation to enhance the quality and speed of software delivery. The core principles of DevOps prioritise flow efficiency over mere resource utilisation, advocate for rapid feedback loops to align with customer needs, and promote automation to minimise errors and delays. Additionally, it fosters shared accountability among developers, operations, and security teams, ensuring collective responsibility for product quality. DevOps encourages a culture of continuous improvement, where teams are committed to experimentation and adaptation. In practice, organisations embracing DevOps focus on eliminating silos, integrating quality and security measures early in the development process, leveraging data for informed decision-making, and automating as many processes as possible. This approach is crucial in agile and DevOps environments as it enables organisations to deliver software more reliably and efficiently, ultimately enhancing their ability to respond to market demands and customer expectations. DevOps is viewed not as a final goal but as an ongoing journey towards improved software delivery. https://engineering-leadership-preview.hinshelwood.com/tags/shift-left-strategy/ Mon, 17 Mar 2025 14:46:11 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/internal-developer-platform/ Mon, 24 Feb 2025 13:04:45 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/acceptance-test-driven-development/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/automated-testing/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/azure-pipelines/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/azure-repos/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/azure-repos/ Azure Repos is a cloud-based source control service within the Azure DevOps ecosystem, designed to help teams manage their code repositories efficiently. It supports both Git and Team Foundation Version Control (TFVC), allowing teams to select the version control system that aligns with their specific workflows. By providing a centralised platform for code collaboration, Azure Repos integrates seamlessly with other Azure DevOps services, such as Azure Pipelines and Azure Boards, thereby enhancing the overall development lifecycle. Its significance lies in its ability to promote collaboration among team members, enabling concurrent work on code while minimising conflicts, which is essential for delivering value in a predictable and sustainable manner. Features like pull requests, branch policies, and code reviews help maintain code quality while facilitating rapid iteration and innovation. Additionally, Azure Repos fosters a culture of transparency and accountability by tracking changes and maintaining a clear history of contributions. This systemic approach to source control streamlines development processes and aligns with agile principles, promoting adaptability and responsiveness to change. By integrating with various tools and practices, Azure Repos empowers teams to focus on delivering high-quality software that effectively meets customer needs. https://engineering-leadership-preview.hinshelwood.com/tags/continuous-integration/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/categories/engineering-excellence/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/categories/engineering-excellence/ Engineering excellence is a critical framework for achieving high-quality, maintainable, and scalable software systems, emphasising a culture of continuous improvement and technical rigor. Originating from the need for organisations to enhance their engineering standards, this approach focuses on delivering predictable, resilient, and valuable software. Its importance lies in several key areas: ensuring quality by driving consistency and reliability, reducing risk through early issue identification, enhancing scalability for long-term growth, improving efficiency in development processes, and strengthening collaboration among teams. Core principles of engineering excellence include software craftsmanship, which prioritises clarity and adaptability; modern software engineering practices that promote continuous validation and automation; proactive technical debt management to maintain code health; metrics and observability for data-driven improvements; and embedding security and compliance into development processes. Additionally, it advocates for scalable and resilient architecture to support sustainable evolution in response to changing demands. By adopting these principles, organisations can foster an environment that not only meets current software needs but also adapts to future challenges, ultimately driving success in agile, DevOps, and product development contexts. https://engineering-leadership-preview.hinshelwood.com/tags/engineering-practices/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/modern-source-control/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/modern-source-control/ Modern source control is a critical practice in software development that focuses on version control and branching strategies to manage codebase changes effectively. Originating from the need for collaborative coding, it utilises systems like Git to allow multiple developers to work simultaneously without conflicts, while also enabling the tracking of modifications, reverting to previous states, and maintaining a comprehensive development history. This practice is vital as it enhances a team’s ability to deliver value in a predictable and sustainable manner, facilitating the implementation of continuous integration and continuous delivery (CI/CD) pipelines that promote rapid feedback and reduced lead times. Such agility empowers organisations to swiftly adapt to market demands and customer feedback, fostering innovation. Additionally, modern source control encourages a systematic approach to development through branching strategies, such as feature branches or trunk-based development, which support parallel workstreams and minimise disruptions to the main codebase. This not only improves collaboration but also helps in managing technical debt by allowing teams to isolate and resolve issues more efficiently. By integrating these practices into their workflows, organisations can cultivate a resilient development environment that prioritises quality and efficiency, ultimately contributing to long-term success in product delivery. https://engineering-leadership-preview.hinshelwood.com/tags/technical-debt/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/categories/technical-leadership/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/categories/technical-leadership/ Technical leadership refers to the practice of guiding development teams by leveraging technical expertise and agile methodologies to enhance their performance and output. Originating from the need for effective direction in software development, it is employed to ensure that teams can deliver value in a predictable and sustainable manner. This role is vital in the context of agile, DevOps, and product development as it fosters an environment conducive to innovation and continuous improvement. Technical leaders help teams navigate complex challenges, ensuring that technical decisions are aligned with both organisational objectives and customer requirements. They promote long-term thinking and systemic approaches, enabling the creation of adaptable solutions. By cultivating a culture of experimentation and learning, technical leaders facilitate collaboration across various disciplines, breaking down silos and encouraging shared ownership of project outcomes. Distinct from Agile leadership, which focuses on team dynamics, technical leadership prioritises the technical skills necessary for informed decision-making regarding architecture, design, and implementation. This focus on empowering teams to pursue technical excellence not only enhances the quality of deliverables but also strengthens the organisation’s capacity to respond effectively to market changes and customer feedback, ultimately contributing to long-term success and resilience in a fast-paced environment. https://engineering-leadership-preview.hinshelwood.com/tags/technical-mastery/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/test-automation/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/test-driven-development/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/application-lifecycle-management/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/application-lifecycle-management/ Application Lifecycle Management (ALM) is the systematic approach to managing software applications throughout their entire lifecycle, from initial development to eventual retirement. Originating from the need for structured processes in software development, ALM integrates various practices, tools, and team collaboration to streamline workflows and enhance communication. Its importance lies in its ability to provide organisations with a comprehensive view of application development, aligning technical efforts with business goals while remaining adaptable to evolving requirements. By implementing methodologies such as continuous integration and continuous delivery, ALM fosters rapid feedback and iterative enhancements, which are critical in dynamic environments. This approach not only reduces deployment risks but also cultivates a culture of accountability and transparency within teams. Furthermore, ALM aids organisations in effectively managing their application portfolios, ensuring optimal resource allocation and proactive technical debt management. This long-term focus is essential for driving innovation and maintaining a competitive edge, as it allows teams to concentrate on delivering high-quality software that satisfies user demands and contributes to overall business success. The synergy between ALM and frameworks like Agile and DevOps amplifies its impact, establishing a solid foundation for ongoing improvement and value creation. https://engineering-leadership-preview.hinshelwood.com/tags/platform-engineering/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/platform-engineering/ Platform Engineering is the discipline focused on the design, construction, and maintenance of internal platforms that empower developers to deliver value independently, reliably, and swiftly. Originating from the need to streamline software development processes, it aims to alleviate cognitive load by abstracting the complexities of infrastructure and operations through well-crafted interfaces, tools, and APIs. This approach treats platforms as products, ensuring clear ownership, regular feedback, and ongoing enhancements based on developer requirements. A robust platform engineering capability fosters paved paths and self-service tools that facilitate secure, observable, and resilient software delivery while avoiding constraints that stifle innovation. By creating an environment conducive to rapid feedback, safe experimentation, and autonomous delivery across teams, Platform Engineering not only provides essential tools but also cultivates a cohesive developer experience that aligns with organisational strategy, ultimately enabling continuous value delivery at scale. https://engineering-leadership-preview.hinshelwood.com/tags/technical-excellence/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership-preview.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. https://engineering-leadership-preview.hinshelwood.com/tags/agentic-software-delivery/ Tue, 21 Jan 2025 10:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/agentic-software-delivery/ Agentic Software Delivery is a strategy for continuously achieving business outcomes through the deliberate integration of autonomous AI agents, human expertise, and organisational context. It is not about automation for automation’s sake, but about enabling teams to move faster and smarter by embedding proactive, context-aware intelligence into their systems of work. The term ‘agentic’ implies more than assistance, it implies agency. These agents operate autonomously within defined boundaries, learning from data, adapting to patterns, and making context-informed decisions. They contribute meaningfully to outcomes across discovery, development, delivery, and operations. This approach relies on the synergy between domain experts and AI agents, requiring lean, empirical systems of work, strong product strategy, and modern engineering practices such as CI/CD, observability, infrastructure as code, and automated testing.