https://engineering-leadership-preview.hinshelwood.com/tags/product-delivery/ Recent content in Product Delivery on Engineering Leadership in AI & Software Hugo en Tue, 16 Jun 2026 17:40:35 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/telling-people-what-to-do-is-not-leadership-it-s-a-failure-of-system-design/ Mon, 04 Aug 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/telling-people-what-to-do-is-not-leadership-it-s-a-failure-of-system-design/ Telling people what to do is not leadership, it is a sign of poor system design that stifles autonomy and slows delivery. Effective leadership means creating systems where teams have clear goals, constraints, and feedback loops so they can self-manage, deliver value, and adapt without micromanagement. Focus on improving your delivery system, set meaningful goals, enable autonomy with clear boundaries, use evidence-based metrics, and empower teams to own outcomes, so you can step back and let professionals do their best work. https://engineering-leadership-preview.hinshelwood.com/articles/stop-building-silos-start-building-systems/ Mon, 07 Jul 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/stop-building-silos-start-building-systems/ Fragmented automation and tool silos slow delivery, increase risk, and create confusion, while a unified engineering system enables speed, safety, and clarity. Standardising on a single platform like Azure Pipelines, with shared processes and guardrails, empowers teams to focus on delivering value instead of managing complexity. To scale effectively, consolidate your toolchain, define clear boundaries, and invest in platform engineering so teams can work autonomously within a reliable system. https://engineering-leadership-preview.hinshelwood.com/articles/don-t-manage-dependencies-remove-them/ Mon, 29 Sep 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/don-t-manage-dependencies-remove-them/ Dependencies are not inevitable but are usually caused by poor system design; instead of managing them, focus on removing them by aligning work, teams, and architecture, making contracts explicit, and clarifying ownership. Only manage the rare dependencies that remain, treating them as design flaws to be fixed, not as normal work. Leadership should prioritise redesigning systems to eliminate dependencies, which leads to faster delivery, fewer defects, and higher team autonomy. https://engineering-leadership-preview.hinshelwood.com/articles/is-agile-really-just-a-mindset/ Mon, 11 Aug 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/is-agile-really-just-a-mindset/ Agile is not just a mindset or set of behaviours; it is a disciplined system of work rooted in engineering excellence, technical leadership, and empirical delivery. True agility requires robust engineering practices like CI/CD, automated testing, and observability, not just ceremonies or coaching. To achieve real Agile outcomes, focus on building systems that enable frequent, reliable delivery and hold both teams and leadership accountable for technical and organisational change. https://engineering-leadership-preview.hinshelwood.com/articles/why-topic-branches-drive-high-quality-delivery/ Mon, 14 Jul 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/why-topic-branches-drive-high-quality-delivery/ Short-lived topic branches help teams deliver high-quality software by making integration easier, reducing merge conflicts, and supporting modular, continuous delivery. Adopting models like GitHub Flow or Release Flow keeps work focused and feedback fast, while long-lived branches increase risk and slow down delivery. Development managers should enforce small, short-lived branches and regularly review branching strategies to maintain flow, agility, and quality. https://engineering-leadership-preview.hinshelwood.com/videos/why-a-shared-definition-of-done-is-the-secret-to-consistent-predictable-quality-in-agile-teams/ Wed, 14 May 2025 07:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-a-shared-definition-of-done-is-the-secret-to-consistent-predictable-quality-in-agile-teams/ When teams lack a shared definition of done, quality and predictability suffer, leading to confusion, hidden risks, and technical debt. Aligning on a clear, organisation-wide standard ensures consistent delivery, builds trust, and reduces production risks. Development managers should prioritise creating and enforcing a common definition of done to achieve reliable outcomes and true agility. https://engineering-leadership-preview.hinshelwood.com/articles/the-estimation-trap-how-tracking-accuracy-undermines-trust-flow-and-value-in-software-delivery/ Mon, 22 Sep 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/the-estimation-trap-how-tracking-accuracy-undermines-trust-flow-and-value-in-software-delivery/ Focusing on estimation accuracy as a performance metric leads to fear, gaming, and a culture of compliance rather than real improvement, which undermines trust, innovation, and actual value delivery. Research shows that when teams are judged on how closely they meet estimates, they pad numbers, hide risks, and avoid complex work, resulting in false success and missed opportunities for learning. Instead, shift attention to evidence-based metrics that reflect customer value, system health, and delivery flow, and use estimates only to support learning and informed conversations, not as tools for control. https://engineering-leadership-preview.hinshelwood.com/articles/the-definition-of-done-is-a-commitment-to-quality/ Mon, 28 Jul 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/the-definition-of-done-is-a-commitment-to-quality/ A clear, shared Definition of Done is essential for delivering quality, releasable software in Scrum and aligns teams on what “complete” means. It ensures transparency, predictability, and accountability, protects your product’s reputation, and must be created, automated, and regularly improved by all teams working on a product. Development managers should prioritise running DoD workshops, making standards visible, automating checks, and reviewing the DoD every sprint to maintain quality and reduce risk. https://engineering-leadership-preview.hinshelwood.com/videos/how-to-tackle-technical-debt-without-halting-progress-smarter-ways-to-keep-your-team-moving-forward/ Mon, 26 May 2025 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/how-to-tackle-technical-debt-without-halting-progress-smarter-ways-to-keep-your-team-moving-forward/ Technical debt slows teams down and hurts morale, but stopping all work to fix it is unrealistic. The most effective approach is to make technical debt visible, prioritize high-impact improvements, and embed continuous improvement into daily workflows. Development managers should focus on changing team practices and decision-making so that managing technical debt becomes a natural, ongoing part of delivering value. https://engineering-leadership-preview.hinshelwood.com/articles/your-evolving-definition-of-done/ Mon, 31 Mar 2025 09:00:00 +0100 https://engineering-leadership-preview.hinshelwood.com/articles/your-evolving-definition-of-done/ The Definition of Done should evolve as teams mature, starting with basic quality standards and expanding to include automation, security, and business-level requirements that align with organisational goals. A strong, consistently applied DoD reduces risk, rework, and delays, ensuring every increment is truly releasable and delivers real value. Development managers should regularly review and raise the DoD, embedding it into team practices to protect quality and support strategic objectives. https://engineering-leadership-preview.hinshelwood.com/signals/velocity-isn-t-how-many-story-points-a-team-burns-down/ Mon, 10 Mar 2025 16:30:02 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/velocity-isn-t-how-many-story-points-a-team-burns-down/ Velocity is about how quickly your team delivers value, not just story points completed. Focus on measuring time to build, self-test, deploy, and learn from user feedback, as these are actionable and within your control. Start tracking these metrics to improve your delivery speed and effectiveness. https://engineering-leadership-preview.hinshelwood.com/articles/stop-hiding-behind-complexity-and-start-delivering-continuously/ Mon, 24 Feb 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/stop-hiding-behind-complexity-and-start-delivering-continuously/ Complexity is not a valid reason to avoid continuous delivery; organisations like Azure DevOps and Starbucks have proven that even large, complex systems can achieve frequent, reliable releases with the right investment in automation, process improvement, and culture change. Key actions include automating everything, adopting trunk-based development, using feature flags, shifting quality left, and iterating on pain points. Development managers should focus on measuring and improving flow metrics and value delivery, prioritising organisational commitment to overcome resistance and realise the benefits of continuous delivery. https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-are-not-glorified-meeting-schedulers/ Sun, 09 Mar 2025 16:30:01 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-are-not-glorified-meeting-schedulers/ Scrum Masters must have strong technical and business skills, including coding knowledge and expertise in modern engineering practices, to effectively lead software teams. They should be able to challenge teams, identify technical debt, and promote quality, not just schedule meetings. Ensure your Scrum Master can engage with developers on technical topics to achieve real agility. https://engineering-leadership-preview.hinshelwood.com/articles/should-you-use-one-project-to-rule-them-all-in-azure-devops/ Mon, 25 Aug 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/should-you-use-one-project-to-rule-them-all-in-azure-devops/ Using a single Azure DevOps project for all teams and products reduces fragmentation, improves visibility, and streamlines governance compared to managing multiple projects or organisations. Key benefits include unified reporting, easier collaboration, and lower administrative overhead, while Area Paths and Teams provide the necessary structure and security within one project. Development managers should consolidate into one project where possible, using Area Paths and Teams to model structure and scale, to optimise flow and delivery. https://engineering-leadership-preview.hinshelwood.com/videos/why-done-only-counts-when-it-s-live-moving-beyond-fake-finishes-to-real-value-in-software-delivery/ Wed, 07 May 2025 11:46:58 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-done-only-counts-when-it-s-live-moving-beyond-fake-finishes-to-real-value-in-software-delivery/ Work is only truly done when it is live in production and delivering value to users, not just when code is written, tested, or demoed. Teams often mistake internal milestones for real progress, which delays learning and frustrates stakeholders; real feedback and value come only from live usage and telemetry. Development managers should redefine “done” as live in production, invest in automation to shorten release cycles, and focus on measuring and celebrating actual user impact. https://engineering-leadership-preview.hinshelwood.com/articles/release-planning-and-predictable-delivery/ Tue, 24 Nov 2020 13:00:01 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/release-planning-and-predictable-delivery/ Predictable delivery and agile release planning are not incompatible, but achieving them requires a shift in mindset, a focus on continuous quality, and embracing transparency. Key actions include making quality non-negotiable, refining backlog items to be small and clear, ensuring teams own the full delivery process, and minimizing dependencies. Development managers should prioritize building working software in regular increments, stop accumulating technical debt, and foster a culture of continuous improvement to improve delivery predictability. https://engineering-leadership-preview.hinshelwood.com/videos/stop-paying-the-hidden-costs-of-weak-delivery-why-a-strong-definition-of-done-transforms-your-team-s-results/ Wed, 21 May 2025 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/stop-paying-the-hidden-costs-of-weak-delivery-why-a-strong-definition-of-done-transforms-your-team-s-results/ Cutting corners on quality and having a weak definition of done leads to hidden costs like rework, production risks, and lost trust. A clear, shared, and enforceable definition of done ensures every increment is truly usable, reliable, and aligned with business goals. Make your definition of done visible, evidence-based, and strictly enforced to improve delivery outcomes and build stakeholder confidence. https://engineering-leadership-preview.hinshelwood.com/signals/engineering-can-fix-technical-debt-but-leadership-has-to-invest-in-it/ Mon, 03 Mar 2025 16:30:35 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/great-scrum-masters-need-technical-business-and-organisational-mastery/ Mon, 24 Mar 2025 09:00:00 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/videos/from-legacy-pain-to-modern-devops-my-proven-roadmap-for-real-engineering-transformation/ Mon, 04 Aug 2025 07:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/from-legacy-pain-to-modern-devops-my-proven-roadmap-for-real-engineering-transformation/ Transforming legacy engineering to modern DevOps requires a flexible, evidence-based approach focused on testing hypotheses, starting with the most challenging products, and automating every step from code commit to production. Involve all stakeholders to define essential requirements, automate approvals and deployments, and use phased rollouts with real-time feedback to minimize risk. Focus on one improvement at a time, build a culture of continuous learning, and scale successful practices across the organization. https://engineering-leadership-preview.hinshelwood.com/articles/testing-in-production-maximises-quality-and-value/ Thu, 13 Feb 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/testing-in-production-maximises-quality-and-value/ Testing in production using audience-based deployment enables faster feedback, safer incremental releases, and better alignment with real user needs compared to traditional Dev-Test-Staging pipelines. Microsoft’s shift to this model, driven by feature flags, progressive rollouts, and real-time monitoring, has improved quality and innovation while reducing risk and overhead. Development managers should consider moving away from environment-based branching and invest in automation, observability, and team upskilling to maximise value and responsiveness. https://engineering-leadership-preview.hinshelwood.com/articles/definition-of-done-objective-vs-subjective/ Fri, 03 Jan 2025 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/definition-of-done-objective-vs-subjective/ The Definition of Done (DoD) in Scrum is an objective, measurable checklist that sets the minimum quality standard for every product increment, distinct from the more subjective Product and Sprint Goals. Teams should ensure their DoD is clear, comprehensive, regularly reviewed, and as automated as possible, avoiding subjective approval steps. Development managers should treat the DoD as a non-negotiable baseline for quality, not a ceiling, and keep it updated to reflect evolving standards and business needs. https://engineering-leadership-preview.hinshelwood.com/articles/work-can-flow-across-the-sprint-boundary/ Tue, 30 Jan 2018 20:12:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/work-can-flow-across-the-sprint-boundary/ Allowing work to flow across Sprint boundaries is permitted in Scrum and can improve delivery speed, responsiveness, and value, as long as teams maintain clear, outcome-focused Sprint Goals and consistently deliver Done increments. Adopting practices like Continuous Delivery, feature toggles, and frequent feedback helps teams validate work early and adapt quickly. Development managers should encourage flow principles and robust engineering practices to maximize throughput and support better business decisions. https://engineering-leadership-preview.hinshelwood.com/articles/are-we-still-pretending-coding-was-the-bottleneck/ Mon, 01 Sep 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/are-we-still-pretending-coding-was-the-bottleneck/ AI writing code is not the real game-changer; coding was never the main bottleneck in software delivery. The real constraints are in poor system design, handoffs, unclear requirements, and lack of built-in quality, which AI will only make more visible. To benefit from AI, focus on improving flow, building quality in from the start, and making teams accountable for outcomes rather than output. https://engineering-leadership-preview.hinshelwood.com/videos/engineering-excellence-isn-t-perfection-how-continuous-improvement-and-fast-feedback-drive-real-agile-and-devops-success/ Mon, 21 Jul 2025 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/engineering-excellence-isn-t-perfection-how-continuous-improvement-and-fast-feedback-drive-real-agile-and-devops-success/ Engineering excellence is not about achieving perfection or creating exhaustive plans, but about building systems that continuously adapt and improve through fast feedback and incremental change. Key practices include clean code, observability, automated testing, and CI/CD, which together enable teams to deliver high-quality software quickly and respond to real-world needs. Development managers should focus on removing manual bottlenecks and technical debt to shorten feedback loops, as this is the foundation of true Agile and DevOps success. https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-your-team-needs-to-win/ Wed, 16 Jul 2025 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-your-team-needs-to-win/ Many teams struggle not with building software but with finishing it in a way that delivers real business value. A clear, evolving definition of done protects revenue, boosts customer satisfaction, reduces rework, and builds trust by ensuring work is truly complete and valuable. Make your definition of done visible, review it regularly with the whole team, and connect it to real outcomes to turn it into a competitive advantage. https://engineering-leadership-preview.hinshelwood.com/videos/acceptance-criteria-vs-definition-of-done-why-getting-this-right-builds-trust-and-delivers-quality-faster/ Wed, 02 Jul 2025 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/acceptance-criteria-vs-definition-of-done-why-getting-this-right-builds-trust-and-delivers-quality-faster/ Acceptance criteria specify what each backlog item must do, while the definition of done sets the minimum quality standards for all work. Confusing the two leads to missed requirements, technical debt, and loss of trust. Make both explicit and review them regularly to ensure faster delivery and consistent quality. https://engineering-leadership-preview.hinshelwood.com/articles/delivery-is-the-only-measure-of-progress-in-scrum/ Mon, 03 Feb 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/delivery-is-the-only-measure-of-progress-in-scrum/ Progress in Scrum should be measured by delivering working software to real users, not just completing internal work. Teams must deliver increments to production every Sprint, gather user feedback quickly, and adapt based on that feedback. To stay competitive, make delivery the default by automating releases, breaking down silos, and ensuring value reaches users every iteration. https://engineering-leadership-preview.hinshelwood.com/videos/transforming-engineering-excellence-the-power-of-naked-agility-in-quality-and-leadership/ Sat, 30 Nov 2024 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/transforming-engineering-excellence-the-power-of-naked-agility-in-quality-and-leadership/ Prioritising quality from the start is essential to protect your brand and build customer trust, and this requires empowering engineering teams to take ownership, address technical debt openly, and integrate practices like continuous integration, user experience, and security early in development. Fostering a culture of transparency, collaboration, and continuous improvement leads to better products and stronger technical leadership. Invest in your teams’ skills and encourage shared responsibility for quality to drive lasting value for your customers and organisation. https://engineering-leadership-preview.hinshelwood.com/videos/stop-testing-quality-in-how-shifting-left-builds-better-software-faster/ Mon, 18 Aug 2025 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/stop-testing-quality-in-how-shifting-left-builds-better-software-faster/ Relying on testers to catch issues late in the process increases costs, slows feedback, and undermines product trust; instead, quality should be built in from the start by moving tests and feedback as close to the engineer as possible. Key practices include automating builds and tests, adopting continuous integration and delivery, using test-driven development, and incrementally improving code quality. Development managers should focus on empowering engineers to own quality, relentlessly shortening feedback loops, and making incremental improvements to achieve faster, more reliable releases. https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-for-real-business-impact-and-agile-growth/ Wed, 18 Jun 2025 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-for-real-business-impact-and-agile-growth/ A strong definition of done is crucial for delivering real business value, not just completing tasks. When done means features are live, usable, and measured for impact, teams deliver value faster, reduce risk, and become more adaptable. Make your definition of done visible, connect it to measurable outcomes, and continuously refine it to drive growth and true agility. https://engineering-leadership-preview.hinshelwood.com/signals/do-more-staging-environments-really-reduce-deployment-risk/ Wed, 26 Feb 2025 16:30:31 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/do-more-staging-environments-really-reduce-deployment-risk/ Adding more staging environments does not actually reduce deployment risk; it only delays issue discovery and creates a false sense of security. Real risk reduction comes from investing in automated testing, continuous integration, and quality practices built into the development process. To minimize downtime and deployment risk, focus on modern engineering practices rather than adding more pre-production gates. https://engineering-leadership-preview.hinshelwood.com/signals/every-delay-increases-the-risk-of-failure/ Mon, 10 Feb 2025 11:00:51 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/every-delay-increases-the-risk-of-failure/ Delaying software releases increases the risk of failure and falling behind competitors. Frequent, smaller releases lead to higher success rates and faster recovery, as shown by industry research. Focus on delivering quickly and iterating rather than waiting for a perfect release. https://engineering-leadership-preview.hinshelwood.com/articles/stop-promoting-branches/ Thu, 06 Feb 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/stop-promoting-branches/ Promoting code through multiple environment branches slows delivery, increases risk, and adds unnecessary complexity. Instead, use simple branching models like GitHub Flow for continuous delivery or Release Flow if you must support multiple live versions; avoid outdated models like Git Flow and never rely on reverse integration. Focus on merging changes directly into main, use feature flags for releases, and keep branching lightweight to deliver value faster. https://engineering-leadership-preview.hinshelwood.com/videos/the-power-of-technical-excellence-in-agile-development/ Thu, 27 Jun 2024 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/the-power-of-technical-excellence-in-agile-development/ Technical excellence is essential for delivering a usable, high-quality product at the end of every iteration, which reduces risk and enables faster, more valuable feature delivery. The Azure DevOps team at Microsoft dramatically increased their output by focusing on paying down technical debt and establishing a strong Definition of Done. Development managers should prioritize technical excellence, avoid sacrificing quality for speed, and ensure their teams have a clear Definition of Done to maximize value and stay competitive. https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-holding-back-quality-agility-and-trust-and-how-to-raise-the-bar/ Wed, 09 Jul 2025 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-holding-back-quality-agility-and-trust-and-how-to-raise-the-bar/ Treating “done” as a vague checklist limits quality, agility, and stakeholder trust; instead, teams should define “done” as delivering thoroughly tested, production-ready, and valuable increments that work in the real world. Clear, objective standards for “done” reduce defects, speed up learning, and build confidence with stakeholders. Development managers should work with their teams to set and uphold a robust definition of “done” to drive better outcomes and long-term success. https://engineering-leadership-preview.hinshelwood.com/articles/how-to-build-for-business-resilience-and-continuity/ Mon, 26 May 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/how-to-build-for-business-resilience-and-continuity/ Building business resilience requires intentional design, strong observability, and aggressive decoupling so failures do not cascade across systems. Empower teams to act quickly, treat deployments as routine, and design for fast recovery using practices like chaos engineering and circuit breakers. Make resilience a core part of your culture and operations, not a one-time project, and use real metrics to guide continuous improvement. https://engineering-leadership-preview.hinshelwood.com/videos/building-a-culture-of-quality/ Fri, 22 Nov 2024 07:00:08 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/building-a-culture-of-quality/ A culture of quality cannot be built by one person; it requires everyone in the organization to demonstrate and model technical excellence and leadership. Focusing only on revenue, as seen in Boeing’s decline, undermines quality and can lead to dangerous outcomes, while a strong culture of quality leads to better, safer products. Development managers should prioritize building and reinforcing engineering excellence and technical leadership across teams, using frameworks and tools as enablers rather than solutions. https://engineering-leadership-preview.hinshelwood.com/videos/mastering-site-reliability-insights-from-azure-devops-on-building-a-resilient-live-site-culture/ Thu, 04 Jun 2020 02:05:28 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/mastering-site-reliability-insights-from-azure-devops-on-building-a-resilient-live-site-culture/ The Azure DevOps team at Microsoft has built a resilient live site culture by prioritising transparency with customers, investing in comprehensive telemetry, and automating deployment processes. Cross-functional teams and structured incident response drive continuous improvement and reliability at scale. Development managers should focus on these practices to boost both agility and system robustness while maintaining customer trust. https://engineering-leadership-preview.hinshelwood.com/videos/how-to-evolve-your-definition-of-done-start-small-grow-smarter-and-build-lasting-momentum/ Wed, 25 Jun 2025 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/how-to-evolve-your-definition-of-done-start-small-grow-smarter-and-build-lasting-momentum/ You do not need a perfect Definition of Done from the start; begin with what is usable, then gradually add quality, testing, and compliance standards as your team grows more capable. Trying to do everything at once can stall progress, so evolve your standards step by step to build momentum and resilience. Focus on essential requirements now and raise the bar as your team is ready. https://engineering-leadership-preview.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/ Sun, 25 May 2025 15:30:23 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/ Scrum allows you to optimise workflow as long as you maintain accountability through a Sprint Goal and a Done Increment. If your team already delivers quality software continuously and meets these standards, you do not need to force all work to finish within strict Sprint timelines. Focus on outcomes and professionalism rather than rigid rules, and let work flow naturally if your processes support it. https://engineering-leadership-preview.hinshelwood.com/signals/technical-debt-isn-t-just-messy-code/ Thu, 13 Mar 2025 16:30:02 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/technical-debt-isn-t-just-messy-code/ Technical debt goes beyond messy code and includes slow feedback, fragile systems, and manual processes that hinder progress. It results from choices like delaying refactoring or skipping automation, and it compounds over time. To avoid bigger problems later, prioritize paying down technical debt now by automating, testing early, and streamlining delivery pipelines. https://engineering-leadership-preview.hinshelwood.com/articles/a-better-way-than-staggered-iterations-for-delivery/ Thu, 10 Dec 2020 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/a-better-way-than-staggered-iterations-for-delivery/ Staggered iterations slow feedback, increase technical debt, and reduce software quality, making delivery less agile and more expensive. Instead, form cross-functional teams that deliver working software every iteration, integrate all required work including testing into each sprint, and automate as much as possible. Shift away from staged handoffs to continuous, team-owned delivery to improve value and quality. https://engineering-leadership-preview.hinshelwood.com/articles/without-delivery-there-is-no-value/ Mon, 10 Feb 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/without-delivery-there-is-no-value/ Value in software is only realised when products are delivered to users, so frequent releases are essential to validate assumptions, gather feedback, and adapt quickly. Delaying delivery increases costs, risks, and missed opportunities, while research shows that teams releasing often are more successful and resilient. Development managers should prioritise short feedback loops and empower teams to release working software regularly to maximise value and minimise waste. https://engineering-leadership-preview.hinshelwood.com/articles/why-handoffs-are-killing-your-agility/ Mon, 13 Jan 2025 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/why-handoffs-are-killing-your-agility/ Excessive handoffs between siloed teams slow delivery, reduce quality, and undermine team morale, making true agility impossible. Key issues include loss of context, increased cycle time, and lower accountability, all of which compound to hurt value delivery. To improve, reorganise into cross-functional teams, automate workflows, limit work in progress, and regularly remove outdated processes to streamline flow and boost team effectiveness. https://engineering-leadership-preview.hinshelwood.com/videos/still-deploying-manually-why-automation-is-the-bare-minimum-for-modern-engineering-and-your-business-survival/ Mon, 11 Aug 2025 07:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/still-deploying-manually-why-automation-is-the-bare-minimum-for-modern-engineering-and-your-business-survival/ Manual deployments put your business at serious risk due to inevitable human error, as shown by real-world failures that have caused massive financial losses. Automation of builds, deployments, tests, and quality checks is now the minimum standard for professional software development, enabling faster, safer, and more reliable releases. To protect your business and deliver value consistently, eliminate manual steps and automate every part of your delivery pipeline as soon as possible. https://engineering-leadership-preview.hinshelwood.com/videos/stop-firefighting-bugs-why-shifting-left-saves-time-money-and-your-reputation/ Wed, 04 Jun 2025 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/stop-firefighting-bugs-why-shifting-left-saves-time-money-and-your-reputation/ Catching bugs late in the process wastes time, increases costs, and damages your reputation, while most issues could be prevented much earlier. Shifting left by embedding quality checks, early validation, and security into every stage of development leads to faster fixes, fewer production surprises, and greater stakeholder trust. Start building quality in from the beginning to avoid last-minute firefighting and deliver more reliable software. https://engineering-leadership-preview.hinshelwood.com/videos/mastering-sustainable-scaling-overcoming-product-development-challenges-with-naked-agility/ Fri, 28 Feb 2025 06:00:27 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/mastering-sustainable-scaling-overcoming-product-development-challenges-with-naked-agility/ Scaling product development is complex and requires more than just adding people; it demands clear priorities, strong leadership, and systems designed for growth. Naked Agility helps organisations address common scaling challenges like alignment, technical debt, and slow feedback by eliminating bottlenecks, using data-driven decisions, and tailoring strategies to each team’s needs. To scale effectively without sacrificing speed or quality, focus on building a culture and systems that support sustainable growth. https://engineering-leadership-preview.hinshelwood.com/videos/transforming-agility-how-azure-devops-went-from-two-year-releases-to-880-000-deployments/ Thu, 06 Feb 2025 10:20:34 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/transforming-agility-how-azure-devops-went-from-two-year-releases-to-880-000-deployments/ Azure DevOps transformed from two-year release cycles to 880,000 deployments per year by adopting continuous delivery, shortening feedback loops, and using real-time data to guide decisions. This shift enabled rapid response to customer needs and market changes, helping them stay ahead of competitors. Development managers should focus on frequent, small releases and data-driven improvements to maximise value and agility. https://engineering-leadership-preview.hinshelwood.com/videos/the-hidden-costs-of-poor-quality-code-and-how-to-turn-it-into-a-superpower/ Tue, 19 Nov 2024 09:58:28 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/the-hidden-costs-of-poor-quality-code-and-how-to-turn-it-into-a-superpower/ Poor-quality code leads to escalating costs, lost productivity, and damage to team morale and brand reputation, while also causing missed opportunities for innovation. Simplifying branching, limiting supported versions, and investing in engineering excellence and security can dramatically boost productivity and customer satisfaction. Development managers should prioritize code quality improvements now to unlock greater efficiency and long-term organizational success. https://engineering-leadership-preview.hinshelwood.com/articles/why-most-scrum-masters-are-failing-and-what-they-should-know/ Thu, 05 Sep 2024 11:14:48 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/why-most-scrum-masters-are-failing-and-what-they-should-know/ Most Scrum Masters lack the necessary understanding of Scrum and related technical and business practices, which has led to widespread layoffs and questions about their value. Companies now expect Scrum Masters to demonstrate clear competence in areas like DevOps, engineering practices, agile frameworks, release planning, stakeholder management, and metrics. Development managers should ensure their Scrum Masters have foundational knowledge in these areas and can show measurable impact on team effectiveness. https://engineering-leadership-preview.hinshelwood.com/articles/why-measuring-individual-cycle-time-is-killing-your-flow-and-what-to-do-instead/ Mon, 03 Mar 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/why-measuring-individual-cycle-time-is-killing-your-flow-and-what-to-do-instead/ Measuring individual cycle time in Kanban misleads teams by focusing on personal speed instead of system flow, which ignores real bottlenecks and encourages counterproductive behaviors. To improve delivery, track system-wide metrics like lead time, work in progress, process cycle efficiency, and blockers, then address constraints at the process level. Development managers should shift measurement and improvement efforts from individuals to the overall workflow to achieve better outcomes. https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-teams-build-software-that-works/ Thu, 03 Dec 2020 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-teams-build-software-that-works/ Professional Scrum teams must deliver high-quality, working software every sprint, prioritizing quality over speed or feature quantity to build trust and protect the organization’s reputation. Developers are accountable for quality and should use automation, DevOps practices, and continuous improvement to avoid technical debt and defects. Managers should empower teams to focus on quality, address technical debt in retrospectives, and consider upskilling developers through professional training. https://engineering-leadership-preview.hinshelwood.com/videos/stop-flying-blind-why-telemetry-belongs-in-your-definition-of-done/ Wed, 11 Jun 2025 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/stop-flying-blind-why-telemetry-belongs-in-your-definition-of-done/ Shipping software without telemetry leaves teams guessing about usage, performance, and user behavior, which prevents learning and improvement. Teams that make telemetry a core part of their Definition of Done catch issues early, validate outcomes with real data, and make better decisions. To deliver real value, define telemetry needs upfront, automate data collection, review feedback regularly, and act on what you learn. https://engineering-leadership-preview.hinshelwood.com/videos/stop-hoping-for-quality-why-automated-pipelines-are-the-only-way-to-deliver-with-confidence/ Wed, 28 May 2025 07:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/stop-hoping-for-quality-why-automated-pipelines-are-the-only-way-to-deliver-with-confidence/ Relying on manual quality checks leads to inconsistency and risk because people inevitably forget or make mistakes, no matter their intentions. Embedding automated quality gates like security scans, static analysis, linting, and automated tests directly into your delivery pipeline ensures that nothing is missed and quality becomes the default. To deliver reliably and protect your team and customers, make all critical checks automatic and non-optional in your pipeline. https://engineering-leadership-preview.hinshelwood.com/articles/can-the-definition-of-done-change-per-sprint/ Mon, 14 Oct 2019 13:55:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/can-the-definition-of-done-change-per-sprint/ The Definition of Done can be improved each Sprint to raise quality but should never be changed to lower standards or to vary by backlog item, as this undermines transparency and product value. Consistency in the Definition of Done ensures everyone understands what a usable increment means and supports reliable delivery. Development managers should encourage teams to strengthen the Definition of Done over time, aiming for a shippable product each Sprint. https://engineering-leadership-preview.hinshelwood.com/signals/why-organisations-believe-their-software-is-too-complex-for-cd/ Mon, 24 Feb 2025 10:51:31 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/why-organisations-believe-their-software-is-too-complex-for-cd/ Software complexity is often used as an excuse to avoid continuous delivery, but real-world examples like Microsoft’s Azure DevOps team show that even large, complex systems can achieve frequent releases by investing in quality practices and addressing technical debt. The main barrier is not complexity but the willingness to make necessary improvements. Development managers should focus on fixing underlying issues rather than blaming complexity. https://engineering-leadership-preview.hinshelwood.com/videos/nkd-agility-your-partner-in-developing-engineering-excellence/ Sat, 23 Nov 2024 07:00:12 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/nkd-agility-your-partner-in-developing-engineering-excellence/ NKD Agility helps organizations build engineering excellence and technical leadership by shifting key practices like testing, security, and architecture closer to development teams and actively addressing technical debt. This approach reduces the high costs of poor-quality products and supports a culture of quality and value creation. Development managers looking to improve software quality and team capability can partner with NKD Agility for modern engineering practices and support. https://engineering-leadership-preview.hinshelwood.com/articles/avoid-the-pick-n-mix-branching-anti-pattern/ Mon, 14 Jul 2014 15:35:35 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/avoid-the-pick-n-mix-branching-anti-pattern/ Explains the risks of the pick-n-mix branching anti-pattern in source control, its impact on code quality, and recommends feature branching and toggles for stability. https://engineering-leadership-preview.hinshelwood.com/videos/devops-the-practical-path-to-modernising-legacy-systems-without-starting-over/ Mon, 02 Jun 2025 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/devops-the-practical-path-to-modernising-legacy-systems-without-starting-over/ DevOps enables organisations to modernise legacy systems without starting from scratch by introducing automation, continuous integration and deployment, and observability, which make change safer and more routine. These practices reduce bottlenecks, lower the cost of change, and help teams deliver improvements continuously. Development managers should focus on identifying friction points and adopting DevOps practices to make ongoing system improvements achievable and sustainable. https://engineering-leadership-preview.hinshelwood.com/signals/rethinking-dev-test-staging-production-pipelines-for-safety/ Fri, 21 Feb 2025 16:30:30 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/rethinking-dev-test-staging-production-pipelines-for-safety/ Traditional Dev-Test-Staging-Production pipelines give a false sense of security because staging environments do not truly reflect production, leading to missed issues and wasted resources. Modern teams should focus on releasing to small user groups in production and using real feedback to guide rollouts. Consider shifting from heavy pre-release testing to faster, data-driven feedback in production to improve safety and efficiency. https://engineering-leadership-preview.hinshelwood.com/videos/maximising-deployment-frequency-the-key-to-faster-time-to-market-and-business-success/ Wed, 22 Jan 2025 14:16:54 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/maximising-deployment-frequency-the-key-to-faster-time-to-market-and-business-success/ Increasing deployment frequency is key to reducing time to market and driving business success, but it only adds value if deployments reach production and enable fast learning from real user feedback. Focus on stable environments, end-to-end pipeline analysis, and shortening the time to learn so you can iterate quickly and align with business needs. Prioritise building trust with stakeholders, collecting actionable data, and enabling continuous delivery to respond rapidly to opportunities and deliver the right features at the right time. https://engineering-leadership-preview.hinshelwood.com/videos/mastering-azure-devops-avoiding-common-pitfalls-for-agile-success/ Tue, 09 Apr 2024 08:00:20 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/mastering-azure-devops-avoiding-common-pitfalls-for-agile-success/ Many teams misuse Azure DevOps by creating flat work item hierarchies, using custom work item types that do not fit agile practices, neglecting traceability, and overcomplicating processes, which reduces the platform’s effectiveness. Sticking to intended structures and keeping processes simple helps teams stay agile and productive. Review your team’s use of Azure DevOps to ensure alignment with agile principles and avoid these common pitfalls. https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-engineering-excellence-how-azure-devops-transforms-traceability-transparency-and-the-developer-experience/ Mon, 28 Jul 2025 07:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-engineering-excellence-how-azure-devops-transforms-traceability-transparency-and-the-developer-experience/ Azure DevOps is a comprehensive platform that enhances engineering excellence by providing end-to-end traceability, transparency, and an integrated developer experience across planning, code, builds, and testing. Key benefits include instant visibility into what is deployed where, streamlined audit and compliance processes, and reduced friction between developers and testers. Development managers should ensure their teams fully leverage Azure DevOps’ capabilities to improve collaboration, accountability, and product quality. https://engineering-leadership-preview.hinshelwood.com/videos/stop-guessing-how-to-make-work-visible-and-drive-real-improvement-with-azure-devops-flow-metrics/ Mon, 25 Aug 2025 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/stop-guessing-how-to-make-work-visible-and-drive-real-improvement-with-azure-devops-flow-metrics/ Relying on gut feeling leads to mediocre results, so making work visible with real data is essential for improvement. Azure DevOps provides a strong data foundation but its built-in metrics and visualisations are basic; using tools like Flow Viz or Actionable Agile Metrics gives deeper insights and actionable flow data. To drive better outcomes, move from guesswork to evidence-based decisions by leveraging these tools to make your team’s work and bottlenecks visible. https://engineering-leadership-preview.hinshelwood.com/signals/evolving-engineering-practices-to-improve-sprint-workflow-in-scrum/ Thu, 29 May 2025 15:30:45 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/evolving-engineering-practices-to-improve-sprint-workflow-in-scrum/ To improve sprint workflow in Scrum without sacrificing quality, teams need to adopt practices like Feature Flags, TDD, and regular refactoring to enable safe, continuous flow of work. These practices help ship incomplete features safely, ensure code reliability, and maintain system health. Development managers should prioritize evolving engineering practices and consider Continuous Delivery essential for sustainable progress. https://engineering-leadership-preview.hinshelwood.com/signals/why-tracking-individual-cycle-time-distorts-team-behaviour/ Wed, 12 Mar 2025 16:30:03 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/the-scrum-master-is-accountable-for-delivery/ Thu, 30 Jan 2025 00:00:00 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/videos/empowering-teams-for-success-the-key-to-thriving-product-development/ Tue, 07 May 2024 11:02:49 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/empowering-teams-for-success-the-key-to-thriving-product-development/ Successful product development depends on empowered, engaged, and happy teams who understand the value of their work and are trusted to make decisions. Key drivers include fostering collaboration, providing continuous feedback, investing in skills development, and enabling direct customer engagement. Development managers should focus on creating an environment where team members feel valued and supported, as this leads to higher quality products and greater innovation. https://engineering-leadership-preview.hinshelwood.com/videos/transform-your-scrum-team-in-90-days-strategies-for-continuous-delivery-and-empowerment/ Tue, 27 Jun 2023 07:00:06 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/i-do-continuous-deliver-why-should-i-sprint/ Mon, 13 Jul 2020 18:42:03 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/i-do-continuous-deliver-why-should-i-sprint/ Sprints are not about limiting release frequency but about providing a regular cadence for planning, communication, and predictability, even if you use continuous delivery. Scrum requires a working increment at least every 30 days, but you can release more often; Sprints help structure feedback loops and align teams and stakeholders. To stay competitive and responsive, use Sprints as a planning container while delivering to production as frequently as possible. https://engineering-leadership-preview.hinshelwood.com/signals/why-engineering-teams-use-staging-environments-for-risk-reduction/ Fri, 14 Feb 2025 16:30:01 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/why-engineering-teams-use-staging-environments-for-risk-reduction/ Staging environments are intended to reduce risk but often lead to wasted time, delayed feedback, and extra costs without truly preventing failures. Modern practices like feature flags, progressive rollouts, and real-time monitoring can help teams deploy safely to production while reducing waste. Consider whether maintaining staging environments is actually benefiting your team or just adding unnecessary overhead. https://engineering-leadership-preview.hinshelwood.com/articles/the-sprint-is-a-container-for-planning-and-not-necessarily-for-delivery/ Tue, 29 Nov 2011 04:36:22 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/the-sprint-is-a-container-for-planning-and-not-necessarily-for-delivery/ Explains how Scrum Sprints are primarily for planning, not fixed delivery, and discusses aligning delivery schedules, continuous deployment, and improving software quality. https://engineering-leadership-preview.hinshelwood.com/signals/executives-want-predictability/ Mon, 31 Mar 2025 15:30:08 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/executives-want-predictability/ If your teams do not have a clear, enforced Definition of Done, you are creating hidden risks and unreliable forecasts, which leads to missed deadlines and frustrated customers. Treating “Done” as negotiable means you are not delivering real value or predictability. Make sure your teams only mark work as done when it meets objective, enforceable standards to ensure true progress and trustworthy commitments. https://engineering-leadership-preview.hinshelwood.com/signals/why-scrum-masters-need-technical-expertise-to-guide-teams/ Fri, 28 Mar 2025 16:30:04 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/videos/shifting-left-quality-from-the-start/ Wed, 20 Nov 2024 07:00:26 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/shifting-left-quality-from-the-start/ Automating code reviews and quality checks as early as possible in the development process reduces defects and speeds up delivery by minimizing manual bottlenecks. Manual code reviews should be a safety net, not the primary method for ensuring quality, and no code should reach the main branch without passing automated checks. Development managers should invest in robust automation for code validation to improve quality and accelerate value delivery. https://engineering-leadership-preview.hinshelwood.com/articles/estimating-better-in-an-overloaded-system-is-a-poor-man-s-strategy/ Mon, 08 Sep 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/estimating-better-in-an-overloaded-system-is-a-poor-man-s-strategy/ Trying to improve estimates in an overloaded system is ineffective because high work in progress causes delays and unpredictability, regardless of estimation accuracy. Real improvements in predictability and throughput come from limiting work in progress, fostering collaboration, and focusing on finishing work rather than starting more. To achieve reliable delivery, reduce WIP and prioritize flow over planning. https://engineering-leadership-preview.hinshelwood.com/videos/stop-chasing-trends-how-real-agility-and-devops-build-resilient-adaptable-teams/ Fri, 27 Jun 2025 06:00:23 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/videos/free-workshop-04-introduction-to-sprint-reviews-review-retrospective/ Sat, 18 Sep 2021 13:32:34 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/free-workshop-04-introduction-to-sprint-reviews-review-retrospective/ The workshop introduced key concepts of Sprint Reviews using interactive tools and received very positive participant feedback, despite technical audio issues during the live stream. The main learning was to check both music and voice before sessions to avoid similar problems, and future events will use a new community platform for easier access. Development managers should ensure thorough technical checks before virtual workshops and consider leveraging interactive formats for better engagement. https://engineering-leadership-preview.hinshelwood.com/videos/embrace-simplicity-how-to-transform-complexity-into-continuous-delivery-success/ Thu, 27 Feb 2025 07:00:10 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/embrace-simplicity-how-to-transform-complexity-into-continuous-delivery-success/ Complexity is not a valid excuse for avoiding continuous delivery; with organisational commitment and a willingness to modernise, even legacy systems can be transformed for faster, more reliable releases. Key steps include honestly assessing your product, investing in ongoing improvement, and addressing technical debt rather than ignoring warning signs. Leaders should prioritise resources and foster a culture that values continuous improvement to avoid costly failures and achieve lasting delivery success. https://engineering-leadership-preview.hinshelwood.com/signals/best-branching-strategies-for-development-teams-explained/ Tue, 25 Feb 2025 16:30:02 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/best-branching-strategies-for-development-teams-explained/ Using separate branches for each environment increases complexity and slows feedback, making it harder to deliver value quickly. Teams should use branches to manage work in progress and rely on feature flags and progressive rollouts to control what users see. Review your current branching approach and consider simplifying it to speed up delivery and reduce risk. https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-rapid-delivery-overcoming-common-devops-challenges-for-agile-success/ Fri, 21 Apr 2023 07:00:06 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-rapid-delivery-overcoming-common-devops-challenges-for-agile-success/ Many teams struggle to deliver products quickly due to slow feedback loops, limited automation, and resistance to change. Key improvements include automating processes, engaging compliance teams early to challenge assumptions, and fostering a culture open to experimentation. Development managers should review their delivery pipelines for bottlenecks and actively involve stakeholders to enable faster, more agile releases. https://engineering-leadership-preview.hinshelwood.com/videos/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-preview.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-preview.hinshelwood.com/videos/why-azure-devops-wins-for-governance-security-and-scale-right-out-of-the-box/ Mon, 01 Sep 2025 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-azure-devops-wins-for-governance-security-and-scale-right-out-of-the-box/ Azure DevOps provides integrated governance, security, compliance, and scalability out of the box, eliminating the need for complex tool setups and manual integration. Its seamless traceability, audit trails, and ability to handle thousands of users make it ideal for large-scale, secure software development. Development managers should consider Azure DevOps to reduce operational friction and focus on delivering value rather than managing disparate tools. https://engineering-leadership-preview.hinshelwood.com/signals/i-ll-never-understand-teams-that-manage-bugs-instead-of-fixing-them/ Thu, 01 May 2025 15:30:38 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/i-ll-never-understand-teams-that-manage-bugs-instead-of-fixing-them/ Teams should focus on fixing bugs as soon as they are found instead of managing or prioritising them in backlogs or meetings. Delaying bug fixes leads to bigger problems and undermines the goal of delivering working software. Development managers should ensure their teams address defects promptly rather than letting them accumulate. https://engineering-leadership-preview.hinshelwood.com/signals/microsoft-shift-from-2-year-cycles-to-3-week-sprints-caused-team-anxiety/ Wed, 23 Apr 2025 15:30:47 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/microsoft-shift-from-2-year-cycles-to-3-week-sprints-caused-team-anxiety/ When Microsoft switched from two-year release cycles to three-week Sprints, teams initially felt anxious because increased transparency exposed inefficiencies and technical debt. However, teams that embraced this openness improved dramatically, moving from delivering 24 features a year to shipping multiple times daily. Development managers should consider whether their teams are ready to use transparency as a tool for continuous improvement. https://engineering-leadership-preview.hinshelwood.com/videos/rethinking-continuous-delivery-why-best-practices-don't-exist-in-complex-environments/ Thu, 23 Jan 2025 06:30:03 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/rethinking-continuous-delivery-why-best-practices-don't-exist-in-complex-environments/ There are no universal best practices for continuous delivery in complex environments; instead, teams should adopt flexible, situation-specific approaches. Key strategies include audience-based delivery for rapid feedback, testing in production to validate real-world performance, and a commitment to quickly finding and fixing issues. Development managers should focus on continuous improvement and adaptability rather than rigid processes. https://engineering-leadership-preview.hinshelwood.com/signals/if-every-release-feels-high-risk-you-lack-a-true-definition-of-done/ Sat, 05 Apr 2025 15:30:00 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/if-every-release-feels-high-risk-you-lack-a-true-definition-of-done/ If every release feels risky and stressful, your team likely lacks a clear Definition of Done that ensures software is truly ready for production. A strong Definition of Done means releases are routine, with quality, security, and compliance built in, so there are no last-minute scrambles. Review your team’s process to make releases predictable and low-stress. https://engineering-leadership-preview.hinshelwood.com/videos/special-sprints-agile-banditry-or-risk-management/ Thu, 04 Jan 2024 11:09:15 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/signals/let-us-do-the-maths/ Wed, 30 Apr 2025 15:30:52 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/let-us-do-the-maths/ Slow release cycles mean customer needs go unmet and competitors gain an edge. Microsoft’s shift from a two-year delivery cycle to three-week sprints allowed them to deliver features in days, improving customer satisfaction and competitiveness. Accelerate your delivery process to stay relevant and meet customer demands faster. https://engineering-leadership-preview.hinshelwood.com/signals/there-a-common-belief-that-rollback-is-the-ultimate-safety-net/ Thu, 13 Feb 2025 15:53:38 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/there-a-common-belief-that-rollback-is-the-ultimate-safety-net/ Relying on rollback as a safety net is risky, especially for stateful applications where it can cause data issues and failures. Safer approaches include progressive delivery methods like feature flags and canary releases, which help detect and limit problems early. Teams should focus on making deployments safe to fail rather than assuming rollback will fix mistakes. https://engineering-leadership-preview.hinshelwood.com/videos/building-a-high-performance-delivery-engine-unlocking-success-through-competence-and-collaboration/ Tue, 03 Dec 2024 06:30:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/building-a-high-performance-delivery-engine-unlocking-success-through-competence-and-collaboration/ To build a high-performing software delivery team, focus on developing both technical and business competence across all members, encouraging everyone to think like product developers rather than just coders. Embrace Agile, DevOps, Lean, and Scrum philosophies, adapt practices as needed, and ensure due diligence before making structural changes. Prioritise collaboration, open communication, and continuous improvement to maximise value delivery and drive business success. https://engineering-leadership-preview.hinshelwood.com/videos/transforming-technical-debt-unlocking-innovation-and-value-through-quality-product-delivery/ Thu, 21 Nov 2024 17:01:52 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/transforming-technical-debt-unlocking-innovation-and-value-through-quality-product-delivery/ Technical debt is more than just a cost; it represents missed opportunities for innovation and value. Allowing technical debt to persist leads to higher maintenance costs, slower delivery, and lower team morale, while prioritising high-quality product delivery enables greater agility, consistent value, and innovation. Development managers should regularly assess and address technical debt, foster a culture of quality, and communicate its impact to stakeholders to unlock their teams’ full potential. https://engineering-leadership-preview.hinshelwood.com/videos/how-important-is-devops-in-continuous-delivery-of-value-to-customers/ Mon, 20 Feb 2023 07:00:10 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/how-important-is-devops-in-continuous-delivery-of-value-to-customers/ DevOps is essential for delivering value to customers because it enables teams to quickly and effectively turn ideas into working software, closely aligning with agile principles. Both DevOps and agile focus on rapid feedback, continuous improvement, and adapting to customer needs, making them deeply interconnected. Development managers should ensure their teams integrate DevOps practices to accelerate delivery, validate value, and reduce risk. https://engineering-leadership-preview.hinshelwood.com/articles/how-lack-of-agency-is-killing-your-devops-initiatives/ Mon, 16 Jun 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/how-lack-of-agency-is-killing-your-devops-initiatives/ DevOps only works when developers have real control over production environments, deployments, and telemetry; without this operational agency, automation just creates fragile systems and blocks learning from real user feedback. Most DevOps efforts fail because they focus on tools instead of empowering developers to deploy, monitor, and adapt in production. To succeed, give your teams full operational ownership so they can deliver value continuously and respond quickly to real-world issues. https://engineering-leadership-preview.hinshelwood.com/articles/pragmatism-crushes-dogma-in-the-wild/ Thu, 21 Mar 2024 09:30:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/pragmatism-crushes-dogma-in-the-wild/ Practical use of Scrum in a mentoring program showed that teams succeed by focusing on adaptability and resilience rather than rigidly following rules. Key insights include the importance of making work visible, inspecting progress, and quickly adapting to change, as outlined in the Scrum Guide. Development managers should prioritize flexibility within Scrum’s essential guardrails to help teams handle real-world challenges effectively. https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-true-potential-of-scrum-why-professionalism-matters-in-agile-teams/ Thu, 20 Apr 2023 07:00:06 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-true-potential-of-scrum-why-professionalism-matters-in-agile-teams/ Many software teams fall short of Scrum’s true potential because organizations prioritize speed over professionalism, leading to shortcuts and unprofessional practices. Achieving real value with Scrum requires a commitment to transparency, production-ready increments each iteration, and honest assessment of current capabilities, often revealing significant gaps. Development managers should focus on fostering a professional work ethic and closing these gaps to unlock Scrum’s full benefits. https://engineering-leadership-preview.hinshelwood.com/signals/deploying-windows-os-directly-to-production-then-vs-now/ Sat, 22 Feb 2025 16:30:00 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/deploying-windows-os-directly-to-production-then-vs-now/ Microsoft now deploys Windows updates directly to production using a gradual, ring-based rollout that starts with internal users and expands outward, guided by real-time feedback and telemetry. This approach catches issues early and enables safe, incremental releases even across complex environments. Development managers should consider adopting similar staged deployment strategies to improve release quality and responsiveness. https://engineering-leadership-preview.hinshelwood.com/videos/story-points-a-ghost-of-agile-past/ Fri, 29 Dec 2023 07:00:14 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/story-points-a-ghost-of-agile-past/ Story points have become a source of dysfunction in Agile teams, shifting focus from delivering value to hitting arbitrary targets and enabling misleading comparisons between teams. These issues are worsened when contracts tie performance to story point delivery, leading to counterproductive behaviors. Development managers should move away from story points and instead adopt flow metrics like cycle time and throughput, which provide more accurate, value-focused insights into team performance. https://engineering-leadership-preview.hinshelwood.com/signals/branch-promotion-is-a-relic-of-slow-manual-software-delivery/ Sat, 08 Feb 2025 16:30:00 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/branch-promotion-is-a-relic-of-slow-manual-software-delivery/ Branch promotion slows down delivery and adds risk, while modern teams merge changes into the main branch as soon as they are ready and use feature flags to separate deployment from release. Testing in production-like environments and instant rollbacks improve speed and safety. Focus on managing the flow of work, not branches, to streamline delivery. https://engineering-leadership-preview.hinshelwood.com/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-preview.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-preview.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-preview.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-preview.hinshelwood.com/signals/too-many-teams-overcomplicate-their-branching-strategies/ Thu, 06 Feb 2025 09:38:01 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/too-many-teams-overcomplicate-their-branching-strategies/ Many teams make branching too complex, which slows delivery and adds risk. Simple models like GitHub Flow or Release Flow help teams move faster and deliver value more consistently. Focus on minimizing branching complexity to improve speed and reliability. https://engineering-leadership-preview.hinshelwood.com/videos/is-your-project-ecosystem-truly-agile/ Wed, 31 Jul 2024 06:45:01 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/is-your-project-ecosystem-truly-agile/ Having Agile development teams is not enough if your deployment processes remain slow and bureaucratic, as this creates delays, reduces value, and frustrates teams. Automating deployment and testing, implementing CI/CD pipelines, and shortening feedback loops are essential to achieving true end-to-end agility and maximizing stakeholder value. Review your current processes for bottlenecks, start automating where possible, and involve stakeholders early and often to ensure your entire project ecosystem is genuinely Agile. https://engineering-leadership-preview.hinshelwood.com/signals/we-hear-self-managing-teams-so-often-it-become-a-clich%C3%A9/ Fri, 09 May 2025 15:30:39 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/we-hear-self-managing-teams-so-often-it-become-a-clich%C3%A9/ Self-management is essential for all Scrum roles, not just developers, and involves active, disciplined work in how Product Owners, Scrum Masters, and Developers fulfill their responsibilities. Scrum requires clear alignment and adaptive discipline, not a loose or chaotic approach. Development managers should ensure their teams understand and practice self-management as a structured, intentional process rather than mistaking it for a lack of direction. https://engineering-leadership-preview.hinshelwood.com/signals/we-don-t-have-time-for-automation-but-manual-testing-slows-releases-and-quality/ Mon, 07 Apr 2025 15:30:01 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/we-don-t-have-time-for-automation-but-manual-testing-slows-releases-and-quality/ Relying on manual testing slows releases, overwhelms testers, and lets bugs slip through, making it impossible to keep up with rapid changes. Automation is essential for maintaining both speed and quality in software development. Teams should prioritize moving to automated testing to avoid bottlenecks and improve release reliability. https://engineering-leadership-preview.hinshelwood.com/videos/embracing-automation-the-key-to-transforming-your-development-process-and-boosting-confidence/ Tue, 14 Jan 2025 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/embracing-automation-the-key-to-transforming-your-development-process-and-boosting-confidence/ Embracing automation in testing, deployment, and validation is essential for faster, more reliable software delivery and increased team confidence. The Azure DevOps team drastically reduced feedback loops and technical debt by shifting to automated, efficient testing and empowering developers with local testing tools. Prioritizing automation and quality builds trust both within teams and with customers, so development managers should focus on automating as much as possible to enable continuous delivery and rapid improvement. https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-code-quality-the-transformative-power-of-frequent-deployments/ Mon, 13 Jan 2025 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-code-quality-the-transformative-power-of-frequent-deployments/ Frequent deployments lead to higher code quality, faster feedback, and better alignment with user needs, while infrequent deployments cause larger, riskier changes and more technical debt. Breaking work into smaller pieces and deploying regularly encourages maintainable code and enables quick pivots based on real user data. Development managers should focus on reducing batch sizes, increasing deployment frequency, and investing in observability to improve both product quality and team performance. https://engineering-leadership-preview.hinshelwood.com/videos/from-chaos-to-clarity-my-journey-through-devops-and-the-three-key-challenges-to-overcome/ Thu, 04 Apr 2024 11:34:59 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/from-chaos-to-clarity-my-journey-through-devops-and-the-three-key-challenges-to-overcome/ The author describes moving from chaotic, manual development practices to adopting DevOps, highlighting three main challenges: shifting culture and collaboration, integrating and automating toolchains, and fostering continuous learning. Success requires systems thinking, strong feedback loops, and a culture of experimentation. Development managers should focus on supporting people, streamlining processes, and encouraging ongoing learning to deliver better products faster. https://engineering-leadership-preview.hinshelwood.com/articles/getting-started-with-a-definition-of-done-dod/ Mon, 14 Dec 2020 13:03:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/getting-started-with-a-definition-of-done-dod/ A clear Definition of Done (DoD) is essential for ensuring software quality and predictable delivery, as it sets shared criteria for what “done” means for every increment. Involve the whole Scrum Team and relevant experts to create a short, measurable checklist that covers code quality, testing, security, and usability, and review it regularly to keep raising the quality bar. Before starting sprints, make sure your current increment meets the DoD, and continuously improve both your software and your DoD to maintain a working, shippable product. https://engineering-leadership-preview.hinshelwood.com/articles/metrics-that-matter-with-evidence-based-management/ Tue, 25 Feb 2014 13:29:14 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/metrics-that-matter-with-evidence-based-management/ Explains how evidence-based management uses reliable metrics and KPIs at team and organisational levels to drive better decisions, value delivery, and process improvement. https://engineering-leadership-preview.hinshelwood.com/articles/building-a-release-pipeline-with-release-management-with-visual-studio-2013/ Tue, 18 Feb 2014 16:30:59 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/building-a-release-pipeline-with-release-management-with-visual-studio-2013/ Explains how to set up a scalable release pipeline using Release Management in Visual Studio 2013, covering continuous release, feedback environments, and DevOps practices. https://engineering-leadership-preview.hinshelwood.com/articles/quality-enablement-to-achieve-predictable-delivery/ Wed, 24 Jul 2013 09:46:22 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/quality-enablement-to-achieve-predictable-delivery/ Explains how defining quality standards, acceptance criteria, and automation in software delivery leads to predictable outcomes, fewer bugs, and improved team performance. https://engineering-leadership-preview.hinshelwood.com/signals/if-software-is-not-delivered-it-is-not-valuable/ Sat, 01 Mar 2025 16:30:03 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/if-software-is-not-delivered-it-is-not-valuable/ Undelivered software provides no value, and long development cycles increase risk, cost, and missed opportunities. Research shows that teams releasing software frequently are more successful and efficient. To maximize value and learning, prioritize frequent delivery to users. https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/videos/transforming-waste-into-value-how-to-boost-roi-with-agile-metrics/ Tue, 17 Dec 2024 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/transforming-waste-into-value-how-to-boost-roi-with-agile-metrics/ Most organisations lose significant value due to waste and lack of focus on engineering excellence, with metrics showing that only a small fraction of development investment results in features customers actually use. Key insights include low innovation rates, poor feature usage, and lagging version adoption, all of which drastically reduce ROI. Development managers should measure and act on innovation and usage metrics, close feedback loops, and focus on delivering value rather than just reducing costs. https://engineering-leadership-preview.hinshelwood.com/videos/the-evolution-of-my-journey-with-azure-devops-lessons-and-insights/ Wed, 31 Jul 2024 09:21:03 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/the-evolution-of-my-journey-with-azure-devops-lessons-and-insights/ Azure DevOps has evolved from TFS to a powerful, flexible platform that can transform team workflows, but successful adoption and migration require careful planning and sometimes custom solutions. Key lessons include the importance of assessing your environment, choosing the right migration tools, and leveraging expert guidance for complex needs. Development managers should ensure their teams are trained and consider consulting support to maximize the benefits and scalability of Azure DevOps. https://engineering-leadership-preview.hinshelwood.com/articles/storms-of-neglect-the-perils-of-not-delivering-usable-products-in-agile-iterations/ Thu, 27 Jul 2023 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/storms-of-neglect-the-perils-of-not-delivering-usable-products-in-agile-iterations/ If teams do not deliver a usable product at the end of each iteration, trust with stakeholders erodes, technical debt grows, adaptability slows, and expectations become misaligned. This also leads to lower team morale and a lack of feedback, making it hard to improve or stay on track. To avoid these issues, ensure every iteration results in a usable product so you maintain trust, alignment, and the ability to adapt quickly. https://engineering-leadership-preview.hinshelwood.com/signals/staging-environments-do-not-prevent-production-failures/ Fri, 28 Feb 2025 16:30:01 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/staging-environments-do-not-prevent-production-failures/ Staging environments do not truly prevent production failures because they cannot fully replicate real-world conditions, often giving teams a false sense of security. Leading teams now deploy changes incrementally to real users in production, using monitoring and automated safeguards to catch issues early. Consider shifting focus from pre-production testing to safer, controlled releases in production to reduce risk and respond faster to problems. https://engineering-leadership-preview.hinshelwood.com/signals/every-unreleased-feature-is-a-cost/ Wed, 05 Feb 2025 16:30:01 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/every-unreleased-feature-is-a-cost/ Unreleased features create hidden costs and risks, as work that is not delivered provides no real value. Evidence shows that frequent releases reduce failure rates and improve stability, while long cycles lead to more rework and missed opportunities. Focus on shipping regularly to ensure your team’s efforts translate into actual value. https://engineering-leadership-preview.hinshelwood.com/videos/maximising-product-value-the-power-of-hypothesis-driven-engineering/ Wed, 11 Dec 2024 06:30:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/maximising-product-value-the-power-of-hypothesis-driven-engineering/ Focusing on hypothesis-driven engineering helps teams maximise product value by testing ideas with small experiments, measuring outcomes, and quickly adapting based on real customer feedback. The Azure DevOps team’s experience showed that even costly initiatives can provide critical learning, allowing resources to be redirected before larger losses occur. Development managers should encourage rapid experimentation and validation at all levels to ensure investments deliver real value and support agility. https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-success-how-small-experiments-transformed-feature-delivery-from-25-to-150-in-software-development/ Wed, 20 Nov 2024 08:02:36 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-success-how-small-experiments-transformed-feature-delivery-from-25-to-150-in-software-development/ A team increased their annual feature delivery from 25 to 150 by breaking down work into smaller experiments, enabling faster feedback, reduced risk, and continuous learning without increasing headcount. This approach allowed them to quickly identify and focus on features that mattered most to customers, leading to better products. Development managers should consider adopting small, frequent experiments to drive both speed and quality in feature delivery. https://engineering-leadership-preview.hinshelwood.com/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-preview.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-preview.hinshelwood.com/articles/if-your-backlog-is-not-refined-then-you-are-doing-it-wrong/ Thu, 17 Dec 2020 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/if-your-backlog-is-not-refined-then-you-are-doing-it-wrong/ If your team starts Sprint Planning with backlog items that are not well understood or sized to fit within a sprint, you are setting up for failure. Regular backlog refinement is essential so developers can confidently select and deliver work, and lack of refinement often leads to missed goals and confusion. Make sure your team spends enough time refining upcoming backlog items so they are clear, appropriately sized, and ready for selection in the next two sprints. https://engineering-leadership-preview.hinshelwood.com/videos/mastering-remote-work-key-insights-for-agile-teams-to-thrive-in-a-digital-world/ Fri, 10 Apr 2020 18:30:42 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/mastering-remote-work-key-insights-for-agile-teams-to-thrive-in-a-digital-world/ Remote work requires strong communication, the right tools, and a focus on delivering value, even when teams are not co-located. Improving feedback loops, observing team dynamics through activities like games, and integrating UX early in Agile processes all help teams collaborate better and build the right products. Development managers should prioritize open communication, continuous process improvement, and shared accountability for user experience to help their teams thrive in a digital environment. https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-and-product-owners-are-held-accountable-for-results/ Mon, 17 Mar 2025 16:30:03 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-and-product-owners-are-held-accountable-for-results/ Scrum Masters and Product Owners are often held accountable for results without having the authority needed to influence outcomes. This mismatch leads to empty expectations and limits team effectiveness. To achieve better results, organisations should empower Scrum Masters with real authority, not just expect them to coach from the sidelines. https://engineering-leadership-preview.hinshelwood.com/signals/agile-is-not-easier-than-traditional-methods-common-misconceptions/ Sat, 08 Mar 2025 16:30:01 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/agile-is-not-easier-than-traditional-methods-common-misconceptions/ Agile is often harder than traditional methods because it requires frequent delivery, decision-making with limited information, and handling uncertainty. Success depends on disciplined teams, strong collaboration, and a focus on delivering value, not just following a framework. Development managers should assess whether their teams are truly embracing Agile principles or simply following routines. https://engineering-leadership-preview.hinshelwood.com/videos/how-effectively-does-an-aps-prepare-a-team-to-do-a-solid-professional-scrum/ Sat, 12 Aug 2023 07:00:10 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/how-effectively-does-an-aps-prepare-a-team-to-do-a-solid-professional-scrum/ The Applied Professional Scrum (APS) course helps teams focus on delivering a working product every iteration and sheds unhelpful habits that slow progress. Through practical exercises like the “Barnacle Exercise,” teams identify and remove outdated practices, leading to more effective Scrum adoption. Development managers should consider APS to build teams that consistently deliver value and embody true Scrum principles. https://engineering-leadership-preview.hinshelwood.com/articles/release-management-with-team-foundation-server-2012/ Wed, 24 Apr 2013 17:38:24 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/release-management-with-team-foundation-server-2012/ Explains how to automate and streamline software release management using Team Foundation Server 2012, Lab Management, and Octopus, focusing on build, deployment, and quality. https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-developer-net-training-in-london/ Fri, 18 Jun 2010 15:53:27 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-developer-net-training-in-london/ Intensive five-day course for software developers covering Scrum, Visual Studio 2010, .NET, and Agile practices through hands-on team sprints and real-world case studies. https://engineering-leadership-preview.hinshelwood.com/signals/scrum-masters-enabling-teams-fostering-agility-removing-blockers/ Wed, 05 Mar 2025 16:30:00 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/videos/evidence-based-management-the-four-key-value-areas-in-scrum/ Fri, 13 Sep 2024 07:00:34 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/decoding-scrum-team-work-balancing-sprint-and-refinement-work/ Thu, 14 Sep 2023 14:25:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/decoding-scrum-team-work-balancing-sprint-and-refinement-work/ Scrum teams need to balance Sprint work, which delivers direct value to stakeholders, with Refinement, which prepares the backlog for future Sprints. Using tools like Azure DevOps to visualise and track both types of work helps teams plan better, avoid unnecessary effort, and stay ready for challenges. Development managers should ensure both work types are visible and managed to improve team efficiency and product outcomes. https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-success-how-empirical-models-transform-project-outcomes/ Wed, 12 Oct 2022 17:08:59 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-agile-success-how-empirical-models-transform-project-outcomes/ Agile methods significantly increase project success rates, especially for larger teams, by maintaining ongoing visibility, enabling flexibility, reducing operational risk, and delivering value incrementally. Unlike traditional models, Agile allows for regular feedback and adaptation, which keeps projects aligned with customer needs and reduces wasted effort. Development managers should consider adopting empirical Agile practices to improve outcomes and stakeholder satisfaction. https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-true-power-of-continuous-delivery-how-automation-transforms-software-development/ Fri, 06 Dec 2024 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-true-power-of-continuous-delivery-how-automation-transforms-software-development/ The main benefit of continuous delivery is the automation it brings, which increases consistency, reliability, and risk mitigation in software deployments. Real-world examples like Azure DevOps and Windows teams show that automation shortens feedback loops, reduces errors, and enables faster, higher-quality releases without increasing team size. Development managers should focus on embedding automation throughout their delivery process to protect the business and empower teams to deliver better software more efficiently. https://engineering-leadership-preview.hinshelwood.com/videos/security-by-design-building-secure-software/ Tue, 26 Nov 2024 13:35:33 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/security-by-design-building-secure-software/ Shifting left means building quality and security into software from the start by making developers responsible for testing, integrating expertise early, and using practices like test-driven development and continuous feedback. Although it may feel slower at first, this approach reduces long-term costs, technical debt, and enables faster, higher-quality delivery as shown by Azure DevOps’ transformation. Development managers should invest in shift-left practices now to empower teams, improve products, and accelerate innovation. https://engineering-leadership-preview.hinshelwood.com/videos/detecting-agile-bs-lessons-from-the-us-department-of-defense/ Fri, 28 Jun 2024 06:45:01 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/detecting-agile-bs-lessons-from-the-us-department-of-defense/ Many organizations claim to be Agile but often fall short of true Agile practices, as highlighted by the US Department of Defense’s “Detecting Agile BS” guide. The guide recommends six key questions to assess real Agile maturity, focusing on frequent delivery to users, regular production releases, adapting to feedback, clear product vision, team empowerment, and a culture of continuous improvement. Development managers should honestly assess their teams against these criteria, start small with improvements, and foster a culture of feedback and learning to achieve genuine Agile transformation. https://engineering-leadership-preview.hinshelwood.com/videos/the-overlooked-virtue-of-agility-diligence/ Thu, 07 Dec 2023 07:00:02 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/videos/unlocking-success-in-agile-why-your-definition-of-done-is-essential-for-quality-delivery/ Mon, 13 Nov 2023 06:56:47 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-success-in-agile-why-your-definition-of-done-is-essential-for-quality-delivery/ A clear and shared Definition of Done is essential for delivering quality products in Agile and Scrum, as it sets the standard for what is considered complete and ensures transparency across the team. Without it, teams risk miscommunication, unfinished work, and features that do not meet user needs. Development managers should regularly review and reinforce the Definition of Done with their teams to improve quality and reduce risk. https://engineering-leadership-preview.hinshelwood.com/videos/mastering-evidence-based-management-for-agile-success/ Wed, 02 Oct 2024 13:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/mastering-evidence-based-management-for-agile-success/ Evidence-Based Management helps Agile teams make better decisions by using data from four key areas: current value, unrealized value, ability to innovate, and time to market. By collecting and analyzing relevant metrics, teams can prioritize improvements, boost innovation, and deliver more value to customers. Start by tracking a few key metrics with simple tools, then use those insights to guide your team’s next steps. https://engineering-leadership-preview.hinshelwood.com/guides/detecting-agile-bs/ Tue, 17 Sep 2024 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/guides/detecting-agile-bs/ Guidance for identifying genuine agile software development in DoD projects, including key principles, warning signs, essential tools, and critical evaluation questions. https://engineering-leadership-preview.hinshelwood.com/videos/stop-starting-and-start-finishing-the-key-to-team-success/ Wed, 31 Jan 2024 14:26:11 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/how-usable-working-products-are-your-ultimate-weapon-against-risks/ Thu, 20 Jul 2023 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/how-usable-working-products-are-your-ultimate-weapon-against-risks/ Continuously delivering a usable working product is the most effective way to reduce risk in Agile development. Focus on releasing functional increments, fixing bugs quickly, automating tests, and keeping documentation lean to stay responsive to market needs. Prioritise regular feedback from users and stakeholders to ensure you are building what truly adds value. https://engineering-leadership-preview.hinshelwood.com/videos/how-does-a-scrum-team-decide-on-a-sprint-goal/ Fri, 02 Jun 2023 07:00:09 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/how-does-a-scrum-team-decide-on-a-sprint-goal/ A Scrum team decides on a Sprint goal through early and ongoing collaboration with stakeholders, aligning the goal with business strategy, market needs, and team capacity. The goal is crafted during Sprint planning by the product owner and developers together, ensuring it is clear, measurable, and agreed upon by all. To improve outcomes, start goal discussions before planning, maintain open communication, and make the goal visible to keep the team focused and adaptable. https://engineering-leadership-preview.hinshelwood.com/articles/the-fallacy-of-the-rejected-backlog-item/ Mon, 13 Jul 2020 08:55:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/the-fallacy-of-the-rejected-backlog-item/ Rejecting individual backlog items at the Sprint Review is a misunderstanding, since the increment is delivered as a whole and removing a single item is complex and risky. The Sprint Review is for feedback and learning, not for accepting or rejecting specific items, and any gaps should inform future backlog updates. Development managers should focus on clear communication, well-structured backlog items, and using feature flags to provide flexibility and faster feedback. https://engineering-leadership-preview.hinshelwood.com/articles/continuous-value-delivery-with-modern-business-applications/ Tue, 27 Nov 2012 23:00:35 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/continuous-value-delivery-with-modern-business-applications/ Explains how modern business applications use continuous delivery to release new features frequently, reduce risk, and improve customer satisfaction through rapid updates. https://engineering-leadership-preview.hinshelwood.com/signals/the-true-role-of-a-scrum-master-beyond-facilitation/ Tue, 25 Mar 2025 16:30:02 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/guides/scrum-guide/ Mon, 01 Feb 2010 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/guides/scrum-guide/ A clear summary of Scrum’s framework, roles, events, artefacts, and values, explaining how teams use Scrum to deliver value and adapt to complex problems. https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-delivering-working-software-every-iteration/ Wed, 26 Jun 2024 06:45:00 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/videos/what-is-your-favourite-devops-consulting-outcome/ Tue, 18 Apr 2023 07:00:08 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/what-is-your-favourite-devops-consulting-outcome/ A fragmented, multi-billion-dollar software project with 80 to 90 teams across nine countries was transformed by unifying processes and source control onto Azure DevOps, greatly improving collaboration and efficiency. The key outcomes were simplification, system unification, and a shift toward a ‘One Engineering System’ approach. Development managers should consider consolidating tools and processes to drive similar improvements in productivity and teamwork. https://engineering-leadership-preview.hinshelwood.com/signals/what-makes-an-effective-scrum-master-beyond-meeting-facilitation/ Sun, 23 Feb 2025 16:30:01 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/signals/you-want-speed-adaptability-resilience/ Sun, 11 May 2025 15:30:29 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/you-want-speed-adaptability-resilience/ Investing in Agile, Scrum, Kanban, and DevOps will not deliver real speed, adaptability, or resilience unless your teams have the agency to truly own their work and outcomes. Without empowering people to take responsibility, you risk superficial processes and disengaged teams. To achieve genuine agility, ensure your system supports team and individual ownership, not just frameworks. https://engineering-leadership-preview.hinshelwood.com/signals/let-us-be-blunt-if-a-scrum-team-isn-t-delivering-is-it-effective/ Fri, 07 Mar 2025 16:30:00 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/let-us-be-blunt-if-a-scrum-team-isn-t-delivering-is-it-effective/ A Scrum Team is only effective if it consistently delivers usable product increments; without delivery, Scrum practices are just empty rituals. The Scrum Master is accountable for enabling the team to deliver by fixing any issues that block progress. If your team is not delivering, focus on identifying and removing obstacles to restore effectiveness. https://engineering-leadership-preview.hinshelwood.com/workshops/sprint-review-1/ Tue, 17 Sep 2024 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/workshops/sprint-review-1/ Guides a 160-minute Sprint Review workshop using Liberating Structures to inspect product progress, gather feedback, and plan next steps for Scrum teams and stakeholders. https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-validation-in-product-development-a-strategic-approach/ Mon, 02 Sep 2024 15:30:15 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/the-importance-of-validation-in-product-development-a-strategic-approach/ Prioritizing features to close sales can fragment your product and lead to long-term costs that outweigh short-term gains. Shifting to a hypothesis-driven approach, where you define, track, and validate the value of new features using data, helps ensure you invest in what truly benefits users and the business. Equip product managers with the right telemetry and authority to make evidence-based decisions, and avoid building features that do not deliver measurable value. https://engineering-leadership-preview.hinshelwood.com/signals/hiring-a-scrum-master-is-hard/ Sun, 16 Feb 2025 16:30:01 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/hiring-a-scrum-master-is-hard/ Hiring a Scrum Master is challenging because many organizations misunderstand the role and focus on the wrong qualifications. A strong Scrum Master needs deep knowledge of Scrum, the ability to drive team effectiveness, and enough technical understanding to support your teams and foster change. Look for candidates who demonstrate commitment, challenge assumptions, and coach teams to deliver real value, not just those with certifications or project management backgrounds. https://engineering-leadership-preview.hinshelwood.com/articles/you-are-doing-it-wrong-if-you-are-not-using-test-first/ Mon, 07 Dec 2020 12:00:58 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/you-are-doing-it-wrong-if-you-are-not-using-test-first/ Using test-first approaches like Test Driven Development helps teams deliver software that meets customer needs, reduces maintenance costs, and prevents bugs from reaching production. Writing tests before coding ensures validation at every step, shortens feedback loops, and makes it easier and cheaper to fix issues early. To improve quality and enable confident continuous delivery, development managers should encourage their teams to adopt test-first practices. https://engineering-leadership-preview.hinshelwood.com/signals/agile-without-a-usable-working-product-is-just-expensive-theatre/ Sun, 20 Apr 2025 15:30:27 +0100 https://engineering-leadership-preview.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-preview.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-preview.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-preview.hinshelwood.com/articles/testing-in-the-modern-application-lifecycle/ Tue, 25 Sep 2012 02:00:46 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/testing-in-the-modern-application-lifecycle/ Explores challenges and solutions for manual testing in agile software development, focusing on tracking, automation, actionable bugs, and integrated test management tools. https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-continuous-delivery-how-feature-flags-transform-software-development/ Thu, 16 Jan 2025 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-continuous-delivery-how-feature-flags-transform-software-development/ Feature flags enable teams to release new features incrementally, gather user feedback early, and quickly respond to issues, supporting safer and more frequent deployments. Real-world examples like Azure DevOps show that this approach allows for controlled rollouts, continuous monitoring, and ongoing improvements based on user input. Development managers should consider adopting feature flags to improve delivery speed, reduce risk, and ensure features better meet user needs. https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-future-of-software-development-why-automation-is-your-key-to-success/ Wed, 15 Jan 2025 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-future-of-software-development-why-automation-is-your-key-to-success/ Automation is essential for faster, more reliable software development, reducing human error and enabling consistent, rapid deployments. Real-world failures like Knight Capital show the high cost of manual processes, while leading teams achieve quick, high-quality releases by building automation into every step. Development managers should prioritize automating all possible tasks to improve quality, speed, and adaptability. https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-sprint-review-workshop-and-how-will-it-help-organisations/ Fri, 30 Jun 2023 07:00:18 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-sprint-review-workshop-and-how-will-it-help-organisations/ The Sprint Review workshop helps teams align product development with stakeholder needs, adapt to market changes, and drive continuous improvement. It offers practical guidance on running effective reviews, boosting stakeholder engagement, and turning feedback into actionable improvements. Development managers should consider this workshop to enhance team performance and ensure products deliver real value. https://engineering-leadership-preview.hinshelwood.com/recipes/sprint-review-recipe/ Tue, 17 Sep 2024 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/recipes/sprint-review-recipe/ Step-by-step guide for running a Sprint Review, including presenting the increment, gathering feedback, updating the backlog, forecasting, and addressing stakeholder questions. https://engineering-leadership-preview.hinshelwood.com/articles/ndc-london-second-look-team-foundation-server-amp-vso/ Wed, 15 Oct 2014 14:49:05 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/ndc-london-second-look-team-foundation-server-amp-vso/ The speaker will present a demo-heavy session at NDC London to showcase major improvements in Team Foundation Server and Visual Studio Online since 2012, targeting developers who previously found TFS lacking. Key insights include end-to-end demonstrations of new features for agile project management, coding, testing, release, and monitoring, with scenarios covering both new features and bug fixes. Development managers should consider revisiting TFS/VSO for .NET projects and can provide feedback on which features or scenarios they want prioritized in the session. https://engineering-leadership-preview.hinshelwood.com/videos/why-more-teams-won't-speed-up-delivery-the-truth-about-scaling-effectively/ Fri, 21 Feb 2025 07:59:43 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-more-teams-won't-speed-up-delivery-the-truth-about-scaling-effectively/ Adding more teams does not automatically speed up software delivery; it often creates more dependencies, coordination overhead, and technical debt, which can slow progress. Effective scaling focuses on reducing friction, structuring teams to minimize dependencies, and prioritizing quality over quantity. Development managers should ensure teams are set up to work independently and efficiently rather than simply increasing headcount. https://engineering-leadership-preview.hinshelwood.com/articles/risk-mitigation-agile-usable-products-vs-documentation-in-traditional-project-management/ Thu, 13 Jul 2023 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/risk-mitigation-agile-usable-products-vs-documentation-in-traditional-project-management/ Delivering working software in small increments helps teams identify and address risks early, adapt to changes quickly, and get real feedback from users, while relying mainly on documentation can slow response to shifting needs. Documentation is still important, but focusing on usable products provides more value in fast-changing environments. Development managers should prioritize building and validating working software while maintaining just enough documentation to support adaptation and clarity. https://engineering-leadership-preview.hinshelwood.com/articles/dod-has-made-it-illegal-to-do-waterfall/ Tue, 01 May 2018 01:02:03 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/my-journey-into-professional-scrum/ Wed, 04 Feb 2015 10:53:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/my-journey-into-professional-scrum/ Professional Scrum has been key to my success in software development and consulting, showing that most team challenges are cultural rather than technical. Building professional, adaptable individuals and teams leads to greater business agility and consistent delivery of valuable software. Avoid one-size-fits-all approaches to scaling Scrum; instead, tailor frameworks and practices to your organisation’s unique culture and needs. https://engineering-leadership-preview.hinshelwood.com/videos/mastering-sprint-planning-key-principles-for-agile-success/ Fri, 26 May 2023 14:00:37 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/mastering-sprint-planning-key-principles-for-agile-success/ Effective Sprint planning depends on everyone understanding the product backlog and having a clear product goal, which ensures alignment, informed decisions, and true teamwork. Without these, teams risk misalignment and reduced collaboration. Make sure your team is prepared and focused on shared objectives to achieve better outcomes. https://engineering-leadership-preview.hinshelwood.com/videos/mastering-scrum-effective-planning-and-prioritisation-for-agile-success/ Fri, 24 Mar 2023 07:00:30 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/mastering-scrum-effective-planning-and-prioritisation-for-agile-success/ Effective Scrum planning and prioritisation require aligning work with business goals, regularly communicating with stakeholders, and keeping the product backlog lean and focused on near-term priorities. Use a simple value, risk, and size formula to help order backlog items, and continuously adjust based on customer data and outcomes. Keep your backlog manageable and iterate often to ensure your team delivers meaningful results that support business objectives. https://engineering-leadership-preview.hinshelwood.com/recipes/daily-scrum-recipe/ Tue, 17 Sep 2024 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/recipes/daily-scrum-recipe/ Guidance for running effective Daily Scrum meetings, focusing on collaboration, transparency, and actionable planning to help teams achieve their Sprint Goals. https://engineering-leadership-preview.hinshelwood.com/articles/the-high-of-release/ Sat, 05 Dec 2015 14:49:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/the-high-of-release/ Microsoft’s new web-based Release Management tools let teams build flexible, integrated release pipelines in VSTS or TFS without being locked into specific deployment tools. The focus is on orchestration and integration, allowing you to use your preferred technologies like Chef, Puppet, Docker, or PowerShell. These tools are now in public preview, so consider evaluating them to streamline your release process and support cloud or on-premises deployments. https://engineering-leadership-preview.hinshelwood.com/articles/create-a-release-management-pipeline-for-professional-developers/ Thu, 04 Dec 2014 12:15:56 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/create-a-release-management-pipeline-for-professional-developers/ This guide walks through setting up an automated release management pipeline using TFS/VSO and Azure, showing how to build, deploy, and parameterize a legacy web app across multiple feedback environments. Key takeaways include the importance of automating builds and releases, using environment-specific parameters, and streamlining approvals for smoother deployments. Development managers should consider investing time upfront to automate and parameterize their pipelines, as this reduces manual errors and accelerates feedback cycles. https://engineering-leadership-preview.hinshelwood.com/videos/who-should-lead-the-sprint-review-unpacking-the-role-of-the-product-owner-in-agile-success/ Wed, 06 Sep 2023 07:00:15 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/who-should-lead-the-sprint-review-unpacking-the-role-of-the-product-owner-in-agile-success/ The Product Owner should lead the Sprint Review because they are accountable for maximising value and are best positioned to gather insights from stakeholders. The review should focus on aligning everyone on the product vision, showcasing progress, encouraging feedback, and updating the product backlog with new information. Development managers should ensure the Product Owner leads this process and experiment with review formats to keep the backlog relevant and guide the team’s next steps. https://engineering-leadership-preview.hinshelwood.com/signals/scrum-master-effectiveness-begins-with-consistent-delivery/ Thu, 06 Mar 2025 16:30:29 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/scrum-master-effectiveness-begins-with-consistent-delivery/ Scrum Master effectiveness depends on ensuring teams deliver something every sprint, as delivery enables feedback and improvement. Without delivery, there is no basis for learning or adding value. Development managers should prioritize consistent delivery as the foundation for team effectiveness and continuous improvement. https://engineering-leadership-preview.hinshelwood.com/videos/are-your-teams-empowered-to-change-requirements-based-on-user-feedback-if-not-you-re-probably-not-very-agile/ Wed, 17 Jul 2024 06:45:01 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/are-your-teams-empowered-to-change-requirements-based-on-user-feedback-if-not-you-re-probably-not-very-agile/ Empowering teams to update or delete requirements based on user feedback is essential for true agility and delivering maximum value. Regularly engaging with the product team, keeping the backlog dynamic, and being willing to pivot or remove features ensures your product stays relevant and user-focused. Review your processes to make sure your teams have the authority and support to make these changes. https://engineering-leadership-preview.hinshelwood.com/articles/sprint-goal-is-an-immediate-tactical-goal/ Mon, 11 Jan 2021 14:36:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/sprint-goal-is-an-immediate-tactical-goal/ The Sprint Goal should be a clear, high-level statement that explains the purpose of the Sprint and connects directly to the Product Goal, guiding the team’s immediate tactical efforts. Product Owners should use tools like Lean Canvas to define business objectives and user behaviors, formulating hypotheses with measurable outcomes to maximize value. Focus on solving users’ current problems and iteratively anticipate their needs to drive engagement and deliver impactful features. https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/signals/design-sprints-in-scrum-common-questions-and-practical-insights/ Wed, 04 Jun 2025 15:31:05 +0100 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/there-is-no-place-like-production/ Mon, 28 Dec 2020 14:12:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/there-is-no-place-like-production/ To deliver real value and reduce risk, teams must release features to production quickly so real users can provide feedback, since assumptions and testing environments cannot replace actual usage. Key measures like customer satisfaction, product usage, and employee satisfaction help validate value, and releasing early also offers financial benefits through capital expenditure write-downs. Prioritize getting small increments into production to maximize learning, value, and organizational savings. https://engineering-leadership-preview.hinshelwood.com/videos/balancing-speed-and-stability-why-quality-should-always-come-first-in-delivery-management/ Fri, 24 Jan 2025 06:30:21 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/balancing-speed-and-stability-why-quality-should-always-come-first-in-delivery-management/ Rushing to meet deadlines often leads to poor-quality products that can damage your brand and erode customer trust, so prioritising stability and quality is essential even if it means missing deadlines or incurring fines. The long-term costs of sacrificing quality far outweigh any short-term gains from speed, as seen in real-world cases like Zoom. Development managers should educate stakeholders about these risks and always choose quality over speed to protect both reputation and customer relationships. https://engineering-leadership-preview.hinshelwood.com/guides/nexus-guide/ Tue, 17 Sep 2024 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/guides/nexus-guide/ Explains the Nexus framework for scaling Scrum with multiple teams, detailing roles, events, and artefacts to coordinate product delivery and manage cross-team dependencies. https://engineering-leadership-preview.hinshelwood.com/videos/mastering-the-art-of-scaling-agile-strategies-to-maintain-agility-across-multiple-teams/ Wed, 26 Feb 2025 06:00:08 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/mastering-the-art-of-scaling-agile-strategies-to-maintain-agility-across-multiple-teams/ Scaling agile across multiple teams introduces complexity and risks slowing down delivery, so it is crucial to choose a scaling approach that fits your organisation’s unique context. Key to success are mapping dependencies, proactively addressing communication pitfalls, and maintaining speed in delivering value as you grow. Consider a tailored, hands-on strategy to preserve agility and empower your teams as you scale. https://engineering-leadership-preview.hinshelwood.com/videos/the-synergy-between-product-management-and-product-development-in-agile-environments/ Thu, 25 Jul 2024 06:45:02 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/the-synergy-between-product-management-and-product-development-in-agile-environments/ Product Management and Product Development must work closely together in agile environments to deliver products that meet current and future market needs. Product Management sets the vision and strategy, while Product Development brings these ideas to life through innovation, quality, and fast delivery, with both functions relying on continuous feedback and improvement. Development managers should ensure strong collaboration and feedback loops between these teams to maximize product value and long-term success. https://engineering-leadership-preview.hinshelwood.com/articles/sculpting-the-product-backlog-a-delicate-balance-between-lean-inventory-and-future-readiness/ Thu, 24 Aug 2023 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/sculpting-the-product-backlog-a-delicate-balance-between-lean-inventory-and-future-readiness/ Keep your product backlog minimal but sufficient, ensuring it is clear and transparent for all stakeholders while also considering future needs to avoid surprises. Regularly review and reflect on completed work and unexpected issues to refine your backlog and adapt to changing circumstances. Aim for a balance that supports both current priorities and readiness for what lies ahead. https://engineering-leadership-preview.hinshelwood.com/videos/mastering-product-backlog-management-essential-skills-for-product-owners/ Mon, 18 Dec 2023 07:00:15 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/mastering-product-backlog-management-essential-skills-for-product-owners/ Effective product backlog management is critical for delivering value, and product owners remain accountable even when delegating tasks. Focus on managing risk, maximizing value, sizing items for quick delivery, and embracing learning through iteration; regular refinement and clear communication with the team and stakeholders are essential. Review your backlog often, break down large or risky items, and seek help if needed to ensure your team delivers the right outcomes efficiently. https://engineering-leadership-preview.hinshelwood.com/videos/7-deadly-sins-of-agile-gluttony/ Wed, 11 Oct 2023 11:35:09 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/videos/navigating-complexity-why-agile-practices-are-essential-for-modern-product-development/ Fri, 07 Oct 2022 10:41:41 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/navigating-complexity-why-agile-practices-are-essential-for-modern-product-development/ Agile practices are essential for modern product development because they help teams deliver value faster and adapt to constant change, unlike traditional methods that struggle with today’s complexity. Key insights include the unpredictability of requirements, technology, and people, and the importance of delivering working products regularly to reduce risk and waste. Development managers should focus on adopting agile approaches to improve responsiveness and ensure products better meet customer needs. https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/videos/what-should-be-top-of-mind-when-a-scrum-team-prepare-for-a-sprint-review/ Mon, 04 Sep 2023 07:00:13 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/what-should-be-top-of-mind-when-a-scrum-team-prepare-for-a-sprint-review/ To get the most out of Sprint reviews, focus on engaging stakeholders by understanding their priorities, communicating value in clear and relevant terms, and encouraging active participation. Regular check-ins, feedback loops, and making information accessible to all stakeholders help build stronger relationships and increase involvement. Make Sprint reviews a collaborative opportunity rather than just a technical update to drive better outcomes and transparency. https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/videos/what-is-sprint-planning/ Wed, 24 May 2023 14:00:36 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/what-is-sprint-planning/ Sprint planning is a team meeting to align on what will be accomplished in the next sprint, ensuring everyone understands the goals and priorities, including new features, technical debt, and unexpected work. It provides clarity, flexibility, and a shared sense of direction, whether you use Scrum or Kanban. Make sure your team uses sprint planning to regularly evaluate priorities and maintain alignment for better outcomes. https://engineering-leadership-preview.hinshelwood.com/guides/manifesto-for-agile-software-development/ Tue, 17 Sep 2024 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/guides/manifesto-for-agile-software-development/ Outlines core Agile values and principles for software development, emphasising collaboration, adaptability, working software, customer focus, and continuous improvement. https://engineering-leadership-preview.hinshelwood.com/videos/transform-your-product-development-unleash-the-power-of-experimentation-and-collaboration/ Sun, 11 Aug 2024 22:00:33 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/transform-your-product-development-unleash-the-power-of-experimentation-and-collaboration/ This course teaches development managers how to boost user value and ROI by using experimentation, agile practices, and better collaboration with stakeholders. Key outcomes include reducing waste, speeding up time-to-market, and unlocking creative solutions by focusing on real problems. Consider applying these methods to streamline your process, make data-driven decisions, and deliver higher-impact products. https://engineering-leadership-preview.hinshelwood.com/videos/transforming-scope-creep-into-success-embrace-agility-and-deliver-value-in-a-changing-market/ Wed, 04 Dec 2024 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/transforming-scope-creep-into-success-embrace-agility-and-deliver-value-in-a-changing-market/ Scope creep is often a sign that traditional fixed-scope approaches are failing in today’s fast-changing market. Focusing on delivering customer value, embracing flexible planning, and actively seeking feedback helps teams adapt and succeed. Development managers should shift from rigid scope management to Agile practices that prioritize value and responsiveness to change. https://engineering-leadership-preview.hinshelwood.com/videos/why-agile-success-relies-on-effective-planning-debunking-the-myths-of-scrum/ Wed, 25 Oct 2023 13:30:11 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-agile-success-relies-on-effective-planning-debunking-the-myths-of-scrum/ Effective planning is essential for Agile and Scrum teams, not something to skip; key Scrum events like sprint planning, backlog refinement, and daily standups all revolve around planning. The goal is to find the right balance, plan enough to provide direction and coordination, especially in large teams, but avoid over-planning that wastes resources. Development managers should ensure their teams have clear goals, roadmaps, and themes to align efforts and adapt as needed. https://engineering-leadership-preview.hinshelwood.com/signals/the-fbi-sentinel-project-was-textbook-waterfall/ Wed, 11 Jun 2025 15:30:44 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/the-fbi-sentinel-project-was-textbook-waterfall/ The FBI’s Sentinel project failed after years and massive spending using a traditional waterfall approach, delivering nothing. Switching to a small, focused Agile team produced a working product in a year at a fraction of the cost. Consider adopting iterative methods to avoid wasted time and resources and deliver real value sooner. https://engineering-leadership-preview.hinshelwood.com/guides/kanban-guide/ Thu, 01 May 2025 00:00:00 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/signals/scrum-is-built-on-empiricism-transparency-inspection-and-adaptation/ Mon, 24 Feb 2025 16:30:29 +0000 https://engineering-leadership-preview.hinshelwood.com/signals/scrum-is-built-on-empiricism-transparency-inspection-and-adaptation/ Scrum relies on delivering a usable product increment every sprint, and if this does not happen, the team is not truly practicing Scrum. The Scrum Master is accountable for ensuring an environment where delivery is consistent and inevitable, with no excuses for missed increments. Development managers should ensure their Scrum Masters take ownership of delivery and address any barriers to producing usable increments each sprint. https://engineering-leadership-preview.hinshelwood.com/articles/quality-enablement-with-visual-studio-2012/ Wed, 15 May 2013 03:13:20 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/quality-enablement-with-visual-studio-2012/ Explores how Visual Studio 2012 supports continuous quality enablement, automated testing, and rapid delivery in modern software development for higher user satisfaction. https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-foundations-in-alameda-california/ Fri, 26 Oct 2012 16:30:24 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/professional-scrum-foundations-in-alameda-california/ Covers a two-day, hands-on Scrum.org course in Alameda, teaching Scrum principles, teamwork, and practical software delivery for all roles in the development process. https://engineering-leadership-preview.hinshelwood.com/articles/what's-in-a-burndown/ Wed, 28 Mar 2012 03:52:22 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/what's-in-a-burndown/ Explains burndown charts in Scrum, their purpose, common issues, and compares tracking by hours, story points, and acceptance tests to improve team progress visibility. https://engineering-leadership-preview.hinshelwood.com/articles/my-first-scrum-team-in-the-wild/ Sun, 03 Apr 2011 21:44:22 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/my-first-scrum-team-in-the-wild/ A real-world account of guiding a new Scrum team through their first sprint, covering estimation, story points, sprint planning, and handling unfinished work. https://engineering-leadership-preview.hinshelwood.com/videos/the-evolution-of-product-management-in-the-agile-era/ Thu, 18 Jul 2024 06:45:01 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/the-evolution-of-product-management-in-the-agile-era/ Agile product management replaces long release cycles with short, frequent delivery, enabling faster feedback, reduced risk, and more responsive adaptation to customer needs. Building quality in from the start and using practices like continuous integration and a clear definition of done minimizes defects and waste. Development managers should focus on shorter cycles, continuous feedback, and embedding quality throughout the process to stay competitive and maximize business value. https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-most-common-mistake-in-sprint-planning/ Thu, 25 May 2023 14:00:20 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/what-is-the-most-common-mistake-in-sprint-planning/ The most common mistake in sprint planning is failing to define a clear and tangible sprint goal, which is essential for guiding the team’s immediate work and connecting it to the broader product vision. A well-defined sprint goal provides focus, enables actionable stakeholder feedback, and helps the team understand and meet expectations. Development managers should ensure every sprint has a concrete goal that can be evaluated at the sprint review to drive progress and alignment. https://engineering-leadership-preview.hinshelwood.com/articles/standard-environments-for-automated-deployment-and-testing/ Sun, 17 Mar 2013 06:23:45 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/standard-environments-for-automated-deployment-and-testing/ Explains how to set up and use Standard Environments in Visual Studio 2012 TFS for automated software deployment and testing, enabling consistent, repeatable pipelines. https://engineering-leadership-preview.hinshelwood.com/articles/automated-testing-in-a-modern-application-lifecycle/ Tue, 25 Sep 2012 04:33:30 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/automated-testing-in-a-modern-application-lifecycle/ Explains the role of automated testing in modern software development, covering types, integration, benefits, challenges, and tools for maintaining code quality. https://engineering-leadership-preview.hinshelwood.com/articles/hiring-a-professional-product-owner/ Mon, 17 May 2021 14:17:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/hiring-a-professional-product-owner/ Hiring a professional Product Owner is increasingly valued, with companies seeking external candidates who bring fresh perspectives and strong business understanding. The Product Owner is accountable for maximizing product value by setting vision, managing stakeholders, collaborating with teams, making key decisions, and using evidence-based approaches to drive outcomes. Ensure candidates have both certification and practical experience, but remember that while responsibilities can be delegated, ultimate accountability always remains with the Product Owner. https://engineering-leadership-preview.hinshelwood.com/videos/does-kanban-integrate-into-a-scrum-environment/ Thu, 15 Feb 2024 07:00:31 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/does-kanban-integrate-into-a-scrum-environment/ Kanban can be integrated with Scrum to improve workflow visibility, provide essential metrics like cycle time and throughput, and support continuous improvement. This combination helps teams answer key delivery questions and identify bottlenecks that Scrum alone may not address. Development managers should consider adding Kanban practices and metrics to their Scrum teams to optimize performance and make more informed decisions. https://engineering-leadership-preview.hinshelwood.com/articles/navigating-the-future-with-a-fine-tuned-product-backlog/ Thu, 10 Aug 2023 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/navigating-the-future-with-a-fine-tuned-product-backlog/ A well-ordered and regularly refined Product Backlog is essential for guiding teams toward delivering customer value, as it ensures everyone understands priorities and next steps. Key practices include clear articulation, ongoing refinement, and sizing of backlog items, which help teams focus on the most valuable work and align with strategic goals. Development managers should prioritize maintaining a transparent and evolving backlog to support effective planning and value delivery. https://engineering-leadership-preview.hinshelwood.com/videos/bridging-the-gap-how-to-align-your-organisation-for-successful-agile-product-management/ Mon, 06 May 2024 13:29:40 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/bridging-the-gap-how-to-align-your-organisation-for-successful-agile-product-management/ Successfully adopting agile product management requires more than dropping old project management methods; organisations must clearly define and communicate a shared vision, focus on delivering real value, and validate progress with the right metrics. Engaging all teams and stakeholders in the goal-setting process and using evidence-based and hypothesis-driven approaches are key to aligning efforts and maximising value. Development managers should prioritise cross-team collaboration and ensure everyone understands and is invested in the common objective to achieve better outcomes. https://engineering-leadership-preview.hinshelwood.com/videos/overview-of-'applying-metrics-for-predictability'-kanban-course/ Tue, 20 Feb 2024 07:00:27 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/overview-of-'applying-metrics-for-predictability'-kanban-course/ The “Applying Metrics for Predictability” Kanban course teaches teams how to use key Kanban metrics and probabilistic forecasting to improve delivery predictability, enabling more accurate planning and increased stakeholder trust. Participants learn to interpret data, identify bottlenecks, and make informed decisions that drive efficiency and consistent value delivery. Development managers whose teams struggle with predictability should consider this course to enhance forecasting and workflow reliability. https://engineering-leadership-preview.hinshelwood.com/signals/in-scrum-we-don-t-do-ux-separately/ Thu, 12 Jun 2025 15:30:39 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/in-scrum-we-don-t-do-ux-separately/ UX should be integrated into regular Scrum work, not handled in separate sprints or phases. Design and validation should happen continuously alongside development to support the Sprint Goal and future planning. Managers should ensure UX is part of the team’s ongoing workflow to improve learning and delivery speed. https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-superpower-of-software-development-how-shifting-left-transforms-quality-assurance/ Fri, 22 Nov 2024 14:04:14 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-the-superpower-of-software-development-how-shifting-left-transforms-quality-assurance/ Shifting quality assurance to the start of the development process leads to higher product quality, faster delivery, and lower costs by catching issues early and fostering better collaboration. Teams that adopt this approach see improved morale and stakeholder confidence. To get started, educate your team, involve QA early, encourage collaboration, use automation, and focus on continuous improvement. https://engineering-leadership-preview.hinshelwood.com/videos/product-ownership-vs-product-management-busting-the-myth-that-they're-separate-roles/ Thu, 01 Aug 2024 06:45:01 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/product-ownership-vs-product-management-busting-the-myth-that-they're-separate-roles/ Product ownership and product management are not separate roles; effective product ownership is a form of product management focused on maximizing value in short, iterative cycles. Organizations should avoid diluting the product owner role with unrelated tasks and instead ensure alignment with strategic goals and market needs. Development managers should treat product ownership as a core accountability within product management, prioritize value delivery, and foster adaptability to stay competitive. https://engineering-leadership-preview.hinshelwood.com/videos/maximise-your-scrum-process-leveraging-azure-devops-for-agile-success/ Wed, 03 Apr 2024 17:21:43 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/maximise-your-scrum-process-leveraging-azure-devops-for-agile-success/ Azure DevOps can be customised to effectively support Scrum by focusing on simple, value-driven backlogs and adapting processes like area and iteration paths to fit your team’s structure and workflow. Metrics and common agile tools are optional, so tailor your setup to your team’s needs rather than following defaults. Use Azure DevOps features like tagging, board views, and backlog management to streamline refinement, planning, and execution, and regularly review and improve your processes for better results. https://engineering-leadership-preview.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-preview.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-preview.hinshelwood.com/articles/why-should-i-use-visual-studio-alm/ Wed, 07 Jan 2015 15:39:20 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/why-should-i-use-visual-studio-alm/ Visual Studio ALM offers a comprehensive set of features beyond just source control and build, covering requirements, project, change, quality, feedback, defect, release, and analytics management in one integrated platform. Replacing it with tools like Git and Jenkins means losing most of this functionality and facing significant integration and maintenance challenges. Development managers should carefully assess what capabilities they need and consider the long-term effort required to replicate Visual Studio ALM’s end-to-end support before switching tools. https://engineering-leadership-preview.hinshelwood.com/articles/create-a-standard-environment-for-release-management-in-azure/ Thu, 04 Dec 2014 11:30:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/create-a-standard-environment-for-release-management-in-azure/ Setting up a standard release management environment in Azure is straightforward, cost-effective, and closely mirrors on-premises setups by using VMs, resource groups, and Application Insights for analytics. Using the old Azure portal gives better control over naming and resource organization, while Azure’s flexibility allows quick scaling and isolation for multiple environments. Development managers should consider scripting environment setup for repeatability and use Application Insights to track application usage and feedback. https://engineering-leadership-preview.hinshelwood.com/articles/execute-tests-with-release-management-for-visual-studio-2013/ Mon, 27 Jan 2014 11:29:14 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/execute-tests-with-release-management-for-visual-studio-2013/ Learn how to automate test execution during deployments using Release Management for Visual Studio 2013, including setup steps, environment tips, and common issues. https://engineering-leadership-preview.hinshelwood.com/articles/scrum-is-hard-to-adopt-and-disruptive-to-your-organisation/ Thu, 22 Sep 2011 01:17:15 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/scrum-is-hard-to-adopt-and-disruptive-to-your-organisation/ Explains why adopting Scrum is challenging and disruptive, highlighting the need for training, mentoring, and dedication for successful organisational change and Agile adoption. https://engineering-leadership-preview.hinshelwood.com/articles/how-visual-studio-2010-and-team-foundation-server-enable-compliance/ Wed, 09 Feb 2011 22:04:04 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/how-visual-studio-2010-and-team-foundation-server-enable-compliance/ Explains how Visual Studio 2010 and Team Foundation Server support compliance by enabling traceability, audit trails, and linking code changes to requirements and tests. https://engineering-leadership-preview.hinshelwood.com/videos/mastering-prioritisation-how-product-owners-can-drive-value-and-accountability/ Mon, 27 Nov 2023 11:00:56 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/mastering-prioritisation-how-product-owners-can-drive-value-and-accountability/ Product Owners play a crucial role in ensuring resources are spent wisely by prioritising the most valuable work, aligning development with business goals, and maintaining stakeholder trust through clear communication. Effective prioritisation maximises value delivery, keeps teams focused, and adapts to changing needs. Development managers should support Product Owners in understanding users, collaborating closely, and staying flexible to drive successful outcomes. https://engineering-leadership-preview.hinshelwood.com/videos/temperance-in-agile-why-less-is-more/ Tue, 05 Dec 2023 07:00:10 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/signals/too-many-organisations-hide-behind-excuses/ Sat, 07 Jun 2025 15:30:25 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/too-many-organisations-hide-behind-excuses/ Even large, regulated, and traditionally slow organizations like the DOD and FBI have successfully adopted iterative delivery, showing that excuses for not embracing agile are unfounded. Agile helps reduce risk, increase flexibility, and deliver value incrementally, which is especially important in regulated industries. Development managers should challenge resistance and prioritize agile practices to improve outcomes regardless of organizational constraints. https://engineering-leadership-preview.hinshelwood.com/videos/how-to-overcome-agile-banditry-a-product-owner-s-journey/ Wed, 10 Jan 2024 07:00:11 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/how-to-overcome-agile-banditry-a-product-owner-s-journey/ Product Owners who micromanage and focus on rigid task planning undermine team engagement and product success. Shifting to a focus on vision, value, and outcomes while empowering teams leads to higher motivation, better collaboration, and improved results. Development managers should encourage Product Owners to let go of detailed control, trust their teams, and prioritize clear goals and customer value. https://engineering-leadership-preview.hinshelwood.com/articles/deployment-documentation/ Mon, 23 Jul 2007 11:13:53 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/deployment-documentation/ Outlines steps to document and improve deployment for a complex business app, focusing on automation, rollback, vendor updates, and multi-environment management. https://engineering-leadership-preview.hinshelwood.com/videos/understanding-the-power-of-kanban-in-scrum/ Mon, 05 Aug 2024 06:45:00 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/videos/understanding-kanban-a-tool-for-transparency-and-continuous-improvement/ Mon, 24 Jun 2024 06:48:02 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/how-to-set-and-achieve-effective-sprint-goals/ Fri, 29 Sep 2023 12:12:59 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/how-to-set-and-achieve-effective-sprint-goals/ Sprint Goals are essential for guiding teams toward delivering real value each Sprint, acting as a clear commitment that balances detail and big-picture alignment. Effective Sprint Goals are collaboratively crafted, reviewed by stakeholders, and should be specific, measurable, and relevant to the product vision. Development managers should ensure their teams focus on creating meaningful Sprint Goals that drive value and accountability, using frameworks like SMART or OKR as needed. https://engineering-leadership-preview.hinshelwood.com/recipes/sprint-planning-recipe/ Tue, 17 Sep 2024 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/recipes/sprint-planning-recipe/ Step-by-step guide to effective Sprint Planning in Scrum, covering goal setting, backlog selection, team capacity, actionable plans, and clear communication with stakeholders. https://engineering-leadership-preview.hinshelwood.com/videos/how-critical-is-a-product-owner-in-developing-a-great-product-backlog/ Wed, 31 May 2023 07:00:05 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/how-critical-is-a-product-owner-in-developing-a-great-product-backlog/ A strong product owner is essential for creating and maintaining a focused, valuable product backlog that aligns with strategy and avoids becoming an unmanageable list of requests. The product owner is fully responsible for prioritizing and communicating the backlog, using discernment to filter out items that do not support the product vision. Development managers should ensure their product owners are empowered and proactive to keep teams focused on delivering real value. https://engineering-leadership-preview.hinshelwood.com/articles/the-product-goal-is-a-commitment-for-the-product-backlog/ Mon, 23 Nov 2020 14:01:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/the-product-goal-is-a-commitment-for-the-product-backlog/ The Product Goal is a clear, measurable long-term objective in the Product Backlog that guides the Scrum Team’s focus and progress. It should be understood by everyone involved, align Sprint Goals, and can be changed if it no longer delivers value. Development managers should ensure their teams have a well-defined Product Goal to drive alignment and transparency. https://engineering-leadership-preview.hinshelwood.com/videos/why-'definition-of-done'-is-crucial-for-success-in-scrum/ Tue, 14 Nov 2023 07:00:30 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-'definition-of-done'-is-crucial-for-success-in-scrum/ The Definition of Done sets clear quality standards for all work, ensuring every deliverable meets your organization’s expectations regardless of the specific feature or project. It aligns teams, reduces defects, and protects your brand by making sure nothing is released before it is truly ready. Regularly review and adapt your Definition of Done with your team to maintain high quality and customer satisfaction. https://engineering-leadership-preview.hinshelwood.com/articles/rethinking-'user-stories'-a-call-for-clarity-in-product-backlog-management/ Thu, 31 Aug 2023 13:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/rethinking-'user-stories'-a-call-for-clarity-in-product-backlog-management/ The author argues that using the term “User Stories” for all work items leads to confusion and unnecessary complexity, as not all tasks fit this format. Switching to a more generic term like “Product Backlog Item” allows teams to describe work more clearly and flexibly, improving communication and transparency. Development managers should consider updating their backlog terminology to better reflect the true nature of their work and support more effective product development. https://engineering-leadership-preview.hinshelwood.com/tags/sprint-review/ Sun, 11 May 2025 10:17:24 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/increment/ Mon, 05 May 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/increment/ Increment refers to the tangible, usable output produced at the end of each iteration, particularly within frameworks like Scrum and Agile. It encapsulates the totality of completed work during a Sprint, ensuring that the product remains potentially shippable and consistently adds measurable value. As a core artifact in Scrum, the Increment embodies the principle of delivering working software incrementally, which facilitates timely feedback, iterative improvements, and mitigates the risks associated with large-scale releases. Its significance lies in the transparency it provides, allowing teams and stakeholders to assess progress clearly, thereby fostering collaboration and alignment. In Agile environments, the Increment serves as a foundation for adaptation, enabling teams to refine their strategies based on feedback and respond effectively to evolving requirements. By prioritising the delivery of increments, organisations can enhance workflows, promote continuous improvement, and ensure that products develop in alignment with customer needs. This focus on delivering working software helps minimise technical debt and prevents over-engineering, aligning development efforts more closely with business objectives. Ultimately, the Increment delivers the concrete, inspectable output that informs decision-making and enhances collaboration, making it a vital component of Agile and Scrum practices. https://engineering-leadership-preview.hinshelwood.com/tags/product-backlog/ Mon, 05 May 2025 10:17:24 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/site-reliability-engineering/ Mon, 05 May 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/site-reliability-engineering/ Site Reliability Engineering (SRE) is a discipline that utilises software engineering principles to develop scalable and reliable systems, effectively bridging the gap between development and operations. Originating from the need to embed reliability within the software development lifecycle, SRE ensures that systems maintain functionality and resilience under diverse conditions. This methodology prioritises automation, monitoring, and incident response, which allows teams to deliver consistent value in a sustainable manner. SRE teams establish service level objectives (SLOs) and service level indicators (SLIs) to create clear performance and reliability metrics, fostering a culture of accountability and continuous improvement. This proactive approach to problem-solving and engineering solutions to operational challenges enhances overall system performance, distinguishing SRE from traditional operations roles. By promoting shared responsibility for reliability across teams, SRE encourages collaboration and knowledge sharing, which not only improves user satisfaction but also drives positive business outcomes. Ultimately, the integration of reliability into the development process supports organisational strategic goals and enhances competitive advantage, making SRE a vital component in agile, DevOps, and product development frameworks. https://engineering-leadership-preview.hinshelwood.com/tags/definition-of-done/ Mon, 05 May 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/definition-of-done/ The Definition of Done (DoD) is a critical framework that establishes a shared understanding of what constitutes a completed and releasable product increment within agile and DevOps environments. Originating from the need for clarity in product development, the DoD serves as an organisational standard that all teams must adhere to, ensuring that every increment meets minimum quality criteria before it can be considered complete. This framework is vital for fostering transparency and consistency across teams, enabling empirical decision-making based on real-world feedback. By defining specific criteria, such as deployment in production, telemetry collection, and validation of initial hypotheses, the DoD helps mitigate risks associated with incomplete or subpar work, thereby reducing technical debt and enhancing the overall quality of deliverables. Furthermore, it facilitates faster feedback loops and iterative learning, allowing teams to adapt their processes based on actual performance data. The DoD not only clarifies expectations for stakeholders but also protects the integrity of the product, ensuring that increments are valuable, verifiable, and ready for real-world use. In essence, the Definition of Done is foundational to maintaining high standards in product development, promoting alignment among teams, and ultimately driving successful outcomes in organisational design and delivery. https://engineering-leadership-preview.hinshelwood.com/tags/lead-time/ Fri, 11 Apr 2025 06:00:00 +0100 https://engineering-leadership-preview.hinshelwood.com/tags/lead-time/ Lead Time is an essential observability metric that quantifies the duration from the initiation of a work item to its delivery to the customer. It is a practical implementation of Cycle Time often used in flow-based systems such as Kanban. This metric provides end-to-end visibility into workflow performance, helping teams identify inefficiencies and optimise delivery for improved predictability and responsiveness. By exposing how long it takes to deliver value, Lead Time enables real-time insight into system health and team effectiveness, supporting continuous improvement across Agile, Lean, and DevOps environments. https://engineering-leadership-preview.hinshelwood.com/tags/time-to-market/ Thu, 10 Apr 2025 14:20:01 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/github/ Thu, 10 Apr 2025 10:16:54 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/github/ GitHub is a comprehensive platform that facilitates version control, collaboration, and integration within software development. Originating as a hosting service for Git repositories, it has evolved to include features such as GitHub Actions for automating continuous integration and continuous delivery workflows, and GitHub Projects for task management and progress tracking. Its significance lies in its ability to enhance collaboration among development teams, reduce friction in development cycles, and support the efficient delivery of value. GitHub is essential for organisations seeking to maintain transparency and integrate workflows between development and operations teams, as its integration with CI/CD practices allows for the automation of testing, builds, and deployments, ensuring continuous validation and delivery of code changes. The platform’s features, including issues, pull requests, and discussions, foster effective communication and alignment on project goals. Additionally, GitHub’s compatibility with a variety of third-party tools and services further amplifies its effectiveness in modern DevOps environments. By utilising GitHub’s extensive toolset, organisations can enhance team collaboration, streamline development processes, and improve software delivery outcomes. https://engineering-leadership-preview.hinshelwood.com/tags/throughput/ Wed, 09 Apr 2025 14:41:23 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/common-goals/ Fri, 21 Mar 2025 14:45:01 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/continuous-delivery/ Fri, 21 Mar 2025 13:37:32 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/continuous-delivery/ Continuous Delivery is a software delivery practice that focuses on producing software in short, reliable cycles, enabling teams to release updates at any time. Originating from the need for more efficient and responsive software development processes, it involves delivering small, incremental improvements directly to users from the initial stages of development. This approach, as defined by Jez Humble, emphasises the ability to safely and quickly implement changes, such as new features, configuration adjustments, and bug fixes, into production. The importance of Continuous Delivery lies in its capacity to facilitate rapid validation of assumptions and collection of user feedback, which are crucial for refining products and achieving valuable outcomes. By automating essential processes like testing, integration, and deployment, Continuous Delivery not only mitigates the risk of errors but also enhances software quality and accelerates the time it takes to deliver value to users. Teams that adopt this practice can more effectively respond to market demands and stakeholder input, thereby fostering a culture of continuous learning, innovation, and adaptability within their organisations. https://engineering-leadership-preview.hinshelwood.com/tags/agile-product-operating-model/ Fri, 21 Mar 2025 09:30:34 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/categories/devops/ Thu, 20 Mar 2025 11:04:38 +0000 https://engineering-leadership-preview.hinshelwood.com/categories/devops/ DevOps is a philosophy that integrates people, processes, and technology to facilitate continuous value delivery in software development. Originating from the need to bridge the gap between development and operations, it emphasises collaboration and automation to enhance the quality and speed of software delivery. The core principles of DevOps prioritise flow efficiency over mere resource utilisation, advocate for rapid feedback loops to align with customer needs, and promote automation to minimise errors and delays. Additionally, it fosters shared accountability among developers, operations, and security teams, ensuring collective responsibility for product quality. DevOps encourages a culture of continuous improvement, where teams are committed to experimentation and adaptation. In practice, organisations embracing DevOps focus on eliminating silos, integrating quality and security measures early in the development process, leveraging data for informed decision-making, and automating as many processes as possible. This approach is crucial in agile and DevOps environments as it enables organisations to deliver software more reliably and efficiently, ultimately enhancing their ability to respond to market demands and customer expectations. DevOps is viewed not as a final goal but as an ongoing journey towards improved software delivery. https://engineering-leadership-preview.hinshelwood.com/tags/shift-left-strategy/ Mon, 17 Mar 2025 14:46:11 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/shift-left-strategy/ The Shift-Left Strategy is a proactive approach in modern software development that emphasises the integration of testing, security, and compliance activities early in the development lifecycle, rather than deferring them to the end. Originating from the need to mitigate risks associated with late-stage defect detection, this strategy allows teams to identify and address issues sooner, thereby reducing the amount of rework required and accelerating feedback loops. By implementing practices such as automated testing, security as code, and continuous integration, organisations can enhance software quality and reliability from the outset. This approach is particularly valuable in agile and DevOps environments, where rapid delivery and high performance are critical. Ultimately, the Shift-Left Strategy fosters a culture of quality and efficiency, ensuring that products are not only delivered faster but also meet the necessary standards for security and compliance, making it an essential component of effective organisational design and product development. https://engineering-leadership-preview.hinshelwood.com/categories/scrum/ Tue, 04 Mar 2025 10:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/categories/scrum/ Scrum is a framework and social technology designed to facilitate the delivery of adaptive solutions in complex environments, grounded in the principles of empiricism, which emphasises transparency, inspection, and adaptation. Originating from the need to manage complex projects effectively, Scrum enables teams to work collaboratively and self-organise to tackle intricate problems while delivering high-value products iteratively and incrementally. Its significance lies in its structured approach to product development, which fosters continuous improvement and value-based prioritisation through defined roles, events, and artifacts. The framework encourages commitment, focus, openness, respect, and courage among team members, promoting a culture of collaboration and accountability. Scrum’s iterative development process, characterised by time-boxed sprints, allows teams to produce potentially releasable increments of work regularly, optimising predictability and minimising risks. As organisations increasingly adopt agile methodologies and DevOps practices, Scrum’s principles and practices become invaluable for enhancing team dynamics, improving product quality, and responding swiftly to changing market demands, ultimately driving organisational success in a fast-paced environment. https://engineering-leadership-preview.hinshelwood.com/tags/internal-developer-platform/ Mon, 24 Feb 2025 13:04:45 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/internal-developer-platform/ An Internal Developer Platform (IDP) is a unified environment designed to enhance the development lifecycle by enabling teams to efficiently build, test, and deploy applications. Originating from the need to simplify infrastructure management and application dependencies, an IDP allows developers to concentrate on delivering value rather than dealing with operational challenges. This platform cultivates a collaborative and innovative culture, empowering teams to experiment and iterate quickly within a structured framework. By embedding best practices into the development process, an IDP promotes reliability and predictability in software delivery. It also facilitates continuous integration and continuous delivery (CI/CD) practices, which are vital for maintaining competitiveness in rapidly evolving markets. By automating repetitive tasks and standardising workflows, an IDP boosts productivity and shortens lead times, enabling organisations to swiftly adapt to changing customer demands. Ultimately, the long-term advantages of an Internal Developer Platform lie in its capacity to foster a sustainable development ecosystem that aligns with organisational objectives, thereby driving innovation and operational excellence. This alignment is essential for nurturing a resilient and adaptive organisational culture focused on continuous improvement and value delivery. https://engineering-leadership-preview.hinshelwood.com/tags/acceptance-test-driven-development/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/acceptance-test-driven-development/ Acceptance Test Driven Development (ATDD) is a collaborative methodology that prioritises the establishment of clear, testable acceptance criteria prior to feature implementation. Originating from the need for alignment among stakeholders, such as product owners, developers, and testers, ATDD ensures a shared understanding of success metrics for features, thereby minimising miscommunication and the potential for rework. This approach enhances the predictability and sustainability of value delivery by integrating quality assurance early in the development process, promoting a shift-left mindset that allows teams to identify and resolve issues proactively. The emphasis on early testing not only improves software quality but also nurtures a culture of collaboration and shared accountability within teams. Furthermore, the long-term advantages of ATDD extend beyond immediate project results; it fosters a systematic working method that encourages continuous improvement and adaptability to evolving requirements. By consistently implementing ATDD, organisations can enhance their agility and efficiency in delivering higher value to customers, making it a fundamental practice that reinforces the overall development process and keeps teams focused on what is essential for the business and its users. https://engineering-leadership-preview.hinshelwood.com/tags/agile-frameworks/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/automated-testing/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/automated-testing/ Automated Testing is a vital practice in software development that utilises automation tools to execute tests systematically, thereby enhancing the quality and reliability of software products. Originating from the need to streamline the testing process, this approach allows development teams to identify and address issues early, significantly minimising manual testing efforts and expediting the delivery of high-quality software. The significance of Automated Testing lies in its capacity to facilitate predictable and sustainable value delivery, fostering a culture of continuous improvement through shortened feedback loops. This practice aligns with Agile and DevOps principles by promoting a shift-left strategy, which encourages earlier testing in the development cycle, enhancing collaboration among cross-functional teams. Furthermore, Automated Testing serves as a long-term enabler of organisational agility, embedding quality assurance within the development workflow. This integration leads to increased throughput and a sustained focus on customer value, ultimately resulting in improved customer satisfaction and retention. By adopting this proactive approach, organisations empower their teams to innovate and adapt, ensuring competitiveness in a fast-paced market environment. https://engineering-leadership-preview.hinshelwood.com/tags/azure-boards/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/azure-pipelines/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/azure-pipelines/ Azure Pipelines is a cloud-based service designed to automate the processes of building, testing, and deploying applications, thereby enabling teams to deliver value in a predictable and sustainable manner. Originating from the need for efficient software development practices, it integrates seamlessly with various version control systems to facilitate continuous integration and continuous delivery (CI/CD). This capability allows teams to implement code changes frequently and reliably, significantly reducing manual errors and accelerating feedback loops while enhancing collaboration among cross-functional teams. The importance of Azure Pipelines lies in its ability to streamline workflows and improve overall efficiency throughout the software development lifecycle, supporting a diverse array of programming languages and platforms to meet varied project needs. By offering a consistent framework for managing builds and releases, it promotes a culture of continuous improvement and innovation. Furthermore, its integration with Azure DevOps tools, such as Azure Boards and Azure Repos, fosters a cohesive project management environment that enhances visibility into the development process and aligns teams towards shared objectives. This systemic approach ultimately drives organisational agility and resilience, with long-term benefits including increased deployment frequency, reduced lead times, and a heightened focus on delivering high-quality software that aligns with customer requirements. https://engineering-leadership-preview.hinshelwood.com/tags/backlog-refinement/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/behaviour-driven-development/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/behaviour-driven-development/ Behaviour Driven Development (BDD) is a collaborative methodology that aligns software development with business objectives by promoting clear communication among all stakeholders involved. Originating from the need to bridge the gap between technical and non-technical participants, BDD utilises natural language to articulate the desired behaviour of a system, fostering a shared understanding of requirements that are both testable and comprehensible. This approach is crucial in agile and DevOps environments, as it encourages teams to focus on user-centric outcomes, thereby enhancing collaboration and minimising ambiguity in requirements. By reducing misunderstandings and the need for rework, BDD enables teams to deliver features that more accurately meet user needs, resulting in a more predictable and sustainable development process. Furthermore, BDD supports continuous improvement by integrating with automated testing and continuous delivery practices, ensuring that teams remain aligned with user value as they iterate on their products. This emphasis on behaviour over mere functionality cultivates a culture of shared ownership and accountability, empowering teams to innovate while maintaining a clear focus on business goals, ultimately driving a deeper understanding of user needs and enhancing overall product quality. https://engineering-leadership-preview.hinshelwood.com/tags/continuous-integration/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/continuous-integration/ Continuous Integration (CI) is a software development practice that focuses on the frequent merging of code changes into a shared repository, facilitating early detection of errors and prompt resolution of integration issues. Originating from the need for more efficient collaboration in software teams, CI automates the build and testing processes, allowing developers to concentrate on delivering value rather than troubleshooting. Its importance lies in fostering a culture of continuous improvement and collaboration, enabling teams to iterate quickly and adapt to evolving requirements. By promoting regular communication and feedback, CI helps maintain a consistent development pace, resulting in more predictable and sustainable feature delivery. Additionally, CI significantly reduces technical debt by encouraging developers to address issues as they arise, which not only enhances code quality but also boosts team morale through a smoother workflow. Ultimately, CI serves as a foundational element that empowers teams to innovate and effectively respond to customer needs, contributing to long-term success in product development. https://engineering-leadership-preview.hinshelwood.com/tags/cross-functional-teams/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/cycle-time/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/cycle-time/ Cycle time is a key performance metric that measures the total duration required to complete a unit of work, from initiation to delivery. It is widely used in agile and DevOps methodologies to enhance team efficiency and predictability in value delivery. By monitoring cycle time, organisations can pinpoint bottlenecks, streamline processes, and optimise workflows, which leads to quicker product and service delivery. Understanding cycle time empowers teams to make data-driven decisions, fostering a culture of continuous improvement and enabling better forecasting and planning based on historical data. This predictability is crucial for aligning stakeholder expectations and meeting customer needs promptly. Furthermore, cycle time promotes a holistic view of value delivery, encouraging teams to consider the entire workflow rather than focusing on individual tasks. By minimising cycle time, organisations can improve their responsiveness to market dynamics and customer feedback, thereby gaining a competitive edge. In an era where rapid and sustainable value delivery is essential, the emphasis on cycle time is vital for organisational success. https://engineering-leadership-preview.hinshelwood.com/tags/deployment-frequency/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/deployment-frequency/ Deployment Frequency is a key metric that measures the rate at which software is released into production, playing a vital role in contemporary product development. It originates from the need for organisations to enhance their responsiveness to customer needs by facilitating quicker feedback loops and adjustments. By optimising deployment frequency, teams can not only release features and fixes more frequently but also validate their assumptions and learn from real-world usage promptly. This concept is crucial for cultivating a culture of continuous improvement and innovation, allowing teams to experiment, iterate, and adapt to market changes effectively. A high deployment frequency reflects a mature DevOps practice characterised by automation, collaboration, and efficient processes that enable rapid delivery without sacrificing quality. Additionally, it fosters a sense of accountability and ownership among team members, as they can directly observe the impact of their contributions on end-users. By prioritising deployment frequency, organisations can establish a sustainable delivery rhythm that enhances customer satisfaction and drives long-term business success through consistent value delivery and adaptability. This systemic approach not only promotes resilience and agility but also ensures that teams remain competitive in an ever-evolving digital landscape. https://engineering-leadership-preview.hinshelwood.com/tags/deployment-strategies/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/deployment-strategies/ Deployment strategies are systematic approaches that organisations utilise to release software into production, balancing the need for speed with risk management. These strategies are essential for enabling teams to deliver value in a predictable and sustainable manner, facilitating rapid iterations and continuous feedback. Techniques such as blue-green deployments, canary releases, and rolling updates help mitigate the impact of potential failures, allowing teams to address issues swiftly without causing significant disruption to users. The effectiveness of deployment strategies lies in their capacity to cultivate a culture of experimentation and learning, encouraging continuous improvement where each deployment provides insights for refining processes. This approach enhances operational efficiency and aligns with Agile and DevOps principles, fostering collaboration and shared responsibility among cross-functional teams. Furthermore, well-defined deployment strategies contribute to a resilient organisational structure, enabling teams to adapt to evolving market demands and technological changes. By prioritising safe and efficient releases, organisations can maintain a competitive advantage while ensuring customer satisfaction remains central to their product development efforts. Ultimately, the integration of deployment strategies into the broader organisational framework supports sustainable growth and reinforces the importance of delivering value through strategic software releases. https://engineering-leadership-preview.hinshelwood.com/tags/forecasting/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/forecasting/ Forecasting is the practice of utilising empirical data to predict delivery timelines, manage risks, and optimise value delivery within Agile and Scrum frameworks. It draws from historical performance and current capacity metrics, such as cycle time, lead time, and throughput, enabling teams to make informed decisions that lead to a more predictable and sustainable approach to product development. This practice is vital for promoting transparency and accountability, as it encourages teams to reflect on their processes and outcomes, moving beyond subjective estimations to data-driven insights that enhance decision-making. By anticipating challenges and adapting proactively, teams can improve overall efficiency and effectiveness. Integrating forecasting into Agile practices not only aids in achieving immediate project goals but also fosters long-term organisational agility, creating a resilient environment that can adapt to changing market demands. This systemic approach ultimately enhances the ability to deliver high-quality products that align with customer needs and business objectives, thereby cultivating a culture of continuous improvement and innovation. https://engineering-leadership-preview.hinshelwood.com/tags/frequent-releases/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/frequent-releases/ Frequent releases are the practice of delivering small, incremental updates to products or services on a regular basis, originating from agile methodologies and widely adopted in DevOps environments. This approach is essential for organisations seeking to swiftly respond to user feedback and market dynamics, ensuring consistent value delivery to stakeholders. By segmenting larger projects into manageable releases, teams can mitigate deployment risks, as smaller updates are easier to test and validate. This practice cultivates a culture of continuous improvement, enabling teams to iterate based on real-world usage and feedback, which is vital for maintaining a competitive edge in adapting to evolving customer needs and technological advancements. Additionally, frequent releases promote collaboration among developers, testers, and product owners, fostering a cohesive environment for product enhancement. They also contribute to a sustainable development pace, reducing the risk of burnout associated with large, infrequent releases, which in turn boosts team morale and builds stakeholder trust through visible progress and tangible outcomes. By integrating frequent releases into their operational frameworks, organisations can ensure they remain responsive and relevant in a rapidly changing market landscape. https://engineering-leadership-preview.hinshelwood.com/tags/lean-product-development/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/product-owner/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/product-owner/ The Product Owner is a key accountability within the Scrum framework, tasked with maximising the value of the product produced by the Scrum Team. This role encompasses more than just managing the product backlog; it involves making strategic decisions that align the product vision with customer needs and business objectives. The importance of the Product Owner lies in their responsibility for outcomes rather than merely tasks, as they prioritise features that balance immediate requirements with long-term goals. By optimising the product backlog and adapting to stakeholder feedback and market changes, the Product Owner significantly influences the product’s success and the team’s effectiveness. They foster collaboration between stakeholders and the development team, ensuring transparency and alignment across the organisation, which enhances decision-making and workflow efficiency. This accountability is crucial for a value-driven approach to product development, as the Product Owner must navigate competing priorities and ensure the product delivers measurable business value. Their strategic decision-making role is distinct from that of the Scrum Master or Development Team, as they continuously assess the product’s value and make evidence-based decisions to guide its evolution. By embedding this accountability within the organisational culture, the Product Owner helps maintain alignment with broader strategic goals, ultimately contributing to the consistency of value delivery and the successful completion of product iterations. https://engineering-leadership-preview.hinshelwood.com/tags/release-management/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/release-management/ Release Management is a systematic approach to planning, scheduling, and controlling the deployment of software releases to testing and live environments. Originating from the need for structured software delivery, it plays a critical role in ensuring that software is released in a predictable and sustainable manner, aligning with both organisational objectives and customer expectations. Effective release management minimises deployment risks, enhances interdepartmental collaboration, and keeps all stakeholders informed and engaged throughout the release process. This practice allows teams to deliver value incrementally, facilitating rapid feedback and adaptation, and fostering a culture of continuous improvement where each release serves as a learning opportunity. It integrates well with Continuous Delivery and Agile methodologies, optimising workflow and maintaining quality at every stage. Unlike Agile Planning or Product Management, which focus on strategic development aspects, Release Management is operational, concentrating on the tactical execution of software delivery. It necessitates a comprehensive understanding of technical and organisational dynamics, making it essential for modern product development. By establishing clear release processes, organisations can better respond to market changes and customer feedback, ultimately enhancing customer satisfaction and loyalty. https://engineering-leadership-preview.hinshelwood.com/tags/scrum-team/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/scrum-team/ A Scrum Team is a fundamental component of the Scrum framework, tasked with delivering value through iterative and incremental work. Comprising a Scrum Master, Product Owner, and Developers, the team operates collaboratively towards a unified Product Goal. Characterised by its self-managing and cross-functional nature, the Scrum Team eschews sub-teams and hierarchies, holding collective accountability for producing a usable Increment at the end of each Sprint. While individual members may have specific roles, the team’s shared responsibility encompasses all facets of product delivery, including stakeholder engagement, development, validation, and release. This structure empowers the Scrum Team to autonomously manage its work, making it a vital element in agile methodologies, DevOps practices, and effective organisational design. Understanding the dynamics and responsibilities of the Scrum Team is crucial for navigating complex and adaptive environments, as it highlights the importance of collaboration and accountability in achieving successful product outcomes. https://engineering-leadership-preview.hinshelwood.com/tags/technical-debt/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/technical-debt/ Technical debt is the concept that encapsulates the hidden costs associated with opting for quick, suboptimal solutions in software development rather than investing time in more effective, long-term strategies. It often emerges from factors such as hurried development processes, insufficient documentation, or reliance on outdated technologies. Recognising and managing technical debt is essential for teams striving to deliver consistent and sustainable value, as its accumulation can impede innovation and responsiveness to market changes, ultimately compromising product quality and delivery timelines. Addressing technical debt requires a commitment to refactoring, enhancing code quality, and adopting superior tools and practices, which not only boosts team efficiency but also cultivates a culture of continuous improvement. By systematically tackling technical debt, organisations can sustain a healthy development pace, ensuring competitiveness and responsiveness to customer demands. This strategic focus on technical debt is crucial for fostering organisational agility, as it directly impacts the ability to innovate and adapt in a fast-evolving landscape. https://engineering-leadership-preview.hinshelwood.com/tags/test-automation/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/test-automation/ Test automation is the practice of employing software tools to execute pre-scripted tests on applications prior to their production release. Originating from the need to enhance software quality and expedite feedback loops, this approach allows development teams to automate repetitive testing tasks, thereby enabling them to concentrate on more intricate scenarios that necessitate human insight. The significance of test automation lies in its capacity to provide predictable and sustainable value, facilitating continuous integration and continuous delivery practices. This enables teams to release software updates more frequently and with increased confidence, as automated tests yield immediate feedback on code changes, allowing for swift identification and resolution of defects. Consequently, this reduces the risk of errors in production and promotes collaboration among cross-functional teams by ensuring access to reliable testing results. Furthermore, test automation nurtures a culture of continuous improvement, empowering teams to measure and refine their testing processes over time. By integrating testing into the development lifecycle rather than treating it as a separate phase, organisations can achieve higher quality products and a more resilient development process, equipping teams to respond effectively to evolving market demands and customer requirements. https://engineering-leadership-preview.hinshelwood.com/tags/value-stream-mapping/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/working-software/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/agile-product-management/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/agile-product-management/ Agile Product Management is a methodology that prioritises maximising product value by aligning organisational strategy with customer needs through iterative and incremental delivery processes. Originating from Agile principles, this approach allows teams to swiftly adapt to changing market demands while ensuring that product development is informed by real user feedback. Unlike Agile Project Management, which focuses on project execution within Agile frameworks, Agile Product Management encompasses the entire product lifecycle, from discovery to delivery, fostering a culture of collaboration among cross-functional teams. This systemic approach to value delivery emphasises not only immediate outputs but also the long-term evolution of products to meet shifting user requirements. By enabling organisations to maintain a competitive edge and adapt to disruptions, Agile Product Management is essential for driving sustained growth and innovation. It enhances organisational agility and resilience, empowering teams to thrive in dynamic environments and ultimately leading to improved customer satisfaction and retention. https://engineering-leadership-preview.hinshelwood.com/tags/application-lifecycle-management/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/application-lifecycle-management/ Application Lifecycle Management (ALM) is the systematic approach to managing software applications throughout their entire lifecycle, from initial development to eventual retirement. Originating from the need for structured processes in software development, ALM integrates various practices, tools, and team collaboration to streamline workflows and enhance communication. Its importance lies in its ability to provide organisations with a comprehensive view of application development, aligning technical efforts with business goals while remaining adaptable to evolving requirements. By implementing methodologies such as continuous integration and continuous delivery, ALM fosters rapid feedback and iterative enhancements, which are critical in dynamic environments. This approach not only reduces deployment risks but also cultivates a culture of accountability and transparency within teams. Furthermore, ALM aids organisations in effectively managing their application portfolios, ensuring optimal resource allocation and proactive technical debt management. This long-term focus is essential for driving innovation and maintaining a competitive edge, as it allows teams to concentrate on delivering high-quality software that satisfies user demands and contributes to overall business success. The synergy between ALM and frameworks like Agile and DevOps amplifies its impact, establishing a solid foundation for ongoing improvement and value creation. https://engineering-leadership-preview.hinshelwood.com/tags/azure-devops/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/azure-devops/ Azure DevOps is a comprehensive suite of tools developed by Microsoft that supports continuous integration and continuous delivery (CI/CD), enhances collaboration, and streamlines agile project management. It encompasses various functionalities, including Azure Boards for work tracking, Azure Repos for source control, Azure Pipelines for automating builds and deployments, and Azure Test Plans for managing testing efforts. This platform is crucial for organisations seeking to deliver value in a predictable and sustainable manner, as it promotes a culture of collaboration and transparency among teams. By providing a unified environment for development and operations, Azure DevOps facilitates the adoption of best practices in agile methodologies and DevOps principles, ensuring efficient software delivery that is responsive to evolving business needs. Its systemic approach encourages continuous improvement and learning, enabling organisations to swiftly adapt to market demands while upholding high-quality standards. The integration of tools within Azure DevOps mitigates silos, enhances communication, and fosters a shared understanding of project objectives, ultimately leading to improved outcomes and a culture of innovation. This capability is vital for organisations aiming to achieve operational excellence and maintain a competitive advantage in a fast-changing landscape. https://engineering-leadership-preview.hinshelwood.com/tags/flow-efficiency/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/one-engineering-system/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/one-engineering-system/ The One Engineering System (1ES) is a strategic framework designed to unify engineering tools and practices across various teams, aiming to reduce friction, enhance collaboration, and ensure consistency at scale. Originating from the need to streamline workflows in software development, 1ES focuses on establishing a shared engineering backbone that allows teams to operate more efficiently by eliminating the chaos associated with disparate toolchains and ad hoc processes. This approach is crucial in agile and DevOps environments, as it promotes a common set of engineering standards that facilitate planning, coding, testing, deployment, and production support. By reducing cognitive overhead and simplifying integration, 1ES enables teams to deliver high-quality outcomes more reliably. Importantly, the framework emphasises that tools should adapt to the teams’ workflows rather than impose rigid structures, allowing for flexibility and coherence rather than uniformity. Successful implementation of 1ES necessitates investment in team enablement, including guidance, training, and support, to ensure effective adoption. When executed properly, 1ES fosters scalable engineering excellence, characterised by clear communication, consistent processes, and a resilient development lifecycle across the organisation. https://engineering-leadership-preview.hinshelwood.com/tags/product-delivery/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership-preview.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-preview.hinshelwood.com/tags/technical-excellence/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/technical-excellence/ Technical Excellence encompasses the quality of engineering practices that facilitate high-quality software delivery, enhanced agility, and ongoing improvement within development teams. Originating from methodologies that prioritise best practices, it empowers teams to create maintainable, scalable, and resilient software. In the context of Agile, Technical Excellence is vital as it allows teams to swiftly adapt to changing requirements and market demands while ensuring product quality and sustainability. Key practices such as Test-Driven Development (TDD) and Continuous Integration and Continuous Delivery (CI/CD) play a significant role in maintaining high standards by automating testing and deployment processes, thus enabling more frequent and reliable software releases. Additionally, modular architecture supports scalability and responsiveness to new requirements, while emergent design principles promote flexibility in adapting software designs as understanding evolves. By fostering a culture of continuous improvement, Technical Excellence encourages teams to regularly evaluate and refine their practices, ensuring they can maintain quality and responsiveness to change. Embedding this capability within an organisation’s culture not only addresses immediate customer needs but also establishes a sustainable foundation for long-term success, allowing organisations to consistently deliver high-quality software while remaining adaptable and efficient in their development processes. https://engineering-leadership-preview.hinshelwood.com/tags/agentic-software-delivery/ Tue, 21 Jan 2025 10:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/agentic-software-delivery/ Agentic Software Delivery is a strategy for continuously achieving business outcomes through the deliberate integration of autonomous AI agents, human expertise, and organisational context. It is not about automation for automation’s sake, but about enabling teams to move faster and smarter by embedding proactive, context-aware intelligence into their systems of work. The term ‘agentic’ implies more than assistance, it implies agency. These agents operate autonomously within defined boundaries, learning from data, adapting to patterns, and making context-informed decisions. They contribute meaningfully to outcomes across discovery, development, delivery, and operations. This approach relies on the synergy between domain experts and AI agents, requiring lean, empirical systems of work, strong product strategy, and modern engineering practices such as CI/CD, observability, infrastructure as code, and automated testing.