https://engineering-leadership.hinshelwood.com/tags/operational-practices/ Recent content in Operational Practices on Engineering Leadership in AI & Software Hugo en Wed, 24 Jun 2026 10:41:27 +0000 https://engineering-leadership.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.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.hinshelwood.com/articles/stop-building-silos-start-building-systems/ Mon, 07 Jul 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/stop-building-silos-start-building-systems/ Fragmented automation and tool silos slow delivery, increase risk, and create confusion, while a unified engineering system enables speed, safety, and clarity. Standardising on a single platform like Azure Pipelines, with shared processes and guardrails, empowers teams to focus on delivering value instead of managing complexity. To scale effectively, consolidate your toolchain, define clear boundaries, and invest in platform engineering so teams can work autonomously within a reliable system. https://engineering-leadership.hinshelwood.com/articles/don-t-manage-dependencies-remove-them/ Mon, 29 Sep 2025 09:00:00 +0000 https://engineering-leadership.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.hinshelwood.com/articles/is-agile-really-just-a-mindset/ Mon, 11 Aug 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/is-agile-really-just-a-mindset/ Agile is not just a mindset or set of behaviours; it is a disciplined system of work rooted in engineering excellence, technical leadership, and empirical delivery. True agility requires robust engineering practices like CI/CD, automated testing, and observability, not just ceremonies or coaching. To achieve real Agile outcomes, focus on building systems that enable frequent, reliable delivery and hold both teams and leadership accountable for technical and organisational change. https://engineering-leadership.hinshelwood.com/articles/rethinking-capacity-planning/ Mon, 21 Jul 2025 09:00:00 +0000 https://engineering-leadership.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.hinshelwood.com/articles/why-topic-branches-drive-high-quality-delivery/ Mon, 14 Jul 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/why-topic-branches-drive-high-quality-delivery/ Short-lived topic branches help teams deliver high-quality software by making integration easier, reducing merge conflicts, and supporting modular, continuous delivery. Adopting models like GitHub Flow or Release Flow keeps work focused and feedback fast, while long-lived branches increase risk and slow down delivery. Development managers should enforce small, short-lived branches and regularly review branching strategies to maintain flow, agility, and quality. https://engineering-leadership.hinshelwood.com/videos/why-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.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.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.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.hinshelwood.com/articles/the-definition-of-done-is-a-commitment-to-quality/ Mon, 28 Jul 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/the-definition-of-done-is-a-commitment-to-quality/ A clear, shared Definition of Done is essential for delivering quality, releasable software in Scrum and aligns teams on what “complete” means. It ensures transparency, predictability, and accountability, protects your product’s reputation, and must be created, automated, and regularly improved by all teams working on a product. Development managers should prioritise running DoD workshops, making standards visible, automating checks, and reviewing the DoD every sprint to maintain quality and reduce risk. https://engineering-leadership.hinshelwood.com/videos/how-to-tackle-technical-debt-without-halting-progress-smarter-ways-to-keep-your-team-moving-forward/ Mon, 26 May 2025 06:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/how-to-tackle-technical-debt-without-halting-progress-smarter-ways-to-keep-your-team-moving-forward/ Technical debt slows teams down and hurts morale, but stopping all work to fix it is unrealistic. The most effective approach is to make technical debt visible, prioritize high-impact improvements, and embed continuous improvement into daily workflows. Development managers should focus on changing team practices and decision-making so that managing technical debt becomes a natural, ongoing part of delivering value. https://engineering-leadership.hinshelwood.com/articles/your-evolving-definition-of-done/ Mon, 31 Mar 2025 09:00:00 +0100 https://engineering-leadership.hinshelwood.com/articles/your-evolving-definition-of-done/ The Definition of Done should evolve as teams mature, starting with basic quality standards and expanding to include automation, security, and business-level requirements that align with organisational goals. A strong, consistently applied DoD reduces risk, rework, and delays, ensuring every increment is truly releasable and delivers real value. Development managers should regularly review and raise the DoD, embedding it into team practices to protect quality and support strategic objectives. https://engineering-leadership.hinshelwood.com/signals/velocity-isn-t-how-many-story-points-a-team-burns-down/ Mon, 10 Mar 2025 16:30:02 +0000 https://engineering-leadership.hinshelwood.com/signals/velocity-isn-t-how-many-story-points-a-team-burns-down/ Velocity is about how quickly your team delivers value, not just story points completed. Focus on measuring time to build, self-test, deploy, and learn from user feedback, as these are actionable and within your control. Start tracking these metrics to improve your delivery speed and effectiveness. https://engineering-leadership.hinshelwood.com/articles/stop-hiding-behind-complexity-and-start-delivering-continuously/ Mon, 24 Feb 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/stop-hiding-behind-complexity-and-start-delivering-continuously/ Complexity is not a valid reason to avoid continuous delivery; organisations like Azure DevOps and Starbucks have proven that even large, complex systems can achieve frequent, reliable releases with the right investment in automation, process improvement, and culture change. Key actions include automating everything, adopting trunk-based development, using feature flags, shifting quality left, and iterating on pain points. Development managers should focus on measuring and improving flow metrics and value delivery, prioritising organisational commitment to overcome resistance and realise the benefits of continuous delivery. https://engineering-leadership.hinshelwood.com/signals/scrum-masters-are-not-glorified-meeting-schedulers/ Sun, 09 Mar 2025 16:30:01 +0000 https://engineering-leadership.hinshelwood.com/signals/scrum-masters-are-not-glorified-meeting-schedulers/ Scrum Masters must have strong technical and business skills, including coding knowledge and expertise in modern engineering practices, to effectively lead software teams. They should be able to challenge teams, identify technical debt, and promote quality, not just schedule meetings. Ensure your Scrum Master can engage with developers on technical topics to achieve real agility. https://engineering-leadership.hinshelwood.com/articles/should-you-use-one-project-to-rule-them-all-in-azure-devops/ Mon, 25 Aug 2025 09:00:00 +0000 https://engineering-leadership.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.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.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.hinshelwood.com/articles/release-planning-and-predictable-delivery/ Tue, 24 Nov 2020 13:00:01 +0000 https://engineering-leadership.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.hinshelwood.com/videos/stop-paying-the-hidden-costs-of-weak-delivery-why-a-strong-definition-of-done-transforms-your-team-s-results/ Wed, 21 May 2025 06:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/stop-paying-the-hidden-costs-of-weak-delivery-why-a-strong-definition-of-done-transforms-your-team-s-results/ Cutting corners on quality and having a weak definition of done leads to hidden costs like rework, production risks, and lost trust. A clear, shared, and enforceable definition of done ensures every increment is truly usable, reliable, and aligned with business goals. Make your definition of done visible, evidence-based, and strictly enforced to improve delivery outcomes and build stakeholder confidence. https://engineering-leadership.hinshelwood.com/signals/engineering-can-fix-technical-debt-but-leadership-has-to-invest-in-it/ Mon, 03 Mar 2025 16:30:35 +0000 https://engineering-leadership.hinshelwood.com/signals/engineering-can-fix-technical-debt-but-leadership-has-to-invest-in-it/ Fixing technical debt requires leadership investment, not just harder work from engineers. Success comes from funding automation, better testing, and empowering teams to address issues directly. If continuous delivery is not happening, leaders should reconsider their priorities and support the necessary improvements. https://engineering-leadership.hinshelwood.com/articles/great-scrum-masters-need-technical-business-and-organisational-mastery/ Mon, 24 Mar 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/great-scrum-masters-need-technical-business-and-organisational-mastery/ Scrum Masters are most effective when they combine strong leadership skills with deep understanding of their team’s technical, business, and organisational context. Mastery in these three areas enables them to better remove obstacles, coach both teams and Product Owners, and drive meaningful change across the organisation. Development managers should ensure their Scrum Masters are experienced professionals who continuously build expertise in these domains to maximise team performance and value delivery. https://engineering-leadership.hinshelwood.com/videos/from-legacy-pain-to-modern-devops-my-proven-roadmap-for-real-engineering-transformation/ Mon, 04 Aug 2025 07:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/from-legacy-pain-to-modern-devops-my-proven-roadmap-for-real-engineering-transformation/ Transforming legacy engineering to modern DevOps requires a flexible, evidence-based approach focused on testing hypotheses, starting with the most challenging products, and automating every step from code commit to production. Involve all stakeholders to define essential requirements, automate approvals and deployments, and use phased rollouts with real-time feedback to minimize risk. Focus on one improvement at a time, build a culture of continuous learning, and scale successful practices across the organization. https://engineering-leadership.hinshelwood.com/signals/scrum-teams-don-t-set-the-bar-for-quality-they-meet-it/ Thu, 03 Apr 2025 15:30:01 +0100 https://engineering-leadership.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.hinshelwood.com/articles/testing-in-production-maximises-quality-and-value/ Thu, 13 Feb 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/testing-in-production-maximises-quality-and-value/ Testing in production using audience-based deployment enables faster feedback, safer incremental releases, and better alignment with real user needs compared to traditional Dev-Test-Staging pipelines. Microsoft’s shift to this model, driven by feature flags, progressive rollouts, and real-time monitoring, has improved quality and innovation while reducing risk and overhead. Development managers should consider moving away from environment-based branching and invest in automation, observability, and team upskilling to maximise value and responsiveness. https://engineering-leadership.hinshelwood.com/articles/definition-of-done-objective-vs-subjective/ Fri, 03 Jan 2025 00:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/definition-of-done-objective-vs-subjective/ The Definition of Done (DoD) in Scrum is an objective, measurable checklist that sets the minimum quality standard for every product increment, distinct from the more subjective Product and Sprint Goals. Teams should ensure their DoD is clear, comprehensive, regularly reviewed, and as automated as possible, avoiding subjective approval steps. Development managers should treat the DoD as a non-negotiable baseline for quality, not a ceiling, and keep it updated to reflect evolving standards and business needs. https://engineering-leadership.hinshelwood.com/articles/work-can-flow-across-the-sprint-boundary/ Tue, 30 Jan 2018 20:12:00 +0000 https://engineering-leadership.hinshelwood.com/articles/work-can-flow-across-the-sprint-boundary/ Allowing work to flow across Sprint boundaries is permitted in Scrum and can improve delivery speed, responsiveness, and value, as long as teams maintain clear, outcome-focused Sprint Goals and consistently deliver Done increments. Adopting practices like Continuous Delivery, feature toggles, and frequent feedback helps teams validate work early and adapt quickly. Development managers should encourage flow principles and robust engineering practices to maximize throughput and support better business decisions. https://engineering-leadership.hinshelwood.com/articles/are-we-still-pretending-coding-was-the-bottleneck/ Mon, 01 Sep 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/are-we-still-pretending-coding-was-the-bottleneck/ AI writing code is not the real game-changer; coding was never the main bottleneck in software delivery. The real constraints are in poor system design, handoffs, unclear requirements, and lack of built-in quality, which AI will only make more visible. To benefit from AI, focus on improving flow, building quality in from the start, and making teams accountable for outcomes rather than output. https://engineering-leadership.hinshelwood.com/videos/engineering-excellence-isn-t-perfection-how-continuous-improvement-and-fast-feedback-drive-real-agile-and-devops-success/ Mon, 21 Jul 2025 06:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/engineering-excellence-isn-t-perfection-how-continuous-improvement-and-fast-feedback-drive-real-agile-and-devops-success/ Engineering excellence is not about achieving perfection or creating exhaustive plans, but about building systems that continuously adapt and improve through fast feedback and incremental change. Key practices include clean code, observability, automated testing, and CI/CD, which together enable teams to deliver high-quality software quickly and respond to real-world needs. Development managers should focus on removing manual bottlenecks and technical debt to shorten feedback loops, as this is the foundation of true Agile and DevOps success. https://engineering-leadership.hinshelwood.com/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.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.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.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.hinshelwood.com/articles/resilience-is-part-of-the-product-not-an-afterthought/ Mon, 09 Jun 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/resilience-is-part-of-the-product-not-an-afterthought/ Resilience must be designed into your product from the start, not added later or left to individual heroics. Building resilience means engineering for failure containment, rapid recovery, and continuous improvement, using tools like telemetry, feature flags, and safe deployment practices. Make resilience a core part of your development process and culture, treating it as a critical feature to avoid costly outages and business risks. https://engineering-leadership.hinshelwood.com/articles/delivery-is-the-only-measure-of-progress-in-scrum/ Mon, 03 Feb 2025 09:00:00 +0000 https://engineering-leadership.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.hinshelwood.com/videos/the-crucible-of-learning-transforming-organizational-effectiveness-through-devops/ Wed, 21 Aug 2024 07:00:19 +0000 https://engineering-leadership.hinshelwood.com/videos/the-crucible-of-learning-transforming-organizational-effectiveness-through-devops/ DevOps transformation delivers major benefits when organizations address technical debt, simplify systems, and empower teams to take ownership of change. Key outcomes include faster delivery, lower costs, and happier, more effective teams, but success requires upskilling and active participation rather than outsourcing the work. Development managers should prioritize regular refactoring and foster a culture of continuous improvement to achieve lasting results. https://engineering-leadership.hinshelwood.com/videos/stop-testing-quality-in-how-shifting-left-builds-better-software-faster/ Mon, 18 Aug 2025 06:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/stop-testing-quality-in-how-shifting-left-builds-better-software-faster/ Relying on testers to catch issues late in the process increases costs, slows feedback, and undermines product trust; instead, quality should be built in from the start by moving tests and feedback as close to the engineer as possible. Key practices include automating builds and tests, adopting continuous integration and delivery, using test-driven development, and incrementally improving code quality. Development managers should focus on empowering engineers to own quality, relentlessly shortening feedback loops, and making incremental improvements to achieve faster, more reliable releases. https://engineering-leadership.hinshelwood.com/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.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.hinshelwood.com/signals/do-more-staging-environments-really-reduce-deployment-risk/ Wed, 26 Feb 2025 16:30:31 +0000 https://engineering-leadership.hinshelwood.com/signals/do-more-staging-environments-really-reduce-deployment-risk/ Adding more staging environments does not actually reduce deployment risk; it only delays issue discovery and creates a false sense of security. Real risk reduction comes from investing in automated testing, continuous integration, and quality practices built into the development process. To minimize downtime and deployment risk, focus on modern engineering practices rather than adding more pre-production gates. https://engineering-leadership.hinshelwood.com/signals/every-delay-increases-the-risk-of-failure/ Mon, 10 Feb 2025 11:00:51 +0000 https://engineering-leadership.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.hinshelwood.com/articles/stop-promoting-branches/ Thu, 06 Feb 2025 09:00:00 +0000 https://engineering-leadership.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.hinshelwood.com/videos/the-power-of-technical-excellence-in-agile-development/ Thu, 27 Jun 2024 06:45:00 +0000 https://engineering-leadership.hinshelwood.com/videos/the-power-of-technical-excellence-in-agile-development/ Technical excellence is essential for delivering a usable, high-quality product at the end of every iteration, which reduces risk and enables faster, more valuable feature delivery. The Azure DevOps team at Microsoft dramatically increased their output by focusing on paying down technical debt and establishing a strong Definition of Done. Development managers should prioritize technical excellence, avoid sacrificing quality for speed, and ensure their teams have a clear Definition of Done to maximize value and stay competitive. https://engineering-leadership.hinshelwood.com/videos/why-your-definition-of-done-is-holding-back-quality-agility-and-trust-and-how-to-raise-the-bar/ Wed, 09 Jul 2025 06:45:00 +0000 https://engineering-leadership.hinshelwood.com/videos/why-your-definition-of-done-is-holding-back-quality-agility-and-trust-and-how-to-raise-the-bar/ Treating “done” as a vague checklist limits quality, agility, and stakeholder trust; instead, teams should define “done” as delivering thoroughly tested, production-ready, and valuable increments that work in the real world. Clear, objective standards for “done” reduce defects, speed up learning, and build confidence with stakeholders. Development managers should work with their teams to set and uphold a robust definition of “done” to drive better outcomes and long-term success. https://engineering-leadership.hinshelwood.com/articles/how-to-build-for-business-resilience-and-continuity/ Mon, 26 May 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/how-to-build-for-business-resilience-and-continuity/ Building business resilience requires intentional design, strong observability, and aggressive decoupling so failures do not cascade across systems. Empower teams to act quickly, treat deployments as routine, and design for fast recovery using practices like chaos engineering and circuit breakers. Make resilience a core part of your culture and operations, not a one-time project, and use real metrics to guide continuous improvement. https://engineering-leadership.hinshelwood.com/videos/mastering-site-reliability-insights-from-azure-devops-on-building-a-resilient-live-site-culture/ Thu, 04 Jun 2020 02:05:28 +0000 https://engineering-leadership.hinshelwood.com/videos/mastering-site-reliability-insights-from-azure-devops-on-building-a-resilient-live-site-culture/ The Azure DevOps team at Microsoft has built a resilient live site culture by prioritising transparency with customers, investing in comprehensive telemetry, and automating deployment processes. Cross-functional teams and structured incident response drive continuous improvement and reliability at scale. Development managers should focus on these practices to boost both agility and system robustness while maintaining customer trust. https://engineering-leadership.hinshelwood.com/videos/how-to-evolve-your-definition-of-done-start-small-grow-smarter-and-build-lasting-momentum/ Wed, 25 Jun 2025 06:45:00 +0000 https://engineering-leadership.hinshelwood.com/videos/how-to-evolve-your-definition-of-done-start-small-grow-smarter-and-build-lasting-momentum/ You do not need a perfect Definition of Done from the start; begin with what is usable, then gradually add quality, testing, and compliance standards as your team grows more capable. Trying to do everything at once can stall progress, so evolve your standards step by step to build momentum and resilience. Focus on essential requirements now and raise the bar as your team is ready. https://engineering-leadership.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/ Sun, 25 May 2025 15:30:23 +0100 https://engineering-leadership.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/ Scrum allows you to optimise workflow as long as you maintain accountability through a Sprint Goal and a Done Increment. If your team already delivers quality software continuously and meets these standards, you do not need to force all work to finish within strict Sprint timelines. Focus on outcomes and professionalism rather than rigid rules, and let work flow naturally if your processes support it. https://engineering-leadership.hinshelwood.com/signals/technical-debt-isn-t-just-messy-code/ Thu, 13 Mar 2025 16:30:02 +0000 https://engineering-leadership.hinshelwood.com/signals/technical-debt-isn-t-just-messy-code/ Technical debt goes beyond messy code and includes slow feedback, fragile systems, and manual processes that hinder progress. It results from choices like delaying refactoring or skipping automation, and it compounds over time. To avoid bigger problems later, prioritize paying down technical debt now by automating, testing early, and streamlining delivery pipelines. https://engineering-leadership.hinshelwood.com/videos/transforming-chaos-into-clarity-how-optimising-systems-fuels-engineering-excellence/ Mon, 16 Dec 2024 06:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/transforming-chaos-into-clarity-how-optimising-systems-fuels-engineering-excellence/ Unmanaged chaos in software delivery leads to poor quality, technical debt, and wasted resources. Optimising systems and processes, as shown by Microsoft’s transformation of their DevOps team, enables faster delivery, higher productivity, and better products by reducing technical debt and improving testing practices. Development managers should prioritise system optimisation and technical leadership to empower teams and drive sustainable engineering excellence. https://engineering-leadership.hinshelwood.com/articles/a-better-way-than-staggered-iterations-for-delivery/ Thu, 10 Dec 2020 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/a-better-way-than-staggered-iterations-for-delivery/ Staggered iterations slow feedback, increase technical debt, and reduce software quality, making delivery less agile and more expensive. Instead, form cross-functional teams that deliver working software every iteration, integrate all required work including testing into each sprint, and automate as much as possible. Shift away from staged handoffs to continuous, team-owned delivery to improve value and quality. https://engineering-leadership.hinshelwood.com/articles/without-delivery-there-is-no-value/ Mon, 10 Feb 2025 09:00:00 +0000 https://engineering-leadership.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.hinshelwood.com/articles/why-handoffs-are-killing-your-agility/ Mon, 13 Jan 2025 00:00:00 +0000 https://engineering-leadership.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.hinshelwood.com/videos/detecting-agile-bs-lessons-from-the-department-of-defense/ Fri, 02 Aug 2024 06:45:02 +0000 https://engineering-leadership.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.hinshelwood.com/videos/still-deploying-manually-why-automation-is-the-bare-minimum-for-modern-engineering-and-your-business-survival/ Mon, 11 Aug 2025 07:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/still-deploying-manually-why-automation-is-the-bare-minimum-for-modern-engineering-and-your-business-survival/ Manual deployments put your business at serious risk due to inevitable human error, as shown by real-world failures that have caused massive financial losses. Automation of builds, deployments, tests, and quality checks is now the minimum standard for professional software development, enabling faster, safer, and more reliable releases. To protect your business and deliver value consistently, eliminate manual steps and automate every part of your delivery pipeline as soon as possible. https://engineering-leadership.hinshelwood.com/videos/stop-firefighting-bugs-why-shifting-left-saves-time-money-and-your-reputation/ Wed, 04 Jun 2025 06:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/stop-firefighting-bugs-why-shifting-left-saves-time-money-and-your-reputation/ Catching bugs late in the process wastes time, increases costs, and damages your reputation, while most issues could be prevented much earlier. Shifting left by embedding quality checks, early validation, and security into every stage of development leads to faster fixes, fewer production surprises, and greater stakeholder trust. Start building quality in from the beginning to avoid last-minute firefighting and deliver more reliable software. https://engineering-leadership.hinshelwood.com/videos/mastering-sustainable-scaling-overcoming-product-development-challenges-with-naked-agility/ Fri, 28 Feb 2025 06:00:27 +0000 https://engineering-leadership.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.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.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.hinshelwood.com/signals/technical-debt-cripples-business-agility-and-slows-engineers-down/ Tue, 06 May 2025 15:30:42 +0100 https://engineering-leadership.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.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.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.hinshelwood.com/videos/the-hidden-costs-of-poor-quality-code-and-how-to-turn-it-into-a-superpower/ Tue, 19 Nov 2024 09:58:28 +0000 https://engineering-leadership.hinshelwood.com/videos/the-hidden-costs-of-poor-quality-code-and-how-to-turn-it-into-a-superpower/ Poor-quality code leads to escalating costs, lost productivity, and damage to team morale and brand reputation, while also causing missed opportunities for innovation. Simplifying branching, limiting supported versions, and investing in engineering excellence and security can dramatically boost productivity and customer satisfaction. Development managers should prioritize code quality improvements now to unlock greater efficiency and long-term organizational success. https://engineering-leadership.hinshelwood.com/articles/why-most-scrum-masters-are-failing-and-what-they-should-know/ Thu, 05 Sep 2024 11:14:48 +0000 https://engineering-leadership.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.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.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.hinshelwood.com/articles/professional-scrum-teams-build-software-that-works/ Thu, 03 Dec 2020 00:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/professional-scrum-teams-build-software-that-works/ Professional Scrum teams must deliver high-quality, working software every sprint, prioritizing quality over speed or feature quantity to build trust and protect the organization’s reputation. Developers are accountable for quality and should use automation, DevOps practices, and continuous improvement to avoid technical debt and defects. Managers should empower teams to focus on quality, address technical debt in retrospectives, and consider upskilling developers through professional training. https://engineering-leadership.hinshelwood.com/videos/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.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.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.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.hinshelwood.com/videos/stop-hoping-for-quality-why-automated-pipelines-are-the-only-way-to-deliver-with-confidence/ Wed, 28 May 2025 07:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/stop-hoping-for-quality-why-automated-pipelines-are-the-only-way-to-deliver-with-confidence/ Relying on manual quality checks leads to inconsistency and risk because people inevitably forget or make mistakes, no matter their intentions. Embedding automated quality gates like security scans, static analysis, linting, and automated tests directly into your delivery pipeline ensures that nothing is missed and quality becomes the default. To deliver reliably and protect your team and customers, make all critical checks automatic and non-optional in your pipeline. https://engineering-leadership.hinshelwood.com/signals/why-organisations-believe-their-software-is-too-complex-for-cd/ Mon, 24 Feb 2025 10:51:31 +0000 https://engineering-leadership.hinshelwood.com/signals/why-organisations-believe-their-software-is-too-complex-for-cd/ Software complexity is often used as an excuse to avoid continuous delivery, but real-world examples like Microsoft’s Azure DevOps team show that even large, complex systems can achieve frequent releases by investing in quality practices and addressing technical debt. The main barrier is not complexity but the willingness to make necessary improvements. Development managers should focus on fixing underlying issues rather than blaming complexity. https://engineering-leadership.hinshelwood.com/articles/avoid-the-pick-n-mix-branching-anti-pattern/ Mon, 14 Jul 2014 15:35:35 +0000 https://engineering-leadership.hinshelwood.com/articles/avoid-the-pick-n-mix-branching-anti-pattern/ Explains the risks of the pick-n-mix branching anti-pattern in source control, its impact on code quality, and recommends feature branching and toggles for stability. https://engineering-leadership.hinshelwood.com/videos/devops-the-practical-path-to-modernising-legacy-systems-without-starting-over/ Mon, 02 Jun 2025 06:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/devops-the-practical-path-to-modernising-legacy-systems-without-starting-over/ DevOps enables organisations to modernise legacy systems without starting from scratch by introducing automation, continuous integration and deployment, and observability, which make change safer and more routine. These practices reduce bottlenecks, lower the cost of change, and help teams deliver improvements continuously. Development managers should focus on identifying friction points and adopting DevOps practices to make ongoing system improvements achievable and sustainable. https://engineering-leadership.hinshelwood.com/signals/rethinking-dev-test-staging-production-pipelines-for-safety/ Fri, 21 Feb 2025 16:30:30 +0000 https://engineering-leadership.hinshelwood.com/signals/rethinking-dev-test-staging-production-pipelines-for-safety/ Traditional Dev-Test-Staging-Production pipelines give a false sense of security because staging environments do not truly reflect production, leading to missed issues and wasted resources. Modern teams should focus on releasing to small user groups in production and using real feedback to guide rollouts. Consider shifting from heavy pre-release testing to faster, data-driven feedback in production to improve safety and efficiency. https://engineering-leadership.hinshelwood.com/videos/maximising-deployment-frequency-the-key-to-faster-time-to-market-and-business-success/ Wed, 22 Jan 2025 14:16:54 +0000 https://engineering-leadership.hinshelwood.com/videos/maximising-deployment-frequency-the-key-to-faster-time-to-market-and-business-success/ Increasing deployment frequency is key to reducing time to market and driving business success, but it only adds value if deployments reach production and enable fast learning from real user feedback. Focus on stable environments, end-to-end pipeline analysis, and shortening the time to learn so you can iterate quickly and align with business needs. Prioritise building trust with stakeholders, collecting actionable data, and enabling continuous delivery to respond rapidly to opportunities and deliver the right features at the right time. https://engineering-leadership.hinshelwood.com/videos/mastering-azure-devops-avoiding-common-pitfalls-for-agile-success/ Tue, 09 Apr 2024 08:00:20 +0000 https://engineering-leadership.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.hinshelwood.com/videos/unlocking-engineering-excellence-how-azure-devops-transforms-traceability-transparency-and-the-developer-experience/ Mon, 28 Jul 2025 07:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/unlocking-engineering-excellence-how-azure-devops-transforms-traceability-transparency-and-the-developer-experience/ Azure DevOps is a comprehensive platform that enhances engineering excellence by providing end-to-end traceability, transparency, and an integrated developer experience across planning, code, builds, and testing. Key benefits include instant visibility into what is deployed where, streamlined audit and compliance processes, and reduced friction between developers and testers. Development managers should ensure their teams fully leverage Azure DevOps’ capabilities to improve collaboration, accountability, and product quality. https://engineering-leadership.hinshelwood.com/signals/why-measuring-individual-cycle-time-fails-to-help-teams/ Sat, 15 Mar 2025 16:30:02 +0000 https://engineering-leadership.hinshelwood.com/signals/why-measuring-individual-cycle-time-fails-to-help-teams/ Measuring individual cycle time does not help teams improve because it focuses on people instead of the overall system. Real bottlenecks come from process issues like queues and overloaded work, not individual speed. To improve team performance, focus on system-level metrics such as lead time, throughput, and process efficiency, and address process bottlenecks rather than monitoring individuals. https://engineering-leadership.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.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.hinshelwood.com/signals/evolving-engineering-practices-to-improve-sprint-workflow-in-scrum/ Thu, 29 May 2025 15:30:45 +0100 https://engineering-leadership.hinshelwood.com/signals/evolving-engineering-practices-to-improve-sprint-workflow-in-scrum/ To improve sprint workflow in Scrum without sacrificing quality, teams need to adopt practices like Feature Flags, TDD, and regular refactoring to enable safe, continuous flow of work. These practices help ship incomplete features safely, ensure code reliability, and maintain system health. Development managers should prioritize evolving engineering practices and consider Continuous Delivery essential for sustainable progress. https://engineering-leadership.hinshelwood.com/signals/why-tracking-individual-cycle-time-distorts-team-behaviour/ Wed, 12 Mar 2025 16:30:03 +0000 https://engineering-leadership.hinshelwood.com/signals/why-tracking-individual-cycle-time-distorts-team-behaviour/ Tracking individual cycle time leads people to focus on looking good rather than improving team performance, causing them to pick easy tasks, rush work, and avoid collaboration. This does not improve actual delivery time and results in local optimisations that do not help deliver value. Focus on measuring and improving team flow metrics like lead time, work in progress, and throughput instead. https://engineering-leadership.hinshelwood.com/articles/the-scrum-master-is-accountable-for-delivery/ Thu, 30 Jan 2025 00:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/the-scrum-master-is-accountable-for-delivery/ The Scrum Master is ultimately accountable for ensuring the Scrum Team delivers a usable product increment every sprint, as delivery is the minimum requirement for team effectiveness. While delivery is a shared team responsibility, the Scrum Master must create the right environment, remove impediments, and enable continuous improvement so delivery becomes inevitable. Development managers should hold Scrum Masters accountable for delivery outcomes and empower them with the authority and resources needed to support team success. https://engineering-leadership.hinshelwood.com/videos/devops-elevating-your-organization-s-performance-through-bespoke-solutions/ Fri, 16 Aug 2024 07:18:10 +0000 https://engineering-leadership.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.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.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.hinshelwood.com/videos/transform-your-scrum-team-in-90-days-strategies-for-continuous-delivery-and-empowerment/ Tue, 27 Jun 2023 07:00:06 +0000 https://engineering-leadership.hinshelwood.com/videos/transform-your-scrum-team-in-90-days-strategies-for-continuous-delivery-and-empowerment/ In the first 90 days, a Scrum team can move from limited delivery to continuous delivery by focusing on frequent releases, clarifying business value, integrating user feedback, and empowering team members to take ownership. Success depends on organisational support and team readiness. Managers should prioritise building a delivery culture and enabling the team to sustain progress independently. https://engineering-leadership.hinshelwood.com/signals/why-engineering-teams-use-staging-environments-for-risk-reduction/ Fri, 14 Feb 2025 16:30:01 +0000 https://engineering-leadership.hinshelwood.com/signals/why-engineering-teams-use-staging-environments-for-risk-reduction/ Staging environments are intended to reduce risk but often lead to wasted time, delayed feedback, and extra costs without truly preventing failures. Modern practices like feature flags, progressive rollouts, and real-time monitoring can help teams deploy safely to production while reducing waste. Consider whether maintaining staging environments is actually benefiting your team or just adding unnecessary overhead. https://engineering-leadership.hinshelwood.com/articles/getting-started-with-a-modern-source-control-system-and-devops/ Mon, 13 Jul 2020 18:41:59 +0000 https://engineering-leadership.hinshelwood.com/articles/getting-started-with-a-modern-source-control-system-and-devops/ Modern source control systems are essential for managing not just code but the entire software development lifecycle, supporting DevOps practices and providing critical metadata for process visibility. Key practices include always using source control, automating release pipelines, minimizing branches with feature flags, moving to Git, and ensuring regular feedback and testing. To stay competitive, development managers should ensure all code is in source control, automate releases, and adopt integrated platforms like VSTS that support any technology and enable continuous delivery. https://engineering-leadership.hinshelwood.com/articles/the-sprint-is-a-container-for-planning-and-not-necessarily-for-delivery/ Tue, 29 Nov 2011 04:36:22 +0000 https://engineering-leadership.hinshelwood.com/articles/the-sprint-is-a-container-for-planning-and-not-necessarily-for-delivery/ Explains how Scrum Sprints are primarily for planning, not fixed delivery, and discusses aligning delivery schedules, continuous deployment, and improving software quality. https://engineering-leadership.hinshelwood.com/signals/executives-want-predictability/ Mon, 31 Mar 2025 15:30:08 +0100 https://engineering-leadership.hinshelwood.com/signals/executives-want-predictability/ If your teams do not have a clear, enforced Definition of Done, you are creating hidden risks and unreliable forecasts, which leads to missed deadlines and frustrated customers. Treating “Done” as negotiable means you are not delivering real value or predictability. Make sure your teams only mark work as done when it meets objective, enforceable standards to ensure true progress and trustworthy commitments. https://engineering-leadership.hinshelwood.com/signals/why-scrum-masters-need-technical-expertise-to-guide-teams/ Fri, 28 Mar 2025 16:30:04 +0000 https://engineering-leadership.hinshelwood.com/signals/why-scrum-masters-need-technical-expertise-to-guide-teams/ Scrum Masters are most effective when they have hands-on experience and technical understanding relevant to their team’s work, such as development practices or domain-specific knowledge. This expertise helps them guide teams toward improvement without doing the work themselves. Development managers should ensure Scrum Masters have sufficient technical background to enable, not just facilitate, their teams. https://engineering-leadership.hinshelwood.com/signals/why-slow-processes-impact-developer-productivity-and-performance/ Fri, 14 Mar 2025 16:30:02 +0000 https://engineering-leadership.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.hinshelwood.com/videos/overview-of-'applying-flow-metrics-for-scrum'-course/ Mon, 19 Feb 2024 07:00:09 +0000 https://engineering-leadership.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.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.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.hinshelwood.com/videos/stop-chasing-trends-how-real-agility-and-devops-build-resilient-adaptable-teams/ Fri, 27 Jun 2025 06:00:23 +0000 https://engineering-leadership.hinshelwood.com/videos/stop-chasing-trends-how-real-agility-and-devops-build-resilient-adaptable-teams/ Focusing on real agility and DevOps means building adaptable teams and resilient systems, not just adopting the latest tools or trends. Key outcomes include smoother delivery, better feedback, and teams that can handle change without disruption. Prioritise embedding adaptability into your culture and processes so your teams can lead rather than react to change. https://engineering-leadership.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.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.hinshelwood.com/videos/embrace-simplicity-how-to-transform-complexity-into-continuous-delivery-success/ Thu, 27 Feb 2025 07:00:10 +0000 https://engineering-leadership.hinshelwood.com/videos/embrace-simplicity-how-to-transform-complexity-into-continuous-delivery-success/ Complexity is not a valid excuse for avoiding continuous delivery; with organisational commitment and a willingness to modernise, even legacy systems can be transformed for faster, more reliable releases. Key steps include honestly assessing your product, investing in ongoing improvement, and addressing technical debt rather than ignoring warning signs. Leaders should prioritise resources and foster a culture that values continuous improvement to avoid costly failures and achieve lasting delivery success. https://engineering-leadership.hinshelwood.com/signals/best-branching-strategies-for-development-teams-explained/ Tue, 25 Feb 2025 16:30:02 +0000 https://engineering-leadership.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.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.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.hinshelwood.com/videos/unlocking-rapid-delivery-overcoming-common-devops-challenges-for-agile-success/ Fri, 21 Apr 2023 07:00:06 +0000 https://engineering-leadership.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.hinshelwood.com/videos/rethinking-agile-why-story-points-team-sizes-and-emergent-architecture-need-a-fresh-perspective/ Wed, 13 May 2020 05:03:57 +0000 https://engineering-leadership.hinshelwood.com/videos/rethinking-agile-why-story-points-team-sizes-and-emergent-architecture-need-a-fresh-perspective/ Story points often create confusion and unpredictability, so focusing on throughput and cycle time gives teams clearer insights and better delivery. Slightly larger teams with diverse roles can handle complex work and maintain quality more effectively. Embracing emergent architecture helps teams stay flexible and competitive, so consider shifting your metrics and team structures to support adaptability and faster value delivery. https://engineering-leadership.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.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.hinshelwood.com/engineering-notes/building-a-resilient-token-server-engineering-for-flow-fault-tolerance-and-speed/ Thu, 08 May 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/engineering-notes/building-a-resilient-token-server-engineering-for-flow-fault-tolerance-and-speed/ Aiming for a resilient, fast, and fault-tolerant token counting system, the author replaced fragile server restarts with a batch-wide server lifecycle, added retry logic for transient failures, and implemented a local fallback to ensure uninterrupted processing. These changes improved reliability, reduced downtime, and provided clear logs for troubleshooting. Development managers should focus on building systems that handle real-world failures gracefully, prioritize flow, and include observability and fallback mechanisms from the start. https://engineering-leadership.hinshelwood.com/signals/microsoft-shift-from-2-year-cycles-to-3-week-sprints-caused-team-anxiety/ Wed, 23 Apr 2025 15:30:47 +0100 https://engineering-leadership.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.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.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.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.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.hinshelwood.com/videos/special-sprints-agile-banditry-or-risk-management/ Thu, 04 Jan 2024 11:09:15 +0000 https://engineering-leadership.hinshelwood.com/videos/special-sprints-agile-banditry-or-risk-management/ Special sprints like bug-fix or hardening sprints undermine Agile by encouraging teams to defer work and accumulate risk, rather than delivering usable products every sprint. The Azure DevOps team found that relying on a safety net led to overwhelming undone work, but shifting to shipping every sprint improved quality and reduced technical debt. Development managers should eliminate special sprints, ensure each sprint delivers a shippable product, and address issues as they arise to maintain true agility and reduce risk. https://engineering-leadership.hinshelwood.com/videos/cloud-migration-without-the-mayhem-how-to-move-legacy-systems-safely-and-set-your-teams-up-for-success/ Mon, 05 May 2025 06:00:53 +0000 https://engineering-leadership.hinshelwood.com/videos/cloud-migration-without-the-mayhem-how-to-move-legacy-systems-safely-and-set-your-teams-up-for-success/ Cloud migration works best when approached gradually, using a hybrid model to reduce risk and avoid simply moving existing problems to the cloud. Success depends on understanding both your technology and how your teams work, aligning people and processes, and focusing on long-term maintainability. Treat migration as an ongoing journey, not a rushed project, and invest in shared understanding and continuous improvement to ensure a smooth transition. https://engineering-leadership.hinshelwood.com/signals/there-a-common-belief-that-rollback-is-the-ultimate-safety-net/ Thu, 13 Feb 2025 15:53:38 +0000 https://engineering-leadership.hinshelwood.com/signals/there-a-common-belief-that-rollback-is-the-ultimate-safety-net/ Relying on rollback as a safety net is risky, especially for stateful applications where it can cause data issues and failures. Safer approaches include progressive delivery methods like feature flags and canary releases, which help detect and limit problems early. Teams should focus on making deployments safe to fail rather than assuming rollback will fix mistakes. https://engineering-leadership.hinshelwood.com/videos/the-importance-of-visualizing-your-work-in-a-kanban-strategy/ Thu, 07 Mar 2024 07:00:10 +0000 https://engineering-leadership.hinshelwood.com/videos/the-importance-of-visualizing-your-work-in-a-kanban-strategy/ Visualizing work in Kanban is essential for team clarity, transparency, and accountability, but its real value comes from aligning everyone on shared workflows and rules. Teams should collaboratively define what gets visualized, map out each workflow stage, and document these agreements to avoid misalignment and inefficiencies. Prioritize team alignment over optimization, and consider using flow metrics and workshops to continuously improve your process. https://engineering-leadership.hinshelwood.com/signals/the-fastest-way-to-cripple-a-scrum-team-hire-the-wrong-scrum-master/ Mon, 17 Feb 2025 16:30:17 +0000 https://engineering-leadership.hinshelwood.com/signals/the-fastest-way-to-cripple-a-scrum-team-hire-the-wrong-scrum-master/ Hiring the wrong Scrum Master, especially one who acts as a process admin rather than a true agile leader, can seriously harm a Scrum Team. Effective Scrum Masters coach teams toward self-management, challenge obstacles, and connect engineering with business goals. To enable real agility and high performance, hire Scrum Masters who drive change and value, not just manage meetings. https://engineering-leadership.hinshelwood.com/videos/the-power-of-kaizen-continuous-improvement-in-scrum-and-beyond/ Sun, 25 Aug 2024 22:00:34 +0000 https://engineering-leadership.hinshelwood.com/videos/the-power-of-kaizen-continuous-improvement-in-scrum-and-beyond/ Kaizen means making small, ongoing improvements that add up to big results over time, and it fits naturally into Scrum through practices like Sprint Retrospectives and workflow optimization. Focusing on incremental changes, measuring their impact, and fostering a culture of continuous improvement can lead to better team collaboration, reduced cycle times, and higher efficiency. Start by encouraging your team to identify and act on small improvements each sprint, measure outcomes, and celebrate progress to build momentum. https://engineering-leadership.hinshelwood.com/videos/unlocking-continuous-improvement-how-metrics-and-visual-tools-transform-your-workflow/ Thu, 15 Aug 2024 07:04:39 +0000 https://engineering-leadership.hinshelwood.com/videos/unlocking-continuous-improvement-how-metrics-and-visual-tools-transform-your-workflow/ Using clear metrics and visual tools helps teams identify improvement areas, increase transparency, and make better decisions. Regularly reviewing processes, experimenting with small changes, and focusing on relevant, actionable data are key to ongoing improvement. Development managers should ensure their teams use these practices to drive meaningful and continuous workflow enhancements. https://engineering-leadership.hinshelwood.com/articles/how-lack-of-agency-is-killing-your-devops-initiatives/ Mon, 16 Jun 2025 09:00:00 +0000 https://engineering-leadership.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.hinshelwood.com/videos/getting-started-with-kanban/ Wed, 14 Feb 2024 07:00:19 +0000 https://engineering-leadership.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.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.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.hinshelwood.com/signals/why-using-a-blocked-column-in-azure-devops-is-a-mistake/ Thu, 20 Feb 2025 16:30:01 +0000 https://engineering-leadership.hinshelwood.com/signals/why-using-a-blocked-column-in-azure-devops-is-a-mistake/ Using a blocked column in Azure DevOps causes work to stall and be forgotten, rather than resolved. Instead, use a visible blocked tag and keep items in their active state to maintain focus and encourage action. Track blockages to address root causes and keep work moving. https://engineering-leadership.hinshelwood.com/signals/deploying-windows-os-directly-to-production-then-vs-now/ Sat, 22 Feb 2025 16:30:00 +0000 https://engineering-leadership.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.hinshelwood.com/signals/branch-promotion-is-a-relic-of-slow-manual-software-delivery/ Sat, 08 Feb 2025 16:30:00 +0000 https://engineering-leadership.hinshelwood.com/signals/branch-promotion-is-a-relic-of-slow-manual-software-delivery/ Branch promotion slows down delivery and adds risk, while modern teams merge changes into the main branch as soon as they are ready and use feature flags to separate deployment from release. Testing in production-like environments and instant rollbacks improve speed and safety. Focus on managing the flow of work, not branches, to streamline delivery. https://engineering-leadership.hinshelwood.com/signals/frequent-releases-are-not-just-a-technical-strategy/ Fri, 07 Feb 2025 16:30:01 +0000 https://engineering-leadership.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.hinshelwood.com/videos/the-problem-with-incompetent-scrum-masters-why-lack-of-skills-in-team-context-results-in-poor-roi/ Tue, 22 Oct 2024 07:00:08 +0000 https://engineering-leadership.hinshelwood.com/videos/the-problem-with-incompetent-scrum-masters-why-lack-of-skills-in-team-context-results-in-poor-roi/ Hiring Scrum Masters without the right skills leads to poor returns because they fail to drive team focus, innovation, and product quality. Key metrics like innovation rate, on-product index, usage index, and installed version index reveal how much value your teams actually deliver, often much less than assumed. To improve ROI, measure these metrics regularly and hold Scrum Masters accountable for tangible progress. https://engineering-leadership.hinshelwood.com/videos/mastering-scrum-key-insights-on-definition-of-done-spikes-and-managing-ad-hoc-work/ Thu, 04 Jun 2020 05:33:42 +0000 https://engineering-leadership.hinshelwood.com/videos/mastering-scrum-key-insights-on-definition-of-done-spikes-and-managing-ad-hoc-work/ Focus on team productivity rather than just feature count, and ensure everyone understands the difference between Definition of Done, which sets quality standards, and acceptance criteria, which specify requirements for each item. Use backlog refinement to address unknowns instead of relying on spikes, and plan sprint capacity to accommodate some ad hoc work while maintaining transparency and continuous improvement. Review your team’s approach to these areas to improve delivery and reduce disruptions. https://engineering-leadership.hinshelwood.com/signals/understanding-blocked-columns-and-stalled-work-in-project-boards/ Tue, 04 Mar 2025 16:30:01 +0000 https://engineering-leadership.hinshelwood.com/signals/understanding-blocked-columns-and-stalled-work-in-project-boards/ Using a separate “Blocked” column on project boards makes stalled work seem normal, leading to forgotten tasks, inflated work-in-progress, and lost context. Instead, keep blocked items visible in their current workflow state and highlight or tag them so the team addresses issues quickly. Review your process to ensure blocked work is surfaced and resolved without becoming invisible. https://engineering-leadership.hinshelwood.com/signals/too-many-teams-overcomplicate-their-branching-strategies/ Thu, 06 Feb 2025 09:38:01 +0000 https://engineering-leadership.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.hinshelwood.com/videos/unlocking-continuous-improvement-how-metrics-and-visualisation-drive-workflow-success/ Mon, 19 Aug 2024 06:45:02 +0000 https://engineering-leadership.hinshelwood.com/videos/unlocking-continuous-improvement-how-metrics-and-visualisation-drive-workflow-success/ Continuous improvement relies on using the right metrics and clear visual tools to identify patterns, increase transparency, and drive meaningful workflow changes. Teams should focus on measuring what truly matters and ensure their visualisations support understanding and collaboration. Regularly reviewing and adjusting processes based on these insights is essential for ongoing success. https://engineering-leadership.hinshelwood.com/videos/is-your-project-ecosystem-truly-agile/ Wed, 31 Jul 2024 06:45:01 +0000 https://engineering-leadership.hinshelwood.com/videos/is-your-project-ecosystem-truly-agile/ Having Agile development teams is not enough if your deployment processes remain slow and bureaucratic, as this creates delays, reduces value, and frustrates teams. Automating deployment and testing, implementing CI/CD pipelines, and shortening feedback loops are essential to achieving true end-to-end agility and maximizing stakeholder value. Review your current processes for bottlenecks, start automating where possible, and involve stakeholders early and often to ensure your entire project ecosystem is genuinely Agile. https://engineering-leadership.hinshelwood.com/signals/building-the-wrong-thing-is-worse-than-fixing-a-bug/ Mon, 14 Apr 2025 15:30:31 +0100 https://engineering-leadership.hinshelwood.com/signals/building-the-wrong-thing-is-worse-than-fixing-a-bug/ Most features built by software teams do not deliver value, with 65 percent considered waste. Shortening feedback loops through frequent reviews and real user input helps teams focus on what matters and avoid building the wrong things. Act now to get faster, actionable feedback and prevent wasted time and resources. https://engineering-leadership.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.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.hinshelwood.com/signals/not-all-delays-are-the-same/ Sat, 15 Feb 2025 16:30:01 +0000 https://engineering-leadership.hinshelwood.com/signals/not-all-delays-are-the-same/ Not all delays are equal; waiting for approval is different from being blocked by missing dependencies. Treating all delays as blocks hides real workflow issues and reduces accountability. Make delay sources explicit, track idle time, and highlight true blockers to identify and fix underlying problems. https://engineering-leadership.hinshelwood.com/videos/embracing-automation-the-key-to-transforming-your-development-process-and-boosting-confidence/ Tue, 14 Jan 2025 06:45:00 +0000 https://engineering-leadership.hinshelwood.com/videos/embracing-automation-the-key-to-transforming-your-development-process-and-boosting-confidence/ Embracing automation in testing, deployment, and validation is essential for faster, more reliable software delivery and increased team confidence. The Azure DevOps team drastically reduced feedback loops and technical debt by shifting to automated, efficient testing and empowering developers with local testing tools. Prioritizing automation and quality builds trust both within teams and with customers, so development managers should focus on automating as much as possible to enable continuous delivery and rapid improvement. https://engineering-leadership.hinshelwood.com/videos/unlocking-code-quality-the-transformative-power-of-frequent-deployments/ Mon, 13 Jan 2025 06:45:00 +0000 https://engineering-leadership.hinshelwood.com/videos/unlocking-code-quality-the-transformative-power-of-frequent-deployments/ Frequent deployments lead to higher code quality, faster feedback, and better alignment with user needs, while infrequent deployments cause larger, riskier changes and more technical debt. Breaking work into smaller pieces and deploying regularly encourages maintainable code and enables quick pivots based on real user data. Development managers should focus on reducing batch sizes, increasing deployment frequency, and investing in observability to improve both product quality and team performance. https://engineering-leadership.hinshelwood.com/videos/from-chaos-to-clarity-my-journey-through-devops-and-the-three-key-challenges-to-overcome/ Thu, 04 Apr 2024 11:34:59 +0000 https://engineering-leadership.hinshelwood.com/videos/from-chaos-to-clarity-my-journey-through-devops-and-the-three-key-challenges-to-overcome/ The author describes moving from chaotic, manual development practices to adopting DevOps, highlighting three main challenges: shifting culture and collaboration, integrating and automating toolchains, and fostering continuous learning. Success requires systems thinking, strong feedback loops, and a culture of experimentation. Development managers should focus on supporting people, streamlining processes, and encouraging ongoing learning to deliver better products faster. https://engineering-leadership.hinshelwood.com/articles/getting-started-with-a-definition-of-done-dod/ Mon, 14 Dec 2020 13:03:00 +0000 https://engineering-leadership.hinshelwood.com/articles/getting-started-with-a-definition-of-done-dod/ A clear Definition of Done (DoD) is essential for ensuring software quality and predictable delivery, as it sets shared criteria for what “done” means for every increment. Involve the whole Scrum Team and relevant experts to create a short, measurable checklist that covers code quality, testing, security, and usability, and review it regularly to keep raising the quality bar. Before starting sprints, make sure your current increment meets the DoD, and continuously improve both your software and your DoD to maintain a working, shippable product. https://engineering-leadership.hinshelwood.com/articles/metrics-that-matter-with-evidence-based-management/ Tue, 25 Feb 2014 13:29:14 +0000 https://engineering-leadership.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.hinshelwood.com/articles/building-a-release-pipeline-with-release-management-with-visual-studio-2013/ Tue, 18 Feb 2014 16:30:59 +0000 https://engineering-leadership.hinshelwood.com/articles/building-a-release-pipeline-with-release-management-with-visual-studio-2013/ Explains how to set up a scalable release pipeline using Release Management in Visual Studio 2013, covering continuous release, feedback environments, and DevOps practices. https://engineering-leadership.hinshelwood.com/articles/quality-enablement-to-achieve-predictable-delivery/ Wed, 24 Jul 2013 09:46:22 +0000 https://engineering-leadership.hinshelwood.com/articles/quality-enablement-to-achieve-predictable-delivery/ Explains how defining quality standards, acceptance criteria, and automation in software delivery leads to predictable outcomes, fewer bugs, and improved team performance. https://engineering-leadership.hinshelwood.com/signals/a-two-day-scrum-master-certification-doesn-t-make-you-a-scrum-master/ Thu, 27 Feb 2025 16:30:31 +0000 https://engineering-leadership.hinshelwood.com/signals/a-two-day-scrum-master-certification-doesn-t-make-you-a-scrum-master/ A two-day Scrum Master certification alone is not enough to prepare someone for the real challenges of leading Scrum Teams and delivering value. Effective Scrum Masters have hands-on experience, understand code quality and DevOps, and have navigated real-world obstacles. Companies should prioritize hiring or developing Scrum Masters with proven experience rather than relying solely on certifications. https://engineering-leadership.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.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.hinshelwood.com/videos/mastering-caman-strategy-how-to-leverage-azure-devops-for-effective-visualisation-in-hybrid-work-environments/ Fri, 29 Mar 2024 16:42:17 +0000 https://engineering-leadership.hinshelwood.com/videos/mastering-caman-strategy-how-to-leverage-azure-devops-for-effective-visualisation-in-hybrid-work-environments/ Using Azure DevOps to implement a Caman strategy helps hybrid teams visualise and manage work more effectively by establishing shared workflow rules, customising boards and columns, and tracking key metrics like lead and cycle time. Involving the whole team in defining and refining these rules improves transparency and reduces local optimisations that can harm overall flow. Development managers should ensure their teams collaborate on workflow setup in Azure DevOps and regularly review it to optimise efficiency and clarity. https://engineering-leadership.hinshelwood.com/signals/staging-environments-do-not-prevent-production-failures/ Fri, 28 Feb 2025 16:30:01 +0000 https://engineering-leadership.hinshelwood.com/signals/staging-environments-do-not-prevent-production-failures/ Staging environments do not truly prevent production failures because they cannot fully replicate real-world conditions, often giving teams a false sense of security. Leading teams now deploy changes incrementally to real users in production, using monitoring and automated safeguards to catch issues early. Consider shifting focus from pre-production testing to safer, controlled releases in production to reduce risk and respond faster to problems. https://engineering-leadership.hinshelwood.com/signals/every-unreleased-feature-is-a-cost/ Wed, 05 Feb 2025 16:30:01 +0000 https://engineering-leadership.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.hinshelwood.com/videos/transforming-chaos-into-collaboration-how-a-common-framework-can-revolutionise-your-team's-dynamics/ Fri, 28 Jul 2017 11:55:30 +0000 https://engineering-leadership.hinshelwood.com/videos/transforming-chaos-into-collaboration-how-a-common-framework-can-revolutionise-your-team's-dynamics/ Introducing a common framework and structured backlog helped transform a chaotic team environment into one marked by better collaboration, clearer communication, and increased trust. Teams benefited from a shared language, improved confidence, and more effective problem-solving, while regular feedback channels boosted morale and engagement. Development managers should consider adopting structured frameworks and open communication practices to drive positive change and sustain team momentum. https://engineering-leadership.hinshelwood.com/videos/empowering-teams-to-tailor-their-processes-a-path-to-true-agility/ Fri, 26 Jul 2024 06:45:00 +0000 https://engineering-leadership.hinshelwood.com/videos/empowering-teams-to-tailor-their-processes-a-path-to-true-agility/ Empowering teams to adapt their processes to their specific needs leads to greater value, less waste, and more innovation, while rigid, one-size-fits-all processes can cause delays, unnecessary costs, and frustration. Development managers should assess whether their teams have the freedom to experiment, minimize bureaucracy, and focus on delivering customer value rather than just following procedures. To achieve true agility, encourage teams to tailor their ways of working and continuously improve based on what they learn. https://engineering-leadership.hinshelwood.com/videos/unlocking-value-in-devops-my-role-as-a-consultant-in-driving-change-and-overcoming-bottlenecks/ Tue, 02 May 2023 07:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/unlocking-value-in-devops-my-role-as-a-consultant-in-driving-change-and-overcoming-bottlenecks/ As a DevOps consultant, my main focus is helping teams rethink how they deliver value by identifying and addressing both technical and process bottlenecks, such as slow builds or approval delays. I do this by asking targeted questions and encouraging teams to examine their workflows, which leads to continuous improvement and better customer outcomes. Development managers should regularly review their processes to spot and resolve the biggest sources of delay. https://engineering-leadership.hinshelwood.com/videos/modernising-legacy-systems-a-practical-low-risk-strategy-for-real-business-transformation/ Mon, 09 Jun 2025 06:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/modernising-legacy-systems-a-practical-low-risk-strategy-for-real-business-transformation/ Modernising legacy systems should be a strategic, low-risk process focused on understanding both technical and workflow bottlenecks, not a risky full replacement. Incremental changes, targeted automation, and addressing process issues often deliver the best results while minimising disruption. Development managers should map how work flows through their systems, prioritise fixes that offer the most value, and shift from reactive firefighting to proactive improvement. https://engineering-leadership.hinshelwood.com/articles/release-management-with-team-foundation-server-2012/ Wed, 24 Apr 2013 17:38:24 +0000 https://engineering-leadership.hinshelwood.com/articles/release-management-with-team-foundation-server-2012/ Explains how to automate and streamline software release management using Team Foundation Server 2012, Lab Management, and Octopus, focusing on build, deployment, and quality. https://engineering-leadership.hinshelwood.com/articles/professional-scrum-developer-net-training-in-london/ Fri, 18 Jun 2010 15:53:27 +0000 https://engineering-leadership.hinshelwood.com/articles/professional-scrum-developer-net-training-in-london/ Intensive five-day course for software developers covering Scrum, Visual Studio 2010, .NET, and Agile practices through hands-on team sprints and real-world case studies. https://engineering-leadership.hinshelwood.com/signals/too-much-refinement-wastes-time/ Tue, 29 Apr 2025 15:30:43 +0100 https://engineering-leadership.hinshelwood.com/signals/too-much-refinement-wastes-time/ Too much backlog refinement wastes time, while too little causes confusion and delays. Aim for just enough detail so developers can start work confidently without needing constant clarification. If Sprint Planning is about making commitments rather than figuring things out, your refinement process is working well. https://engineering-leadership.hinshelwood.com/signals/scrum-masters-enabling-teams-fostering-agility-removing-blockers/ Wed, 05 Mar 2025 16:30:00 +0000 https://engineering-leadership.hinshelwood.com/signals/scrum-masters-enabling-teams-fostering-agility-removing-blockers/ Scrum Masters are responsible for ensuring teams deliver effectively by creating the right conditions for success, not just facilitating meetings or shielding teams from pressure. Their accountability lies in identifying and addressing blockers, improving team effectiveness, and ensuring consistent delivery each sprint. Development managers should hold Scrum Masters accountable for team delivery outcomes, not just process adherence. https://engineering-leadership.hinshelwood.com/videos/evidence-based-management-the-four-key-value-areas-in-scrum/ Fri, 13 Sep 2024 07:00:34 +0000 https://engineering-leadership.hinshelwood.com/videos/evidence-based-management-the-four-key-value-areas-in-scrum/ Evidence-based management in Scrum focuses on four key value areas, current value, unrealized value, ability to innovate, and time to market, to guide data-driven decisions and balance innovation with stability. Tracking metrics in these areas helps teams improve customer satisfaction, identify growth opportunities, manage technical debt, and speed up delivery. Development managers should start measuring these areas to align teams with evidence-based management and drive sustainable product success. https://engineering-leadership.hinshelwood.com/engineering-notes/convert-legacy-projects-and-asp-net-mvc-apps-to-sdk-style-with-confidence/ Thu, 29 May 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/engineering-notes/convert-legacy-projects-and-asp-net-mvc-apps-to-sdk-style-with-confidence/ Upgrading legacy .NET projects to SDK-style makes your codebase easier to maintain, improves build and CI/CD integration, and prepares you for future .NET upgrades. Converting class libraries is straightforward and highly recommended, while web apps require more care and are best handled with the MSBuild.SDK.SystemWeb package if you want SDK-style; otherwise, you can leave them in the old format. Start by converting class libraries now to simplify your engineering system and reduce technical debt. https://engineering-leadership.hinshelwood.com/videos/unlocking-the-true-power-of-continuous-delivery-how-automation-transforms-software-development/ Fri, 06 Dec 2024 06:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/unlocking-the-true-power-of-continuous-delivery-how-automation-transforms-software-development/ The main benefit of continuous delivery is the automation it brings, which increases consistency, reliability, and risk mitigation in software deployments. Real-world examples like Azure DevOps and Windows teams show that automation shortens feedback loops, reduces errors, and enables faster, higher-quality releases without increasing team size. Development managers should focus on embedding automation throughout their delivery process to protect the business and empower teams to deliver better software more efficiently. https://engineering-leadership.hinshelwood.com/videos/detecting-agile-bs-lessons-from-the-us-department-of-defense/ Fri, 28 Jun 2024 06:45:01 +0000 https://engineering-leadership.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.hinshelwood.com/videos/illuminate-your-workflow-harnessing-candan-strategies-for-continuous-improvement-and-transparency/ Fri, 08 Mar 2024 07:00:31 +0000 https://engineering-leadership.hinshelwood.com/videos/illuminate-your-workflow-harnessing-candan-strategies-for-continuous-improvement-and-transparency/ Adopting a Candan strategy helps teams achieve continuous improvement and greater transparency by using flow metrics to identify workflow issues and inefficiencies. Visualising these metrics enables more informed decisions and motivates action, especially for Scrum teams that lack built-in measurement tools. To maximise benefits, integrate flow metrics into your processes and seek expert support or training if needed. https://engineering-leadership.hinshelwood.com/videos/how-long-does-it-take-to-transition-from-project-management-to-kanban/ Fri, 16 Feb 2024 07:00:10 +0000 https://engineering-leadership.hinshelwood.com/videos/how-long-does-it-take-to-transition-from-project-management-to-kanban/ Transitioning from traditional project management to Kanban is a gradual process that starts by documenting your current workflow, collecting and analyzing data, and making incremental improvements based on evidence. Kanban allows teams to identify and address bottlenecks at their own pace, reducing disruption and avoiding the pitfalls of rushed Agile adoption. Development managers should consider starting with Kanban to enable continuous improvement without overwhelming their teams. https://engineering-leadership.hinshelwood.com/videos/the-overlooked-virtue-of-agility-diligence/ Thu, 07 Dec 2023 07:00:02 +0000 https://engineering-leadership.hinshelwood.com/videos/the-overlooked-virtue-of-agility-diligence/ Diligence, or consistently following through on quality standards like the definition of done, is often overlooked in Agile teams but is essential for reliable delivery and long-term success. Without diligence, teams risk inconsistent quality and increased rework, while a strong focus on it leads to better products and faster delivery over time. Development managers should ensure the definition of done is clear, visible, and enforced, and foster a culture of accountability and perseverance to make diligence a team habit. https://engineering-leadership.hinshelwood.com/videos/mastering-evidence-based-management-for-agile-success/ Wed, 02 Oct 2024 13:17:24 +0000 https://engineering-leadership.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.hinshelwood.com/guides/detecting-agile-bs/ Tue, 17 Sep 2024 00:00:00 +0000 https://engineering-leadership.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.hinshelwood.com/videos/stop-starting-and-start-finishing-the-key-to-team-success/ Wed, 31 Jan 2024 14:26:11 +0000 https://engineering-leadership.hinshelwood.com/videos/stop-starting-and-start-finishing-the-key-to-team-success/ Trying to do too many tasks at once reduces team productivity due to context switching and leads to slower delivery and burnout. Focusing on finishing work before starting new tasks, limiting work in progress, and prioritizing by business value helps teams deliver faster and more predictably. Development managers should ensure their teams complete current work before taking on new tasks to maximize efficiency and business impact. https://engineering-leadership.hinshelwood.com/videos/quotes-less-is-more-true-or-false/ Sat, 14 Oct 2023 07:00:13 +0000 https://engineering-leadership.hinshelwood.com/videos/quotes-less-is-more-true-or-false/ Focusing on fewer, high-value tasks rather than trying to do everything leads to better productivity and higher quality in Agile teams. Regularly refining the backlog and planning sprints around essential work helps eliminate waste and ensures efforts align with project goals. Development managers should encourage teams to prioritize what matters most to maximize results. https://engineering-leadership.hinshelwood.com/articles/how-usable-working-products-are-your-ultimate-weapon-against-risks/ Thu, 20 Jul 2023 09:00:00 +0000 https://engineering-leadership.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.hinshelwood.com/articles/evidence-based-management-gathering-the-metrics/ Wed, 30 Dec 2020 14:02:07 +0000 https://engineering-leadership.hinshelwood.com/articles/evidence-based-management-gathering-the-metrics/ Evidence-based Management helps software organizations focus on delivering real value by tracking metrics in three areas: current value, time to market, and ability to innovate. Traditional measures like on-time and on-budget delivery miss customer value, so organizations should gather and regularly review these agile-focused metrics to guide improvement. Start collecting baseline data now and reassess quarterly to track progress and demonstrate the impact of agile investments. https://engineering-leadership.hinshelwood.com/signals/the-true-role-of-a-scrum-master-beyond-facilitation/ Tue, 25 Mar 2025 16:30:02 +0000 https://engineering-leadership.hinshelwood.com/signals/the-true-role-of-a-scrum-master-beyond-facilitation/ A Scrum Master’s real value is in driving team improvement and organisational change, not just running meetings or handling admin tasks. They should coach teams, remove obstacles, and ensure Scrum is used to deliver value. Development managers should empower Scrum Masters to act as change agents rather than limiting them to facilitation. https://engineering-leadership.hinshelwood.com/videos/mastering-agile-the-power-of-just-enough-and-no-more-for-optimal-efficiency/ Tue, 05 Dec 2023 11:00:27 +0000 https://engineering-leadership.hinshelwood.com/videos/mastering-agile-the-power-of-just-enough-and-no-more-for-optimal-efficiency/ Applying the principle of “just enough and no more” across backlog management, team size, refinement, and planning helps teams stay focused, efficient, and adaptable. Prioritising value, embracing simplicity, and iterating regularly reduces wasted effort and maximises productivity. Development managers should encourage teams to do only what is necessary to deliver value and continuously improve. https://engineering-leadership.hinshelwood.com/videos/the-importance-of-delivering-working-software-every-iteration/ Wed, 26 Jun 2024 06:45:00 +0000 https://engineering-leadership.hinshelwood.com/videos/the-importance-of-delivering-working-software-every-iteration/ Delivering working software to real users every iteration is essential for true agility because it enables rapid feedback, validates assumptions early, and maximizes value for stakeholders. Key practices include starting with a minimal viable product, prioritizing user stories for value, involving stakeholders regularly, automating testing and deployment, and fostering continuous improvement. To ensure your team is truly Agile, focus on releasing usable software each iteration and use real user feedback to guide development and avoid wasted effort. https://engineering-leadership.hinshelwood.com/signals/not-all-surprises-in-product-development-are-true-unknowns/ Mon, 28 Apr 2025 15:30:55 +0100 https://engineering-leadership.hinshelwood.com/signals/not-all-surprises-in-product-development-are-true-unknowns/ Many surprises in product development are due to poor backlog management rather than true unknowns. Regularly reviewing and categorizing past surprises helps teams improve their backlog and anticipate issues. Development managers should ensure their teams use backlog refinement to build foresight and reduce avoidable disruptions. https://engineering-leadership.hinshelwood.com/signals/what-makes-an-effective-scrum-master-beyond-meeting-facilitation/ Sun, 23 Feb 2025 16:30:01 +0000 https://engineering-leadership.hinshelwood.com/signals/what-makes-an-effective-scrum-master-beyond-meeting-facilitation/ An effective Scrum Master builds a self-sustaining team that consistently delivers valuable, high-quality products by enabling data-driven planning, supporting meaningful backlog management, removing organizational obstacles, and fostering true cross-team collaboration. Their real value is seen when the team thrives independently rather than relying on constant guidance. If your team would struggle without the Scrum Master, it may be time to reassess their approach. https://engineering-leadership.hinshelwood.com/videos/embrace-kaizen-unlocking-continuous-improvement-for-personal-and-team-success/ Wed, 14 Aug 2024 07:04:17 +0000 https://engineering-leadership.hinshelwood.com/videos/embrace-kaizen-unlocking-continuous-improvement-for-personal-and-team-success/ Kaizen is a philosophy of making small, ongoing improvements that can lead to significant gains in team performance, collaboration, and personal growth. By regularly observing, measuring, and refining processes, teams can boost productivity and quality while fostering a culture where everyone feels empowered to suggest changes. Development managers should encourage open communication, celebrate small wins, and be patient as continuous improvement is a long-term journey. https://engineering-leadership.hinshelwood.com/articles/blocked-columns-on-kanban-boards-obfuscate-workflow-and-undermine-effectiveness/ Tue, 13 Feb 2024 15:44:53 +0000 https://engineering-leadership.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.hinshelwood.com/guides/evidence-based-management-guide/ Wed, 01 Jan 2020 00:00:00 +0000 https://engineering-leadership.hinshelwood.com/guides/evidence-based-management-guide/ Evidence-Based Management (EBM) guides organisations to improve value delivery under uncertainty by using empirical goals, measurement, and continuous experimentation. https://engineering-leadership.hinshelwood.com/videos/unlocking-agile-success-embrace-continuous-forecasting-and-transform-your-training-experience/ Thu, 21 May 2020 05:26:17 +0000 https://engineering-leadership.hinshelwood.com/videos/unlocking-agile-success-embrace-continuous-forecasting-and-transform-your-training-experience/ Continuous forecasting in Agile, supported by metrics and tools like Monte Carlo simulations, enables teams to plan flexibly and adapt quickly rather than committing to a full sprint plan upfront. Virtual training with interactive tools and follow-up sessions has improved learning and engagement. Development managers should consider adopting continuous forecasting and leveraging available training resources to enhance team performance and responsiveness. https://engineering-leadership.hinshelwood.com/videos/transform-your-leadership-the-power-of-evidence-based-management-in-agile/ Wed, 29 Nov 2023 11:00:03 +0000 https://engineering-leadership.hinshelwood.com/videos/transform-your-leadership-the-power-of-evidence-based-management-in-agile/ Evidence-based management helps Agile leaders make better decisions by using data on team performance, customer satisfaction, and product quality, leading to continuous improvement and stronger collaboration. Real-world examples show that adopting EBM can improve delivery times, morale, and outcomes. Development managers should invest in EBM training, encourage data-driven practices, and support experimentation to drive team success. https://engineering-leadership.hinshelwood.com/signals/teams-are-self-managing/ Fri, 21 Mar 2025 16:30:04 +0000 https://engineering-leadership.hinshelwood.com/signals/teams-are-self-managing/ Self-managing teams still need structure and boundaries to be effective, which is where the Scrum Master plays a key role by ensuring clarity, alignment, and accountability. Without this support, autonomy can lead to chaos and poor delivery. Development managers should balance team autonomy with proactive leadership to maintain high performance. https://engineering-leadership.hinshelwood.com/articles/you-are-doing-it-wrong-if-you-are-not-using-test-first/ Mon, 07 Dec 2020 12:00:58 +0000 https://engineering-leadership.hinshelwood.com/articles/you-are-doing-it-wrong-if-you-are-not-using-test-first/ Using test-first approaches like Test Driven Development helps teams deliver software that meets customer needs, reduces maintenance costs, and prevents bugs from reaching production. Writing tests before coding ensures validation at every step, shortens feedback loops, and makes it easier and cheaper to fix issues early. To improve quality and enable confident continuous delivery, development managers should encourage their teams to adopt test-first practices. https://engineering-leadership.hinshelwood.com/signals/agile-without-a-usable-working-product-is-just-expensive-theatre/ Sun, 20 Apr 2025 15:30:27 +0100 https://engineering-leadership.hinshelwood.com/signals/agile-without-a-usable-working-product-is-just-expensive-theatre/ Agile only delivers value if each sprint results in a usable working product; focusing on rituals, documentation, or velocity without real output wastes time and resources. The key measure of success is having something shippable at the end of every sprint, which enables feedback and reduces risk. Development managers should ensure their teams are consistently delivering usable products rather than just going through the motions. https://engineering-leadership.hinshelwood.com/videos/harnessing-evidence-based-management-transform-your-decision-making-with-data-driven-insights/ Wed, 14 Aug 2024 07:12:45 +0000 https://engineering-leadership.hinshelwood.com/videos/harnessing-evidence-based-management-transform-your-decision-making-with-data-driven-insights/ Evidence-based management helps you make better decisions by using data to inform, not control, your actions and team behaviours. Focus on choosing the right metrics that align with your business goals, understand the context behind the numbers, and engage with teams to uncover root causes. Use data as a guide for continuous improvement and be ready to adapt your strategies as new insights emerge. https://engineering-leadership.hinshelwood.com/videos/combatting-the-agile-apocalypse-how-to-overcome-the-famine-of-feedback-and-engagement/ Wed, 08 Nov 2023 06:45:00 +0000 https://engineering-leadership.hinshelwood.com/videos/combatting-the-agile-apocalypse-how-to-overcome-the-famine-of-feedback-and-engagement/ A lack of feedback and engagement from stakeholders, especially the product owner, leads to disengaged teams, poor product alignment, and increased risk of failure. Regular feedback sessions, open communication, and early stakeholder involvement are essential to keep teams motivated and ensure products meet business needs. Development managers should prioritise active stakeholder participation to maintain team morale and deliver better outcomes. https://engineering-leadership.hinshelwood.com/videos/unlocking-the-future-of-software-development-why-automation-is-your-key-to-success/ Wed, 15 Jan 2025 06:45:00 +0000 https://engineering-leadership.hinshelwood.com/videos/unlocking-the-future-of-software-development-why-automation-is-your-key-to-success/ Automation is essential for faster, more reliable software development, reducing human error and enabling consistent, rapid deployments. Real-world failures like Knight Capital show the high cost of manual processes, while leading teams achieve quick, high-quality releases by building automation into every step. Development managers should prioritize automating all possible tasks to improve quality, speed, and adaptability. https://engineering-leadership.hinshelwood.com/videos/mastering-evidence-based-management-in-agile-inform-don-t-control/ Wed, 11 Sep 2024 13:36:29 +0000 https://engineering-leadership.hinshelwood.com/videos/mastering-evidence-based-management-in-agile-inform-don-t-control/ Evidence-Based Management helps you use data to guide decisions and understand team behaviors, but it should inform rather than control actions. Define clear outcomes, choose metrics that align with those goals, and use data as a conversation starter to uncover challenges and drive improvement. Regularly review metrics with your teams to stay aligned and focus on delivering real value, not just hitting targets. https://engineering-leadership.hinshelwood.com/articles/create-your-own-path-to-organisational-agility/ Thu, 11 Jan 2018 13:28:00 +0000 https://engineering-leadership.hinshelwood.com/articles/create-your-own-path-to-organisational-agility/ A one-size-fits-all agile framework rarely works because every organisation’s path to agility is unique; instead, you should define a clear vision, form a cross-functional change team, and use an incremental, evidence-based approach to improvement. Broad, consistent training across all levels ensures everyone understands and supports the change, while involving stakeholders in identifying and prioritising impediments helps create a relevant organisational change backlog. To succeed, secure executive buy-in, empower teams to drive change, and focus on continuous, measurable improvements tailored to your context. https://engineering-leadership.hinshelwood.com/articles/dod-has-made-it-illegal-to-do-waterfall/ Tue, 01 May 2018 01:02:03 +0000 https://engineering-leadership.hinshelwood.com/articles/dod-has-made-it-illegal-to-do-waterfall/ The US Department of Defense has updated its procurement rules to require agile, iterative development instead of traditional waterfall methods, following high-profile failures like the FBI’s Sentinel project. Agile approaches have proven to deliver higher success rates, lower costs, and reduced risk, and these changes are now influencing government and vendor practices across the US and UK. Development managers working with government clients should adopt agile methods to align with new regulations and improve project outcomes. https://engineering-leadership.hinshelwood.com/videos/the-importance-of-evidence-based-management-in-agile-environments/ Mon, 22 Jan 2024 11:00:07 +0000 https://engineering-leadership.hinshelwood.com/videos/the-importance-of-evidence-based-management-in-agile-environments/ Evidence-based management helps Agile teams make smarter decisions by tracking key metrics like value delivered, time to market, and ability to innovate, ensuring changes actually lead to improvement. Without data, teams risk wasting time and resources on ineffective changes, but with regular measurement and analysis, they can adapt quickly and foster continuous improvement. Start by identifying and tracking a few important metrics, involve your team, and use the insights to guide your next steps. https://engineering-leadership.hinshelwood.com/videos/mastering-product-backlog-management-key-strategies-for-agile-success/ Thu, 30 Nov 2023 11:00:31 +0000 https://engineering-leadership.hinshelwood.com/videos/mastering-product-backlog-management-key-strategies-for-agile-success/ Effective product backlog management is crucial for Agile success; prioritising tasks, limiting work in progress, and holding regular refinement sessions help teams stay focused and deliver more value. Engaging stakeholders and using visual tools can further improve clarity and alignment. Development managers should regularly review their backlog practices to ensure they are working on the most valuable items and maintaining a manageable, focused backlog. https://engineering-leadership.hinshelwood.com/videos/the-power-of-metrics-why-pal-ebm-is-essential-for-your-organization/ Sat, 27 Jan 2024 07:00:19 +0000 https://engineering-leadership.hinshelwood.com/videos/the-power-of-metrics-why-pal-ebm-is-essential-for-your-organization/ The PAL-EBM class helps leaders and teams understand how to use metrics effectively to drive organizational success by focusing on real data, transparency, and the human impact of measurement. Participants learn through real-world stories why some metrics fail, how to avoid negative behaviors like those seen with Microsoft’s stack ranking, and how to foster strategic conversations that lead to better outcomes. Leadership teams are encouraged to take the class together to align on measuring success, iteratively strategize, and make informed decisions that support long-term goals. https://engineering-leadership.hinshelwood.com/articles/create-a-release-management-pipeline-for-professional-developers/ Thu, 04 Dec 2014 12:15:56 +0000 https://engineering-leadership.hinshelwood.com/articles/create-a-release-management-pipeline-for-professional-developers/ This guide walks through setting up an automated release management pipeline using TFS/VSO and Azure, showing how to build, deploy, and parameterize a legacy web app across multiple feedback environments. Key takeaways include the importance of automating builds and releases, using environment-specific parameters, and streamlining approvals for smoother deployments. Development managers should consider investing time upfront to automate and parameterize their pipelines, as this reduces manual errors and accelerates feedback cycles. https://engineering-leadership.hinshelwood.com/articles/guidance-a-branching-strategy-for-scrum-teams/ Wed, 14 Apr 2010 20:11:36 +0000 https://engineering-leadership.hinshelwood.com/articles/guidance-a-branching-strategy-for-scrum-teams/ Explains an effective branching strategy for Scrum teams, covering best practices, common pitfalls, and step-by-step guidance for managing code, releases, and bug fixes. https://engineering-leadership.hinshelwood.com/videos/transforming-agile-training-into-action-experimentation-and-engagement-in-the-workplace/ Mon, 24 Apr 2023 07:00:03 +0000 https://engineering-leadership.hinshelwood.com/videos/transforming-agile-training-into-action-experimentation-and-engagement-in-the-workplace/ Agile training is most effective when participants actively experiment with new tools and techniques in their own work environments, adapting them to fit their team’s context. Techniques like “One, Two, Four, All” foster inclusive engagement and help turn group ideas into actionable plans, even in virtual settings. Development managers should encourage their teams to try these approaches and create safe spaces for sharing, which leads to better collaboration and practical results. https://engineering-leadership.hinshelwood.com/articles/what-my-father-taught-me-about-evidence-based-management-34-years-before-it-was-invented/ Mon, 13 Jul 2020 18:42:12 +0000 https://engineering-leadership.hinshelwood.com/articles/what-my-father-taught-me-about-evidence-based-management-34-years-before-it-was-invented/ Explores how evidence-based management uses data-driven practices to improve organisational agility, value delivery, and decision-making in both business and software contexts. https://engineering-leadership.hinshelwood.com/videos/scaling-agility-navigating-the-dragons-of-change-in-the-future-of-work/ Wed, 25 Mar 2020 16:17:15 +0000 https://engineering-leadership.hinshelwood.com/videos/scaling-agility-navigating-the-dragons-of-change-in-the-future-of-work/ Scaling agility is about more than just expanding frameworks like Scrum or Nexus; it requires focusing on core practices, using meaningful metrics, and adapting to new ways of working such as virtual training. Key insights include the importance of revisiting Scrum fundamentals, tailoring metrics to your context, and leveraging technology for effective remote collaboration. Development managers should prioritize continuous learning, experiment with virtual tools, and stay open to sharing experiences to navigate the challenges of scaling in today’s changing work environment. https://engineering-leadership.hinshelwood.com/articles/tfs-for-cross-team-and-cross-business-line-work-item-tracking/ Tue, 04 Mar 2014 16:34:13 +0000 https://engineering-leadership.hinshelwood.com/articles/tfs-for-cross-team-and-cross-business-line-work-item-tracking/ Explains how to use a single Team Project and Team Field in TFS to streamline cross-team work item tracking, reporting, and collaboration across business lines. https://engineering-leadership.hinshelwood.com/signals/design-sprints-in-scrum-common-questions-and-practical-insights/ Wed, 04 Jun 2025 15:31:05 +0100 https://engineering-leadership.hinshelwood.com/signals/design-sprints-in-scrum-common-questions-and-practical-insights/ There are no special Sprints in Scrum for design or other functions; all work needed to meet the Sprint Goal, including UX and design, should happen within the Sprint or during Refinement if it is for future preparation. Segmenting Sprints by function creates silos and goes against Scrum’s purpose of delivering high-quality working software. Development managers should focus on integrating design and architecture work into the regular Sprint flow rather than isolating it. https://engineering-leadership.hinshelwood.com/videos/maximizing-transparency-and-improvement-in-software-engineering-with-kanban/ Mon, 29 Jul 2024 06:45:02 +0000 https://engineering-leadership.hinshelwood.com/videos/maximizing-transparency-and-improvement-in-software-engineering-with-kanban/ Kanban helps software teams gain transparency into their workflow, making it easier to spot bottlenecks and inefficiencies and enabling continuous improvement through data-driven decisions. By visualizing work and tracking key metrics like lead time and throughput, teams can adapt quickly, improve delivery speed, and foster better collaboration. Start small with Kanban, set clear work-in-progress limits, and regularly review your process to drive ongoing improvement. https://engineering-leadership.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-don't-have-a-working-agreement/ Fri, 01 Mar 2024 07:00:17 +0000 https://engineering-leadership.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-don't-have-a-working-agreement/ Not having a working agreement causes chaos, misalignment, and inefficiency in teams using Kanban or similar frameworks. Clear agreements on roles, goals, processes, and workflows are essential for team alignment and success. Development managers should ensure their teams regularly create and review working agreements to avoid confusion and improve outcomes. https://engineering-leadership.hinshelwood.com/videos/how-do-you-know-the-value-currently-delivered-in-your-organization/ Tue, 23 Jan 2024 11:00:05 +0000 https://engineering-leadership.hinshelwood.com/videos/how-do-you-know-the-value-currently-delivered-in-your-organization/ Evidence-Based Management helps organizations measure and improve the value they deliver by using key metrics like customer satisfaction, employee engagement, revenue per employee, product cost ratio, and customer usage. This approach enables clearer goals, better decisions, and ongoing improvement by relying on data instead of assumptions. Start small with relevant metrics, involve your team, and regularly review results to drive meaningful change. https://engineering-leadership.hinshelwood.com/signals/at-the-end-of-the-day-kanban-is-about-improving-flow/ Mon, 03 Mar 2025 15:46:26 +0000 https://engineering-leadership.hinshelwood.com/signals/at-the-end-of-the-day-kanban-is-about-improving-flow/ Kanban focuses on improving workflow by removing constraints and bottlenecks, not by pushing people to work harder or longer. Key to better delivery is reducing work in progress and identifying blockers to increase efficiency. Managers should identify and address the biggest constraint in their current workflow to see meaningful improvements. https://engineering-leadership.hinshelwood.com/signals/detecting-agile-theatre-with-real-delivery-signals/ Mon, 25 May 2026 00:00:00 +0000 https://engineering-leadership.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.hinshelwood.com/videos/how-do-you-know-how-long-it-takes-to-deliver-value/ Fri, 26 Jan 2024 11:00:51 +0000 https://engineering-leadership.hinshelwood.com/videos/how-do-you-know-how-long-it-takes-to-deliver-value/ Measuring and improving Time to Market is essential for delivering value quickly and staying competitive. Key metrics like lead time, cycle time, time to pivot, time to learn, and time to fix help teams identify bottlenecks and make better decisions. Focus on streamlining processes, automating tasks, gathering fast feedback, and building cross-functional teams to reduce delivery times and ensure you are delivering what customers need most. https://engineering-leadership.hinshelwood.com/videos/taming-the-chaos-how-to-align-your-agile-team-for-success/ Fri, 03 Nov 2023 05:11:45 +0000 https://engineering-leadership.hinshelwood.com/videos/taming-the-chaos-how-to-align-your-agile-team-for-success/ Chaos in Agile teams is usually caused by unclear goals, lack of direction, and poor communication, which leads to inefficiency and confusion. Aligning teams through clear goals, regular check-ins, open communication, and visualising progress increases motivation, collaboration, and productivity. Development managers should prioritise establishing and communicating shared objectives to reduce chaos and drive team success. https://engineering-leadership.hinshelwood.com/videos/7-deadly-sins-of-agile-gluttony/ Wed, 11 Oct 2023 11:35:09 +0000 https://engineering-leadership.hinshelwood.com/videos/7-deadly-sins-of-agile-gluttony/ Excessive backlog items, overambitious sprint plans, and unnecessary product features can slow teams down and reduce focus. Regularly prioritise and trim the backlog, set realistic sprint goals, and remove unused features to keep the team agile and deliver real value. Focus on quality and relevance rather than quantity to improve productivity and morale. https://engineering-leadership.hinshelwood.com/videos/overview-of-the-'scaling-with-portfolio-kanban'-course/ Thu, 22 Feb 2024 07:00:26 +0000 https://engineering-leadership.hinshelwood.com/videos/overview-of-the-'scaling-with-portfolio-kanban'-course/ The “Scaling Portfolio Kanban” course helps development leaders move from team-level to organization-wide workflow management, enabling better visibility, predictability, and value delivery across multiple teams. Key outcomes include improved forecasting, data-driven decision-making, and optimized flow of high-value projects. If your current workflow lacks predictability or efficiency, consider applying these Kanban strategies to drive measurable improvement. https://engineering-leadership.hinshelwood.com/videos/mastering-evidence-based-management-ebm-for-product-owners-maximizing-value-delivery/ Mon, 29 Jan 2024 07:00:07 +0000 https://engineering-leadership.hinshelwood.com/videos/mastering-evidence-based-management-ebm-for-product-owners-maximizing-value-delivery/ Evidence-Based Management (EBM) helps product owners make better decisions by tracking key metrics like current value, unrealized value, ability to innovate, and time to market, ensuring teams focus on delivering the right value efficiently. Using EBM enables you to identify when to pivot, align stakeholders, and engage your team in the product’s success. Consider adopting EBM practices or training, such as the PAL-EBM course, to maximize value delivery and team effectiveness. https://engineering-leadership.hinshelwood.com/guides/kanban-guide-for-scrum-teams/ Tue, 17 Sep 2024 00:00:00 +0000 https://engineering-leadership.hinshelwood.com/guides/kanban-guide-for-scrum-teams/ Explains how Scrum Teams can use Kanban practices to optimise workflow, track flow metrics, and enhance transparency, efficiency, and continuous improvement in product delivery. https://engineering-leadership.hinshelwood.com/videos/turning-user-feedback-into-actionable-work-a-guide-to-maximizing-product-value/ Wed, 10 Jul 2024 06:45:01 +0000 https://engineering-leadership.hinshelwood.com/videos/turning-user-feedback-into-actionable-work-a-guide-to-maximizing-product-value/ Turning user feedback into actionable work quickly is essential for delivering real product value and staying truly agile. Teams that engage users regularly, prioritize feedback effectively, and integrate it into each Sprint see higher satisfaction and better business results. Review feedback weekly, involve stakeholders, and empower your team to act fast so your product evolves in line with user needs. https://engineering-leadership.hinshelwood.com/videos/my-journey-with-kanban-and-why-i-actively-recommend-it-to-clients/ Fri, 23 Feb 2024 07:00:12 +0000 https://engineering-leadership.hinshelwood.com/videos/my-journey-with-kanban-and-why-i-actively-recommend-it-to-clients/ Kanban is a practical strategy for improving workflow and predictability by making work processes more transparent and data-driven, which builds trust and enables better decision-making. Integrating Kanban with Scrum helps teams deliver more consistently and reduces stakeholder uncertainty. Development managers should consider adopting Kanban to optimize team performance and deliver greater value across any context. https://engineering-leadership.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-use-vanity-metrics/ Thu, 29 Feb 2024 07:00:09 +0000 https://engineering-leadership.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-use-vanity-metrics/ Relying on vanity metrics like story points and velocity can undermine your Kanban strategy, as they do not provide actionable insights. Instead, focus on key metrics such as work in progress, cycle time, throughput, and work item age to identify bottlenecks, optimize flow, and improve predictability. Use data from your workflow tools to drive continuous improvement and make informed decisions for better team performance. https://engineering-leadership.hinshelwood.com/guides/kanban-guide/ Thu, 01 May 2025 00:00:00 +0000 https://engineering-leadership.hinshelwood.com/guides/kanban-guide/ Comprehensive reference outlining Kanban principles, practices, and metrics for optimising workflow, value delivery, and continuous improvement in knowledge work. https://engineering-leadership.hinshelwood.com/videos/how-to-achieve-predictability-in-business-through-agile-principles/ Tue, 08 Oct 2024 10:33:32 +0000 https://engineering-leadership.hinshelwood.com/videos/how-to-achieve-predictability-in-business-through-agile-principles/ Predictability in software development is achieved by aligning teams around clear goals, optimizing systems, and adopting Agile principles that balance planning with adaptability. Key insights include the importance of well-defined processes, empowering teams to make decisions, and tailoring Agile frameworks to fit your unique business needs, as seen in Microsoft’s transformation. To improve predictability, focus on continuous improvement, effective communication, and collaboration both within teams and with customers. https://engineering-leadership.hinshelwood.com/articles/quality-enablement-with-visual-studio-2012/ Wed, 15 May 2013 03:13:20 +0000 https://engineering-leadership.hinshelwood.com/articles/quality-enablement-with-visual-studio-2012/ Explores how Visual Studio 2012 supports continuous quality enablement, automated testing, and rapid delivery in modern software development for higher user satisfaction. https://engineering-leadership.hinshelwood.com/guides/okr-guide/ Thu, 26 Jun 2025 00:00:00 +0000 https://engineering-leadership.hinshelwood.com/guides/okr-guide/ Comprehensive guide to using OKRs for shared focus, measurable outcomes, and strategic learning, including roles, events, best practices, and common pitfalls. https://engineering-leadership.hinshelwood.com/videos/in-wip-less-is-more-why/ Tue, 09 May 2023 07:00:19 +0000 https://engineering-leadership.hinshelwood.com/videos/in-wip-less-is-more-why/ Limiting work in progress leads to higher productivity because multitasking and context switching reduce efficiency and slow down progress. Keeping tasks small and focusing on finishing before starting new work helps teams deliver more in less time. Development managers should encourage teams to reduce simultaneous tasks and prioritize completing work to improve outcomes. https://engineering-leadership.hinshelwood.com/videos/why-embracing-automation-is-essential-for-reducing-human-error-in-software-development/ Wed, 18 Dec 2024 06:45:00 +0000 https://engineering-leadership.hinshelwood.com/videos/why-embracing-automation-is-essential-for-reducing-human-error-in-software-development/ Automation is essential in software development because it reduces human error, speeds up feedback, and creates more reliable processes. Relying on manual steps leads to costly mistakes and unsustainable workloads, while automation enables faster, higher-quality releases and happier customers. Development managers should prioritise automating repetitive tasks and rearchitecting processes that cannot be automated to improve quality and efficiency. https://engineering-leadership.hinshelwood.com/articles/standard-environments-for-automated-deployment-and-testing/ Sun, 17 Mar 2013 06:23:45 +0000 https://engineering-leadership.hinshelwood.com/articles/standard-environments-for-automated-deployment-and-testing/ Explains how to set up and use Standard Environments in Visual Studio 2012 TFS for automated software deployment and testing, enabling consistent, repeatable pipelines. https://engineering-leadership.hinshelwood.com/articles/automated-testing-in-a-modern-application-lifecycle/ Tue, 25 Sep 2012 04:33:30 +0000 https://engineering-leadership.hinshelwood.com/articles/automated-testing-in-a-modern-application-lifecycle/ Explains the role of automated testing in modern software development, covering types, integration, benefits, challenges, and tools for maintaining code quality. https://engineering-leadership.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-sweep-problems-under-the-rug/ Mon, 04 Mar 2024 07:00:13 +0000 https://engineering-leadership.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.hinshelwood.com/videos/navigating-the-balance-how-lean-governance-can-boost-agility-and-innovation-in-your-organisation/ Sun, 09 Feb 2025 22:00:37 +0000 https://engineering-leadership.hinshelwood.com/videos/navigating-the-balance-how-lean-governance-can-boost-agility-and-innovation-in-your-organisation/ Excessive or siloed governance can slow down your organisation and stifle innovation, often leading to unnecessary processes that do not add value. Focusing on lean governance by regularly reviewing policies, integrating compliance into your tools, and eliminating waste helps maintain agility and efficiency. Review your current governance practices and remove or streamline anything that does not directly support compliance or business value. https://engineering-leadership.hinshelwood.com/workshops/the-importance-of-batch-to-optimise-flow/ Tue, 17 Sep 2024 00:00:00 +0000 https://engineering-leadership.hinshelwood.com/workshops/the-importance-of-batch-to-optimise-flow/ Explains how breaking large tasks into smaller batches improves workflow, predictability, and delivery speed, using hands-on exercises based on queuing theory principles. https://engineering-leadership.hinshelwood.com/videos/does-kanban-integrate-into-a-scrum-environment/ Thu, 15 Feb 2024 07:00:31 +0000 https://engineering-leadership.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.hinshelwood.com/articles/introducing-kanban-for-professional-scrum-teams/ Mon, 26 Feb 2018 15:00:08 +0000 https://engineering-leadership.hinshelwood.com/articles/introducing-kanban-for-professional-scrum-teams/ A new Professional Scrum with Kanban class and guide now enable Scrum teams to integrate Kanban practices like workflow visualization, limiting work in progress, and flow-based metrics without changing Scrum itself. This approach helps teams focus on value delivery and can replace traditional metrics like velocity with more actionable measures such as throughput and cycle time. Development managers should consider reviewing the Kanban Guide for Scrum Teams and exploring the training to enhance their teams’ effectiveness. https://engineering-leadership.hinshelwood.com/videos/the-key-to-a-kanban-strategy-understanding-wip-limits/ Wed, 06 Mar 2024 07:00:17 +0000 https://engineering-leadership.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.hinshelwood.com/videos/overview-of-'applying-metrics-for-predictability'-kanban-course/ Tue, 20 Feb 2024 07:00:27 +0000 https://engineering-leadership.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.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.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.hinshelwood.com/videos/3-core-practices-of-kanban-actively-managing-work-items-in-a-workflow/ Mon, 26 Feb 2024 14:06:47 +0000 https://engineering-leadership.hinshelwood.com/videos/3-core-practices-of-kanban-actively-managing-work-items-in-a-workflow/ Actively managing your Kanban workflow is essential for keeping work moving efficiently; this involves regularly reviewing your board, adjusting work in progress limits, and quickly addressing bottlenecks or blocked items. Monitoring for aging or stuck tasks and using data to optimize flow helps prevent delays and maximize team productivity. Development managers should ensure their teams are not just visualizing work but actively engaging with and improving the workflow. https://engineering-leadership.hinshelwood.com/videos/rethinking-backlog-management-why-a-flat-structure-boosts-agility-and-value-delivery/ Tue, 26 Mar 2024 10:56:26 +0000 https://engineering-leadership.hinshelwood.com/videos/rethinking-backlog-management-why-a-flat-structure-boosts-agility-and-value-delivery/ Using a flat backlog instead of a hierarchical one makes it easier to prioritise work, adapt to changing needs, and focus on delivering value rather than just managing tasks. Flat structures avoid the inflexibility and complexity of parent-child relationships, allowing teams to use tags and flexible visualisations for context. Development managers should consider shifting to a flat backlog to improve agility and value delivery. https://engineering-leadership.hinshelwood.com/videos/3-core-practices-of-kanban-improving-a-workflow/ Wed, 28 Feb 2024 07:00:19 +0000 https://engineering-leadership.hinshelwood.com/videos/3-core-practices-of-kanban-improving-a-workflow/ Continuous improvement is a key Kanban practice that focuses on identifying and removing workflow blockages and reducing waiting times to maximize value delivery. Making inefficiencies and their costs visible, as shown in a real-life example, can prompt immediate behavioral changes and significant efficiency gains. Development managers should regularly review processes, use visual aids to highlight delays, and engage stakeholders to drive ongoing workflow improvements. https://engineering-leadership.hinshelwood.com/videos/temperance-in-agile-why-less-is-more/ Tue, 05 Dec 2023 07:00:10 +0000 https://engineering-leadership.hinshelwood.com/videos/temperance-in-agile-why-less-is-more/ Focusing on just enough work and keeping your backlog, planning, and team size lean helps your team deliver more value and avoid waste or burnout. Prioritize only high-impact tasks, limit work in progress, and avoid over-refining or over-planning. Say no to non-essential work, balance short-term wins with long-term goals, and seek coaching if you struggle to maintain this balance. https://engineering-leadership.hinshelwood.com/videos/what-is-the-difference-between-resource-efficiency-and-flow-efficiency/ Thu, 09 Mar 2023 07:00:02 +0000 https://engineering-leadership.hinshelwood.com/videos/what-is-the-difference-between-resource-efficiency-and-flow-efficiency/ Resource efficiency focuses on maximizing how much each team member produces, while flow efficiency looks at how smoothly work moves through the entire process. Overemphasizing resource efficiency can lead to burnout and bottlenecks, but balancing both approaches helps create a healthier, more productive workflow. Review your current processes to ensure you are not just keeping people busy but also delivering value efficiently across the system. https://engineering-leadership.hinshelwood.com/videos/the-open-guide-to-kanban-unlocking-collaborative-flow-and-real-world-value-for-every-team/ Thu, 03 Jul 2025 05:22:41 +0000 https://engineering-leadership.hinshelwood.com/videos/the-open-guide-to-kanban-unlocking-collaborative-flow-and-real-world-value-for-every-team/ The Open Guide to Kanban is a collaborative, community-driven resource that makes Kanban accessible and practical for all teams, focusing on real-world value rather than rigid rules or jargon. It encourages managers and teams to start small, visualize work, and continuously improve by contributing to and adapting the guide. Managers should engage directly with their teams, use the guide to enhance visibility and flow, and participate in the community to solve real problems together. https://engineering-leadership.hinshelwood.com/articles/engaging-with-complexity-team-foundation-server-edition/ Mon, 01 Jul 2013 17:00:31 +0000 https://engineering-leadership.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.hinshelwood.com/videos/unlocking-the-power-of-kanban-transform-your-workflow-with-data-driven-insights/ Wed, 23 Aug 2023 07:00:10 +0000 https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-kanban-transform-your-workflow-with-data-driven-insights/ Kanban can be applied to any workflow to provide visibility into how work moves through your system, enabling teams to optimise delivery speed and manage capacity effectively. By using data analysis and probabilistic forecasting, such as Monte Carlo simulations, you can set realistic expectations with stakeholders and make more informed decisions. Consider adopting Kanban to improve transparency, predictability, and continuous improvement in your development processes. https://engineering-leadership.hinshelwood.com/articles/upgrading-from-tfs-2008-and-wss-v3-0-with-sftsv2-to-tfs-2010-and-sf-2010-with-sftsv3/ Thu, 30 Jun 2011 15:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/upgrading-from-tfs-2008-and-wss-v3-0-with-sftsv2-to-tfs-2010-and-sf-2010-with-sftsv3/ Step-by-step guide to upgrading TFS 2008 and WSS v3.0 with SfTSv2 to TFS 2010 and SharePoint 2010, including process template migration and data handling. https://engineering-leadership.hinshelwood.com/videos/mastering-kanban-a-simple-guide-to-its-core-principles/ Mon, 01 Jul 2024 07:00:24 +0000 https://engineering-leadership.hinshelwood.com/videos/mastering-kanban-a-simple-guide-to-its-core-principles/ Kanban helps teams boost productivity by visualizing their workflow, actively managing tasks, and continuously improving processes. Key benefits include increased transparency, better communication, and faster delivery through proactive management and small, ongoing improvements. Start by mapping your workflow, then focus on daily task management and regular process reviews to drive efficiency. https://engineering-leadership.hinshelwood.com/videos/understanding-the-power-of-kanban-in-scrum/ Mon, 05 Aug 2024 06:45:00 +0000 https://engineering-leadership.hinshelwood.com/videos/understanding-the-power-of-kanban-in-scrum/ Kanban is not a replacement for Scrum but a complementary strategy that increases transparency, helps teams visualize workflow, and manage work in progress, leading to better focus and faster feedback. Integrating Kanban with Scrum enables teams to identify bottlenecks, improve efficiency, and consistently meet sprint goals. Development managers should consider adding Kanban boards and WIP limits to their Scrum process to enhance team performance and value delivery. https://engineering-leadership.hinshelwood.com/videos/understanding-kanban-a-tool-for-transparency-and-continuous-improvement/ Mon, 24 Jun 2024 06:48:02 +0000 https://engineering-leadership.hinshelwood.com/videos/understanding-kanban-a-tool-for-transparency-and-continuous-improvement/ Kanban is a tool that helps teams visualize their workflow, track key metrics, and identify bottlenecks, leading to greater transparency and continuous improvement without changing existing processes. By starting with a simple board, setting work-in-progress limits, and regularly reviewing metrics, teams can quickly spot issues and make data-driven improvements. Development managers should consider implementing Kanban to gain clearer insights into team performance and drive ongoing process enhancements. https://engineering-leadership.hinshelwood.com/videos/mastering-kanban-the-essential-guide-to-defining-and-visualising-your-workflow-for-maximum-efficiency/ Tue, 27 Feb 2024 07:00:31 +0000 https://engineering-leadership.hinshelwood.com/videos/mastering-kanban-the-essential-guide-to-defining-and-visualising-your-workflow-for-maximum-efficiency/ Defining and visualising your workflow in Kanban creates shared understanding, clarity, and alignment among team members, which leads to greater efficiency. Establishing clear rules for task selection, workflow stages, and work in progress is essential for a stable and productive system. Take time to document and visualise your process so everyone knows how work flows and can contribute effectively. https://engineering-leadership.hinshelwood.com/videos/why-limiting-work-in-progress-is-key-to-success-in-kanban/ Mon, 22 Jul 2024 06:00:19 +0000 https://engineering-leadership.hinshelwood.com/videos/why-limiting-work-in-progress-is-key-to-success-in-kanban/ Limiting work in progress is essential for effective Kanban because it helps teams focus, exposes bottlenecks, and supports a sustainable pace, leading to higher quality and faster delivery. Teams that set and adjust WIP limits based on capacity see improved productivity and less stress. To get the benefits, involve your team in setting WIP limits and regularly review them to keep your workflow smooth and predictable. https://engineering-leadership.hinshelwood.com/videos/why-is-kanban-such-a-popular-approach-for-people-in-creative-industries/ Fri, 25 Aug 2023 07:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/why-is-kanban-such-a-popular-approach-for-people-in-creative-industries/ Kanban is popular in creative industries because it adapts to existing workflows, reduces chaos, and helps teams align on priorities without stifling creativity. It improves efficiency by visualising work, shortening cycle times, and encouraging collective decision-making. Development managers should consider mapping their team’s current process with Kanban to enhance collaboration and deliver creative work more predictably. https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-caman-why-it-s-the-perfect-companion-to-scrum-for-process-optimisation/ Tue, 13 Aug 2024 07:04:49 +0000 https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-caman-why-it-s-the-perfect-companion-to-scrum-for-process-optimisation/ Caman is a strategy that complements Scrum by increasing transparency and providing deeper insights into workflows, helping teams identify bottlenecks and optimise processes. It is universally applicable across different systems and industries, not just software development. Development managers should use Caman alongside Scrum by mapping processes, involving teams in discussions, and iterating improvements to enhance value delivery. https://engineering-leadership.hinshelwood.com/videos/the-importance-of-product-backlog-management-in-today's-agile-landscape/ Fri, 01 Dec 2023 07:00:11 +0000 https://engineering-leadership.hinshelwood.com/videos/the-importance-of-product-backlog-management-in-today's-agile-landscape/ Effective product backlog management is essential for team focus, stakeholder alignment, and delivering real value, yet many organizations neglect it, leading to confusion and wasted effort. Key issues include oversized or outdated backlogs, lack of regular refinement, insufficient detail, and poor stakeholder involvement. To improve, keep the backlog lean, refine it regularly with the whole team, ensure transparency and clarity, and use data to guide priorities; making this a priority will boost team performance and stakeholder satisfaction. https://engineering-leadership.hinshelwood.com/videos/mastering-your-kanban-board-a-practical-guide-to-visualising-workflows-for-maximum-efficiency/ Mon, 08 Jul 2024 06:00:07 +0000 https://engineering-leadership.hinshelwood.com/videos/mastering-your-kanban-board-a-practical-guide-to-visualising-workflows-for-maximum-efficiency/ A clear and accurate Kanban board is essential for understanding and improving your team’s workflow. Map your actual process, adjust columns to reflect real work stages, and use visual cues to highlight priorities and bottlenecks. Regularly review and adapt your board to boost team collaboration, identify issues early, and drive continuous improvement. https://engineering-leadership.hinshelwood.com/videos/mastering-product-backlog-management-insights-from-the-new-scrum-org-course/ Thu, 30 Nov 2023 07:00:11 +0000 https://engineering-leadership.hinshelwood.com/videos/mastering-product-backlog-management-insights-from-the-new-scrum-org-course/ Scrum.org’s new Product Backlog Management course offers focused, practical training in backlog management, helping teams capture, prioritize, and break down work for better clarity and alignment. The compact 8-hour format teaches actionable techniques to minimize distractions, improve transparency, and ensure teams deliver high-value work that supports business goals. Development managers should consider this course to streamline their backlog processes and boost team efficiency. https://engineering-leadership.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.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.hinshelwood.com/videos/what-is-kanban/ Mon, 12 Feb 2024 07:00:11 +0000 https://engineering-leadership.hinshelwood.com/videos/what-is-kanban/ Kanban is a flexible strategy for improving existing workflows by making processes visible, tracking data, and enabling continuous, incremental improvements. Key steps include documenting your current workflow, visualizing work to spot issues, and using metrics to guide changes. Start by mapping your team’s process and use the insights to drive efficiency and effectiveness. https://engineering-leadership.hinshelwood.com/articles/create-a-portfolio-backlog-hierarchy-in-team-foundation-server-2013/ Mon, 08 Jul 2013 21:35:24 +0000 https://engineering-leadership.hinshelwood.com/articles/create-a-portfolio-backlog-hierarchy-in-team-foundation-server-2013/ Learn how to customise Team Foundation Server 2013 to add a multi-level Portfolio Backlog hierarchy by editing work item types, categories, and process configuration. https://engineering-leadership.hinshelwood.com/tags/predictive-operating-model/ Mon, 24 Nov 2025 13:22:30 +0000 https://engineering-leadership.hinshelwood.com/tags/predictive-operating-model/ The Predictive Operating Model is a traditional framework for organizing work that originated during the industrial revolution and is grounded in scientific management principles, notably those of Frederick Taylor and Henry Ford. It is characterized by hierarchical structures, centralized planning and control, functional specialization, and a strong emphasis on efficiency, standardization, and minimizing variability. This model assumes that customer demand and market conditions are stable, work can be fully specified in advance, and performance is best improved through detailed planning, specialization, and strict adherence to procedures. It operates through mechanisms such as predictive plans, fixed scopes and resources, stage gates, and individual accountability, with success measured by output consistency, cost control, and on-time delivery. The Predictive Operating Model excels in stable, predictable environments where repeatable processes and operational excellence provide competitive advantage, enabling organizations to scale efficiently and maintain clear accountability. However, it faces significant limitations in dynamic or uncertain contexts, such as slow adaptation to change, siloed functions, long feedback loops, and limited capacity for learning or innovation. As markets and customer needs become more volatile and complex, many organizations are transitioning toward more adaptive models that emphasize flexibility, cross-functional collaboration, and iterative learning. Understanding the Predictive Operating Model is crucial for organizations aiming to evolve their operating practices, as it highlights both the strengths that can be leveraged in stable settings and the constraints that must be addressed to succeed in agile, DevOps, or product-centric environments. https://engineering-leadership.hinshelwood.com/tags/customer-focus/ Tue, 13 May 2025 09:00:00 +0100 https://engineering-leadership.hinshelwood.com/tags/customer-focus/ Customer Focus is not a platitude. It’s the first principle of agile delivery and product development. It defines value, directs investment, and constrains decisions. If you’re not anchored in real customer outcomes, you’re optimising the wrong system. This principle demands more than empathy. It demands feedback, evidence, and relentless alignment to customer need. https://engineering-leadership.hinshelwood.com/tags/sprint-review/ Sun, 11 May 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/sprint-review/ The Sprint Review is a fundamental event within the Scrum framework, aimed at evaluating the work completed during a sprint and refining the product backlog based on feedback from stakeholders. This collaborative meeting involves the Scrum Team and key stakeholders, promoting transparency and open communication regarding the product’s progress and future direction. By presenting the increment, teams can assess their achievements against the sprint goal, ensuring alignment with customer needs and expectations. This practice is crucial for enabling teams to deliver value consistently and sustainably, as it fosters continuous improvement through real-time feedback, which is essential in a rapidly changing market. The Sprint Review enhances accountability and nurtures a culture of collaboration and shared ownership among team members and stakeholders. Additionally, it provides a forum for discussing future priorities, ensuring that the product evolves to maximise value delivery. By incorporating stakeholder insights, teams can make informed decisions that improve the product’s development trajectory, ultimately leading to a more resilient and adaptive process. The Sprint Review is not just a routine check; it is a vital tool for promoting innovation and responsiveness within the organisation, contributing to long-term success and customer satisfaction through a commitment to ongoing learning and adaptation. https://engineering-leadership.hinshelwood.com/tags/increment/ Mon, 05 May 2025 10:17:24 +0000 https://engineering-leadership.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.hinshelwood.com/tags/product-backlog/ Mon, 05 May 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/product-backlog/ The Product Backlog is a dynamic and prioritised list of work items that acts as the definitive source for what needs to be accomplished in order to deliver a product. It includes features, enhancements, bug fixes, and technical tasks, providing teams with a clear understanding of their objectives. This concept is vital as it allows teams to deliver value in a predictable and sustainable manner by offering transparency regarding priorities and progress. Effective management of the backlog encourages collaboration among stakeholders and enables continuous refinement based on feedback and shifting market conditions. It empowers teams to make informed decisions about their next steps, aligning their work with strategic goals and customer needs. The Product Backlog is more than just a to-do list; it is a living artefact that captures the evolving understanding of the product and its context, promoting a culture of continuous improvement and adaptability. By maintaining a well-structured backlog, organisations can enhance agility, minimise waste, and optimise resource allocation, leading to more successful product outcomes. This systematic approach to backlog management supports long-term planning while remaining flexible enough to address new insights and challenges as they emerge. Ultimately, the Product Backlog is foundational to effective Agile practices, ensuring that teams focus on delivering high-quality, valuable products that meet user expectations and contribute to business success. https://engineering-leadership.hinshelwood.com/tags/site-reliability-engineering/ Mon, 05 May 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/site-reliability-engineering/ Site Reliability Engineering (SRE) is a discipline that utilises software engineering principles to develop scalable and reliable systems, effectively bridging the gap between development and operations. Originating from the need to embed reliability within the software development lifecycle, SRE ensures that systems maintain functionality and resilience under diverse conditions. This methodology prioritises automation, monitoring, and incident response, which allows teams to deliver consistent value in a sustainable manner. SRE teams establish service level objectives (SLOs) and service level indicators (SLIs) to create clear performance and reliability metrics, fostering a culture of accountability and continuous improvement. This proactive approach to problem-solving and engineering solutions to operational challenges enhances overall system performance, distinguishing SRE from traditional operations roles. By promoting shared responsibility for reliability across teams, SRE encourages collaboration and knowledge sharing, which not only improves user satisfaction but also drives positive business outcomes. Ultimately, the integration of reliability into the development process supports organisational strategic goals and enhances competitive advantage, making SRE a vital component in agile, DevOps, and product development frameworks. https://engineering-leadership.hinshelwood.com/tags/service-level-expectation/ Mon, 05 May 2025 09:46:11 +0000 https://engineering-leadership.hinshelwood.com/tags/service-level-expectation/ A Service Level Expectation (SLE) is a forecast used by Scrum Teams to estimate the time it should take for a work item to move from initiation to completion within their workflow. Originating from practices that combine elements of Scrum and Kanban, the SLE is defined by two components: a specific range of elapsed days and the probability that work items will be completed within that timeframe, such as stating that 85 percent of items should be finished in eight days or less. The SLE is calculated using the team’s historical cycle time data, which measures how long work items have taken to complete in the past. If such data is not yet available, teams are encouraged to make an informed estimate and refine it as more data becomes available. The SLE is made transparent to all team members and stakeholders, serving as a tool for identifying flow issues and prompting inspection and adaptation when expectations are not met. In agile and DevOps contexts, the SLE is valuable because it enhances predictability, supports continuous improvement, and helps teams manage stakeholder expectations by providing a clear, data-driven understanding of delivery timelines. Keeping the SLE shorter than the length of a Sprint further improves the team’s ability to deliver reliably and respond to change. https://engineering-leadership.hinshelwood.com/tags/definition-of-done/ Mon, 05 May 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/tags/definition-of-done/ The Definition of Done (DoD) is a critical framework that establishes a shared understanding of what constitutes a completed and releasable product increment within agile and DevOps environments. Originating from the need for clarity in product development, the DoD serves as an organisational standard that all teams must adhere to, ensuring that every increment meets minimum quality criteria before it can be considered complete. This framework is vital for fostering transparency and consistency across teams, enabling empirical decision-making based on real-world feedback. By defining specific criteria, such as deployment in production, telemetry collection, and validation of initial hypotheses, the DoD helps mitigate risks associated with incomplete or subpar work, thereby reducing technical debt and enhancing the overall quality of deliverables. Furthermore, it facilitates faster feedback loops and iterative learning, allowing teams to adapt their processes based on actual performance data. The DoD not only clarifies expectations for stakeholders but also protects the integrity of the product, ensuring that increments are valuable, verifiable, and ready for real-world use. In essence, the Definition of Done is foundational to maintaining high standards in product development, promoting alignment among teams, and ultimately driving successful outcomes in organisational design and delivery. https://engineering-leadership.hinshelwood.com/tags/definition-of-workflow/ Mon, 05 May 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/tags/definition-of-workflow/ The Definition of Workflow in the context of Kanban is a dynamic and explicit model that outlines how work progresses through a value stream, making the flow of work visible and understandable. Rather than being a fixed checklist, it consists of clear agreements and policies that determine how work is selected, initiated, managed, and completed. Key elements include entry criteria, which specify when work is ready to begin; limits on work in progress, which help manage capacity and focus; and exit policies, which define what it means for work to be considered finished at each stage. This approach is not intended for micromanagement but to enhance the transparency and legibility of the system, enabling teams to inspect and continuously improve their processes. In Kanban, the Definition of Workflow is central to making work explicit and fostering a culture of ongoing refinement. While Scrum does not formally define a Definition of Workflow, it incorporates related concepts such as the Definition of Done and encourages teams to visualise their work. Understanding and applying a Definition of Workflow is valuable in agile, DevOps, and product development environments because it clarifies expectations, supports collaboration, and provides a foundation for process improvement and adaptability. https://engineering-leadership.hinshelwood.com/tags/liberating-structures/ Mon, 14 Apr 2025 14:50:18 +0000 https://engineering-leadership.hinshelwood.com/tags/liberating-structures/ Liberating Structures are a modular toolkit of facilitation techniques used to structure team interactions, promote equal participation, and improve collaboration. Designed as plug-and-play alternatives to conventional meeting formats, each structure provides a clear pattern for group engagement, making them easy to learn and adapt. In Agile, Lean, and DevOps contexts, they support team self-organisation by enabling rapid idea generation, shared understanding, and collective decision-making. When applied intentionally, these methods enhance team effectiveness and help build a culture of trust and psychological safety, without requiring major changes to existing workflows. https://engineering-leadership.hinshelwood.com/tags/lead-time/ Fri, 11 Apr 2025 06:00:00 +0100 https://engineering-leadership.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.hinshelwood.com/tags/current-value/ Thu, 10 Apr 2025 14:21:05 +0000 https://engineering-leadership.hinshelwood.com/tags/current-value/ Current Value is a vital metric within Evidence-Based Management that quantifies the real-time value a product or service provides to its users. It includes various indicators such as customer satisfaction, revenue impact, and performance feedback, which together offer insights into the value being realised at any moment. This concept is crucial for teams striving to deliver value in a predictable and sustainable manner, as it facilitates continuous assessment and adjustment based on actual performance rather than assumptions. By tracking Current Value, organisations can make data-driven decisions that improve their offerings and better align them with customer needs. This ongoing evaluation promotes a culture of responsiveness and adaptability, allowing teams to swiftly adjust to feedback and shifting market conditions. Unlike static measures, Current Value is dynamic and systemic, reflecting the changing landscape of customer expectations and business environments. It empowers teams to concentrate on delivering meaningful outcomes, ensuring that their efforts lead to long-term success and customer loyalty. This emphasis on real-time value delivery distinguishes Current Value from other concepts such as Value Stream Management or Customer Satisfaction, which may not fully capture the immediacy and comprehensive nature of the value being generated. https://engineering-leadership.hinshelwood.com/tags/time-to-market/ Thu, 10 Apr 2025 14:20:01 +0000 https://engineering-leadership.hinshelwood.com/tags/time-to-market/ Time to Market is a critical metric that evaluates how quickly an organisation can transform ideas into market-ready products or features, incorporating various measures such as lead time and cycle time to provide a comprehensive understanding of product development efficiency. This concept is essential for organisations striving to deliver value in a predictable and sustainable manner, as a shorter Time to Market allows teams to swiftly address customer needs and adapt to market fluctuations. By prioritising Time to Market, organisations can gain a competitive advantage, ensuring that their innovations reach customers ahead of competitors. This focus on agility promotes a culture of continuous improvement, encouraging teams to refine processes and eliminate inefficiencies. The systemic nature of Time to Market impacts not only individual projects but also the overall organisational capacity for innovation and adaptability. It aligns with Lean and Agile methodologies, fostering a mindset that prioritises speed while maintaining quality. Ultimately, a strong commitment to Time to Market nurtures an environment where delivering value becomes a core organisational principle, contributing to long-term success and resilience in an ever-evolving marketplace. https://engineering-leadership.hinshelwood.com/tags/throughput/ Wed, 09 Apr 2025 14:41:23 +0000 https://engineering-leadership.hinshelwood.com/tags/throughput/ Throughput is a critical observability metric that quantifies the volume of work completed by a system within a defined timeframe, serving as an indicator of the flow of value delivered by teams. Originating from Agile and Lean methodologies, throughput is utilised to assess system performance holistically rather than focusing on individual contributions. By monitoring throughput, teams can uncover trends, pinpoint bottlenecks, and evaluate the impact of workflow modifications on overall efficiency. Visualisation tools such as cumulative flow diagrams and flow analytics facilitate real-time tracking of throughput data, enabling teams to inspect flow health alongside other metrics like lead time and cycle time. This empirical approach fosters informed decision-making, guiding adjustments in work-in-progress limits, team structures, and planning processes. Ultimately, throughput enhances transparency and supports a culture of continuous improvement, allowing organisations to optimise their processes without relying on subjective evaluations of performance. https://engineering-leadership.hinshelwood.com/tags/scaling/ Wed, 09 Apr 2025 13:53:11 +0000 https://engineering-leadership.hinshelwood.com/tags/scaling/ Scaling refers to the capacity of an organisation to effectively coordinate multiple teams in the delivery of complex products while maintaining agility. This concept originates from the need to align efforts, optimise workflow, and enhance value delivery across the enterprise. It is particularly important in the contexts of agile methodologies and DevOps, as it allows organisations to respond swiftly to market changes without compromising on quality or speed. By implementing lean principles and adaptive product structures, scaling promotes a cohesive approach to product development, enabling teams to operate autonomously while remaining aligned with broader business objectives. This alignment is crucial for maximising efficiency and minimising waste, thereby leveraging the organisation’s collective capabilities. Furthermore, scaling fosters a culture of continuous improvement, where feedback loops and collaboration are integral to the development process. By prioritising these aspects, organisations can achieve sustainable growth and deliver value consistently, enhancing their competitive advantage in a rapidly changing environment. Ultimately, scaling is not just about increasing size but about establishing a robust framework that supports innovation and responsiveness throughout the organisation. https://engineering-leadership.hinshelwood.com/concepts/method/ Wed, 09 Apr 2025 14:00:00 +0100 https://engineering-leadership.hinshelwood.com/concepts/method/ Method refers to a structured, step-by-step approach employed to achieve specific objectives within a system, distinguishing itself from frameworks that provide broader guidelines. In Agile, Lean, and DevOps environments, methods are vital for guiding teams through systematic processes that enhance collaborative work, value delivery, and continuous improvement. They are utilised to optimise workflows, manage iterative development, and measure progress effectively. For example, the Scrum method outlines a sequence of events such as Sprint Planning and Daily Scrum to facilitate work in short cycles, while the Kanban method aids in visualising workflows and limiting work in progress. Methods ensure consistency and predictability in outcomes by breaking down complex processes into manageable tasks, allowing teams to execute with precision and adapt to real-time feedback. In Lean, methods focus on eliminating waste to maximise value delivery, whereas in DevOps, practices like Continuous Integration and Continuous Delivery enable rapid and reliable software releases. It is crucial to differentiate methods from frameworks, which provide structural foundations, and practices, which are individual techniques within broader methods. By adhering to structured methods, teams can enhance efficiency, ensure alignment, and consistently deliver value, empowering them to be proactive and adaptable in problem-solving, ultimately leading to improved performance and outcomes. Methods are flexible and can be tailored to fit the unique context of a team or project, allowing for continuous refinement while maintaining a clear path toward goal achievement. https://engineering-leadership.hinshelwood.com/concepts/observability/ Wed, 09 Apr 2025 14:00:00 +0100 https://engineering-leadership.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.hinshelwood.com/concepts/practice/ Wed, 09 Apr 2025 14:00:00 +0100 https://engineering-leadership.hinshelwood.com/concepts/practice/ Practice refers to the consistent and repeatable techniques or habits that teams employ to improve their effectiveness, collaboration, and value delivery. Originating from Agile, Lean, and DevOps methodologies, practices such as Pair Programming, Continuous Deployment, and Retrospectives are integral to fostering ongoing, systematic routines that enhance team dynamics and performance. Unlike structured methods, which provide defined steps, practices focus on the habitual actions that teams incorporate into their workflows. For instance, Pair Programming not only boosts code quality but also promotes knowledge sharing, while Retrospectives allow teams to reflect on their processes and identify areas for improvement, thus supporting continuous enhancement. Although tools like Kanban boards can facilitate these practices, the essence lies in how teams manage their workflows and adapt their routines to evolving challenges. The long-term value of practices is evident in their ability to embed behaviours that lead to predictable and sustainable outcomes, such as the frequent and reliable software releases enabled by Continuous Deployment. Ultimately, practices are crucial for effective teamwork, as they shape collaboration, drive continuous improvement, and ensure responsiveness to both internal and external demands, making them essential in the fast-paced environments characteristic of modern product development and organisational design. https://engineering-leadership.hinshelwood.com/concepts/tool/ Wed, 09 Apr 2025 14:00:00 +0100 https://engineering-leadership.hinshelwood.com/concepts/tool/ A tool is a mechanism, technique, or software that assists teams in effectively implementing methods and practices within Agile, Lean, and DevOps environments. These tools are crucial for supporting collaboration, managing workflows, and fostering continuous improvement, as they enable teams to visualise and track progress, manage backlogs, and align with product goals. For instance, project management tools like JIRA and Azure Boards facilitate Agile practices by allowing teams to iterate and adapt to feedback. In DevOps, tools such as Jenkins and GitLab automate processes like Continuous Integration and Continuous Delivery, enhancing delivery speed and reliability while reducing human error. However, tools are not standalone solutions; they must be integrated into a broader organisational framework and aligned with defined methodologies. While they can enhance efficiency and provide visibility into workflows, tools cannot address organisational dysfunctions or improve processes without a solid methodological foundation. Therefore, tools should be viewed as enablers that support well-defined practices rather than replacements for strong methods or frameworks. Ultimately, the effective use of tools can significantly improve team performance and adaptability in complex environments, making them valuable assets in product development and organisational design. https://engineering-leadership.hinshelwood.com/tags/system-configuration/ Wed, 09 Apr 2025 13:08:13 +0100 https://engineering-leadership.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.hinshelwood.com/tags/test-first-development/ Tue, 25 Mar 2025 07:40:33 +0000 https://engineering-leadership.hinshelwood.com/tags/test-first-development/ Test First Development is a contemporary engineering practice that emphasises the importance of defining success criteria before the actual implementation of software begins. Originating from the need for clarity and quality in software delivery, this approach involves establishing tests, whether through examples, specifications, or executable tests, prior to coding. This shift-left strategy enhances collaboration among developers, testers, designers, and product owners by ensuring a shared understanding of what constitutes a successful outcome. Test First encompasses both manual and automated validation methods, with a preference for automation due to its ability to facilitate rapid feedback, support continuous integration, and mitigate regression risks. While manual testing serves a role in exploratory validation, automated practices like Test-Driven Development (TDD) and Acceptance Test-Driven Development (ATDD) are more effective in driving design and exposing ambiguities. Importantly, Test First transcends traditional testing; it is fundamentally a design, collaboration, and feedback practice that streamlines workflows by aligning expectations early and grounding development efforts in actual customer needs. By adopting Test First, teams can significantly reduce rework and enhance the overall quality of their software products, making it a valuable methodology in agile, DevOps, and product development contexts. https://engineering-leadership.hinshelwood.com/tags/scrum-master/ Tue, 25 Mar 2025 07:35:53 +0000 https://engineering-leadership.hinshelwood.com/tags/scrum-master/ The Scrum Master is an accountability within Scrum, serving as a change agent who enables team effectiveness and organizational transformation. Far from a passive facilitator, they are accountable for creating conditions where delivery becomes inevitable through technical, business, and organizational mastery. They teach, coach, mentor, and facilitate while ensuring teams consistently deliver valuable increments every Sprint. https://engineering-leadership.hinshelwood.com/tags/common-goals/ Fri, 21 Mar 2025 14:45:01 +0000 https://engineering-leadership.hinshelwood.com/tags/common-goals/ Common Goals are a foundational principle for effective delivery within organisations, serving to align strategy with execution and ensuring that every decision, Sprint, and line of code contributes to a shared purpose. These goals are not mere aspirational statements; they represent the strategic objectives that unify efforts and connect individual contributions to meaningful outcomes. In the context of agile, DevOps, and product development, understanding and committing to common goals fosters ownership, clarity, and accountability among team members, enabling distributed decision-making and reducing friction in prioritisation. This alignment is crucial for creating adaptive and high-performing systems, as it allows teams to surface misalignments early and make informed trade-offs without waiting for permission. Furthermore, the integration of tactical commitments, such as Product Goals and Sprint Goals, ensures that strategic intent is operationalised at every level of delivery. By maintaining a focus on measurable outcomes and desired impacts, organisations can avoid the pitfalls of busywork and ensure that their efforts are directed towards achieving significant results. Ultimately, common goals provide the necessary framework for teams to understand their role in the larger organisational context, making it imperative for leaders to establish and communicate these objectives clearly. https://engineering-leadership.hinshelwood.com/tags/evidence-based-management/ Fri, 21 Mar 2025 14:44:46 +0000 https://engineering-leadership.hinshelwood.com/tags/evidence-based-management/ Evidence-Based Management (EBM) is a strategic approach designed to enhance organisational agility by providing a framework for assessing and improving value delivery. Unlike traditional frameworks or methodologies, EBM focuses on empirical data to inform decision-making, enabling organisations to move beyond superficial metrics and truly understand their performance. It centres on four critical areas: Current Value, which evaluates immediate value delivery; Time to Market, which measures responsiveness and speed; Ability to Innovate, which assesses the capacity for creating new value amidst existing challenges; and Unrealised Value, which identifies potential opportunities for growth. By utilising these metrics, leaders can make informed decisions about resource allocation and prioritisation, ultimately fostering a culture of continuous improvement. EBM is particularly valuable in the contexts of agile, DevOps, and product development, as it encourages a shift from output-focused practices to outcome-driven strategies. This empirical approach not only clarifies organisational goals but also provides the necessary feedback to adapt and evolve, ensuring that efforts are aligned with delivering real value rather than merely maintaining the status quo. In a landscape where many organisations struggle with agility, EBM offers a practical solution for those seeking to enhance their effectiveness and responsiveness in a complex and dynamic environment. https://engineering-leadership.hinshelwood.com/concepts/artifact/ Fri, 21 Mar 2025 13:59:46 +0000 https://engineering-leadership.hinshelwood.com/concepts/artifact/ An artifact is a formal, inspectable output that signifies work and progress within a delivery system, particularly in Agile, Lean, and DevOps methodologies. These artifacts, which include the Product Backlog, Sprint Backlog, and Increment in Scrum, are essential for fostering a shared understanding among teams and stakeholders regarding the status of work, what has been completed, and what remains to be done. They are not merely tools or documents; rather, they are defined constructs that promote transparency, inspection, and adaptation. Artifacts play a crucial role in empirical decision-making by allowing teams to assess the current state of work, identify potential risks, and adjust their strategies accordingly. In Kanban and DevOps, similar constructs such as visual work boards and deployment pipelines serve as artifacts that reveal delivery progress and system behaviour. By actively facilitating delivery governance, artifacts enhance alignment, support evidence-based forecasting, and build trust between stakeholders and teams through the visibility of progress and value delivery. Their effective use is vital for successful product development and organisational design, as they contribute to a culture of continuous improvement and responsiveness to change. https://engineering-leadership.hinshelwood.com/tags/continuous-delivery/ Fri, 21 Mar 2025 13:37:32 +0000 https://engineering-leadership.hinshelwood.com/tags/continuous-delivery/ Continuous Delivery is a software delivery practice that focuses on producing software in short, reliable cycles, enabling teams to release updates at any time. Originating from the need for more efficient and responsive software development processes, it involves delivering small, incremental improvements directly to users from the initial stages of development. This approach, as defined by Jez Humble, emphasises the ability to safely and quickly implement changes, such as new features, configuration adjustments, and bug fixes, into production. The importance of Continuous Delivery lies in its capacity to facilitate rapid validation of assumptions and collection of user feedback, which are crucial for refining products and achieving valuable outcomes. By automating essential processes like testing, integration, and deployment, Continuous Delivery not only mitigates the risk of errors but also enhances software quality and accelerates the time it takes to deliver value to users. Teams that adopt this practice can more effectively respond to market demands and stakeholder input, thereby fostering a culture of continuous learning, innovation, and adaptability within their organisations. https://engineering-leadership.hinshelwood.com/tags/continuous-improvement/ Fri, 21 Mar 2025 13:28:30 +0000 https://engineering-leadership.hinshelwood.com/tags/continuous-improvement/ Continuous Improvement is a fundamental principle of Business Agility, crucial for organisations aiming to achieve resilience and sustainable success in dynamic and complex markets. It involves a continuous commitment to reflecting on outcomes, evaluating performance through empirical evidence, and adapting strategies based on insights gained. This principle is not a one-off initiative but rather an integral part of an organisation’s culture, guiding teams and leaders towards more effective and responsive ways of working. Continuous Improvement enhances an organisation’s ability to swiftly respond to market changes and customer demands, fostering a proactive approach to experimentation and data-driven decision-making. In Lean methodologies, Continuous Improvement is central to the philosophy of “Kaizen,” which promotes small, incremental enhancements and engages all team members in the improvement process. In Scrum, it is embedded through structured cycles of transparency, inspection, and adaptation, particularly during Sprint Retrospectives, which facilitate reflection and collaborative learning. Kanban drives Continuous Improvement through visualisation and workflow optimisation, encouraging teams to identify and address bottlenecks while making incremental adjustments. By embedding Continuous Improvement into their core practices, organisations can leverage change as a competitive advantage, consistently driving innovation and delivering greater value. https://engineering-leadership.hinshelwood.com/tags/agile-product-operating-model/ Fri, 21 Mar 2025 09:30:34 +0000 https://engineering-leadership.hinshelwood.com/tags/agile-product-operating-model/ The Agile Product Operating Model (APOM) is an operating model that integrates agile methodologies with contemporary product management principles, enabling organisations to consistently deliver value through a product-centric approach. As a specialization of the Adaptive Operating Model, APOM addresses the specific need to shift away from traditional project-based approaches, which often emphasise rigid timelines and budgets, toward continuous value delivery and responsiveness to customer feedback. This model is crucial in the context of agile, DevOps, and product development as it aligns organisational efforts around well-defined outcomes, ensuring that every product has clear boundaries, stakeholders, and measurable value. By integrating elements such as business and technology roadmaps, operational stability, and governance, APOM allows organisations to adapt swiftly to market changes while maintaining a clear connection to their strategic goals. Furthermore, it emphasises evidence-based decision-making, fostering transparency and collaboration across teams, which enhances the ability to manage and optimise product value effectively. While non-agile product operating models are possible, APOM provides the recommended approach that empowers organisations to shape their unique operating models, driving sustainable value creation in a dynamic environment. https://engineering-leadership.hinshelwood.com/categories/devops/ Thu, 20 Mar 2025 11:04:38 +0000 https://engineering-leadership.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.hinshelwood.com/tags/shift-left-strategy/ Mon, 17 Mar 2025 14:46:11 +0000 https://engineering-leadership.hinshelwood.com/tags/shift-left-strategy/ The Shift-Left Strategy is a proactive approach in modern software development that emphasises the integration of testing, security, and compliance activities early in the development lifecycle, rather than deferring them to the end. Originating from the need to mitigate risks associated with late-stage defect detection, this strategy allows teams to identify and address issues sooner, thereby reducing the amount of rework required and accelerating feedback loops. By implementing practices such as automated testing, security as code, and continuous integration, organisations can enhance software quality and reliability from the outset. This approach is particularly valuable in agile and DevOps environments, where rapid delivery and high performance are critical. Ultimately, the Shift-Left Strategy fosters a culture of quality and efficiency, ensuring that products are not only delivered faster but also meet the necessary standards for security and compliance, making it an essential component of effective organisational design and product development. https://engineering-leadership.hinshelwood.com/tags/internal-developer-platform/ Mon, 24 Feb 2025 13:04:45 +0000 https://engineering-leadership.hinshelwood.com/tags/internal-developer-platform/ An Internal Developer Platform (IDP) is a unified environment designed to enhance the development lifecycle by enabling teams to efficiently build, test, and deploy applications. Originating from the need to simplify infrastructure management and application dependencies, an IDP allows developers to concentrate on delivering value rather than dealing with operational challenges. This platform cultivates a collaborative and innovative culture, empowering teams to experiment and iterate quickly within a structured framework. By embedding best practices into the development process, an IDP promotes reliability and predictability in software delivery. It also facilitates continuous integration and continuous delivery (CI/CD) practices, which are vital for maintaining competitiveness in rapidly evolving markets. By automating repetitive tasks and standardising workflows, an IDP boosts productivity and shortens lead times, enabling organisations to swiftly adapt to changing customer demands. Ultimately, the long-term advantages of an Internal Developer Platform lie in its capacity to foster a sustainable development ecosystem that aligns with organisational objectives, thereby driving innovation and operational excellence. This alignment is essential for nurturing a resilient and adaptive organisational culture focused on continuous improvement and value delivery. https://engineering-leadership.hinshelwood.com/tags/acceptance-test-driven-development/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/acceptance-test-driven-development/ Acceptance Test Driven Development (ATDD) is a collaborative methodology that prioritises the establishment of clear, testable acceptance criteria prior to feature implementation. Originating from the need for alignment among stakeholders, such as product owners, developers, and testers, ATDD ensures a shared understanding of success metrics for features, thereby minimising miscommunication and the potential for rework. This approach enhances the predictability and sustainability of value delivery by integrating quality assurance early in the development process, promoting a shift-left mindset that allows teams to identify and resolve issues proactively. The emphasis on early testing not only improves software quality but also nurtures a culture of collaboration and shared accountability within teams. Furthermore, the long-term advantages of ATDD extend beyond immediate project results; it fosters a systematic working method that encourages continuous improvement and adaptability to evolving requirements. By consistently implementing ATDD, organisations can enhance their agility and efficiency in delivering higher value to customers, making it a fundamental practice that reinforces the overall development process and keeps teams focused on what is essential for the business and its users. https://engineering-leadership.hinshelwood.com/tags/agile-frameworks/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/agile-frameworks/ Agile frameworks are structured methodologies designed to implement Agile principles within organisations, allowing teams to deliver value in a predictable and sustainable manner. Originating from the need for more flexible and responsive approaches to project management, frameworks such as Scrum, Kanban, and Lean provide defined roles, events, and artefacts that enhance collaboration, transparency, and continuous improvement among team members. The importance of these frameworks lies in their ability to help organisations adapt to changing market demands and customer needs, thereby maintaining competitiveness and relevance. By fostering a culture of experimentation and learning, Agile frameworks enable teams to iterate on processes and products, identify inefficiencies, and optimise workflows, which ultimately enhances value delivery. Additionally, they promote cross-functional collaboration, breaking down silos and leveraging diverse skill sets towards common objectives. This holistic approach not only improves team dynamics but also aligns organisational goals with customer satisfaction, leading to better outcomes. By integrating Agile frameworks into their operations, organisations can create an environment that prioritises responsiveness and innovation, equipping them to navigate the complexities of modern product development and market dynamics. The emphasis on continuous delivery and improvement cultivates resilience, empowering teams to thrive in an ever-evolving landscape. https://engineering-leadership.hinshelwood.com/tags/agile-planning/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/agile-planning/ Agile Planning is a strategic methodology that enables teams to effectively balance flexibility and predictability, allowing them to adapt to evolving requirements while consistently delivering value. Originating from Agile frameworks, this approach involves setting clear objectives, prioritising tasks, and aligning team efforts to optimise delivery. Its significance lies in fostering collaboration and transparency, which empowers teams to respond quickly to feedback and market changes. By implementing Agile Planning, organisations can establish a structured yet adaptable framework that promotes continuous improvement and value delivery. This process encourages teams to decompose work into manageable increments, facilitating regular reassessment and adjustment of priorities based on real-time insights. Such an iterative approach not only boosts team motivation and engagement but also cultivates a culture of accountability and ownership. Agile Planning transcends mere task scheduling; it represents a long-term, systemic strategy that integrates with various Agile practices, enabling teams to make informed decisions, manage dependencies effectively, and maintain a strong focus on customer needs. Ultimately, this alignment contributes to sustainable delivery and provides a competitive advantage in fast-paced markets, underscoring the critical role of Agile Planning in contemporary product development. https://engineering-leadership.hinshelwood.com/tags/agile-planning-tools/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/agile-planning-tools/ Agile Planning Tools are vital resources that support effective backlog management, forecasting, and collaboration within Agile teams. Originating from the principles of Agile methodology, these tools enable teams to visualise their work, prioritise tasks, and monitor progress in real-time, ensuring alignment and focus on delivering value. Their importance lies in enhancing predictability and sustainability in value delivery, allowing teams to make informed decisions based on empirical data, which fosters a culture of continuous improvement and adaptability in dynamic environments. By providing a structured approach to planning, Agile Planning Tools help teams anticipate challenges and respond to changing requirements, streamlining workflows and promoting a collaborative atmosphere. Unlike Agile Project Management or Agile Product Management, which target specific project execution or product lifecycle aspects, these tools form the foundational layer that underpins all Agile practices. They facilitate not just task management but also the creation of an environment conducive to team innovation and customer satisfaction through effective planning and execution. Integrating Agile Planning Tools into daily operations enhances organisational agility and resilience, ultimately leading to improved outcomes and sustained success. https://engineering-leadership.hinshelwood.com/categories/artificial-intelligence/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/categories/artificial-intelligence/ Artificial Intelligence (AI) is the capability of machines to perform tasks that typically require human intelligence, such as learning, reasoning, and problem-solving. In organisational settings, AI enhances decision-making by providing data-driven insights, automating repetitive tasks, and fostering innovation. This is particularly important in Agile, DevOps, and modern product development, as it enables teams to respond quickly to changing market demands and customer needs. By streamlining workflows, optimising resource allocation, and improving forecasting accuracy, AI allows organisations to deliver value predictably and sustainably. Integrating AI into practices not only supports immediate project goals but also promotes a culture of continuous improvement and learning. The long-term advantages of AI include the ability to adapt to complex environments and make informed decisions based on real-time data analysis, empowering teams to concentrate on high-value activities. This ultimately leads to better products and services that align with customer expectations. Furthermore, AI plays a crucial role in enhancing collaboration and team performance, aligning with Agile and Lean methodologies, and driving organisations towards greater agility and resilience in a rapidly evolving landscape. https://engineering-leadership.hinshelwood.com/tags/asynchronous-development/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/asynchronous-development/ Asynchronous Development is a collaborative approach that enables team members to work independently and at different times, rather than depending on real-time interactions. This method is particularly advantageous for distributed teams, as it accommodates diverse time zones and personal schedules, facilitating continuous progress without the limitations of synchronous communication. By utilising tools and practices that support asynchronous workflows, teams can improve their efficiency and flexibility, leading to more predictable and sustainable value delivery. This concept is vital in contemporary product development, where rapid adaptation and responsiveness are essential. Asynchronous Development creates an environment where team members can contribute insights and work at their own pace, minimising bottlenecks caused by waiting for others. It fosters a culture of ownership and accountability, encouraging individuals to take responsibility for their tasks while remaining aligned with team objectives. Additionally, this approach aligns with Lean and Agile principles, promoting continuous improvement and learning. By allowing teams to operate asynchronously, organisations can better manage complexity and enhance collaboration, ensuring consistent value delivery to customers without the friction of traditional synchronous methods. This systemic shift not only boosts productivity but also nurtures a more engaged and motivated workforce, ultimately driving long-term success and innovation. https://engineering-leadership.hinshelwood.com/tags/automated-testing/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/automated-testing/ Automated Testing is a vital practice in software development that utilises automation tools to execute tests systematically, thereby enhancing the quality and reliability of software products. Originating from the need to streamline the testing process, this approach allows development teams to identify and address issues early, significantly minimising manual testing efforts and expediting the delivery of high-quality software. The significance of Automated Testing lies in its capacity to facilitate predictable and sustainable value delivery, fostering a culture of continuous improvement through shortened feedback loops. This practice aligns with Agile and DevOps principles by promoting a shift-left strategy, which encourages earlier testing in the development cycle, enhancing collaboration among cross-functional teams. Furthermore, Automated Testing serves as a long-term enabler of organisational agility, embedding quality assurance within the development workflow. This integration leads to increased throughput and a sustained focus on customer value, ultimately resulting in improved customer satisfaction and retention. By adopting this proactive approach, organisations empower their teams to innovate and adapt, ensuring competitiveness in a fast-paced market environment. https://engineering-leadership.hinshelwood.com/tags/azure-boards/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/azure-boards/ Azure Boards is an integral component of the Azure DevOps suite, specifically designed to enhance the management of Agile projects. It provides teams with tools to track work items, manage backlogs, and optimise planning through visual boards that accommodate methodologies such as Scrum and Kanban. By offering a comprehensive view of tasks, progress, and team capacity, Azure Boards promotes collaboration and communication, ensuring that all team members are aligned on priorities and deliverables. Its importance lies in fostering transparency and accountability within teams, enabling them to deliver value in a predictable and sustainable manner. The tool supports continuous improvement by allowing teams to analyse workflows, identify bottlenecks, and adapt processes based on real-time data, which streamlines project management and enhances responsiveness to changing requirements and customer feedback. Unlike other tools that may focus solely on task management, Azure Boards integrates seamlessly with other Azure DevOps services, creating a unified environment for development, testing, and deployment. This integration is vital for maintaining a consistent workflow and ensuring that all facets of product development are interconnected, ultimately leading to improved outcomes and greater organisational agility. The long-term advantages of adopting Azure Boards extend beyond immediate project needs, as it fosters a culture of continuous delivery and improvement, reinforcing the principles of Agile and Lean methodologies across the organisation. https://engineering-leadership.hinshelwood.com/tags/azure-pipelines/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/azure-pipelines/ Azure Pipelines is a cloud-based service designed to automate the processes of building, testing, and deploying applications, thereby enabling teams to deliver value in a predictable and sustainable manner. Originating from the need for efficient software development practices, it integrates seamlessly with various version control systems to facilitate continuous integration and continuous delivery (CI/CD). This capability allows teams to implement code changes frequently and reliably, significantly reducing manual errors and accelerating feedback loops while enhancing collaboration among cross-functional teams. The importance of Azure Pipelines lies in its ability to streamline workflows and improve overall efficiency throughout the software development lifecycle, supporting a diverse array of programming languages and platforms to meet varied project needs. By offering a consistent framework for managing builds and releases, it promotes a culture of continuous improvement and innovation. Furthermore, its integration with Azure DevOps tools, such as Azure Boards and Azure Repos, fosters a cohesive project management environment that enhances visibility into the development process and aligns teams towards shared objectives. This systemic approach ultimately drives organisational agility and resilience, with long-term benefits including increased deployment frequency, reduced lead times, and a heightened focus on delivering high-quality software that aligns with customer requirements. https://engineering-leadership.hinshelwood.com/tags/backlog-refinement/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/backlog-refinement/ Backlog Refinement is a fundamental practice within Agile methodologies that focuses on ensuring the product backlog is clearly defined, prioritised, and prepared for execution. Originating from the need for effective collaboration between product owners and development teams, this ongoing process involves clarifying requirements, estimating effort, and adjusting priorities based on evolving insights and stakeholder feedback. The importance of Backlog Refinement lies in its ability to enhance focus and alignment on delivering value, thereby enabling teams to deliver outcomes predictably and sustainably. By regularly refining the backlog, teams can reduce risks associated with ambiguity and miscommunication, facilitating smoother sprint planning and execution. This practice promotes a culture of continuous improvement, allowing teams to adapt to changing circumstances and customer needs while maintaining momentum. Additionally, it supports long-term planning by prioritising the most valuable items, optimising resource allocation, and enhancing overall productivity. By integrating Backlog Refinement into their workflows, organisations can foster a more responsive and agile environment, leading to improved product outcomes and greater stakeholder satisfaction. This systemic approach not only streamlines the development process but also encourages a proactive mindset among team members, empowering them to take ownership of their work and align with the organisation’s strategic objectives. https://engineering-leadership.hinshelwood.com/tags/coaching/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/coaching/ Coaching is a practice aimed at unlocking the potential of teams and leaders through guidance rather than directives, fostering an environment conducive to skill development, enhanced decision-making, and a mindset of continuous improvement. Originating from methodologies in agile, lean, and DevOps, coaching is vital for empowering teams to adapt to changing circumstances and deliver value in a predictable and sustainable manner. By prioritising the long-term development of individuals and teams, coaching cultivates a culture of learning and experimentation, promoting self-organisation and accountability that enables collaborative problem-solving. This systemic approach not only improves team performance but also aligns with organisational goals, ensuring that product and service delivery effectively meets customer needs. Unlike mentoring, which often involves knowledge transfer, coaching emphasises the coachee’s self-discovery and growth, focusing on asking the right questions to facilitate insights and actionable outcomes. This distinction is essential for building resilience and adaptability, traits that are increasingly important in fast-paced development environments. Additionally, by fostering psychological safety, coaching encourages open communication and trust, which are critical components of high-performing teams. https://engineering-leadership.hinshelwood.com/tags/continuous-integration/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/continuous-integration/ Continuous Integration (CI) is a software development practice that focuses on the frequent merging of code changes into a shared repository, facilitating early detection of errors and prompt resolution of integration issues. Originating from the need for more efficient collaboration in software teams, CI automates the build and testing processes, allowing developers to concentrate on delivering value rather than troubleshooting. Its importance lies in fostering a culture of continuous improvement and collaboration, enabling teams to iterate quickly and adapt to evolving requirements. By promoting regular communication and feedback, CI helps maintain a consistent development pace, resulting in more predictable and sustainable feature delivery. Additionally, CI significantly reduces technical debt by encouraging developers to address issues as they arise, which not only enhances code quality but also boosts team morale through a smoother workflow. Ultimately, CI serves as a foundational element that empowers teams to innovate and effectively respond to customer needs, contributing to long-term success in product development. https://engineering-leadership.hinshelwood.com/tags/cross-functional-teams/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/cross-functional-teams/ Cross Functional Teams are essential components in Agile, Lean, and DevOps frameworks, designed to deliver comprehensive value throughout the project lifecycle, from initial conception to final delivery. These teams consist of individuals with varied skills and expertise, enabling them to independently manage all project facets without external dependencies. This integrated approach enhances collaboration and communication, facilitating quicker decision-making and responsiveness to evolving requirements and customer feedback. The importance of Cross Functional Teams lies in their capacity to establish a sustainable workflow focused on value delivery by merging different disciplines, such as development, testing, design, and operations, thereby streamlining processes, minimising handoffs, and reducing bottlenecks. This not only boosts efficiency but also improves product quality, as team members collaborate closely to align on objectives. Additionally, the systemic nature of these teams fosters a culture of continuous improvement and knowledge sharing, creating an environment conducive to innovation. This collaborative ethos is vital for organisations seeking to maintain a competitive advantage in fast-changing markets, empowering teams to experiment and adapt based on real-time insights. Ultimately, the long-term advantages of Cross Functional Teams extend beyond immediate project results, contributing to a resilient organisational culture that embraces change and values collective expertise. https://engineering-leadership.hinshelwood.com/tags/cycle-time/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.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.hinshelwood.com/tags/daily-scrum/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/daily-scrum/ The Daily Scrum is a fundamental practice within the Scrum framework that aims to improve team alignment and adaptability. Originating from agile methodologies, this brief, time-constrained meeting, usually lasting 15 minutes, provides an opportunity for team members to synchronise their activities, review progress towards the Sprint Goal, and adjust their plans as necessary. During the meeting, participants discuss their accomplishments since the last session, outline their next steps, and highlight any obstacles they are encountering. This structured yet adaptable format promotes transparency and accountability, allowing teams to respond effectively to changes and challenges. By fostering regular communication, the Daily Scrum helps maintain a focus on delivering value and ensures that the team remains aligned with the Sprint’s overall objectives. It also encourages a culture of continuous improvement, enabling team members to swiftly identify and resolve issues that may impede progress. Beyond addressing immediate project needs, the Daily Scrum nurtures long-term habits of collaboration and self-organisation, which are crucial for sustainable success in agile environments. Ultimately, the Daily Scrum serves as a powerful facilitator of team dynamics and performance, driving collective efforts towards shared goals and enhancing overall productivity. https://engineering-leadership.hinshelwood.com/tags/definition-of-ready/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/definition-of-ready/ Definition of Ready (DoR) is a concept within the Scrum framework that outlines the criteria necessary for a Backlog Item to be considered ready for implementation by the development team. It emerges from the collaborative understanding among Developers, the Product Owner, and Stakeholders regarding what is required to proceed with a Backlog Item. The importance of DoR lies in its potential to enhance clarity and alignment within agile teams, yet it also presents challenges, such as creating a false sense of readiness, neglecting the need for ongoing refinement, and leading to misconceptions about its equivalence with the Definition of Done (DoD). Unlike the DoD, which is an absolute measure of completion, the subjective nature of DoR can result in partial implementation, risking the integrity of the development process. To mitigate these issues, it is suggested that teams adopt a more nuanced approach to defining readiness, ensuring that each Backlog Item meets specific criteria, such as having a clear outcome, hypothesis, and telemetry for evaluation. The INVEST criteria further guide the formulation of Product Backlog Items, emphasising their independence, negotiability, value, estimability, size, and testability. Ultimately, a well-defined DoR fosters effective communication and understanding within agile teams, contributing to successful product development and organisational design. https://engineering-leadership.hinshelwood.com/tags/deployment-frequency/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.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.hinshelwood.com/tags/deployment-strategies/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/deployment-strategies/ Deployment strategies are systematic approaches that organisations utilise to release software into production, balancing the need for speed with risk management. These strategies are essential for enabling teams to deliver value in a predictable and sustainable manner, facilitating rapid iterations and continuous feedback. Techniques such as blue-green deployments, canary releases, and rolling updates help mitigate the impact of potential failures, allowing teams to address issues swiftly without causing significant disruption to users. The effectiveness of deployment strategies lies in their capacity to cultivate a culture of experimentation and learning, encouraging continuous improvement where each deployment provides insights for refining processes. This approach enhances operational efficiency and aligns with Agile and DevOps principles, fostering collaboration and shared responsibility among cross-functional teams. Furthermore, well-defined deployment strategies contribute to a resilient organisational structure, enabling teams to adapt to evolving market demands and technological changes. By prioritising safe and efficient releases, organisations can maintain a competitive advantage while ensuring customer satisfaction remains central to their product development efforts. Ultimately, the integration of deployment strategies into the broader organisational framework supports sustainable growth and reinforces the importance of delivering value through strategic software releases. https://engineering-leadership.hinshelwood.com/tags/empirical-process-control/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/empirical-process-control/ Empirical Process Control is a key principle that focuses on making decisions grounded in observation and experimentation rather than assumptions. Originating from methodologies such as Agile, Lean, and DevOps, it empowers teams to refine their processes and outputs through ongoing inspection and transparency. This reliance on real data and feedback enables organisations to discern effective practices from ineffective ones, fostering a culture of continuous learning and improvement. By adopting this approach, teams can deliver value in a predictable and sustainable manner, adjusting their strategies based on actual performance rather than theoretical frameworks. It promotes a mindset of experimentation, where hypotheses are tested in real-world scenarios, leading to informed decisions that enhance product quality and customer satisfaction. Beyond being a tactical tool, Empirical Process Control serves as a long-term enabler of organisational agility, creating an environment where teams can swiftly adapt to changing conditions and remain aligned with customer needs and market dynamics. In today’s fast-paced development landscape, the ability to pivot based on evidence is crucial for success. By integrating empirical practices into their workflows, organisations can cultivate a more resilient and responsive operational model that prioritises value delivery and continuous improvement. https://engineering-leadership.hinshelwood.com/tags/engineering-practices/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/engineering-practices/ Engineering Practices refer to a collection of essential techniques and methodologies aimed at delivering high-quality software within an Agile framework. Originating from the need for reliable and maintainable software, these practices include principles such as clean code, automation, and test-first development, which are integrated into the software development lifecycle to ensure a consistent flow of value to customers. Their importance lies in fostering a culture of technical excellence and continuous improvement, enabling teams to adapt quickly to changing requirements while minimising technical debt, thereby maintaining the software’s robustness over time. This holistic approach enhances collaboration among cross-functional teams and aligns technical initiatives with business goals, promoting overall organisational agility. Additionally, Engineering Practices facilitate the establishment of Continuous Integration and Continuous Delivery pipelines, which optimise the deployment process and shorten lead times. By emphasising quality throughout development, these practices empower teams to innovate with confidence, ensuring that each software release meets customer expectations and contributes to sustained success. The incorporation of these practices into everyday workflows nurtures an environment conducive to learning and experimentation, ultimately boosting team motivation and performance. https://engineering-leadership.hinshelwood.com/tags/estimation/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/estimation/ Estimation is a fundamental practice within Agile and Scrum methodologies that allows teams to predict the effort and time necessary to complete tasks or deliver features. Originating from the need to manage uncertainty in project management, estimation employs empirical data and collaborative techniques to align stakeholder expectations and foster a shared understanding of project scope and timelines. This practice transcends mere numerical assignment; it involves engaging the entire team in discussions that utilise collective knowledge and experience, thereby enhancing both accuracy and team buy-in. Effective estimation is crucial as it enables teams to deliver value in a predictable and sustainable manner, facilitating improved planning and resource allocation. It also supports continuous improvement through a feedback loop that compares past estimates with actual outcomes, refining future forecasting. This iterative process promotes a culture of transparency and accountability, which is vital for high-performing teams. Unlike broader concepts such as Agile Planning or Backlog Refinement, estimation focuses on the tactical execution of tasks, serving as a foundational element for successful Agile practices. By incorporating estimation into their workflows, organisations can improve their agility and responsiveness in a rapidly changing market, ultimately leading to better outcomes for customers and stakeholders. https://engineering-leadership.hinshelwood.com/tags/experimentation/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/experimentation/ Experimentation is a fundamental practice within agile workflows that utilises hypothesis-driven methods to test ideas and validate assumptions. Originating from the need to systematically address uncertainties, this approach enables teams to make informed decisions based on empirical evidence rather than relying solely on intuition. The importance of experimentation is underscored by its ability to facilitate predictable and sustainable value delivery, fostering a culture where failure is perceived as a learning opportunity that drives continuous improvement and resilience. Through iterative testing and feedback loops, teams can refine their products and processes, ensuring they align with customer needs and organisational objectives. Furthermore, experimentation promotes long-term systemic change by integrating a scientific mindset into the organisational culture, enhancing collaboration among cross-functional teams and boosting engagement as team members witness the direct impact of their efforts. By prioritising experimentation, organisations can create an environment that values learning and adaptability, which is essential for effective and innovative product development in today’s complex and rapidly changing landscape. This practice serves not just as a tactic but as a foundational element that influences how teams operate and evolve. https://engineering-leadership.hinshelwood.com/tags/forecasting/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.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.hinshelwood.com/tags/frequent-releases/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.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.hinshelwood.com/tags/lean-principles/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/lean-principles/ Lean Principles are a methodology aimed at minimising waste and maximising value through iterative learning and continuous improvement, primarily used in product development processes. Originating from manufacturing practices, these principles are now widely adopted across various sectors to enhance organisational efficiency and responsiveness. The importance of Lean Principles lies in their ability to foster a culture of experimentation and feedback, enabling teams to identify and eliminate non-value-adding activities, streamline workflows, and optimise resource utilisation. By focusing on value delivery, Lean ensures that all actions align with customer needs, promoting sustainable product development. Techniques such as value stream mapping are employed to visualise the flow of information and materials, helping to identify bottlenecks and areas for improvement. This comprehensive approach not only enhances current processes but also establishes a foundation for long-term agility and adaptability. Unlike Agile frameworks that may concentrate on iterative cycles, Lean Principles advocate for a holistic perspective, integrating insights from various methodologies to create a cohesive strategy for continuous improvement. This enables organisations to effectively respond to changing market demands while maintaining a commitment to delivering high-quality products that meet customer expectations. By embedding Lean thinking into the organisational culture, teams can foster an environment of ongoing learning and innovation, ultimately driving sustained success and resilience in a competitive landscape. https://engineering-leadership.hinshelwood.com/tags/lean-product-development/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/lean-product-development/ Lean Product Development is a methodology that centres on minimising waste and maximising learning throughout the product creation process, drawing from Lean principles that prioritise efficiency and value delivery by eliminating non-value-adding activities. This approach is utilised to foster a culture of continuous improvement, enabling teams to swiftly adapt to changing market demands and customer feedback, thereby ensuring the development of relevant and high-quality products. By empowering cross-functional teams to collaborate effectively and employing tools like Kanban to visualise workflows and identify bottlenecks, Lean Product Development promotes iterative cycles of experimentation that allow for the validation of assumptions and necessary pivots. This is particularly vital in today’s fast-paced environment, where responsiveness is key. The focus on systemic thinking aligns all aspects of product development with organisational goals, encouraging a sustainable approach to innovation. By integrating Lean practices, organisations can enhance their capacity to deliver value predictably, cultivating a culture that values learning and adaptability over rigid processes. This long-term emphasis on efficiency and responsiveness equips teams to excel in a competitive landscape, ultimately leading to improved outcomes for both the organisation and its customers. https://engineering-leadership.hinshelwood.com/tags/lean-thinking/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/lean-thinking/ Lean Thinking is a methodology aimed at maximising value by minimising waste within organisational processes, originating from manufacturing practices and now widely applied across various sectors. It focuses on understanding customer needs and aligning workflows to efficiently deliver products and services that meet those needs. The importance of Lean Thinking lies in its ability to foster a culture of continuous improvement, where teams are encouraged to identify non-value-adding activities, streamline operations, and enhance productivity. This approach is not solely about cost reduction; rather, it aims to create sustainable systems that support long-term value delivery. By adopting Lean principles, organisations can respond more swiftly to changing market demands while ensuring high quality and customer satisfaction. Furthermore, integrating Lean practices leads to greater predictability in delivery cycles, reduced lead times, and improved collaboration among cross-functional teams. This systemic approach empowers individuals at all levels to engage in process enhancements, cultivating a sense of ownership that drives innovation and resilience. Ultimately, Lean Thinking transforms organisational operations, enabling them to remain competitive and responsive in a rapidly evolving landscape. https://engineering-leadership.hinshelwood.com/tags/operational-practices/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/operational-practices/ Operational Practices refer to the techniques and strategies that organisations implement to improve their operational efficiency and delivery capabilities. Originating from methodologies such as Lean, Agile, and DevOps, these practices are utilised to streamline workflows, minimise waste, and optimise resource allocation. Their importance lies in fostering a culture of continuous improvement, enabling teams to swiftly adapt to changing demands while ensuring high-quality outputs. By establishing clear processes and enhancing collaboration, Operational Practices empower teams to make data-driven decisions, which collectively enhance performance and customer satisfaction. This systemic approach ensures that operational improvements are ingrained within the organisational culture, promoting resilience and adaptability rather than being merely reactive. Furthermore, Operational Practices align team efforts with strategic goals, ensuring that every action contributes to the organisation’s overarching mission. By prioritising these practices, organisations can create an environment conducive to innovation and consistent value delivery, ultimately leading to a more agile and responsive structure capable of navigating the complexities of modern product development and market dynamics. https://engineering-leadership.hinshelwood.com/tags/release-management/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.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.hinshelwood.com/tags/remote-working/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/remote-working/ Remote working is a practice that enables teams to collaborate and deliver value from various locations, moving beyond the constraints of a physical office. This approach has gained prominence in today’s technology-driven landscape, allowing organisations to access a wider talent pool, improve employee satisfaction, and sustain productivity irrespective of geographical limitations. By utilising digital collaboration tools and nurturing a culture of trust and accountability, remote working empowers teams to function effectively, adapting quickly to market changes and customer demands. Its systemic nature fosters sustainable practices through continuous communication and feedback loops, which are crucial for iterative development. This flexibility supports agile methodologies and aligns with lean principles by reducing waste and optimising resource use. Additionally, remote working enhances team members’ sense of ownership, boosting engagement and motivation. As teams embrace this model, they cultivate resilience and agility, equipping them to tackle challenges and seize opportunities in a dynamic environment. Ultimately, the emphasis on delivering value ensures that organisations can thrive in a competitive landscape while promoting innovation and collaboration among dispersed teams. https://engineering-leadership.hinshelwood.com/tags/team-collaboration/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/team-collaboration/ Team collaboration is the practice of enhancing teamwork, communication, and shared ownership among team members to achieve high performance. Originating from the need for effective interaction within teams, it is crucial for enabling organisations to deliver value in a predictable and sustainable manner. By fostering a culture of openness and trust, team collaboration empowers individuals to contribute their ideas and skills, thereby enhancing problem-solving capabilities and accelerating decision-making. This collaborative approach helps break down silos, facilitating the free flow of knowledge and expertise across functions, which in turn improves efficiency and adaptability in response to changing requirements and customer feedback. The long-term advantages of strong collaboration include increased innovation, higher employee engagement, and improved overall performance, aligning teams more closely with organisational goals and customer needs. Furthermore, the use of effective collaboration tools and practices is essential in agile, lean, and DevOps environments, supporting seamless communication and coordination. Ultimately, team collaboration serves as a foundational element that drives continuous improvement and value delivery, making it vital for modern product development and organisational success. https://engineering-leadership.hinshelwood.com/tags/team-performance/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/team-performance/ Team performance is the consistent ability of a team to deliver outcomes through its established system of work, reflecting delivery capability over time as indicated by observable patterns in flow, responsiveness, and quality. This concept originates from the understanding that performance is shaped by the structure and constraints of the operational system, influenced by factors such as team composition, collaboration habits, skill alignment, and clarity of purpose. As a system-level capability, team performance transcends individual or cultural traits, making it crucial for organisations aiming to enhance their agile and DevOps practices. By employing flow metrics, retrospectives, and empirical signals to evaluate performance, organisations can discern whether teams are improving, stagnating, or hindered by external dependencies. High-performing teams demonstrate both consistency and adaptability in their delivery, even amidst change. Enhancing team performance involves a focus on system design, which includes limiting work in progress, refining collaboration patterns, and increasing visibility into obstacles. This systemic approach ensures that improvements are not only effective but also sustainable and repeatable across the organisation, ultimately contributing to more efficient product development and organisational design. https://engineering-leadership.hinshelwood.com/tags/technical-debt/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/technical-debt/ Technical debt is the concept that encapsulates the hidden costs associated with opting for quick, suboptimal solutions in software development rather than investing time in more effective, long-term strategies. It often emerges from factors such as hurried development processes, insufficient documentation, or reliance on outdated technologies. Recognising and managing technical debt is essential for teams striving to deliver consistent and sustainable value, as its accumulation can impede innovation and responsiveness to market changes, ultimately compromising product quality and delivery timelines. Addressing technical debt requires a commitment to refactoring, enhancing code quality, and adopting superior tools and practices, which not only boosts team efficiency but also cultivates a culture of continuous improvement. By systematically tackling technical debt, organisations can sustain a healthy development pace, ensuring competitiveness and responsiveness to customer demands. This strategic focus on technical debt is crucial for fostering organisational agility, as it directly impacts the ability to innovate and adapt in a fast-evolving landscape. https://engineering-leadership.hinshelwood.com/tags/test-automation/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/test-automation/ Test automation is the practice of employing software tools to execute pre-scripted tests on applications prior to their production release. Originating from the need to enhance software quality and expedite feedback loops, this approach allows development teams to automate repetitive testing tasks, thereby enabling them to concentrate on more intricate scenarios that necessitate human insight. The significance of test automation lies in its capacity to provide predictable and sustainable value, facilitating continuous integration and continuous delivery practices. This enables teams to release software updates more frequently and with increased confidence, as automated tests yield immediate feedback on code changes, allowing for swift identification and resolution of defects. Consequently, this reduces the risk of errors in production and promotes collaboration among cross-functional teams by ensuring access to reliable testing results. Furthermore, test automation nurtures a culture of continuous improvement, empowering teams to measure and refine their testing processes over time. By integrating testing into the development lifecycle rather than treating it as a separate phase, organisations can achieve higher quality products and a more resilient development process, equipping teams to respond effectively to evolving market demands and customer requirements. https://engineering-leadership.hinshelwood.com/tags/test-driven-development/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/test-driven-development/ Test Driven Development (TDD) is a software development methodology that prioritises the creation of automated tests prior to writing the actual code. Originating from the need for a structured approach to software design, TDD ensures that development is guided by the requirements specified in the tests, which clarifies the intended functionality of the software. This practice is crucial in the context of Agile and DevOps as it promotes a culture of quality and accountability, allowing teams to deliver consistent and sustainable value. By embedding testing into the development lifecycle from the beginning, TDD significantly reduces the risk of defects and simplifies the process of refactoring, with tests acting as a safety net. The long-term advantages of TDD extend beyond immediate improvements in code quality; it fosters a mindset of continuous improvement and adaptability among team members. This approach aligns seamlessly with Agile principles, enhancing collaboration and responsiveness to change while supporting technical excellence. By focusing on test coverage, teams can confidently introduce new features and enhancements, ensuring that existing functionalities remain intact. Ultimately, TDD not only improves individual projects but also cultivates a culture of reliability and trust within the organisation, leading to better outcomes for stakeholders and customers. https://engineering-leadership.hinshelwood.com/tags/value-stream-mapping/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/value-stream-mapping/ Value Stream Mapping is a visual tool designed to analyse and optimise workflows within an organisation by focusing on the flow of materials and information necessary for delivering a product or service. This method involves mapping each step of the process to identify inefficiencies, bottlenecks, and areas of waste, thereby enabling teams to streamline operations and enhance value delivery. Its importance lies in facilitating predictable and sustainable value delivery, empowering teams to make informed decisions based on empirical data, and allowing for adjustments that improve overall performance. By aligning processes with customer needs, Value Stream Mapping ensures that every step adds value towards the end goal. It is not a one-time exercise but a long-term, systemic practice that promotes ongoing reflection and adaptation, helping teams remain agile in response to changing demands and market conditions. This ultimately leads to improved customer satisfaction and organisational resilience. The insights gained from Value Stream Mapping can drive strategic initiatives and foster a culture of collaboration and shared understanding across cross-functional teams, which is essential for achieving sustained success in modern product development. https://engineering-leadership.hinshelwood.com/tags/working-software/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/working-software/ Working Software is a fundamental artifact in Agile, Scrum, and Lean frameworks, serving as the tangible output of a team’s efforts throughout the development process. It emerges from iterative development cycles and acts as a demonstration of progress and value delivery. In Scrum, working software is the primary success metric for each Sprint, encapsulated in the Increment artifact, which is subject to inspection and adaptation based on stakeholder feedback. The Definition of Done ensures that the software meets established quality criteria, making it valuable and ready for release. The importance of working software lies in its ability to provide a concrete measure of progress, aligning teams and stakeholders around completed work and remaining tasks. It transcends mere code, representing deliverables that address real-world needs and customer expectations, thereby maintaining a focus on value delivery. In agile methodologies, the emphasis on working software fosters continuous feedback and improvement, enabling teams to release increments iteratively and adapt to evolving requirements. This focus enhances collaboration, increases transparency, and drives ongoing improvement within organisations. Ultimately, working software is not solely about technical execution; it is about consistently delivering value, responding to customer needs, and ensuring long-term sustainability, thereby contributing to customer satisfaction, innovation, and overall business success. https://engineering-leadership.hinshelwood.com/tags/application-lifecycle-management/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership.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.hinshelwood.com/tags/azure-devops/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership.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.hinshelwood.com/tags/business-agility/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership.hinshelwood.com/tags/business-agility/ Business Agility is the capacity of an organisation to swiftly adapt to market fluctuations, customer needs, and new opportunities while prioritising value delivery. Originating from the need for organisations to remain competitive in a fast-paced environment, this concept is vital as it enables teams to foster continuous innovation, streamline processes, and improve cross-functional collaboration. Business Agility extends beyond merely implementing Agile methodologies; it involves a comprehensive approach that incorporates principles from Lean, DevOps, and continuous improvement. This integrated perspective allows organisations to optimise workflows, shorten lead times, and boost customer satisfaction. By cultivating a culture that values flexibility, experimentation, and learning, organisations can quickly adjust their strategies based on feedback and data insights. The long-term advantages of embracing Business Agility include enhanced resilience, sustained competitive edge, and consistent delivery of high-quality products and services. By embedding agility into their core operations, organisations can proactively navigate change, drive innovation, and achieve strategic objectives, ultimately leading to greater value creation and organisational success. https://engineering-leadership.hinshelwood.com/tags/flow-efficiency/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership.hinshelwood.com/tags/flow-efficiency/ Flow efficiency is the optimisation of work throughput within a value stream, aimed at minimising waste and reducing bottlenecks. This concept is essential for organisations seeking to deliver value in a predictable and sustainable manner, as it significantly influences the speed at which teams can respond to customer demands and market fluctuations. By examining and enhancing flow efficiency, teams can pinpoint delays and implement targeted improvements that boost overall performance. This methodology is closely aligned with Lean principles, which emphasise the removal of non-value-adding activities. Unlike metrics such as cycle time or lead time that focus on specific durations, flow efficiency offers a comprehensive view of how effectively work progresses through the system, promoting collaboration across various teams and disciplines to ensure seamless operation throughout the value stream. By emphasising flow efficiency, organisations foster a culture of continuous improvement, empowering teams to innovate and experiment. This not only increases productivity but also enhances resilience, allowing teams to adapt to evolving circumstances while consistently delivering value. Ultimately, the focus on flow efficiency nurtures an environment conducive to sustainable practices, leading to long-term success and heightened customer satisfaction. https://engineering-leadership.hinshelwood.com/tags/install-and-configuration/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership.hinshelwood.com/tags/install-and-configuration/ Install and Configuration encompasses the critical processes necessary for setting up and optimising tools, software, and platforms that underpin agile, lean, and DevOps methodologies. Originating from the need to establish efficient operational frameworks, this concept is vital for ensuring that teams have the appropriate systems in place to enhance collaboration, communication, and the continuous delivery of value. By prioritising proper installation and configuration, organisations can significantly reduce disruptions and technical debt, enabling teams to focus on producing high-quality products. This proactive strategy not only facilitates predictable and sustainable value delivery but also supports the creation of well-configured environments that align with team workflows and methodologies. Furthermore, effective practices in installation and configuration lead to long-term systemic improvements, fostering adaptability to changing requirements and promoting continuous innovation. This approach transcends mere technical setup; it reflects a strategic mindset that aligns tools with organisational objectives, ultimately boosting overall performance and agility. The capacity to swiftly adjust systems in response to feedback and evolving needs is a defining characteristic of high-performing teams, enhancing both efficiency and effectiveness in product development. https://engineering-leadership.hinshelwood.com/categories/kanban/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership.hinshelwood.com/categories/kanban/ Kanban is a change management strategy that focuses on improving workflow and value delivery within organisations, rather than being merely a tool or visual board. Originating from Lean principles and systems thinking, Kanban encourages teams to begin with their current processes, fostering an understanding of existing systems to facilitate evolutionary improvements. Unlike prescriptive frameworks that dictate roles or time constraints, Kanban emphasises observability through visualisation of work, limiting work in progress, managing flow, and making policies explicit. This approach helps identify bottlenecks and supports evidence-based enhancements without necessitating major organisational changes. By complementing methodologies like Scrum and DevOps, Kanban enhances transparency and decision-making, allowing teams to adapt their practices over time based on feedback and performance metrics such as lead time and throughput. While often misconceived as merely a visual task management tool, the true strength of Kanban lies in its ability to create a shared understanding of system dynamics, enabling strategic improvements. This empowers teams to deliver value in a predictable, sustainable manner, making Kanban a vital strategy for organisations operating in complex and rapidly changing environments. https://engineering-leadership.hinshelwood.com/categories/lean/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership.hinshelwood.com/categories/lean/ Lean is a strategic methodology focused on maximising value while minimising waste, originating from the principles of the Toyota Production System. It is utilised to enhance organisational efficiency by delivering customer value through streamlined processes and fostering a culture of continuous improvement and respect for individuals. By systematically identifying and eliminating non-value-adding activities, Lean enables teams to optimise workflows, boost productivity, and swiftly adapt to changing market conditions. This approach transcends mere tools, embodying a mindset that prioritises long-term sustainability and systemic transformation. Techniques such as value stream mapping and flow efficiency allow teams to visualise their processes, pinpoint bottlenecks, and improve resource allocation, leading to the reliable delivery of high-quality products and services, which in turn enhances customer satisfaction and loyalty. Lean’s focus on empirical decision-making and iterative learning aligns seamlessly with Agile and DevOps principles, creating a collaborative environment that fosters rapid innovation while maintaining a commitment to value delivery. By promoting a culture of experimentation and feedback, Lean equips organisations to navigate and thrive in a dynamic landscape, ensuring their competitiveness and relevance in the market. https://engineering-leadership.hinshelwood.com/tags/metrics-and-learning/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership.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.hinshelwood.com/tags/one-engineering-system/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership.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.hinshelwood.com/tags/platform-engineering/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership.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.hinshelwood.com/tags/product-delivery/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership.hinshelwood.com/tags/product-delivery/ Product Delivery refers to the comprehensive process of delivering functional software products to customers, integrating various stages such as planning, development, testing, and deployment into a unified workflow. Originating from methodologies like Agile, Lean, and DevOps, this approach is essential for organisations aiming to deliver consistent value in a predictable and sustainable manner, ensuring that products align with customer needs and expectations. By emphasising an end-to-end delivery process, Product Delivery enhances collaboration among cross-functional teams, streamlines workflows, and reduces cycle times. It fosters a culture of continuous improvement and adaptability, driven by feedback loops that allow teams to respond swiftly to customer insights and market changes. This systemic approach not only improves product quality but also establishes a resilient organisational framework conducive to long-term success. Prioritising Product Delivery cultivates an environment where innovation flourishes and team ownership is encouraged, leading to increased employee engagement and satisfaction. Ultimately, this focus on delivering value through a structured process is vital for maintaining competitiveness and responsiveness in a rapidly changing landscape, positioning Product Delivery as a cornerstone of contemporary product development. https://engineering-leadership.hinshelwood.com/tags/value-delivery/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership.hinshelwood.com/tags/value-delivery/ Value Delivery is a systematic approach aimed at providing consistent and meaningful outcomes to customers through iterative and incremental processes. Originating from methodologies such as Lean and Agile, it is used in product development to ensure that efforts are aligned with customer needs, allowing for every release to contribute tangible benefits. This concept is vital as it enables teams to deliver value predictably and sustainably, fostering a culture of continuous improvement and responsiveness to change. By prioritising value delivery, organisations can significantly enhance customer satisfaction and loyalty, as products are more likely to meet expectations. It promotes cross-functional collaboration, encouraging teams to work together to identify and eliminate waste, optimise workflows, and streamline processes. Value Delivery encompasses the entire lifecycle of product development, from initial discovery to delivery and beyond, ensuring that teams can adapt to evolving market demands and customer feedback. This long-term focus ultimately leads to sustained organisational success and resilience in a competitive landscape, as embedding value delivery into the organisational culture creates a robust framework that supports innovation and drives continuous value creation for customers and stakeholders alike. https://engineering-leadership.hinshelwood.com/tags/value-stream-management/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership.hinshelwood.com/tags/value-stream-management/ Value Stream Management is a strategic methodology aimed at improving the flow of value within an organisation by optimising processes, reducing waste, and aligning efforts with customer outcomes. Originating from the need to enhance operational efficiency, it involves mapping the entire value stream from ideation to delivery, enabling teams to identify and address bottlenecks and inefficiencies that impede performance. This approach is vital in the context of agile, DevOps, and product development, as it fosters a culture of continuous improvement and responsiveness to market changes. By promoting collaboration across departments and breaking down silos, Value Stream Management ensures a shared understanding of how work contributes to overarching business goals. It empowers teams to focus on delivering high-quality products that satisfy customer needs while balancing speed and efficiency. Unlike specific Agile frameworks or Lean principles that concentrate on particular practices, Value Stream Management offers a comprehensive perspective on the entire process, ensuring that each step adds value. This long-term, systemic approach not only enhances operational performance but also nurtures an environment conducive to innovation, ultimately leading to greater organisational resilience and adaptability in a fast-changing landscape. https://engineering-leadership.hinshelwood.com/tags/agentic-software-delivery/ Tue, 21 Jan 2025 10:00:00 +0000 https://engineering-leadership.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.