https://engineering-leadership-preview.hinshelwood.com/categories/engineering-excellence/ Recent content in Engineering Excellence on Engineering Leadership in AI & Software Hugo en Tue, 16 Jun 2026 17:40:35 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/telling-people-what-to-do-is-not-leadership-it-s-a-failure-of-system-design/ Mon, 04 Aug 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/telling-people-what-to-do-is-not-leadership-it-s-a-failure-of-system-design/ Telling people what to do is not leadership, it is a sign of poor system design that stifles autonomy and slows delivery. Effective leadership means creating systems where teams have clear goals, constraints, and feedback loops so they can self-manage, deliver value, and adapt without micromanagement. Focus on improving your delivery system, set meaningful goals, enable autonomy with clear boundaries, use evidence-based metrics, and empower teams to own outcomes, so you can step back and let professionals do their best work. 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/don-t-manage-dependencies-remove-them/ Mon, 29 Sep 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/don-t-manage-dependencies-remove-them/ Dependencies are not inevitable but are usually caused by poor system design; instead of managing them, focus on removing them by aligning work, teams, and architecture, making contracts explicit, and clarifying ownership. Only manage the rare dependencies that remain, treating them as design flaws to be fixed, not as normal work. Leadership should prioritise redesigning systems to eliminate dependencies, which leads to faster delivery, fewer defects, and higher team autonomy. https://engineering-leadership-preview.hinshelwood.com/articles/flow-of-value-vs-flow-of-work/ Mon, 15 Sep 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/flow-of-value-vs-flow-of-work/ The phrase “flow of value” is often misused in software development, as value is only confirmed when customers validate it, not just when work is completed. Teams should focus on validating outcomes quickly, breaking work into small, testable increments, and using data to cut features that do not deliver real value. To truly optimise value, ensure every item has a clear hypothesis, measure time to feedback, and prioritise learning over simply moving work through the 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/rethinking-capacity-planning/ Mon, 21 Jul 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/rethinking-capacity-planning/ Capacity planning should focus on optimising system flow and predictability, not tracking individual hours or task assignments. Shifting from micromanagement to managing work as a system at portfolio, category, and team levels helps prevent overload, improves value delivery, and enables reliable forecasting. Development managers should prioritise system-level metrics, enforce work-in-progress limits, and empower teams to pull well-prepared work, creating sustainable and predictable delivery. 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/why-outsourcing-devops-fails-and-how-real-engineering-excellence-starts-with-your-team/ Mon, 15 Sep 2025 06:30:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-outsourcing-devops-fails-and-how-real-engineering-excellence-starts-with-your-team/ Outsourcing DevOps often leads to vendor lock-in, legacy systems, and teams that cannot maintain or evolve their own tools. Real engineering excellence comes from building internal capability through partnership, where experts mentor and guide your team to modernize workflows and systems themselves. Invest in developing your engineers’ skills and mindset so your organization can achieve sustainable progress and avoid costly dependencies. https://engineering-leadership-preview.hinshelwood.com/articles/the-estimation-trap-how-tracking-accuracy-undermines-trust-flow-and-value-in-software-delivery/ Mon, 22 Sep 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/the-estimation-trap-how-tracking-accuracy-undermines-trust-flow-and-value-in-software-delivery/ Focusing on estimation accuracy as a performance metric leads to fear, gaming, and a culture of compliance rather than real improvement, which undermines trust, innovation, and actual value delivery. Research shows that when teams are judged on how closely they meet estimates, they pad numbers, hide risks, and avoid complex work, resulting in false success and missed opportunities for learning. Instead, shift attention to evidence-based metrics that reflect customer value, system health, and delivery flow, and use estimates only to support learning and informed conversations, not as tools for control. https://engineering-leadership-preview.hinshelwood.com/articles/the-definition-of-done-is-a-commitment-to-quality/ Mon, 28 Jul 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/the-definition-of-done-is-a-commitment-to-quality/ A clear, shared Definition of Done is essential for delivering quality, releasable software in Scrum and aligns teams on what “complete” means. It ensures transparency, predictability, and accountability, protects your product’s reputation, and must be created, automated, and regularly improved by all teams working on a product. Development managers should prioritise running DoD workshops, making standards visible, automating checks, and reviewing the DoD every sprint to maintain quality and reduce risk. https://engineering-leadership-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/signals/velocity-isn-t-how-many-story-points-a-team-burns-down/ Mon, 10 Mar 2025 16:30:02 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/velocity-isn-t-how-many-story-points-a-team-burns-down/ Velocity is about how quickly your team delivers value, not just story points completed. Focus on measuring time to build, self-test, deploy, and learn from user feedback, as these are actionable and within your control. Start tracking these metrics to improve your delivery speed and effectiveness. https://engineering-leadership-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/articles/should-you-use-one-project-to-rule-them-all-in-azure-devops/ Mon, 25 Aug 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/should-you-use-one-project-to-rule-them-all-in-azure-devops/ Using a single Azure DevOps project for all teams and products reduces fragmentation, improves visibility, and streamlines governance compared to managing multiple projects or organisations. Key benefits include unified reporting, easier collaboration, and lower administrative overhead, while Area Paths and Teams provide the necessary structure and security within one project. Development managers should consolidate into one project where possible, using Area Paths and Teams to model structure and scale, to optimise flow and delivery. https://engineering-leadership-preview.hinshelwood.com/videos/why-done-only-counts-when-it-s-live-moving-beyond-fake-finishes-to-real-value-in-software-delivery/ Wed, 07 May 2025 11:46:58 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-done-only-counts-when-it-s-live-moving-beyond-fake-finishes-to-real-value-in-software-delivery/ Work is only truly done when it is live in production and delivering value to users, not just when code is written, tested, or demoed. Teams often mistake internal milestones for real progress, which delays learning and frustrates stakeholders; real feedback and value come only from live usage and telemetry. Development managers should redefine “done” as live in production, invest in automation to shorten release cycles, and focus on measuring and celebrating actual user impact. https://engineering-leadership-preview.hinshelwood.com/articles/release-planning-and-predictable-delivery/ Tue, 24 Nov 2020 13:00:01 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/release-planning-and-predictable-delivery/ Predictable delivery and agile release planning are not incompatible, but achieving them requires a shift in mindset, a focus on continuous quality, and embracing transparency. Key actions include making quality non-negotiable, refining backlog items to be small and clear, ensuring teams own the full delivery process, and minimizing dependencies. Development managers should prioritize building working software in regular increments, stop accumulating technical debt, and foster a culture of continuous improvement to improve delivery predictability. 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/articles/work-can-flow-across-the-sprint-boundary/ Tue, 30 Jan 2018 20:12:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/work-can-flow-across-the-sprint-boundary/ Allowing work to flow across Sprint boundaries is permitted in Scrum and can improve delivery speed, responsiveness, and value, as long as teams maintain clear, outcome-focused Sprint Goals and consistently deliver Done increments. Adopting practices like Continuous Delivery, feature toggles, and frequent feedback helps teams validate work early and adapt quickly. Development managers should encourage flow principles and robust engineering practices to maximize throughput and support better business decisions. https://engineering-leadership-preview.hinshelwood.com/articles/are-we-still-pretending-coding-was-the-bottleneck/ Mon, 01 Sep 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/are-we-still-pretending-coding-was-the-bottleneck/ AI writing code is not the real game-changer; coding was never the main bottleneck in software delivery. The real constraints are in poor system design, handoffs, unclear requirements, and lack of built-in quality, which AI will only make more visible. To benefit from AI, focus on improving flow, building quality in from the start, and making teams accountable for outcomes rather than output. https://engineering-leadership-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/videos/why-your-definition-of-done-is-the-secret-weapon-your-team-needs-to-win/ Wed, 16 Jul 2025 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-your-team-needs-to-win/ Many teams struggle not with building software but with finishing it in a way that delivers real business value. A clear, evolving definition of done protects revenue, boosts customer satisfaction, reduces rework, and builds trust by ensuring work is truly complete and valuable. Make your definition of done visible, review it regularly with the whole team, and connect it to real outcomes to turn it into a competitive advantage. https://engineering-leadership-preview.hinshelwood.com/videos/acceptance-criteria-vs-definition-of-done-why-getting-this-right-builds-trust-and-delivers-quality-faster/ Wed, 02 Jul 2025 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/acceptance-criteria-vs-definition-of-done-why-getting-this-right-builds-trust-and-delivers-quality-faster/ Acceptance criteria specify what each backlog item must do, while the definition of done sets the minimum quality standards for all work. Confusing the two leads to missed requirements, technical debt, and loss of trust. Make both explicit and review them regularly to ensure faster delivery and consistent quality. 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/videos/why-your-definition-of-done-is-the-secret-weapon-for-real-business-impact-and-agile-growth/ Wed, 18 Jun 2025 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-for-real-business-impact-and-agile-growth/ A strong definition of done is crucial for delivering real business value, not just completing tasks. When done means features are live, usable, and measured for impact, teams deliver value faster, reduce risk, and become more adaptable. Make your definition of done visible, connect it to measurable outcomes, and continuously refine it to drive growth and true agility. 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/signals/every-delay-increases-the-risk-of-failure/ Mon, 10 Feb 2025 11:00:51 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/every-delay-increases-the-risk-of-failure/ Delaying software releases increases the risk of failure and falling behind competitors. Frequent, smaller releases lead to higher success rates and faster recovery, as shown by industry research. Focus on delivering quickly and iterating rather than waiting for a perfect release. 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/building-a-culture-of-quality/ Fri, 22 Nov 2024 07:00:08 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/building-a-culture-of-quality/ A culture of quality cannot be built by one person; it requires everyone in the organization to demonstrate and model technical excellence and leadership. Focusing only on revenue, as seen in Boeing’s decline, undermines quality and can lead to dangerous outcomes, while a strong culture of quality leads to better, safer products. Development managers should prioritize building and reinforcing engineering excellence and technical leadership across teams, using frameworks and tools as enablers rather than solutions. https://engineering-leadership-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/scrum-doesn-t-stop-you-from-optimising-flow/ Sun, 25 May 2025 15:30:23 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/ Scrum allows you to optimise workflow as long as you maintain accountability through a Sprint Goal and a Done Increment. If your team already delivers quality software continuously and meets these standards, you do not need to force all work to finish within strict Sprint timelines. Focus on outcomes and professionalism rather than rigid rules, and let work flow naturally if your processes support it. https://engineering-leadership-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/videos/cultivating-a-culture-of-quality-lessons-from-boeing-and-volkswagen-for-engineering-excellence/ Fri, 29 Nov 2024 07:00:17 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/cultivating-a-culture-of-quality-lessons-from-boeing-and-volkswagen-for-engineering-excellence/ A strong culture of quality and technical excellence is essential for building reliable and valuable software products, as shown by the negative consequences at Boeing and Volkswagen when profit was prioritised over quality. Relying solely on frameworks like Agile is not enough; the real difference comes from collective commitment to quality, ethical leadership, and applying sound engineering principles. Development managers should focus on fostering this culture within their teams to ensure long-term success and avoid costly mistakes. https://engineering-leadership-preview.hinshelwood.com/articles/a-better-way-than-staggered-iterations-for-delivery/ Thu, 10 Dec 2020 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/a-better-way-than-staggered-iterations-for-delivery/ Staggered iterations slow feedback, increase technical debt, and reduce software quality, making delivery less agile and more expensive. Instead, form cross-functional teams that deliver working software every iteration, integrate all required work including testing into each sprint, and automate as much as possible. Shift away from staged handoffs to continuous, team-owned delivery to improve value and quality. https://engineering-leadership-preview.hinshelwood.com/articles/without-delivery-there-is-no-value/ Mon, 10 Feb 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/without-delivery-there-is-no-value/ Value in software is only realised when products are delivered to users, so frequent releases are essential to validate assumptions, gather feedback, and adapt quickly. Delaying delivery increases costs, risks, and missed opportunities, while research shows that teams releasing often are more successful and resilient. Development managers should prioritise short feedback loops and empower teams to release working software regularly to maximise value and minimise waste. 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/detecting-agile-bs-lessons-from-the-department-of-defense/ Fri, 02 Aug 2024 06:45:02 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/detecting-agile-bs-lessons-from-the-department-of-defense/ Adopting Agile development practices is not enough if the rest of your organization remains slow and bureaucratic; true agility requires continuous delivery, high product quality, and minimal manual or bureaucratic steps across the entire process. Use the Department of Defense’s six-question test to assess your real agility, and focus on automating testing, streamlining deployment, and building quality in from the start. Regularly review and improve your processes to eliminate bottlenecks and ensure your whole ecosystem supports rapid, reliable delivery. 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/videos/mastering-sustainable-scaling-overcoming-product-development-challenges-with-naked-agility/ Fri, 28 Feb 2025 06:00:27 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/mastering-sustainable-scaling-overcoming-product-development-challenges-with-naked-agility/ Scaling product development is complex and requires more than just adding people; it demands clear priorities, strong leadership, and systems designed for growth. Naked Agility helps organisations address common scaling challenges like alignment, technical debt, and slow feedback by eliminating bottlenecks, using data-driven decisions, and tailoring strategies to each team’s needs. To scale effectively without sacrificing speed or quality, focus on building a culture and systems that support sustainable growth. https://engineering-leadership-preview.hinshelwood.com/videos/scaling-smart-how-to-tackle-technical-debt-for-sustainable-growth/ Tue, 25 Feb 2025 06:00:28 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/scaling-smart-how-to-tackle-technical-debt-for-sustainable-growth/ Unchecked technical debt slows development, increases bugs, and reduces team productivity, making scaling risky and inefficient. Addressing weak points through sustainable architecture, automated testing, and continuous integration enables faster feedback, more reliable releases, and confident growth. Development managers should prioritize managing technical debt and automation to support sustainable scaling and maintain innovation. https://engineering-leadership-preview.hinshelwood.com/videos/transforming-agility-how-azure-devops-went-from-two-year-releases-to-880-000-deployments/ Thu, 06 Feb 2025 10:20:34 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/transforming-agility-how-azure-devops-went-from-two-year-releases-to-880-000-deployments/ Azure DevOps transformed from two-year release cycles to 880,000 deployments per year by adopting continuous delivery, shortening feedback loops, and using real-time data to guide decisions. This shift enabled rapid response to customer needs and market changes, helping them stay ahead of competitors. Development managers should focus on frequent, small releases and data-driven improvements to maximise value and agility. https://engineering-leadership-preview.hinshelwood.com/signals/technical-debt-cripples-business-agility-and-slows-engineers-down/ Tue, 06 May 2025 15:30:42 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/technical-debt-cripples-business-agility-and-slows-engineers-down/ Technical debt severely limits business agility and slows down engineering teams, making it harder to respond to market opportunities and innovate. This is a real risk seen in major companies and happens when technical debt is ignored. To stay competitive, focus on shortening feedback loops, automating processes, increasing transparency, and actively managing technical debt rather than accepting it. https://engineering-leadership-preview.hinshelwood.com/signals/if-teams-struggle-with-quality-or-delivery-the-problem-is-often-the-system/ Wed, 02 Apr 2025 15:30:05 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/if-teams-struggle-with-quality-or-delivery-the-problem-is-often-the-system/ When teams face issues with quality or delivery, the root cause is often the broader system, not just the team itself. Consistent quality requires clear engineering standards, automation, and strong leadership support, not just team-level efforts. Leaders should ensure these foundations are in place rather than simply demanding results. 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/why-measuring-individual-cycle-time-is-killing-your-flow-and-what-to-do-instead/ Mon, 03 Mar 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/why-measuring-individual-cycle-time-is-killing-your-flow-and-what-to-do-instead/ Measuring individual cycle time in Kanban misleads teams by focusing on personal speed instead of system flow, which ignores real bottlenecks and encourages counterproductive behaviors. To improve delivery, track system-wide metrics like lead time, work in progress, process cycle efficiency, and blockers, then address constraints at the process level. Development managers should shift measurement and improvement efforts from individuals to the overall workflow to achieve better outcomes. 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/mastering-agility-balancing-engineering-excellence-and-effective-processes-in-a-rapidly-changing-business-landscape/ Wed, 25 Mar 2020 21:07:01 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/mastering-agility-balancing-engineering-excellence-and-effective-processes-in-a-rapidly-changing-business-landscape/ Balancing strong engineering practices with effective processes is essential for thriving in today’s fast-changing business environment; neglecting either can lead to costly failures or products that miss user needs. Success with Agile requires more than process changes, it demands a culture of transparency, collaboration, and continuous learning, along with well-trained product owners and meaningful outcome-focused metrics. Development managers should invest in engineering excellence, support ongoing training, and adopt an experimental, evidence-based approach to drive real agility and business value. 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/videos/embracing-change-how-architectural-adaptation-fuels-software-development-success/ Thu, 06 Feb 2025 17:06:47 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/embracing-change-how-architectural-adaptation-fuels-software-development-success/ Adapting software architecture to meet changing demands is essential for long-term product success. Investing in teams, enabling incremental changes, and maintaining a long-term vision, like the Azure DevOps team’s four-year transformation, help reduce risk and support continuous improvement. Development managers should foster adaptability, prioritize architectural health, and clearly communicate long-term goals to ensure sustained progress. https://engineering-leadership-preview.hinshelwood.com/videos/navigating-the-unpredictability-of-software-development-embrace-agile-for-success/ Mon, 02 Dec 2024 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/navigating-the-unpredictability-of-software-development-embrace-agile-for-success/ Software development is inherently unpredictable, often leading to missed deadlines and budget overruns, but this can be managed by focusing on strong technical leadership and engineering excellence. Relying on a single best practice is a mistake; instead, adopting Agile principles like iterative development, continuous delivery, feedback, and testing helps teams adapt and deliver value. Development managers should foster these capabilities to navigate complexity and drive better project outcomes. 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/videos/maximising-deployment-frequency-the-key-to-faster-time-to-market-and-business-success/ Wed, 22 Jan 2025 14:16:54 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/maximising-deployment-frequency-the-key-to-faster-time-to-market-and-business-success/ Increasing deployment frequency is key to reducing time to market and driving business success, but it only adds value if deployments reach production and enable fast learning from real user feedback. Focus on stable environments, end-to-end pipeline analysis, and shortening the time to learn so you can iterate quickly and align with business needs. Prioritise building trust with stakeholders, collecting actionable data, and enabling continuous delivery to respond rapidly to opportunities and deliver the right features at the right time. https://engineering-leadership-preview.hinshelwood.com/videos/mastering-azure-devops-avoiding-common-pitfalls-for-agile-success/ Tue, 09 Apr 2024 08:00:20 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/mastering-azure-devops-avoiding-common-pitfalls-for-agile-success/ Many teams misuse Azure DevOps by creating flat work item hierarchies, using custom work item types that do not fit agile practices, neglecting traceability, and overcomplicating processes, which reduces the platform’s effectiveness. Sticking to intended structures and keeping processes simple helps teams stay agile and productive. Review your team’s use of Azure DevOps to ensure alignment with agile principles and avoid these common pitfalls. https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-engineering-excellence-how-azure-devops-transforms-traceability-transparency-and-the-developer-experience/ Mon, 28 Jul 2025 07:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-engineering-excellence-how-azure-devops-transforms-traceability-transparency-and-the-developer-experience/ Azure DevOps is a comprehensive platform that enhances engineering excellence by providing end-to-end traceability, transparency, and an integrated developer experience across planning, code, builds, and testing. Key benefits include instant visibility into what is deployed where, streamlined audit and compliance processes, and reduced friction between developers and testers. Development managers should ensure their teams fully leverage Azure DevOps’ capabilities to improve collaboration, accountability, and product quality. https://engineering-leadership-preview.hinshelwood.com/videos/stop-guessing-how-to-make-work-visible-and-drive-real-improvement-with-azure-devops-flow-metrics/ Mon, 25 Aug 2025 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/stop-guessing-how-to-make-work-visible-and-drive-real-improvement-with-azure-devops-flow-metrics/ Relying on gut feeling leads to mediocre results, so making work visible with real data is essential for improvement. Azure DevOps provides a strong data foundation but its built-in metrics and visualisations are basic; using tools like Flow Viz or Actionable Agile Metrics gives deeper insights and actionable flow data. To drive better outcomes, move from guesswork to evidence-based decisions by leveraging these tools to make your team’s work and bottlenecks visible. 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/videos/devops-elevating-your-organization-s-performance-through-bespoke-solutions/ Fri, 16 Aug 2024 07:18:10 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/devops-elevating-your-organization-s-performance-through-bespoke-solutions/ Tailoring DevOps to your organization’s unique needs starts with assessing your current state, streamlining processes, and choosing the right tools, which leads to higher quality and more frequent software deliveries. Key actions include conducting solo interviews to uncover real issues, automating and rationalizing tools, and empowering teams with end-to-end ownership while ensuring compliance does not block DevOps practices. Start with small, controlled deployments and strategic timing to minimize risk and maximize efficiency. https://engineering-leadership-preview.hinshelwood.com/videos/empowering-teams-for-success-the-key-to-thriving-product-development/ Tue, 07 May 2024 11:02:49 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/empowering-teams-for-success-the-key-to-thriving-product-development/ Successful product development depends on empowered, engaged, and happy teams who understand the value of their work and are trusted to make decisions. Key drivers include fostering collaboration, providing continuous feedback, investing in skills development, and enabling direct customer engagement. Development managers should focus on creating an environment where team members feel valued and supported, as this leads to higher quality products and greater innovation. https://engineering-leadership-preview.hinshelwood.com/videos/if-a-client-hasn't-considered-devops-consulting-as-part-of-their-agile-consulting-needs-why-should-they/ Mon, 21 Aug 2023 07:00:01 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/if-a-client-hasn't-considered-devops-consulting-as-part-of-their-agile-consulting-needs-why-should-they/ Relying on Agile alone limits your team’s ability to deliver quality software quickly and efficiently; integrating DevOps consulting breaks down silos, accelerates time to market, and embeds quality from the start. DevOps is more than tools, it is a culture shift that harmonizes development and operations, enabling continuous improvement and resilient deployments. To maximize Agile’s benefits, development managers should invest in DevOps consulting to create a truly high-performing, adaptable software delivery process. https://engineering-leadership-preview.hinshelwood.com/videos/legacy-systems-aren-t-the-enemy-friction-is-how-to-unblock-innovation-and-accelerate-agile-delivery/ Mon, 14 Jul 2025 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/legacy-systems-aren-t-the-enemy-friction-is-how-to-unblock-innovation-and-accelerate-agile-delivery/ Legacy systems are only a problem when they create friction that slows delivery, increases fragility, and blocks innovation. The real issue is not system age but lack of ongoing maintenance and improvement, which leads to bottlenecks for both engineers and management. To accelerate agile delivery, focus on identifying and removing friction points, prioritising continuous improvement, and communicating the value of these efforts to the business. 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-insufficiency-of-scrum-is-a-fallacy/ Sat, 23 Mar 2013 17:37:31 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/the-insufficiency-of-scrum-is-a-fallacy/ Scrum alone does not cause project failure; lacking strong engineering practices and effective retrospectives leads to technical debt and poor Agile outcomes. https://engineering-leadership-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/videos/unlocking-legacy-systems-how-to-embrace-automation-and-drive-innovation/ Mon, 28 Apr 2025 06:00:34 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-legacy-systems-how-to-embrace-automation-and-drive-innovation/ Legacy systems can and should be automated, with the main barrier being mindset rather than technology. By encouraging a culture that questions old processes and starting with small, incremental automation efforts, teams can reduce bottlenecks and unlock significant efficiency gains. Development managers should identify manual pain points and begin automating them to drive innovation and continuous improvement. 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/signals/why-slow-processes-impact-developer-productivity-and-performance/ Fri, 14 Mar 2025 16:30:02 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/why-slow-processes-impact-developer-productivity-and-performance/ Developer performance issues are often caused by slow or broken processes, not individual shortcomings. Focusing on improving systems like training, reviews, and team handoffs leads to better results than blaming people. To boost productivity, address process bottlenecks rather than targeting individuals. https://engineering-leadership-preview.hinshelwood.com/videos/shifting-left-quality-from-the-start/ Wed, 20 Nov 2024 07:00:26 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/shifting-left-quality-from-the-start/ Automating code reviews and quality checks as early as possible in the development process reduces defects and speeds up delivery by minimizing manual bottlenecks. Manual code reviews should be a safety net, not the primary method for ensuring quality, and no code should reach the main branch without passing automated checks. Development managers should invest in robust automation for code validation to improve quality and accelerate value delivery. https://engineering-leadership-preview.hinshelwood.com/videos/the-competence-crisis-in-scrum-master-roles-a-call-for-excellence/ Wed, 16 Oct 2024 07:00:09 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/the-competence-crisis-in-scrum-master-roles-a-call-for-excellence/ There is a widespread lack of competence among Scrum Masters due to high demand, low entry barriers, and insufficient experience, which undermines team and organizational effectiveness. Effective Scrum Masters need deep practical experience, a solid understanding of software development and DevOps, and the ability to support both teams and Product Owners while driving organizational change. Development managers should prioritize hiring or developing Scrum Masters with real-world experience and a commitment to continuous learning, rather than relying on certifications alone. https://engineering-leadership-preview.hinshelwood.com/videos/overview-of-'applying-flow-metrics-for-scrum'-course/ Mon, 19 Feb 2024 07:00:09 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/overview-of-'applying-flow-metrics-for-scrum'-course/ The “Applying Flow Metrics for Scrum” course teaches Scrum teams how to use Kanban metrics to improve value delivery, transparency, and continuous improvement. Key benefits include better visibility into workflow, data-driven decision-making, and more predictable outcomes for stakeholders. Development managers should consider this course if their teams need to deliver value more consistently and want practical tools for ongoing improvement. https://engineering-leadership-preview.hinshelwood.com/articles/estimating-better-in-an-overloaded-system-is-a-poor-man-s-strategy/ Mon, 08 Sep 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/estimating-better-in-an-overloaded-system-is-a-poor-man-s-strategy/ Trying to improve estimates in an overloaded system is ineffective because high work in progress causes delays and unpredictability, regardless of estimation accuracy. Real improvements in predictability and throughput come from limiting work in progress, fostering collaboration, and focusing on finishing work rather than starting more. To achieve reliable delivery, reduce WIP and prioritize flow over planning. 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/videos/bridging-the-gap-understanding-the-true-meaning-of-done-in-agile-teams/ Thu, 07 Dec 2023 11:00:05 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/bridging-the-gap-understanding-the-true-meaning-of-done-in-agile-teams/ Many Agile teams misunderstand what “done” really means, leading to gaps in quality and unmet expectations. Clearly defining “done” with input from both leadership and the team ensures consistent quality, reduces rework, and builds trust with stakeholders. Development managers should regularly review and refine their team’s definition of done to align with evolving business needs and maintain high standards. https://engineering-leadership-preview.hinshelwood.com/videos/embrace-simplicity-how-to-transform-complexity-into-continuous-delivery-success/ Thu, 27 Feb 2025 07:00:10 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/embrace-simplicity-how-to-transform-complexity-into-continuous-delivery-success/ Complexity is not a valid excuse for avoiding continuous delivery; with organisational commitment and a willingness to modernise, even legacy systems can be transformed for faster, more reliable releases. Key steps include honestly assessing your product, investing in ongoing improvement, and addressing technical debt rather than ignoring warning signs. Leaders should prioritise resources and foster a culture that values continuous improvement to avoid costly failures and achieve lasting delivery success. https://engineering-leadership-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/navigating-the-legacy-system-dilemma-balancing-stability-and-innovation-for-modernisation-success/ Mon, 14 Apr 2025 06:00:33 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/navigating-the-legacy-system-dilemma-balancing-stability-and-innovation-for-modernisation-success/ Balancing stability and innovation in legacy systems is challenging, as rapid changes can cause technical debt and confusion, while inaction leads to stagnation. Gradual, collaborative modernisation focused on engineering best practices allows for progress without disrupting what works. Consider incremental improvements to maintain resilience and competitiveness while modernising. https://engineering-leadership-preview.hinshelwood.com/videos/avoiding-agile-banditry-why-story-points-and-velocity-are-misleading-metrics/ Mon, 08 Jan 2024 07:00:06 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/avoiding-agile-banditry-why-story-points-and-velocity-are-misleading-metrics/ Story points and velocity often distract teams from delivering real customer value and can lead to counterproductive behaviors, especially when used as performance measures or written into contracts. Instead, focus on metrics like throughput and cycle time, which better reflect actual progress and value delivery. Use story points only for internal team discussions, then discard them, and never include them in contracts or external reporting. 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/signals/microsoft-shift-from-2-year-cycles-to-3-week-sprints-caused-team-anxiety/ Wed, 23 Apr 2025 15:30:47 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/microsoft-shift-from-2-year-cycles-to-3-week-sprints-caused-team-anxiety/ When Microsoft switched from two-year release cycles to three-week Sprints, teams initially felt anxious because increased transparency exposed inefficiencies and technical debt. However, teams that embraced this openness improved dramatically, moving from delivering 24 features a year to shipping multiple times daily. Development managers should consider whether their teams are ready to use transparency as a tool for continuous improvement. https://engineering-leadership-preview.hinshelwood.com/signals/a-changing-definition-of-done-undermines-quality-and-predictability-in-teams/ Fri, 04 Apr 2025 15:30:02 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/a-changing-definition-of-done-undermines-quality-and-predictability-in-teams/ Frequently changing the Definition of Done makes it hard for teams to deliver predictable results and maintain quality. The Definition of Done should only evolve to raise standards, not lower them. To improve predictability and quality, keep your Definition of Done consistent and ensure it is followed. 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/videos/code-reviews-for-quality-assurance/ Wed, 27 Nov 2024 06:00:25 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/code-reviews-for-quality-assurance/ Automating code validation before pull requests speeds up delivery, catches defects earlier, and ensures consistent quality, allowing manual reviews to focus on architecture and business alignment instead of minor issues. Development managers should invest in automated testing, static analysis, and security checks, making pull requests mandatory and using manual reviews strategically. This approach reduces bottlenecks and helps teams deliver high-quality software faster. https://engineering-leadership-preview.hinshelwood.com/articles/deciphering-the-enigma-of-story-points-across-teams/ Thu, 21 Sep 2023 08:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/deciphering-the-enigma-of-story-points-across-teams/ Story Points are useful for team discussions and backlog refinement but are too subjective for comparing teams or predicting delivery. Focus instead on objective metrics like throughput, cycle time, and work in process to measure and improve team performance, while also considering value delivered using evidence-based management practices. Shift your attention from normalising Story Points to tracking flow metrics and value to make better decisions and optimise outcomes. https://engineering-leadership-preview.hinshelwood.com/signals/if-every-release-feels-high-risk-you-lack-a-true-definition-of-done/ Sat, 05 Apr 2025 15:30:00 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/if-every-release-feels-high-risk-you-lack-a-true-definition-of-done/ If every release feels risky and stressful, your team likely lacks a clear Definition of Done that ensures software is truly ready for production. A strong Definition of Done means releases are routine, with quality, security, and compliance built in, so there are no last-minute scrambles. Review your team’s process to make releases predictable and low-stress. https://engineering-leadership-preview.hinshelwood.com/signals/let-us-do-the-maths/ Wed, 30 Apr 2025 15:30:52 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/let-us-do-the-maths/ Slow release cycles mean customer needs go unmet and competitors gain an edge. Microsoft’s shift from a two-year delivery cycle to three-week sprints allowed them to deliver features in days, improving customer satisfaction and competitiveness. Accelerate your delivery process to stay relevant and meet customer demands faster. 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/maximising-roi-in-software-development-unlocking-value-through-quality-and-expertise/ Fri, 13 Dec 2024 06:30:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/maximising-roi-in-software-development-unlocking-value-through-quality-and-expertise/ Maximising ROI in software development requires treating code as a valuable asset, investing in quality, and ensuring regular reviews to maintain standards. Bridging the gap between business and technical expertise is essential, so equip your leadership with the right knowledge and consider external coaching if needed. Prioritise quality, technical skill, and hypothesis-driven practices to ensure your teams deliver the most value for your investment. https://engineering-leadership-preview.hinshelwood.com/videos/modernising-legacy-systems-how-to-tackle-security-risks-without-breaking-your-business/ Mon, 12 May 2025 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/modernising-legacy-systems-how-to-tackle-security-risks-without-breaking-your-business/ Modernising legacy systems is essential for security, but rushing the process can create new risks; instead, map your workflows, embed security throughout development, empower teams, and focus on maintainability and compliance. Treat security as an ongoing mindset, not a one-time task, and continuously adapt as threats evolve. Start by assessing how work and security practices flow in your organisation before making changes. 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/videos/getting-started-with-kanban/ Wed, 14 Feb 2024 07:00:19 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/getting-started-with-kanban/ Kanban helps teams improve workflow and productivity by visualizing work, setting clear processes, and using metrics like cycle time and throughput to drive continuous improvement. Start with a small, willing team, define and visualize your workflow, and use data to identify and address bottlenecks. Begin with a pilot, focus on collaboration and regular feedback, and use metrics to build credibility and guide ongoing enhancements. https://engineering-leadership-preview.hinshelwood.com/videos/mastering-agile-3-essential-strategies-to-boost-your-team's-sprint-success/ Thu, 16 Nov 2023 07:00:16 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/mastering-agile-3-essential-strategies-to-boost-your-team's-sprint-success/ To improve your team’s Sprint outcomes, clearly define what “done” means for every task, avoid overcommitting by leaving room for technical debt and unexpected issues, and make backlog refinement a regular priority to catch blockers early. These steps help align expectations, reduce surprises, and create a smoother workflow. Review your current practices and adjust to ensure these strategies are in place. https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-true-potential-of-scrum-why-professionalism-matters-in-agile-teams/ Thu, 20 Apr 2023 07:00:06 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-true-potential-of-scrum-why-professionalism-matters-in-agile-teams/ Many software teams fall short of Scrum’s true potential because organizations prioritize speed over professionalism, leading to shortcuts and unprofessional practices. Achieving real value with Scrum requires a commitment to transparency, production-ready increments each iteration, and honest assessment of current capabilities, often revealing significant gaps. Development managers should focus on fostering a professional work ethic and closing these gaps to unlock Scrum’s full benefits. https://engineering-leadership-preview.hinshelwood.com/signals/deploying-windows-os-directly-to-production-then-vs-now/ Sat, 22 Feb 2025 16:30:00 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/deploying-windows-os-directly-to-production-then-vs-now/ Microsoft now deploys Windows updates directly to production using a gradual, ring-based rollout that starts with internal users and expands outward, guided by real-time feedback and telemetry. This approach catches issues early and enables safe, incremental releases even across complex environments. Development managers should consider adopting similar staged deployment strategies to improve release quality and responsiveness. https://engineering-leadership-preview.hinshelwood.com/videos/story-points-a-ghost-of-agile-past/ Fri, 29 Dec 2023 07:00:14 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/story-points-a-ghost-of-agile-past/ Story points have become a source of dysfunction in Agile teams, shifting focus from delivering value to hitting arbitrary targets and enabling misleading comparisons between teams. These issues are worsened when contracts tie performance to story point delivery, leading to counterproductive behaviors. Development managers should move away from story points and instead adopt flow metrics like cycle time and throughput, which provide more accurate, value-focused insights into team performance. 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/signals/frequent-releases-are-not-just-a-technical-strategy/ Fri, 07 Feb 2025 16:30:01 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/frequent-releases-are-not-just-a-technical-strategy/ Frequent releases help teams learn from real users and avoid wasting effort on features that may not work, as shown by Microsoft’s costly Windows 8 failure. Research shows that teams releasing often recover faster and reduce costs. To reduce risk and improve outcomes, prioritize frequent releases and adapt based on user feedback. 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/videos/transforming-enterprises-how-devops-drives-collaboration-and-continuous-improvement/ Tue, 16 Jun 2020 12:16:52 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/transforming-enterprises-how-devops-drives-collaboration-and-continuous-improvement/ DevOps can transform enterprise software teams by fostering collaboration, encouraging continuous improvement, and enabling automation, which together lead to faster delivery and higher quality. Focusing on a customer-centric approach helps teams respond quickly to feedback and market changes. Development managers should prioritize building a culture that supports these principles to drive meaningful organizational change. 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/transforming-organisational-culture-unlocking-engineering-excellence-through-system-optimisation/ Sat, 21 Dec 2024 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/transforming-organisational-culture-unlocking-engineering-excellence-through-system-optimisation/ To achieve engineering excellence, focus on understanding and measuring your current delivery system, then use those insights to optimise for maximum value rather than just cutting costs. Transparent metrics and iterative improvements help control costs and drive technical leadership. Start by assessing your workflows and processes to identify where changes will have the most impact. https://engineering-leadership-preview.hinshelwood.com/videos/why-are-a-scrum-team-better-served-by-an-agile-consultant-than-a-professional-coach/ Mon, 26 Jun 2023 07:00:07 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-are-a-scrum-team-better-served-by-an-agile-consultant-than-a-professional-coach/ Scrum teams benefit more from Agile consultants than professional coaches because consultants provide the technical and practical guidance teams often lack, especially in the early stages. Teams need help understanding what they do not know and how to apply effective engineering practices, not just support in finding their own solutions. Development managers should consider bringing in Agile consultants to build foundational knowledge and accelerate team capability. 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/videos/from-chaos-to-clarity-my-journey-through-devops-and-the-three-key-challenges-to-overcome/ Thu, 04 Apr 2024 11:34:59 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/from-chaos-to-clarity-my-journey-through-devops-and-the-three-key-challenges-to-overcome/ The author describes moving from chaotic, manual development practices to adopting DevOps, highlighting three main challenges: shifting culture and collaboration, integrating and automating toolchains, and fostering continuous learning. Success requires systems thinking, strong feedback loops, and a culture of experimentation. Development managers should focus on supporting people, streamlining processes, and encouraging ongoing learning to deliver better products faster. https://engineering-leadership-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/metrics-that-matter-with-evidence-based-management/ Tue, 25 Feb 2014 13:29:14 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/metrics-that-matter-with-evidence-based-management/ Explains how evidence-based management uses reliable metrics and KPIs at team and organisational levels to drive better decisions, value delivery, and process improvement. 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/articles/quality-enablement-to-achieve-predictable-delivery/ Wed, 24 Jul 2013 09:46:22 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/quality-enablement-to-achieve-predictable-delivery/ Explains how defining quality standards, acceptance criteria, and automation in software delivery leads to predictable outcomes, fewer bugs, and improved team performance. https://engineering-leadership-preview.hinshelwood.com/videos/transforming-waste-into-value-how-to-boost-roi-with-agile-metrics/ Tue, 17 Dec 2024 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/transforming-waste-into-value-how-to-boost-roi-with-agile-metrics/ Most organisations lose significant value due to waste and lack of focus on engineering excellence, with metrics showing that only a small fraction of development investment results in features customers actually use. Key insights include low innovation rates, poor feature usage, and lagging version adoption, all of which drastically reduce ROI. Development managers should measure and act on innovation and usage metrics, close feedback loops, and focus on delivering value rather than just reducing costs. 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/signals/every-unreleased-feature-is-a-cost/ Wed, 05 Feb 2025 16:30:01 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/every-unreleased-feature-is-a-cost/ Unreleased features create hidden costs and risks, as work that is not delivered provides no real value. Evidence shows that frequent releases reduce failure rates and improve stability, while long cycles lead to more rework and missed opportunities. Focus on shipping regularly to ensure your team’s efforts translate into actual value. https://engineering-leadership-preview.hinshelwood.com/videos/maximising-product-value-the-power-of-hypothesis-driven-engineering/ Wed, 11 Dec 2024 06:30:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/maximising-product-value-the-power-of-hypothesis-driven-engineering/ Focusing on hypothesis-driven engineering helps teams maximise product value by testing ideas with small experiments, measuring outcomes, and quickly adapting based on real customer feedback. The Azure DevOps team’s experience showed that even costly initiatives can provide critical learning, allowing resources to be redirected before larger losses occur. Development managers should encourage rapid experimentation and validation at all levels to ensure investments deliver real value and support agility. https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-success-how-small-experiments-transformed-feature-delivery-from-25-to-150-in-software-development/ Wed, 20 Nov 2024 08:02:36 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-success-how-small-experiments-transformed-feature-delivery-from-25-to-150-in-software-development/ A team increased their annual feature delivery from 25 to 150 by breaking down work into smaller experiments, enabling faster feedback, reduced risk, and continuous learning without increasing headcount. This approach allowed them to quickly identify and focus on features that mattered most to customers, leading to better products. Development managers should consider adopting small, frequent experiments to drive both speed and quality in feature delivery. https://engineering-leadership-preview.hinshelwood.com/articles/constructing-a-framework-for-the-tfs-automation-platform/ Sun, 12 Jun 2011 04:44:02 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/constructing-a-framework-for-the-tfs-automation-platform/ Outlines the structure and components of a framework for the TFS Automation Platform, detailing its architecture, plugin management, and development approach. https://engineering-leadership-preview.hinshelwood.com/articles/live-site-culture-site-reliability-engineering/ Wed, 17 Jun 2020 13:23:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/live-site-culture-site-reliability-engineering/ To stay competitive in a fast-changing market, teams must adopt DevOps and continuous delivery, shifting from infrequent releases to deploying updates daily. This requires faster feedback, shared responsibility for quality and operations, and new ways of working, as shown by Microsoft’s Azure DevOps team. Development managers should consider evolving their team structures and practices to support rapid, customer-focused delivery. https://engineering-leadership-preview.hinshelwood.com/signals/would-your-cfo-approve-misrepresenting-corporate-assets/ Mon, 21 Apr 2025 15:30:34 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/would-your-cfo-approve-misrepresenting-corporate-assets/ Ignoring technical debt is like misrepresenting the value of your software assets, which can lead to future losses and operational risks. Most businesses fail to track this risk, even though technical debt reduces asset value and increases costs. Development managers should ensure technical debt is monitored and addressed to protect the true value of software investments. 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/release-management-with-team-foundation-server-2012/ Wed, 24 Apr 2013 17:38:24 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/release-management-with-team-foundation-server-2012/ Explains how to automate and streamline software release management using Team Foundation Server 2012, Lab Management, and Octopus, focusing on build, deployment, and quality. https://engineering-leadership-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/unlocking-the-true-power-of-continuous-delivery-how-automation-transforms-software-development/ Fri, 06 Dec 2024 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-true-power-of-continuous-delivery-how-automation-transforms-software-development/ The main benefit of continuous delivery is the automation it brings, which increases consistency, reliability, and risk mitigation in software deployments. Real-world examples like Azure DevOps and Windows teams show that automation shortens feedback loops, reduces errors, and enables faster, higher-quality releases without increasing team size. Development managers should focus on embedding automation throughout their delivery process to protect the business and empower teams to deliver better software more efficiently. https://engineering-leadership-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/videos/detecting-agile-bs-lessons-from-the-us-department-of-defense/ Fri, 28 Jun 2024 06:45:01 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/detecting-agile-bs-lessons-from-the-us-department-of-defense/ Many organizations claim to be Agile but often fall short of true Agile practices, as highlighted by the US Department of Defense’s “Detecting Agile BS” guide. The guide recommends six key questions to assess real Agile maturity, focusing on frequent delivery to users, regular production releases, adapting to feedback, clear product vision, team empowerment, and a culture of continuous improvement. Development managers should honestly assess their teams against these criteria, start small with improvements, and foster a culture of feedback and learning to achieve genuine Agile transformation. https://engineering-leadership-preview.hinshelwood.com/videos/mastering-evidence-based-management-for-agile-success/ Wed, 02 Oct 2024 13:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/mastering-evidence-based-management-for-agile-success/ Evidence-Based Management helps Agile teams make better decisions by using data from four key areas: current value, unrealized value, ability to innovate, and time to market. By collecting and analyzing relevant metrics, teams can prioritize improvements, boost innovation, and deliver more value to customers. Start by tracking a few key metrics with simple tools, then use those insights to guide your team’s next steps. https://engineering-leadership-preview.hinshelwood.com/guides/detecting-agile-bs/ Tue, 17 Sep 2024 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/guides/detecting-agile-bs/ Guidance for identifying genuine agile software development in DoD projects, including key principles, warning signs, essential tools, and critical evaluation questions. https://engineering-leadership-preview.hinshelwood.com/articles/how-usable-working-products-are-your-ultimate-weapon-against-risks/ Thu, 20 Jul 2023 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/how-usable-working-products-are-your-ultimate-weapon-against-risks/ Continuously delivering a usable working product is the most effective way to reduce risk in Agile development. Focus on releasing functional increments, fixing bugs quickly, automating tests, and keeping documentation lean to stay responsive to market needs. Prioritise regular feedback from users and stakeholders to ensure you are building what truly adds value. https://engineering-leadership-preview.hinshelwood.com/articles/continuous-value-delivery-with-modern-business-applications/ Tue, 27 Nov 2012 23:00:35 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/continuous-value-delivery-with-modern-business-applications/ Explains how modern business applications use continuous delivery to release new features frequently, reduce risk, and improve customer satisfaction through rapid updates. https://engineering-leadership-preview.hinshelwood.com/videos/what-is-your-favourite-devops-consulting-outcome/ Tue, 18 Apr 2023 07:00:08 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/what-is-your-favourite-devops-consulting-outcome/ A fragmented, multi-billion-dollar software project with 80 to 90 teams across nine countries was transformed by unifying processes and source control onto Azure DevOps, greatly improving collaboration and efficiency. The key outcomes were simplification, system unification, and a shift toward a ‘One Engineering System’ approach. Development managers should consider consolidating tools and processes to drive similar improvements in productivity and teamwork. https://engineering-leadership-preview.hinshelwood.com/articles/blocked-columns-on-kanban-boards-obfuscate-workflow-and-undermine-effectiveness/ Tue, 13 Feb 2024 15:44:53 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/blocked-columns-on-kanban-boards-obfuscate-workflow-and-undermine-effectiveness/ Using Blocked columns on Kanban boards hides the true status of work, encourages team disengagement, and leads to stale tasks and inflated work-in-progress limits. Instead, teams should tag blocked items within their current workflow stage and provide clear context, which maintains transparency and accountability. Managers should avoid Blocked columns and use tags or annotations to highlight issues without disrupting the flow or losing critical information. https://engineering-leadership-preview.hinshelwood.com/articles/who-broke-the-build/ Mon, 29 Mar 2010 18:47:08 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/who-broke-the-build/ Explains the importance of passing builds, common causes of build failures, how to identify issues and responsible users, and best practices for build ownership. https://engineering-leadership-preview.hinshelwood.com/signals/everyone-has-a-disaster-recovery-plan-on-paper/ Wed, 14 May 2025 15:30:37 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/everyone-has-a-disaster-recovery-plan-on-paper/ Many organizations have disaster recovery plans, but these often fail in real situations because critical dependencies are overlooked and not tested end to end. Successful drills can give a false sense of security if they do not include all essential systems, like authentication services. To ensure true resilience, regularly test your recovery process under real conditions and verify that all dependencies are restored and functional. https://engineering-leadership-preview.hinshelwood.com/articles/alm-consulting-in-scotland-uk-scandinavia-amp-europe/ Mon, 11 Nov 2013 15:08:44 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/alm-consulting-in-scotland-uk-scandinavia-amp-europe/ Provides ALM consulting, training, and assessments across Scotland, UK, and Europe, specialising in lean-agile, TFS, Visual Studio, Scrum, and process improvement. https://engineering-leadership-preview.hinshelwood.com/articles/team-foundation-server-2013-is-production-ready/ Tue, 23 Jul 2013 09:44:42 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/team-foundation-server-2013-is-production-ready/ Team Foundation Server 2013 is stable for production use, addressing past update issues with improved agility, technical debt management, and enhanced ALM features. https://engineering-leadership-preview.hinshelwood.com/articles/presenting-visual-studio-alm-and-upgrading-tfs-2010-to-tfs-2012-in-production-%E2%80%93-done/ Sun, 10 Jun 2012 19:03:56 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/presenting-visual-studio-alm-and-upgrading-tfs-2010-to-tfs-2012-in-production-%E2%80%93-done/ Covers presenting Visual Studio ALM features and the process of upgrading from TFS 2010 to TFS 2012, including benefits, challenges, and key considerations for organisations. 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/videos/unlocking-continuous-delivery-how-feature-flags-transform-software-development/ Thu, 16 Jan 2025 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-continuous-delivery-how-feature-flags-transform-software-development/ Feature flags enable teams to release new features incrementally, gather user feedback early, and quickly respond to issues, supporting safer and more frequent deployments. Real-world examples like Azure DevOps show that this approach allows for controlled rollouts, continuous monitoring, and ongoing improvements based on user input. Development managers should consider adopting feature flags to improve delivery speed, reduce risk, and ensure features better meet user needs. https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-future-of-software-development-why-automation-is-your-key-to-success/ Wed, 15 Jan 2025 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-future-of-software-development-why-automation-is-your-key-to-success/ Automation is essential for faster, more reliable software development, reducing human error and enabling consistent, rapid deployments. Real-world failures like Knight Capital show the high cost of manual processes, while leading teams achieve quick, high-quality releases by building automation into every step. Development managers should prioritize automating all possible tasks to improve quality, speed, and adaptability. https://engineering-leadership-preview.hinshelwood.com/articles/ndc-london-second-look-team-foundation-server-amp-vso/ Wed, 15 Oct 2014 14:49:05 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/ndc-london-second-look-team-foundation-server-amp-vso/ The speaker will present a demo-heavy session at NDC London to showcase major improvements in Team Foundation Server and Visual Studio Online since 2012, targeting developers who previously found TFS lacking. Key insights include end-to-end demonstrations of new features for agile project management, coding, testing, release, and monitoring, with scenarios covering both new features and bug fixes. Development managers should consider revisiting TFS/VSO for .NET projects and can provide feedback on which features or scenarios they want prioritized in the session. https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-best-application-of-scrum-in-the-world/ Fri, 26 May 2023 07:00:16 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-best-application-of-scrum-in-the-world/ Microsoft’s Azure DevOps team successfully transitioned from waterfall to Scrum, dramatically reducing build times from over 20 hours to just 3.5 minutes and delivering a product that better meets customer needs. This highlights how effective Scrum can be when applied well, especially in overcoming technical debt and improving efficiency. Development managers should consider how adopting Scrum could drive similar improvements in their own teams. https://engineering-leadership-preview.hinshelwood.com/articles/the-high-of-release/ Sat, 05 Dec 2015 14:49:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/the-high-of-release/ Microsoft’s new web-based Release Management tools let teams build flexible, integrated release pipelines in VSTS or TFS without being locked into specific deployment tools. The focus is on orchestration and integration, allowing you to use your preferred technologies like Chef, Puppet, Docker, or PowerShell. These tools are now in public preview, so consider evaluating them to streamline your release process and support cloud or on-premises deployments. 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/articles/avoid-bug-task-anti-pattern-tfs/ Wed, 06 Aug 2014 14:46:41 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/avoid-bug-task-anti-pattern-tfs/ Explains why treating bugs as tasks in Azure DevOps is an anti-pattern, its impact on transparency, quality, and planning, and offers guidance for agile teams to avoid it. https://engineering-leadership-preview.hinshelwood.com/videos/balancing-speed-and-stability-why-quality-should-always-come-first-in-delivery-management/ Fri, 24 Jan 2025 06:30:21 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/balancing-speed-and-stability-why-quality-should-always-come-first-in-delivery-management/ Rushing to meet deadlines often leads to poor-quality products that can damage your brand and erode customer trust, so prioritising stability and quality is essential even if it means missing deadlines or incurring fines. The long-term costs of sacrificing quality far outweigh any short-term gains from speed, as seen in real-world cases like Zoom. Development managers should educate stakeholders about these risks and always choose quality over speed to protect both reputation and customer relationships. https://engineering-leadership-preview.hinshelwood.com/articles/is-alm-a-useful-term/ Sat, 25 Feb 2012 03:41:53 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/is-alm-a-useful-term/ Explores whether Application Lifecycle Management (ALM) is a useful term, its role in agile software delivery, and differences in adoption across organisations and regions. https://engineering-leadership-preview.hinshelwood.com/signals/git-flow-should-have-died-years-ago/ Sun, 09 Feb 2025 16:30:00 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/git-flow-should-have-died-years-ago/ Git Flow is outdated and causes unnecessary delays and complications for modern software teams. Long-lived branches and complex merges slow down delivery and increase risk. Switch to simpler workflows like GitHub Flow or Release Flow to speed up development and focus on delivering value. https://engineering-leadership-preview.hinshelwood.com/signals/detecting-agile-theatre-with-real-delivery-signals/ Mon, 25 May 2026 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/detecting-agile-theatre-with-real-delivery-signals/ Agile is measured by delivery, feedback, and decision-making authority in the hands of teams, not by visible ceremonies or tooling. https://engineering-leadership-preview.hinshelwood.com/articles/branch-policies-for-tfvc/ Wed, 13 Jan 2016 15:49:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/branch-policies-for-tfvc/ A new branch policy tool for TFVC allows you to apply policies like branch locks, code reviews, and work item requirements across multiple branches using simple patterns, making policy management much easier for large, complex codebases. This approach avoids cumbersome path-based setups and helps ensure key quality steps are not missed without overburdening developers. You can try the tool, provide feedback, or contribute to its development on GitHub. https://engineering-leadership-preview.hinshelwood.com/articles/guidance-how-to-layout-you-files-for-an-ideal-solution/ Mon, 17 May 2010 11:08:16 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/guidance-how-to-layout-you-files-for-an-ideal-solution/ Learn best practices for organising solution and project files in version control, including folder structure, naming conventions, and branching for maintainable code. https://engineering-leadership-preview.hinshelwood.com/signals/when-heathrow-went-down-they-blamed-the-power-supplier/ Thu, 15 May 2025 15:30:30 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/when-heathrow-went-down-they-blamed-the-power-supplier/ Heathrow’s outage was not caused by a power loss but by an overly sensitive internal system that shut everything down in response to a minor fluctuation, revealing that their disaster recovery measures were untested for real-world chaos. Investing in infrastructure does not guarantee true resilience; resilience is proven only when systems are tested against unexpected failures. Development managers should regularly test and challenge their recovery processes to ensure they work under real conditions, not just ideal scenarios. https://engineering-leadership-preview.hinshelwood.com/articles/an-adoption-strategy-for-testing-with-visual-studio-2010/ Wed, 25 Jan 2012 22:41:24 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/an-adoption-strategy-for-testing-with-visual-studio-2010/ Guidance on adopting Visual Studio 2010 test tools, including Microsoft Test Manager, hands-on labs, and agile training to improve collaboration and software quality. https://engineering-leadership-preview.hinshelwood.com/articles/the-future-of-software-development/ Sat, 14 Jul 2007 19:03:24 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/the-future-of-software-development/ Explores how software factories, web services, and specialised development teams can speed up software delivery, improve adaptability, and meet fast-changing business needs. 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/videos/why-is-lego-a-shit-idea-for-a-scrum-trainer-part-2/ Wed, 04 Oct 2023 11:24:58 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-is-lego-a-shit-idea-for-a-scrum-trainer-part-2/ Using Lego in Scrum training oversimplifies the real complexity of software development, as Lego pieces fit together too easily and do not reflect the integration challenges teams actually face. This can create unrealistic expectations and trivialize the difficulties of real projects. Development managers should choose training tools that better represent the unpredictable and varied nature of software work. https://engineering-leadership-preview.hinshelwood.com/videos/why-embracing-automation-is-essential-for-reducing-human-error-in-software-development/ Wed, 18 Dec 2024 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-embracing-automation-is-essential-for-reducing-human-error-in-software-development/ Automation is essential in software development because it reduces human error, speeds up feedback, and creates more reliable processes. Relying on manual steps leads to costly mistakes and unsustainable workloads, while automation enables faster, higher-quality releases and happier customers. Development managers should prioritise automating repetitive tasks and rearchitecting processes that cannot be automated to improve quality and efficiency. https://engineering-leadership-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/videos/3-best-ways-to-wreck-kanban-sweep-problems-under-the-rug/ Mon, 04 Mar 2024 07:00:13 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-sweep-problems-under-the-rug/ Ignoring problems in your Kanban process leads to bigger issues, workflow blockages, and potential crises like project delays or cost overruns. Teams should regularly identify, visualize, and address problems, foster transparency, and take prompt action to prevent issues from escalating. Make it a priority to surface and resolve problems early to keep your workflow effective and avoid costly setbacks. https://engineering-leadership-preview.hinshelwood.com/videos/does-kanban-integrate-into-a-scrum-environment/ Thu, 15 Feb 2024 07:00:31 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/does-kanban-integrate-into-a-scrum-environment/ Kanban can be integrated with Scrum to improve workflow visibility, provide essential metrics like cycle time and throughput, and support continuous improvement. This combination helps teams answer key delivery questions and identify bottlenecks that Scrum alone may not address. Development managers should consider adding Kanban practices and metrics to their Scrum teams to optimize performance and make more informed decisions. https://engineering-leadership-preview.hinshelwood.com/videos/the-key-to-a-kanban-strategy-understanding-wip-limits/ Wed, 06 Mar 2024 07:00:17 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/the-key-to-a-kanban-strategy-understanding-wip-limits/ Setting work-in-progress (WIP) limits is essential for an effective Kanban strategy because it prevents overload, exposes bottlenecks, and improves workflow. The optimal WIP limit for each stage should be found through experimentation and regular adjustment, aiming for a balance that maximizes flow without causing idle time or bottlenecks. Start small, monitor results, and adjust limits as needed to boost team productivity and collaboration. https://engineering-leadership-preview.hinshelwood.com/videos/overview-of-'applying-metrics-for-predictability'-kanban-course/ Tue, 20 Feb 2024 07:00:27 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/overview-of-'applying-metrics-for-predictability'-kanban-course/ The “Applying Metrics for Predictability” Kanban course teaches teams how to use key Kanban metrics and probabilistic forecasting to improve delivery predictability, enabling more accurate planning and increased stakeholder trust. Participants learn to interpret data, identify bottlenecks, and make informed decisions that drive efficiency and consistent value delivery. Development managers whose teams struggle with predictability should consider this course to enhance forecasting and workflow reliability. https://engineering-leadership-preview.hinshelwood.com/videos/transform-your-team's-skills-the-power-of-immersive-learning-in-the-workplace/ Mon, 31 Jul 2023 07:00:12 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/transform-your-team's-skills-the-power-of-immersive-learning-in-the-workplace/ Immersive learning is more effective than traditional training because it focuses on applying concepts directly to real work, encourages feedback and reflection, and helps teams challenge old habits. Including coaching and group support makes the learning more relevant and impactful for each participant. Consider adopting immersive learning to build stronger, more adaptable teams. 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/the-definition-of-done-ensuring-quality-without-compromising-value/ Wed, 27 Sep 2023 09:59:46 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/the-definition-of-done-ensuring-quality-without-compromising-value/ The Definition of Done (DoD) ensures every release meets clear quality standards, while acceptance criteria define specific content requirements. Mixing acceptance criteria into the DoD can undermine transparency and adaptability, but consistently required quality measures should be added to the DoD itself. Review your acceptance criteria regularly and only update the DoD if it preserves both clarity and flexibility in your team’s delivery. 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/do-you-know-the-minimum-builds-to-create-on-any-branch/ Thu, 18 Mar 2010 14:51:42 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/do-you-know-the-minimum-builds-to-create-on-any-branch/ Explains the essential three build types, Gate, CI, and Nightly, needed per branch to ensure code quality, test coverage, and collaboration in team projects. 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/articles/does-test-driven-development-speed-up-development/ Mon, 15 Dec 2008 14:55:51 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/does-test-driven-development-speed-up-development/ Explores whether test-driven development (TDD) accelerates software delivery by reducing complexity, rework, and design flaws, and improving adaptability and productivity. https://engineering-leadership-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/create-a-build-vnext-build-definition/ Wed, 04 Mar 2015 17:37:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/create-a-build-vnext-build-definition/ Microsoft’s new Build vNext system for TFS and VSO is more modular and user-friendly, offering a wide range of out-of-the-box build and deployment tasks, improved configuration options, and better auditability of changes. It currently supports only Git repositories and continuous integration triggers, with plans for greater extensibility and additional features in the future. Development managers should consider evaluating Build vNext in test environments to prepare for its eventual adoption and to explore its enhanced flexibility and control. https://engineering-leadership-preview.hinshelwood.com/articles/configure-a-build-vnext-agent/ Wed, 14 Jan 2015 14:55:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/configure-a-build-vnext-agent/ Microsoft’s new modular build system for TFS and VSO, currently in early preview, replaces the old controller model with a more flexible pool and queue approach, simplifying agent management and permissions. Setting up a vNext Build Agent requires spinning up your own VM, installing Visual Studio 2013 or 2015, and configuring the agent via PowerShell. Development managers should prepare for a shift to this new system and consider early testing to understand its benefits and requirements. https://engineering-leadership-preview.hinshelwood.com/articles/why-should-i-use-visual-studio-alm/ Wed, 07 Jan 2015 15:39:20 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/why-should-i-use-visual-studio-alm/ Visual Studio ALM offers a comprehensive set of features beyond just source control and build, covering requirements, project, change, quality, feedback, defect, release, and analytics management in one integrated platform. Replacing it with tools like Git and Jenkins means losing most of this functionality and facing significant integration and maintenance challenges. Development managers should carefully assess what capabilities they need and consider the long-term effort required to replicate Visual Studio ALM’s end-to-end support before switching tools. https://engineering-leadership-preview.hinshelwood.com/articles/migrating-source-from-perforce-to-git-on-vso/ Wed, 20 Aug 2014 14:06:13 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/migrating-source-from-perforce-to-git-on-vso/ Step-by-step guide to migrating source code from Perforce to Git on VSO, covering repository setup, dependency management, build processes, and key migration tips. https://engineering-leadership-preview.hinshelwood.com/articles/execute-tests-with-release-management-for-visual-studio-2013/ Mon, 27 Jan 2014 11:29:14 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/execute-tests-with-release-management-for-visual-studio-2013/ Learn how to automate test execution during deployments using Release Management for Visual Studio 2013, including setup steps, environment tips, and common issues. 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/full-fidelity-history-and-data-migration-are-mutually-exclusive/ Tue, 29 May 2012 01:24:56 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/full-fidelity-history-and-data-migration-are-mutually-exclusive/ Explains why preserving complete historical data and accurate dates is often incompatible with data migration, especially for compliance and traceability in regulated industries. https://engineering-leadership-preview.hinshelwood.com/articles/visual-studio-2010-overview-code-management-and-build/ Tue, 31 Jan 2012 03:34:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/visual-studio-2010-overview-code-management-and-build/ Explains branching, merging, and build strategies in Visual Studio 2010, including integration with Team Foundation Server and new tools for code management and ALM. https://engineering-leadership-preview.hinshelwood.com/articles/visual-studio-2010-overview-intellitrace-and-test-impact-analysis/ Thu, 26 Jan 2012 18:21:55 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/visual-studio-2010-overview-intellitrace-and-test-impact-analysis/ Explains how IntelliTrace aids bug diagnosis and how Test Impact Analysis helps prioritise regression tests in Visual Studio 2010 for efficient debugging and testing. https://engineering-leadership-preview.hinshelwood.com/articles/do-you-know-about-the-visual-studio-2010-database-projects-guidance/ Wed, 16 Feb 2011 12:40:07 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/do-you-know-about-the-visual-studio-2010-database-projects-guidance/ Guidance on using Visual Studio 2010 Database Projects, covering project management, source control, deployment automation, integration, and database testing. https://engineering-leadership-preview.hinshelwood.com/articles/how-visual-studio-2010-and-team-foundation-server-enable-compliance/ Wed, 09 Feb 2011 22:04:04 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/how-visual-studio-2010-and-team-foundation-server-enable-compliance/ Explains how Visual Studio 2010 and Team Foundation Server support compliance by enabling traceability, audit trails, and linking code changes to requirements and tests. 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/msbuild-and-business-intelligence-packages-ahhhhhh/ Fri, 24 Oct 2008 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/msbuild-and-business-intelligence-packages-ahhhhhh/ Discusses challenges in automating builds, testing, and deployment for SQL Server BI solutions, focusing on SSIS and SSAS packages and gaps in MSBuild support. https://engineering-leadership-preview.hinshelwood.com/articles/post-event-developer-day-scotland/ Mon, 12 May 2008 10:32:21 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/post-event-developer-day-scotland/ Highlights from Developer Day Scotland, featuring sessions on ADO.NET Data Services, anti-patterns, continuous integration, and test-driven development by expert speakers. https://engineering-leadership-preview.hinshelwood.com/articles/access-denied-for-orchestration-plan-on-build/ Wed, 16 Dec 2015 14:18:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/access-denied-for-orchestration-plan-on-build/ When setting up a TFS build agent for a high-volume customer, a permissions error blocked builds because the “Project Collection Build Service” lacked write access to the orchestration plan. The issue is tied to permission inheritance and a known bug in TFS 2015 RTM, and can be fixed by ensuring both “Project Build Service” and “Project Collection Build Service” have inherited permissions on build definitions via Visual Studio. Development managers should verify these permissions to avoid similar build failures and streamline onboarding to new build systems. https://engineering-leadership-preview.hinshelwood.com/articles/visual-studio-2012-rtm-available-installed/ Wed, 15 Aug 2012 18:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/visual-studio-2012-rtm-available-installed/ Covers installing and upgrading to Visual Studio 2012 RTM and Team Foundation Server, key new features, upgrade tips, common issues, and practical migration advice. https://engineering-leadership-preview.hinshelwood.com/articles/engaging-with-complexity-team-foundation-server-edition/ Mon, 01 Jul 2013 17:00:31 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/engaging-with-complexity-team-foundation-server-edition/ Detailed walkthrough of a complex Team Foundation Server migration, covering remediation, hardware moves, upgrades, user management, and validation in large enterprise environments. 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/articles/project-of-projects-with-team-foundation-server-2010/ Tue, 04 Jan 2011 23:51:49 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/project-of-projects-with-team-foundation-server-2010/ Guidance on structuring projects in Team Foundation Server 2010 using Areas, Iterations, source code organisation, work item queries, and build naming for clarity and scalability. https://engineering-leadership-preview.hinshelwood.com/articles/syncing-many-dynamics-ax-instances-to-a-single-tfs-2010-team-project/ Fri, 08 Oct 2010 16:20:46 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/syncing-many-dynamics-ax-instances-to-a-single-tfs-2010-team-project/ Explains how to configure multiple Dynamics AX instances to sync with a single TFS 2010 Team Project, streamlining source control and work item management for many clients. https://engineering-leadership-preview.hinshelwood.com/articles/how-to-deal-with-a-stuck-or-infinitely-queued-build/ Thu, 09 Sep 2010 12:59:23 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/how-to-deal-with-a-stuck-or-infinitely-queued-build/ Learn how to identify, troubleshoot, and resolve stuck or infinitely queued builds in Team Foundation Build, including tips for monitoring and restarting build services. https://engineering-leadership-preview.hinshelwood.com/articles/rangers-shipped-visual-studio-2010-database-guide/ Wed, 25 Aug 2010 14:04:14 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/rangers-shipped-visual-studio-2010-database-guide/ Comprehensive guidance and hands-on labs for managing, testing, and deploying Visual Studio 2010 Database projects, including source control and automation tips. https://engineering-leadership-preview.hinshelwood.com/articles/tfs-event-handler-in-net-3-5-part-1-the-architecture/ Tue, 21 Aug 2007 21:10:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/tfs-event-handler-in-net-3-5-part-1-the-architecture/ Explains designing a resilient, scalable TFS event handler in .NET 3.5, focusing on system architecture using Visual Studio diagrams for planning and deployment. 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/the-benefits-of-visual-studio-online-for-the-enterprise/ Mon, 26 Jan 2015 14:13:11 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/the-benefits-of-visual-studio-online-for-the-enterprise/ Visual Studio Online offers enterprises always up-to-date tools, integrated build and release management, global access, and reduced infrastructure overhead, enabling greater agility and faster feature delivery. While some customisation and reporting features from TFS are still missing, Microsoft is actively addressing these gaps, and most teams can work around them using tags and new reporting options. Development managers should consider VSO to streamline operations, lower support costs, and keep pace with evolving business needs, provided they are ready for the cultural shift to cloud-based development. https://engineering-leadership-preview.hinshelwood.com/articles/create-log-entries-in-release-management/ Fri, 12 Dec 2014 17:13:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/create-log-entries-in-release-management/ Creating log entries in Release Management can be challenging because standard output commands like Write-Host and Write-Output do not appear in deployment logs. To capture log information, you need to use Write-Verbose with the -verbose flag in your PowerShell scripts. Ensure your deployment scripts use this approach so you have logs for both successful and failed steps, which is important for troubleshooting and auditing. https://engineering-leadership-preview.hinshelwood.com/articles/ndc-london-2014-why-tfs-no-longer-sucks-and-vso-is-awesome/ Wed, 10 Dec 2014 16:23:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/ndc-london-2014-why-tfs-no-longer-sucks-and-vso-is-awesome/ Team Foundation Server has significantly improved since 2012, and Visual Studio Online now offers a streamlined, cloud-based experience that eliminates many previous pain points. Recent demos showed that setup is fast, workflows are smoother, and release management is much easier, though some minor technical issues can still occur. Development managers should consider revisiting TFS and VSO for modern, efficient project and release management. https://engineering-leadership-preview.hinshelwood.com/articles/the-tfs-automation-platform-is-dead-long-live-the-tfplugable/ Thu, 31 Jan 2013 20:52:16 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/the-tfs-automation-platform-is-dead-long-live-the-tfplugable/ Explores the shift from TFS Automation Platform to TfPlugable, aiming to simplify discovery, deployment, and management of Team Foundation Server extensions. https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-to-team-foundation-server-2012-update-1-in-production-%E2%80%93-done/ Mon, 31 Dec 2012 18:47:34 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/upgrading-to-team-foundation-server-2012-update-1-in-production-%E2%80%93-done/ Step-by-step guide to upgrading Team Foundation Server 2012 to Update 1, including prerequisites, backup, disk space, configuration, troubleshooting, and build server setup. https://engineering-leadership-preview.hinshelwood.com/articles/visual-studio-2012-launch-roadshows-around-the-world/ Fri, 21 Sep 2012 21:08:33 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/visual-studio-2012-launch-roadshows-around-the-world/ Global Visual Studio 2012 launch events featuring keynotes on IT consumerisation and agile development, with sessions in the UK, US, and Netherlands. https://engineering-leadership-preview.hinshelwood.com/articles/tfs-2012-issue-stuck-builds-in-team-foundation-build-with-no-build-number/ Thu, 30 Aug 2012 05:40:19 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/tfs-2012-issue-stuck-builds-in-team-foundation-build-with-no-build-number/ Explains how to resolve stuck builds in TFS 2012 where no build number is assigned, caused by IIS multiple site bindings, with steps to fix via web.config settings. https://engineering-leadership-preview.hinshelwood.com/articles/deploy-from-visual-studio-2012-to-ios-windows-phone-android-and-windows/ Fri, 03 Aug 2012 01:00:56 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/deploy-from-visual-studio-2012-to-ios-windows-phone-android-and-windows/ Learn how to use Visual Studio 2012 and C# to build and deploy a single codebase to iOS, Android, Windows, and more, with options for generic or platform-specific UIs. 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/visual-studio-2010-overview-reporting-process/ Thu, 02 Feb 2012 17:00:03 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/visual-studio-2010-overview-reporting-process/ Learn how to customise Visual Studio 2010 process templates and use reporting tools to track, adapt, and improve team workflows with TFS for better project management. https://engineering-leadership-preview.hinshelwood.com/articles/not-just-happy-but-ecstatic/ Fri, 16 Sep 2011 00:01:51 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/not-just-happy-but-ecstatic/ A consultant reflects on a successful Microsoft Dynamics deployment, improved build automation, and positive client feedback, inspiring interest in future UK and European projects. https://engineering-leadership-preview.hinshelwood.com/articles/a-working-test-track-pro-adapter-for-the-tfs-integration-platform/ Mon, 06 Jun 2011 14:23:09 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/a-working-test-track-pro-adapter-for-the-tfs-integration-platform/ Describes building a working Test Track Pro Adapter for the TFS Integration Platform, detailing code changes, conflict handling, and incremental work item migration. https://engineering-leadership-preview.hinshelwood.com/articles/test-track-pro-and-the-case-of-the-missing-data/ Mon, 06 Jun 2011 05:24:51 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/test-track-pro-and-the-case-of-the-missing-data/ Explains issues with Test Track Pro data queries in TFS Integration, highlighting problems with date filters causing missing records and suggesting hourly filtering as a fix. https://engineering-leadership-preview.hinshelwood.com/articles/anatomy-of-an-automation-for-the-tfs-automation-platform/ Wed, 01 Jun 2011 13:25:46 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/anatomy-of-an-automation-for-the-tfs-automation-platform/ Explains how to build, install, configure, and run automations for TFS, covering plugin deployment, activation, settings, UI integration, and job processing steps. https://engineering-leadership-preview.hinshelwood.com/articles/ssw-brain-quest-team-foundation-server-and-sharepoint-2010-london/ Fri, 02 Jul 2010 11:05:43 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/ssw-brain-quest-team-foundation-server-and-sharepoint-2010-london/ Full-day training covering new features and best practices in Visual Studio 2010, Team Foundation Server 2010, and SharePoint 2010 for project management and integration. https://engineering-leadership-preview.hinshelwood.com/articles/solution-getting-silverlight-to-build-on-team-foundation-build-services-2010/ Wed, 03 Mar 2010 14:46:08 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/solution-getting-silverlight-to-build-on-team-foundation-build-services-2010/ Step-by-step guide to resolving build failures when compiling Silverlight 3 projects with Team Foundation Build Services 2010, including SDK, MSBuild, and code analysis fixes. https://engineering-leadership-preview.hinshelwood.com/articles/unity-and-asp-net/ Fri, 08 May 2009 17:31:10 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/unity-and-asp-net/ Explains how to use Unity for dependency injection in ASP.NET, enabling runtime component swapping without redeploying, with practical code and config examples. https://engineering-leadership-preview.hinshelwood.com/articles/fail-a-build-if-tests-fail/ Fri, 01 May 2009 11:11:37 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/fail-a-build-if-tests-fail/ Explains how to configure TFS 2008 builds to automatically fail if any tests fail by setting TreatTestFailureAsBuildFailure to true in the build project file. https://engineering-leadership-preview.hinshelwood.com/articles/visual-studio-team-test-quick-reference-guide-1-0/ Wed, 01 Apr 2009 16:28:13 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/visual-studio-team-test-quick-reference-guide-1-0/ A practical guide offering solutions, workarounds, and troubleshooting tips for Microsoft Visual Studio Team Test, based on real-world testing experience and expert advice. https://engineering-leadership-preview.hinshelwood.com/articles/vsts-sync-migration-tool-update-and-bugfix/ Wed, 21 Jun 2017 13:08:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/vsts-sync-migration-tool-update-and-bugfix/ The VSTS Sync Migration Tool has been updated with new features like work item history and query migration, plus important bug fixes such as resolving closed date issues. Community contributions have improved bulk updates and project migrations, and users now receive update notifications automatically. Development managers should install the latest version to benefit from these enhancements and stay informed about future updates. https://engineering-leadership-preview.hinshelwood.com/videos/mastering-cloud-migration-how-to-leverage-microsoft-s-tool-for-a-seamless-transition/ Wed, 18 Sep 2024 11:59:33 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/mastering-cloud-migration-how-to-leverage-microsoft-s-tool-for-a-seamless-transition/ Using Microsoft’s migration tool helps identify and address potential issues with your systems and customisations before moving to the cloud, reducing post-migration problems. Review all customisations for compatibility, plan necessary rewrites, and track tasks to ensure nothing is missed. Proactively using these steps will make your cloud migration smoother and more reliable. https://engineering-leadership-preview.hinshelwood.com/articles/migrating-from-codeplex-to-github/ Wed, 02 Mar 2016 14:29:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/migrating-from-codeplex-to-github/ Migrating a Codeplex repository to GitHub is necessary due to declining support and features on Codeplex, but GitHub’s import tool is unreliable and does not handle folder selection or branches well. Using Git-TF with Chocolatey provides a more flexible and effective migration, allowing you to select specific folders and preserve history, though some manual steps are needed for wiki pages and other content. Development managers should use Git-TF for smoother migrations and plan for some manual adjustments, especially for documentation. https://engineering-leadership-preview.hinshelwood.com/articles/using-the-build-vnext-capabilities-and-demands-system/ Wed, 11 Mar 2015 14:10:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/using-the-build-vnext-capabilities-and-demands-system/ Build vNext in TFS 2015 introduces a capabilities and demands system that replaces the old agent tagging approach, making it easier to match build agents to specific build requirements. Agents now auto-detect many capabilities, and you can add custom ones like OS version to ensure builds run on suitable machines. This streamlines build configuration and targeting, so managers should explore Build vNext to improve build reliability and agent management. 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/professional-application-lifecycle-management-with-visual-studio-2013/ Mon, 07 Apr 2014 17:11:35 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/professional-application-lifecycle-management-with-visual-studio-2013/ Guide to using Visual Studio 2013 for application lifecycle management, covering new ALM features, agile practices, Git integration, and cross-platform development. https://engineering-leadership-preview.hinshelwood.com/articles/should-i-upgrade-to-tfs-2013-update-2/ Thu, 03 Apr 2014 19:26:22 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/should-i-upgrade-to-tfs-2013-update-2/ Covers new features and upgrade steps for Team Foundation Server 2013 Update 2, including improvements in backlog, test, release, and version management. https://engineering-leadership-preview.hinshelwood.com/articles/powershell-tfs-2013-api-2-adding-to-a-globallist/ Wed, 16 Oct 2013 10:30:57 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/powershell-tfs-2013-api-2-adding-to-a-globallist/ Learn how to use PowerShell and the TFS 2013 API to automate adding items to a GlobalList by exporting, editing, and re-importing global lists as XML. https://engineering-leadership-preview.hinshelwood.com/articles/creating-a-custom-activity-for-team-foundation-build/ Mon, 22 Jul 2013 08:56:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/creating-a-custom-activity-for-team-foundation-build/ Learn how to create and integrate custom activities in Team Foundation Build, including class library setup, workflow design, argument handling, and build configuration. https://engineering-leadership-preview.hinshelwood.com/articles/tfs-integration-tools-%E2%80%93-issue-error-occurred-during-the-code-review-of-change-group/ Wed, 11 Jul 2012 20:51:03 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/tfs-integration-tools-%E2%80%93-issue-error-occurred-during-the-code-review-of-change-group/ Explains causes and solutions for the “Error occurred during the code review of change group” in TFS Integration Tools, including common triggers and recommended workarounds. https://engineering-leadership-preview.hinshelwood.com/articles/upgrade-to-visual-studio-11-team-foundation-service-done/ Fri, 24 Feb 2012 19:26:30 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/upgrade-to-visual-studio-11-team-foundation-service-done/ Explains migrating source control and work item tracking to Visual Studio 11 Team Foundation Service, highlighting cloud benefits, limitations, and steps for a smooth upgrade. https://engineering-leadership-preview.hinshelwood.com/articles/visual-studio-2010-overview-architecture/ Wed, 01 Feb 2012 19:10:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/visual-studio-2010-overview-architecture/ Explains how Visual Studio 2010 supports teams in visualising, analysing, and maintaining software architecture, with tools for design, standards, and verification. https://engineering-leadership-preview.hinshelwood.com/articles/visual-studio-2010-overview-microsoft-test-manager/ Tue, 31 Jan 2012 03:57:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/visual-studio-2010-overview-microsoft-test-manager/ Covers using Microsoft Test Manager with Visual Studio 2010 and TFS to create, run, and manage manual and automated tests, including real-time test data collection. https://engineering-leadership-preview.hinshelwood.com/articles/configuring-a-powershell-adapter-for-the-tfs-integration-platform/ Thu, 23 Jun 2011 03:58:19 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/configuring-a-powershell-adapter-for-the-tfs-integration-platform/ Explains how to set up and configure a PowerShell adapter in the TFS Integration Platform to automate source control migrations, with custom scripts for each change type. https://engineering-leadership-preview.hinshelwood.com/articles/what-is-the-tfs-automation-platform/ Tue, 31 May 2011 18:00:04 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/what-is-the-tfs-automation-platform/ A platform for automating Team Foundation Server tasks, enabling scheduled, event-driven, and on-demand workflows, with extensible package and Visual Studio integration. https://engineering-leadership-preview.hinshelwood.com/articles/do-you-know-about-the-visual-studio-2010-architecture-guidance/ Fri, 04 Feb 2011 01:08:04 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/do-you-know-about-the-visual-studio-2010-architecture-guidance/ Provides practical samples, checklists, and hands-on labs to help developers and architects use Visual Studio 2010 Ultimate’s architecture modelling tools effectively. https://engineering-leadership-preview.hinshelwood.com/articles/silverlight-4-mvvm-and-test-driven-development/ Tue, 20 Apr 2010 14:54:56 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/silverlight-4-mvvm-and-test-driven-development/ Learn how to use Silverlight 4 and the MVVM pattern for test-driven development, including refactoring, dependency injection, and building real-world applications. https://engineering-leadership-preview.hinshelwood.com/articles/when-should-i-use-areas-in-tfs-instead-of-team-projects-in-team-foundation-server-2010/ Tue, 09 Mar 2010 12:27:20 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/when-should-i-use-areas-in-tfs-instead-of-team-projects-in-team-foundation-server-2010/ Explains when to use Areas versus Team Projects in TFS 2010, comparing benefits, drawbacks, and best practices for managing multiple projects and process templates. https://engineering-leadership-preview.hinshelwood.com/articles/mvvm-for-dummies/ Fri, 05 Mar 2010 16:54:54 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/mvvm-for-dummies/ Explains the MVVM pattern in WPF and Silverlight, highlighting separation of concerns, code structure, and the roles of commanding, dependency injection, and design patterns. https://engineering-leadership-preview.hinshelwood.com/articles/updating-the-command-line-parser/ Mon, 17 Aug 2009 01:11:08 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/updating-the-command-line-parser/ Explains how to enhance a .NET command line parser to support multiple and nested commands, custom switches, and delegate-based execution for flexible CLI applications. https://engineering-leadership-preview.hinshelwood.com/articles/wpf-drag-drop-behaviour/ Fri, 14 Aug 2009 04:16:04 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/wpf-drag-drop-behaviour/ Explains how to implement flexible drag and drop in WPF using MVVM, with customisable drop behaviour and bindable options for ItemsControls, including code examples. https://engineering-leadership-preview.hinshelwood.com/articles/a-perfect-match-tfs-and-dlr/ Mon, 27 Jul 2009 22:25:25 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/a-perfect-match-tfs-and-dlr/ Explores integrating Team Foundation Server check-in policies with the Dynamic Language Runtime to enable flexible, centralised policy management across clients. https://engineering-leadership-preview.hinshelwood.com/articles/visual-studio-team-system-2008-database-edition-gdr-has-been-released/ Wed, 26 Nov 2008 09:55:11 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/visual-studio-team-system-2008-database-edition-gdr-has-been-released/ The new Database Edition GDR for Visual Studio Team System 2008 adds model-based SQL schema design, extensibility, provider support, and standalone deployment tools. https://engineering-leadership-preview.hinshelwood.com/articles/branch-madness/ Wed, 22 Oct 2008 14:44:57 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/branch-madness/ Describes a complex source control issue in TFS involving branch mismanagement, its impact on merging, and step-by-step actions taken to restore proper branch structure. https://engineering-leadership-preview.hinshelwood.com/articles/heat-itsm/ Fri, 22 Aug 2008 08:35:30 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/heat-itsm/ Describes integrating Heat ITSM with Team Foundation Server to sync and manage support calls, automate work item creation, and streamline IT support workflows. https://engineering-leadership-preview.hinshelwood.com/articles/creating-a-better-tfs-sticky-buddy-core/ Mon, 14 Apr 2008 09:36:36 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/creating-a-better-tfs-sticky-buddy-core/ Explains building a flexible WPF data model in VB.NET for visualising hierarchical relationships using generics, ObservableCollections, and INotifyPropertyChanged. https://engineering-leadership-preview.hinshelwood.com/articles/microsoft's-internal-uptake-of-team-foundation-server/ Sun, 05 Aug 2007 12:19:04 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/microsoft's-internal-uptake-of-team-foundation-server/ Microsoft widely adopted Team Foundation Server internally, with 21 instances supporting 734 projects and 5,600 users, driving rapid product development and updates. https://engineering-leadership-preview.hinshelwood.com/articles/creating-a-managed-service-factory/ Tue, 19 Jun 2007 20:28:07 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/creating-a-managed-service-factory/ Explains how to build a managed service factory to access and manage local or remote services across multiple servers, supporting flexible service discovery and integration. https://engineering-leadership-preview.hinshelwood.com/articles/custom-wcf-proxy/ Tue, 29 May 2007 23:41:16 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/custom-wcf-proxy/ Explains how to create custom WCF proxies in .NET to avoid redundant class generation and object conversion when consuming Windows Communication Foundation services. 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/increment/ Mon, 05 May 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/increment/ Increment refers to the tangible, usable output produced at the end of each iteration, particularly within frameworks like Scrum and Agile. It encapsulates the totality of completed work during a Sprint, ensuring that the product remains potentially shippable and consistently adds measurable value. As a core artifact in Scrum, the Increment embodies the principle of delivering working software incrementally, which facilitates timely feedback, iterative improvements, and mitigates the risks associated with large-scale releases. Its significance lies in the transparency it provides, allowing teams and stakeholders to assess progress clearly, thereby fostering collaboration and alignment. In Agile environments, the Increment serves as a foundation for adaptation, enabling teams to refine their strategies based on feedback and respond effectively to evolving requirements. By prioritising the delivery of increments, organisations can enhance workflows, promote continuous improvement, and ensure that products develop in alignment with customer needs. This focus on delivering working software helps minimise technical debt and prevents over-engineering, aligning development efforts more closely with business objectives. Ultimately, the Increment delivers the concrete, inspectable output that informs decision-making and enhances collaboration, making it a vital component of Agile and Scrum practices. 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/lead-time/ Fri, 11 Apr 2025 06:00:00 +0100 https://engineering-leadership-preview.hinshelwood.com/tags/lead-time/ Lead Time is an essential observability metric that quantifies the duration from the initiation of a work item to its delivery to the customer. It is a practical implementation of Cycle Time often used in flow-based systems such as Kanban. This metric provides end-to-end visibility into workflow performance, helping teams identify inefficiencies and optimise delivery for improved predictability and responsiveness. By exposing how long it takes to deliver value, Lead Time enables real-time insight into system health and team effectiveness, supporting continuous improvement across Agile, Lean, and DevOps environments. https://engineering-leadership-preview.hinshelwood.com/tags/github/ Thu, 10 Apr 2025 10:16:54 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/github/ GitHub is a comprehensive platform that facilitates version control, collaboration, and integration within software development. Originating as a hosting service for Git repositories, it has evolved to include features such as GitHub Actions for automating continuous integration and continuous delivery workflows, and GitHub Projects for task management and progress tracking. Its significance lies in its ability to enhance collaboration among development teams, reduce friction in development cycles, and support the efficient delivery of value. GitHub is essential for organisations seeking to maintain transparency and integrate workflows between development and operations teams, as its integration with CI/CD practices allows for the automation of testing, builds, and deployments, ensuring continuous validation and delivery of code changes. The platform’s features, including issues, pull requests, and discussions, foster effective communication and alignment on project goals. Additionally, GitHub’s compatibility with a variety of third-party tools and services further amplifies its effectiveness in modern DevOps environments. By utilising GitHub’s extensive toolset, organisations can enhance team collaboration, streamline development processes, and improve software delivery outcomes. https://engineering-leadership-preview.hinshelwood.com/concepts/observability/ Wed, 09 Apr 2025 14:00:00 +0100 https://engineering-leadership-preview.hinshelwood.com/concepts/observability/ Observability is the practice of gaining comprehensive insights into systems and processes, enabling teams to understand work flows and value delivery. It transcends traditional monitoring by offering a holistic view of system behaviour, which allows teams to identify patterns, diagnose issues, and make informed decisions based on real-time data. This capability is essential for fostering transparency and collaboration within teams and across organisational silos. By implementing observability, organisations can improve their ability to deliver value predictably and sustainably, supporting continuous improvement through learning and adaptation. It encompasses not only technical telemetry but also signals reflecting team dynamics, product experiences, and alignment with strategic goals, thus providing a complete view of performance that includes both human and technical factors. When integrated into daily practices, observability cultivates a feedback-rich environment that enhances decision-making and strengthens delivery capabilities. It represents a cultural shift that empowers teams to take ownership of their processes and outcomes, aligning with Lean and Agile principles focused on understanding flow and eliminating waste. By embedding observability into the organisational framework, teams can create a resilient environment that leverages data-driven insights, ultimately leading to improved products, stronger teams, and more strategic business outcomes. 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/tags/competence/ Fri, 21 Mar 2025 14:44:55 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/competence/ Competence is a critical element of professional effectiveness, encompassing the development, demonstration, and application of essential skills, knowledge, and judgement to achieve quality outcomes. It is derived from a commitment to continuous learning and deliberate practice, requiring individuals and organisations to earn and adapt their capabilities over time. In the context of agile methodologies, DevOps practices, product development, and organisational design, competence is vital as it underpins the successful execution of frameworks, processes, and tools. Without a foundation of competence, efforts may devolve into performative activities that fail to yield meaningful progress, jeopardising quality, trust, and value delivery. Therefore, every decision and action taken within an organisation must be rooted in the ability to execute with professionalism and expertise, ensuring that the outcomes align with the intended goals and standards. https://engineering-leadership-preview.hinshelwood.com/tags/continuous-delivery/ Fri, 21 Mar 2025 13:37:32 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/continuous-delivery/ Continuous Delivery is a software delivery practice that focuses on producing software in short, reliable cycles, enabling teams to release updates at any time. Originating from the need for more efficient and responsive software development processes, it involves delivering small, incremental improvements directly to users from the initial stages of development. This approach, as defined by Jez Humble, emphasises the ability to safely and quickly implement changes, such as new features, configuration adjustments, and bug fixes, into production. The importance of Continuous Delivery lies in its capacity to facilitate rapid validation of assumptions and collection of user feedback, which are crucial for refining products and achieving valuable outcomes. By automating essential processes like testing, integration, and deployment, Continuous Delivery not only mitigates the risk of errors but also enhances software quality and accelerates the time it takes to deliver value to users. Teams that adopt this practice can more effectively respond to market demands and stakeholder input, thereby fostering a culture of continuous learning, innovation, and adaptability within their organisations. https://engineering-leadership-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/behaviour-driven-development/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/behaviour-driven-development/ Behaviour Driven Development (BDD) is a collaborative methodology that aligns software development with business objectives by promoting clear communication among all stakeholders involved. Originating from the need to bridge the gap between technical and non-technical participants, BDD utilises natural language to articulate the desired behaviour of a system, fostering a shared understanding of requirements that are both testable and comprehensible. This approach is crucial in agile and DevOps environments, as it encourages teams to focus on user-centric outcomes, thereby enhancing collaboration and minimising ambiguity in requirements. By reducing misunderstandings and the need for rework, BDD enables teams to deliver features that more accurately meet user needs, resulting in a more predictable and sustainable development process. Furthermore, BDD supports continuous improvement by integrating with automated testing and continuous delivery practices, ensuring that teams remain aligned with user value as they iterate on their products. This emphasis on behaviour over mere functionality cultivates a culture of shared ownership and accountability, empowering teams to innovate while maintaining a clear focus on business goals, ultimately driving a deeper understanding of user needs and enhancing overall product quality. https://engineering-leadership-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/tags/cycle-time/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/cycle-time/ Cycle time is a key performance metric that measures the total duration required to complete a unit of work, from initiation to delivery. It is widely used in agile and DevOps methodologies to enhance team efficiency and predictability in value delivery. By monitoring cycle time, organisations can pinpoint bottlenecks, streamline processes, and optimise workflows, which leads to quicker product and service delivery. Understanding cycle time empowers teams to make data-driven decisions, fostering a culture of continuous improvement and enabling better forecasting and planning based on historical data. This predictability is crucial for aligning stakeholder expectations and meeting customer needs promptly. Furthermore, cycle time promotes a holistic view of value delivery, encouraging teams to consider the entire workflow rather than focusing on individual tasks. By minimising cycle time, organisations can improve their responsiveness to market dynamics and customer feedback, thereby gaining a competitive edge. In an era where rapid and sustainable value delivery is essential, the emphasis on cycle time is vital for organisational success. https://engineering-leadership-preview.hinshelwood.com/tags/deployment-frequency/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/deployment-frequency/ Deployment Frequency is a key metric that measures the rate at which software is released into production, playing a vital role in contemporary product development. It originates from the need for organisations to enhance their responsiveness to customer needs by facilitating quicker feedback loops and adjustments. By optimising deployment frequency, teams can not only release features and fixes more frequently but also validate their assumptions and learn from real-world usage promptly. This concept is crucial for cultivating a culture of continuous improvement and innovation, allowing teams to experiment, iterate, and adapt to market changes effectively. A high deployment frequency reflects a mature DevOps practice characterised by automation, collaboration, and efficient processes that enable rapid delivery without sacrificing quality. Additionally, it fosters a sense of accountability and ownership among team members, as they can directly observe the impact of their contributions on end-users. By prioritising deployment frequency, organisations can establish a sustainable delivery rhythm that enhances customer satisfaction and drives long-term business success through consistent value delivery and adaptability. This systemic approach not only promotes resilience and agility but also ensures that teams remain competitive in an ever-evolving digital landscape. https://engineering-leadership-preview.hinshelwood.com/tags/deployment-strategies/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/deployment-strategies/ Deployment strategies are systematic approaches that organisations utilise to release software into production, balancing the need for speed with risk management. These strategies are essential for enabling teams to deliver value in a predictable and sustainable manner, facilitating rapid iterations and continuous feedback. Techniques such as blue-green deployments, canary releases, and rolling updates help mitigate the impact of potential failures, allowing teams to address issues swiftly without causing significant disruption to users. The effectiveness of deployment strategies lies in their capacity to cultivate a culture of experimentation and learning, encouraging continuous improvement where each deployment provides insights for refining processes. This approach enhances operational efficiency and aligns with Agile and DevOps principles, fostering collaboration and shared responsibility among cross-functional teams. Furthermore, well-defined deployment strategies contribute to a resilient organisational structure, enabling teams to adapt to evolving market demands and technological changes. By prioritising safe and efficient releases, organisations can maintain a competitive advantage while ensuring customer satisfaction remains central to their product development efforts. Ultimately, the integration of deployment strategies into the broader organisational framework supports sustainable growth and reinforces the importance of delivering value through strategic software releases. https://engineering-leadership-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/forecasting/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/forecasting/ Forecasting is the practice of utilising empirical data to predict delivery timelines, manage risks, and optimise value delivery within Agile and Scrum frameworks. It draws from historical performance and current capacity metrics, such as cycle time, lead time, and throughput, enabling teams to make informed decisions that lead to a more predictable and sustainable approach to product development. This practice is vital for promoting transparency and accountability, as it encourages teams to reflect on their processes and outcomes, moving beyond subjective estimations to data-driven insights that enhance decision-making. By anticipating challenges and adapting proactively, teams can improve overall efficiency and effectiveness. Integrating forecasting into Agile practices not only aids in achieving immediate project goals but also fosters long-term organisational agility, creating a resilient environment that can adapt to changing market demands. This systemic approach ultimately enhances the ability to deliver high-quality products that align with customer needs and business objectives, thereby cultivating a culture of continuous improvement and innovation. https://engineering-leadership-preview.hinshelwood.com/tags/frequent-releases/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/frequent-releases/ Frequent releases are the practice of delivering small, incremental updates to products or services on a regular basis, originating from agile methodologies and widely adopted in DevOps environments. This approach is essential for organisations seeking to swiftly respond to user feedback and market dynamics, ensuring consistent value delivery to stakeholders. By segmenting larger projects into manageable releases, teams can mitigate deployment risks, as smaller updates are easier to test and validate. This practice cultivates a culture of continuous improvement, enabling teams to iterate based on real-world usage and feedback, which is vital for maintaining a competitive edge in adapting to evolving customer needs and technological advancements. Additionally, frequent releases promote collaboration among developers, testers, and product owners, fostering a cohesive environment for product enhancement. They also contribute to a sustainable development pace, reducing the risk of burnout associated with large, infrequent releases, which in turn boosts team morale and builds stakeholder trust through visible progress and tangible outcomes. By integrating frequent releases into their operational frameworks, organisations can ensure they remain responsive and relevant in a rapidly changing market landscape. 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/release-management/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/release-management/ Release Management is a systematic approach to planning, scheduling, and controlling the deployment of software releases to testing and live environments. Originating from the need for structured software delivery, it plays a critical role in ensuring that software is released in a predictable and sustainable manner, aligning with both organisational objectives and customer expectations. Effective release management minimises deployment risks, enhances interdepartmental collaboration, and keeps all stakeholders informed and engaged throughout the release process. This practice allows teams to deliver value incrementally, facilitating rapid feedback and adaptation, and fostering a culture of continuous improvement where each release serves as a learning opportunity. It integrates well with Continuous Delivery and Agile methodologies, optimising workflow and maintaining quality at every stage. Unlike Agile Planning or Product Management, which focus on strategic development aspects, Release Management is operational, concentrating on the tactical execution of software delivery. It necessitates a comprehensive understanding of technical and organisational dynamics, making it essential for modern product development. By establishing clear release processes, organisations can better respond to market changes and customer feedback, ultimately enhancing customer satisfaction and loyalty. https://engineering-leadership-preview.hinshelwood.com/tags/software-development/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/software-development/ Software Development refers to the systematic techniques and methodologies used to create high-quality software solutions that align with user needs and business objectives. Originating from various practices such as Agile, Lean, and DevOps, it aims to improve collaboration, efficiency, and adaptability within development teams. This approach is vital as it allows organisations to deliver value in a predictable and sustainable manner, fostering a culture of continuous improvement and responsiveness to change. By emphasising iterative development, teams can swiftly adapt to feedback and changing requirements, ensuring the software remains relevant and effective. Additionally, the focus on automation, testing, and integration mitigates the risk of defects and accelerates delivery cycles, leading to more frequent releases and increased customer satisfaction. Software Development also encourages a comprehensive view of the software lifecycle, promoting cross-functional collaboration and knowledge sharing among team members. This long-term, systemic approach not only enhances software quality but also nurtures an innovative environment, enabling organisations to stay competitive in a fast-evolving market. The incorporation of evidence-based management principles further aids informed decision-making, equipping teams to effectively navigate complexity and uncertainty. By prioritising these practices, organisations can secure a sustainable competitive advantage through improved software development capabilities that align with their strategic goals and customer expectations. 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/azure-devops/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/azure-devops/ Azure DevOps is a comprehensive suite of tools developed by Microsoft that supports continuous integration and continuous delivery (CI/CD), enhances collaboration, and streamlines agile project management. It encompasses various functionalities, including Azure Boards for work tracking, Azure Repos for source control, Azure Pipelines for automating builds and deployments, and Azure Test Plans for managing testing efforts. This platform is crucial for organisations seeking to deliver value in a predictable and sustainable manner, as it promotes a culture of collaboration and transparency among teams. By providing a unified environment for development and operations, Azure DevOps facilitates the adoption of best practices in agile methodologies and DevOps principles, ensuring efficient software delivery that is responsive to evolving business needs. Its systemic approach encourages continuous improvement and learning, enabling organisations to swiftly adapt to market demands while upholding high-quality standards. The integration of tools within Azure DevOps mitigates silos, enhances communication, and fosters a shared understanding of project objectives, ultimately leading to improved outcomes and a culture of innovation. This capability is vital for organisations aiming to achieve operational excellence and maintain a competitive advantage in a fast-changing landscape. https://engineering-leadership-preview.hinshelwood.com/tags/metrics-and-learning/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/metrics-and-learning/ Metrics and Learning is a fundamental concept that centres on the utilisation of data, metrics, and feedback to drive continuous improvement within teams and organisational processes. Originating from the need for empirical decision-making, this approach allows organisations to enhance their value delivery by systematically collecting and analysing performance metrics. By doing so, teams can pinpoint areas for enhancement, monitor their progress, and adjust their strategies in alignment with changing customer demands. The focus on learning through metrics fosters a culture of experimentation and adaptability, enabling teams to respond swiftly to feedback and pivot as necessary. This systemic approach not only facilitates immediate improvements but also lays the groundwork for sustained development and innovation. Unlike methodologies that may be prescriptive, Metrics and Learning empowers teams to take ownership of their performance, which is essential for maintaining agility in a fast-paced environment. By integrating metrics into everyday operations, organisations can establish a continuous feedback loop that informs practices and strategies, ultimately leading to more effective and resilient product development. https://engineering-leadership-preview.hinshelwood.com/tags/one-engineering-system/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/one-engineering-system/ The One Engineering System (1ES) is a strategic framework designed to unify engineering tools and practices across various teams, aiming to reduce friction, enhance collaboration, and ensure consistency at scale. Originating from the need to streamline workflows in software development, 1ES focuses on establishing a shared engineering backbone that allows teams to operate more efficiently by eliminating the chaos associated with disparate toolchains and ad hoc processes. This approach is crucial in agile and DevOps environments, as it promotes a common set of engineering standards that facilitate planning, coding, testing, deployment, and production support. By reducing cognitive overhead and simplifying integration, 1ES enables teams to deliver high-quality outcomes more reliably. Importantly, the framework emphasises that tools should adapt to the teams’ workflows rather than impose rigid structures, allowing for flexibility and coherence rather than uniformity. Successful implementation of 1ES necessitates investment in team enablement, including guidance, training, and support, to ensure effective adoption. When executed properly, 1ES fosters scalable engineering excellence, characterised by clear communication, consistent processes, and a resilient development lifecycle across the organisation. 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.