https://engineering-leadership.hinshelwood.com/tags/team-performance/ Recent content in Team Performance on Engineering Leadership in AI & Software Hugo en Tue, 16 Jun 2026 17:40:35 +0000 https://engineering-leadership.hinshelwood.com/articles/telling-people-what-to-do-is-not-leadership-it-s-a-failure-of-system-design/ Mon, 04 Aug 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/telling-people-what-to-do-is-not-leadership-it-s-a-failure-of-system-design/ Telling people what to do is not leadership, it is a sign of poor system design that stifles autonomy and slows delivery. Effective leadership means creating systems where teams have clear goals, constraints, and feedback loops so they can self-manage, deliver value, and adapt without micromanagement. Focus on improving your delivery system, set meaningful goals, enable autonomy with clear boundaries, use evidence-based metrics, and empower teams to own outcomes, so you can step back and let professionals do their best work. https://engineering-leadership.hinshelwood.com/articles/don-t-manage-dependencies-remove-them/ Mon, 29 Sep 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/don-t-manage-dependencies-remove-them/ Dependencies are not inevitable but are usually caused by poor system design; instead of managing them, focus on removing them by aligning work, teams, and architecture, making contracts explicit, and clarifying ownership. Only manage the rare dependencies that remain, treating them as design flaws to be fixed, not as normal work. Leadership should prioritise redesigning systems to eliminate dependencies, which leads to faster delivery, fewer defects, and higher team autonomy. https://engineering-leadership.hinshelwood.com/articles/flow-of-value-vs-flow-of-work/ Mon, 15 Sep 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/flow-of-value-vs-flow-of-work/ The phrase “flow of value” is often misused in software development, as value is only confirmed when customers validate it, not just when work is completed. Teams should focus on validating outcomes quickly, breaking work into small, testable increments, and using data to cut features that do not deliver real value. To truly optimise value, ensure every item has a clear hypothesis, measure time to feedback, and prioritise learning over simply moving work through the system. https://engineering-leadership.hinshelwood.com/articles/is-agile-really-just-a-mindset/ Mon, 11 Aug 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/is-agile-really-just-a-mindset/ Agile is not just a mindset or set of behaviours; it is a disciplined system of work rooted in engineering excellence, technical leadership, and empirical delivery. True agility requires robust engineering practices like CI/CD, automated testing, and observability, not just ceremonies or coaching. To achieve real Agile outcomes, focus on building systems that enable frequent, reliable delivery and hold both teams and leadership accountable for technical and organisational change. https://engineering-leadership.hinshelwood.com/articles/why-topic-branches-drive-high-quality-delivery/ Mon, 14 Jul 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/why-topic-branches-drive-high-quality-delivery/ Short-lived topic branches help teams deliver high-quality software by making integration easier, reducing merge conflicts, and supporting modular, continuous delivery. Adopting models like GitHub Flow or Release Flow keeps work focused and feedback fast, while long-lived branches increase risk and slow down delivery. Development managers should enforce small, short-lived branches and regularly review branching strategies to maintain flow, agility, and quality. https://engineering-leadership.hinshelwood.com/videos/why-a-shared-definition-of-done-is-the-secret-to-consistent-predictable-quality-in-agile-teams/ Wed, 14 May 2025 07:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/why-a-shared-definition-of-done-is-the-secret-to-consistent-predictable-quality-in-agile-teams/ When teams lack a shared definition of done, quality and predictability suffer, leading to confusion, hidden risks, and technical debt. Aligning on a clear, organisation-wide standard ensures consistent delivery, builds trust, and reduces production risks. Development managers should prioritise creating and enforcing a common definition of done to achieve reliable outcomes and true agility. https://engineering-leadership.hinshelwood.com/videos/why-outsourcing-devops-fails-and-how-real-engineering-excellence-starts-with-your-team/ Mon, 15 Sep 2025 06:30:00 +0000 https://engineering-leadership.hinshelwood.com/videos/why-outsourcing-devops-fails-and-how-real-engineering-excellence-starts-with-your-team/ Outsourcing DevOps often leads to vendor lock-in, legacy systems, and teams that cannot maintain or evolve their own tools. Real engineering excellence comes from building internal capability through partnership, where experts mentor and guide your team to modernize workflows and systems themselves. Invest in developing your engineers’ skills and mindset so your organization can achieve sustainable progress and avoid costly dependencies. https://engineering-leadership.hinshelwood.com/articles/the-estimation-trap-how-tracking-accuracy-undermines-trust-flow-and-value-in-software-delivery/ Mon, 22 Sep 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/the-estimation-trap-how-tracking-accuracy-undermines-trust-flow-and-value-in-software-delivery/ Focusing on estimation accuracy as a performance metric leads to fear, gaming, and a culture of compliance rather than real improvement, which undermines trust, innovation, and actual value delivery. Research shows that when teams are judged on how closely they meet estimates, they pad numbers, hide risks, and avoid complex work, resulting in false success and missed opportunities for learning. Instead, shift attention to evidence-based metrics that reflect customer value, system health, and delivery flow, and use estimates only to support learning and informed conversations, not as tools for control. https://engineering-leadership.hinshelwood.com/articles/the-definition-of-done-is-a-commitment-to-quality/ Mon, 28 Jul 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/the-definition-of-done-is-a-commitment-to-quality/ A clear, shared Definition of Done is essential for delivering quality, releasable software in Scrum and aligns teams on what “complete” means. It ensures transparency, predictability, and accountability, protects your product’s reputation, and must be created, automated, and regularly improved by all teams working on a product. Development managers should prioritise running DoD workshops, making standards visible, automating checks, and reviewing the DoD every sprint to maintain quality and reduce risk. https://engineering-leadership.hinshelwood.com/articles/your-evolving-definition-of-done/ Mon, 31 Mar 2025 09:00:00 +0100 https://engineering-leadership.hinshelwood.com/articles/your-evolving-definition-of-done/ The Definition of Done should evolve as teams mature, starting with basic quality standards and expanding to include automation, security, and business-level requirements that align with organisational goals. A strong, consistently applied DoD reduces risk, rework, and delays, ensuring every increment is truly releasable and delivers real value. Development managers should regularly review and raise the DoD, embedding it into team practices to protect quality and support strategic objectives. https://engineering-leadership.hinshelwood.com/signals/velocity-isn-t-how-many-story-points-a-team-burns-down/ Mon, 10 Mar 2025 16:30:02 +0000 https://engineering-leadership.hinshelwood.com/signals/velocity-isn-t-how-many-story-points-a-team-burns-down/ Velocity is about how quickly your team delivers value, not just story points completed. Focus on measuring time to build, self-test, deploy, and learn from user feedback, as these are actionable and within your control. Start tracking these metrics to improve your delivery speed and effectiveness. https://engineering-leadership.hinshelwood.com/articles/should-you-use-one-project-to-rule-them-all-in-azure-devops/ Mon, 25 Aug 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/should-you-use-one-project-to-rule-them-all-in-azure-devops/ Using a single Azure DevOps project for all teams and products reduces fragmentation, improves visibility, and streamlines governance compared to managing multiple projects or organisations. Key benefits include unified reporting, easier collaboration, and lower administrative overhead, while Area Paths and Teams provide the necessary structure and security within one project. Development managers should consolidate into one project where possible, using Area Paths and Teams to model structure and scale, to optimise flow and delivery. https://engineering-leadership.hinshelwood.com/videos/why-done-only-counts-when-it-s-live-moving-beyond-fake-finishes-to-real-value-in-software-delivery/ Wed, 07 May 2025 11:46:58 +0000 https://engineering-leadership.hinshelwood.com/videos/why-done-only-counts-when-it-s-live-moving-beyond-fake-finishes-to-real-value-in-software-delivery/ Work is only truly done when it is live in production and delivering value to users, not just when code is written, tested, or demoed. Teams often mistake internal milestones for real progress, which delays learning and frustrates stakeholders; real feedback and value come only from live usage and telemetry. Development managers should redefine “done” as live in production, invest in automation to shorten release cycles, and focus on measuring and celebrating actual user impact. https://engineering-leadership.hinshelwood.com/videos/stop-paying-the-hidden-costs-of-weak-delivery-why-a-strong-definition-of-done-transforms-your-team-s-results/ Wed, 21 May 2025 06:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/stop-paying-the-hidden-costs-of-weak-delivery-why-a-strong-definition-of-done-transforms-your-team-s-results/ Cutting corners on quality and having a weak definition of done leads to hidden costs like rework, production risks, and lost trust. A clear, shared, and enforceable definition of done ensures every increment is truly usable, reliable, and aligned with business goals. Make your definition of done visible, evidence-based, and strictly enforced to improve delivery outcomes and build stakeholder confidence. https://engineering-leadership.hinshelwood.com/signals/engineering-can-fix-technical-debt-but-leadership-has-to-invest-in-it/ Mon, 03 Mar 2025 16:30:35 +0000 https://engineering-leadership.hinshelwood.com/signals/engineering-can-fix-technical-debt-but-leadership-has-to-invest-in-it/ Fixing technical debt requires leadership investment, not just harder work from engineers. Success comes from funding automation, better testing, and empowering teams to address issues directly. If continuous delivery is not happening, leaders should reconsider their priorities and support the necessary improvements. https://engineering-leadership.hinshelwood.com/articles/there-is-no-such-thing-as-a-junior-scrum-master/ Mon, 17 Feb 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/there-is-no-such-thing-as-a-junior-scrum-master/ The Scrum Master role requires deep technical, business, and organisational expertise and should not be treated as an entry-level or “junior” position. The most effective Scrum Masters emerge from within high-performing teams, having already demonstrated real-world competence and leadership, not just certification. To ensure team effectiveness and delivery, select Scrum Masters based on proven experience and peer respect, not on cost savings or minimal qualifications. https://engineering-leadership.hinshelwood.com/articles/great-scrum-masters-need-technical-business-and-organisational-mastery/ Mon, 24 Mar 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/great-scrum-masters-need-technical-business-and-organisational-mastery/ Scrum Masters are most effective when they combine strong leadership skills with deep understanding of their team’s technical, business, and organisational context. Mastery in these three areas enables them to better remove obstacles, coach both teams and Product Owners, and drive meaningful change across the organisation. Development managers should ensure their Scrum Masters are experienced professionals who continuously build expertise in these domains to maximise team performance and value delivery. https://engineering-leadership.hinshelwood.com/signals/scrum-teams-don-t-set-the-bar-for-quality-they-meet-it/ Thu, 03 Apr 2025 15:30:01 +0100 https://engineering-leadership.hinshelwood.com/signals/scrum-teams-don-t-set-the-bar-for-quality-they-meet-it/ Scrum teams are responsible for meeting, not setting, the quality standard defined by the Definition of Done, which should be a strict, non-negotiable measure of what is releasable. Weakening or fluctuating the DoD increases risk and technical debt, undermining quality and predictability. Development managers should ensure their teams consistently strengthen the DoD over time rather than lowering it to deliver more features. https://engineering-leadership.hinshelwood.com/articles/definition-of-done-objective-vs-subjective/ Fri, 03 Jan 2025 00:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/definition-of-done-objective-vs-subjective/ The Definition of Done (DoD) in Scrum is an objective, measurable checklist that sets the minimum quality standard for every product increment, distinct from the more subjective Product and Sprint Goals. Teams should ensure their DoD is clear, comprehensive, regularly reviewed, and as automated as possible, avoiding subjective approval steps. Development managers should treat the DoD as a non-negotiable baseline for quality, not a ceiling, and keep it updated to reflect evolving standards and business needs. https://engineering-leadership.hinshelwood.com/articles/work-can-flow-across-the-sprint-boundary/ Tue, 30 Jan 2018 20:12:00 +0000 https://engineering-leadership.hinshelwood.com/articles/work-can-flow-across-the-sprint-boundary/ Allowing work to flow across Sprint boundaries is permitted in Scrum and can improve delivery speed, responsiveness, and value, as long as teams maintain clear, outcome-focused Sprint Goals and consistently deliver Done increments. Adopting practices like Continuous Delivery, feature toggles, and frequent feedback helps teams validate work early and adapt quickly. Development managers should encourage flow principles and robust engineering practices to maximize throughput and support better business decisions. https://engineering-leadership.hinshelwood.com/articles/are-we-still-pretending-coding-was-the-bottleneck/ Mon, 01 Sep 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/are-we-still-pretending-coding-was-the-bottleneck/ AI writing code is not the real game-changer; coding was never the main bottleneck in software delivery. The real constraints are in poor system design, handoffs, unclear requirements, and lack of built-in quality, which AI will only make more visible. To benefit from AI, focus on improving flow, building quality in from the start, and making teams accountable for outcomes rather than output. https://engineering-leadership.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-your-team-needs-to-win/ Wed, 16 Jul 2025 06:45:00 +0000 https://engineering-leadership.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-your-team-needs-to-win/ Many teams struggle not with building software but with finishing it in a way that delivers real business value. A clear, evolving definition of done protects revenue, boosts customer satisfaction, reduces rework, and builds trust by ensuring work is truly complete and valuable. Make your definition of done visible, review it regularly with the whole team, and connect it to real outcomes to turn it into a competitive advantage. https://engineering-leadership.hinshelwood.com/videos/stop-testing-quality-in-how-shifting-left-builds-better-software-faster/ Mon, 18 Aug 2025 06:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/stop-testing-quality-in-how-shifting-left-builds-better-software-faster/ Relying on testers to catch issues late in the process increases costs, slows feedback, and undermines product trust; instead, quality should be built in from the start by moving tests and feedback as close to the engineer as possible. Key practices include automating builds and tests, adopting continuous integration and delivery, using test-driven development, and incrementally improving code quality. Development managers should focus on empowering engineers to own quality, relentlessly shortening feedback loops, and making incremental improvements to achieve faster, more reliable releases. https://engineering-leadership.hinshelwood.com/signals/every-delay-increases-the-risk-of-failure/ Mon, 10 Feb 2025 11:00:51 +0000 https://engineering-leadership.hinshelwood.com/signals/every-delay-increases-the-risk-of-failure/ Delaying software releases increases the risk of failure and falling behind competitors. Frequent, smaller releases lead to higher success rates and faster recovery, as shown by industry research. Focus on delivering quickly and iterating rather than waiting for a perfect release. https://engineering-leadership.hinshelwood.com/articles/stop-promoting-branches/ Thu, 06 Feb 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/stop-promoting-branches/ Promoting code through multiple environment branches slows delivery, increases risk, and adds unnecessary complexity. Instead, use simple branching models like GitHub Flow for continuous delivery or Release Flow if you must support multiple live versions; avoid outdated models like Git Flow and never rely on reverse integration. Focus on merging changes directly into main, use feature flags for releases, and keep branching lightweight to deliver value faster. https://engineering-leadership.hinshelwood.com/videos/how-to-evolve-your-definition-of-done-start-small-grow-smarter-and-build-lasting-momentum/ Wed, 25 Jun 2025 06:45:00 +0000 https://engineering-leadership.hinshelwood.com/videos/how-to-evolve-your-definition-of-done-start-small-grow-smarter-and-build-lasting-momentum/ You do not need a perfect Definition of Done from the start; begin with what is usable, then gradually add quality, testing, and compliance standards as your team grows more capable. Trying to do everything at once can stall progress, so evolve your standards step by step to build momentum and resilience. Focus on essential requirements now and raise the bar as your team is ready. https://engineering-leadership.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/ Sun, 25 May 2025 15:30:23 +0100 https://engineering-leadership.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/ Scrum allows you to optimise workflow as long as you maintain accountability through a Sprint Goal and a Done Increment. If your team already delivers quality software continuously and meets these standards, you do not need to force all work to finish within strict Sprint timelines. Focus on outcomes and professionalism rather than rigid rules, and let work flow naturally if your processes support it. https://engineering-leadership.hinshelwood.com/signals/technical-debt-isn-t-just-messy-code/ Thu, 13 Mar 2025 16:30:02 +0000 https://engineering-leadership.hinshelwood.com/signals/technical-debt-isn-t-just-messy-code/ Technical debt goes beyond messy code and includes slow feedback, fragile systems, and manual processes that hinder progress. It results from choices like delaying refactoring or skipping automation, and it compounds over time. To avoid bigger problems later, prioritize paying down technical debt now by automating, testing early, and streamlining delivery pipelines. https://engineering-leadership.hinshelwood.com/articles/a-better-way-than-staggered-iterations-for-delivery/ Thu, 10 Dec 2020 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/a-better-way-than-staggered-iterations-for-delivery/ Staggered iterations slow feedback, increase technical debt, and reduce software quality, making delivery less agile and more expensive. Instead, form cross-functional teams that deliver working software every iteration, integrate all required work including testing into each sprint, and automate as much as possible. Shift away from staged handoffs to continuous, team-owned delivery to improve value and quality. https://engineering-leadership.hinshelwood.com/articles/why-handoffs-are-killing-your-agility/ Mon, 13 Jan 2025 00:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/why-handoffs-are-killing-your-agility/ Excessive handoffs between siloed teams slow delivery, reduce quality, and undermine team morale, making true agility impossible. Key issues include loss of context, increased cycle time, and lower accountability, all of which compound to hurt value delivery. To improve, reorganise into cross-functional teams, automate workflows, limit work in progress, and regularly remove outdated processes to streamline flow and boost team effectiveness. https://engineering-leadership.hinshelwood.com/signals/the-hidden-costs-of-supporting-multiple-versions-in-production/ Thu, 06 Feb 2025 16:30:01 +0000 https://engineering-leadership.hinshelwood.com/signals/the-hidden-costs-of-supporting-multiple-versions-in-production/ Supporting multiple versions in production drains engineering resources through increased context-switching, merge conflicts, and bug risks. Back-porting fixes and maintaining separate branches for each customer make things worse, leading to instability and technical debt. To avoid these problems, teams should simplify and standardise their branching strategy. https://engineering-leadership.hinshelwood.com/articles/why-most-scrum-masters-are-failing-and-what-they-should-know/ Thu, 05 Sep 2024 11:14:48 +0000 https://engineering-leadership.hinshelwood.com/articles/why-most-scrum-masters-are-failing-and-what-they-should-know/ Most Scrum Masters lack the necessary understanding of Scrum and related technical and business practices, which has led to widespread layoffs and questions about their value. Companies now expect Scrum Masters to demonstrate clear competence in areas like DevOps, engineering practices, agile frameworks, release planning, stakeholder management, and metrics. Development managers should ensure their Scrum Masters have foundational knowledge in these areas and can show measurable impact on team effectiveness. https://engineering-leadership.hinshelwood.com/articles/professional-scrum-teams-build-software-that-works/ Thu, 03 Dec 2020 00:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/professional-scrum-teams-build-software-that-works/ Professional Scrum teams must deliver high-quality, working software every sprint, prioritizing quality over speed or feature quantity to build trust and protect the organization’s reputation. Developers are accountable for quality and should use automation, DevOps practices, and continuous improvement to avoid technical debt and defects. Managers should empower teams to focus on quality, address technical debt in retrospectives, and consider upskilling developers through professional training. https://engineering-leadership.hinshelwood.com/articles/the-role-of-agency-in-scrum-why-self-management-without-agency-is-a-lie/ Thu, 01 May 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/the-role-of-agency-in-scrum-why-self-management-without-agency-is-a-lie/ Scrum only works when teams have real decision-making power, not just the appearance of self-management. Without agency, accountability is hollow and Scrum devolves into empty rituals that fail to deliver true agility or value. To achieve the benefits of Scrum, leaders must ensure teams and roles have genuine authority to own outcomes and drive change. https://engineering-leadership.hinshelwood.com/articles/can-the-definition-of-done-change-per-sprint/ Mon, 14 Oct 2019 13:55:00 +0000 https://engineering-leadership.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.hinshelwood.com/signals/why-measuring-individual-cycle-time-fails-to-help-teams/ Sat, 15 Mar 2025 16:30:02 +0000 https://engineering-leadership.hinshelwood.com/signals/why-measuring-individual-cycle-time-fails-to-help-teams/ Measuring individual cycle time does not help teams improve because it focuses on people instead of the overall system. Real bottlenecks come from process issues like queues and overloaded work, not individual speed. To improve team performance, focus on system-level metrics such as lead time, throughput, and process efficiency, and address process bottlenecks rather than monitoring individuals. https://engineering-leadership.hinshelwood.com/videos/stop-guessing-how-to-make-work-visible-and-drive-real-improvement-with-azure-devops-flow-metrics/ Mon, 25 Aug 2025 06:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/stop-guessing-how-to-make-work-visible-and-drive-real-improvement-with-azure-devops-flow-metrics/ Relying on gut feeling leads to mediocre results, so making work visible with real data is essential for improvement. Azure DevOps provides a strong data foundation but its built-in metrics and visualisations are basic; using tools like Flow Viz or Actionable Agile Metrics gives deeper insights and actionable flow data. To drive better outcomes, move from guesswork to evidence-based decisions by leveraging these tools to make your team’s work and bottlenecks visible. https://engineering-leadership.hinshelwood.com/signals/evolving-engineering-practices-to-improve-sprint-workflow-in-scrum/ Thu, 29 May 2025 15:30:45 +0100 https://engineering-leadership.hinshelwood.com/signals/evolving-engineering-practices-to-improve-sprint-workflow-in-scrum/ To improve sprint workflow in Scrum without sacrificing quality, teams need to adopt practices like Feature Flags, TDD, and regular refactoring to enable safe, continuous flow of work. These practices help ship incomplete features safely, ensure code reliability, and maintain system health. Development managers should prioritize evolving engineering practices and consider Continuous Delivery essential for sustainable progress. https://engineering-leadership.hinshelwood.com/signals/why-tracking-individual-cycle-time-distorts-team-behaviour/ Wed, 12 Mar 2025 16:30:03 +0000 https://engineering-leadership.hinshelwood.com/signals/why-tracking-individual-cycle-time-distorts-team-behaviour/ Tracking individual cycle time leads people to focus on looking good rather than improving team performance, causing them to pick easy tasks, rush work, and avoid collaboration. This does not improve actual delivery time and results in local optimisations that do not help deliver value. Focus on measuring and improving team flow metrics like lead time, work in progress, and throughput instead. https://engineering-leadership.hinshelwood.com/articles/the-scrum-master-is-accountable-for-delivery/ Thu, 30 Jan 2025 00:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/the-scrum-master-is-accountable-for-delivery/ The Scrum Master is ultimately accountable for ensuring the Scrum Team delivers a usable product increment every sprint, as delivery is the minimum requirement for team effectiveness. While delivery is a shared team responsibility, the Scrum Master must create the right environment, remove impediments, and enable continuous improvement so delivery becomes inevitable. Development managers should hold Scrum Masters accountable for delivery outcomes and empower them with the authority and resources needed to support team success. https://engineering-leadership.hinshelwood.com/videos/where-agile-went-wrong-understanding-the-competence-crisis/ Mon, 14 Oct 2024 07:00:38 +0000 https://engineering-leadership.hinshelwood.com/videos/where-agile-went-wrong-understanding-the-competence-crisis/ Agile has struggled because its founders assumed widespread competence and commitment to continuous learning, but most organizations lack enough skilled practitioners, especially in key roles like Scrum Master. This competence gap is worsened by low hiring standards and overreliance on basic certifications, leading to ineffective teams and missed opportunities for improvement. Development managers should prioritize hiring and promoting individuals with proven learning habits, deep contextual understanding, and advanced expertise to build high-performing Agile teams. https://engineering-leadership.hinshelwood.com/videos/empowering-teams-for-success-the-key-to-thriving-product-development/ Tue, 07 May 2024 11:02:49 +0000 https://engineering-leadership.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.hinshelwood.com/articles/the-insufficiency-of-scrum-is-a-fallacy/ Sat, 23 Mar 2013 17:37:31 +0000 https://engineering-leadership.hinshelwood.com/articles/the-insufficiency-of-scrum-is-a-fallacy/ Scrum alone does not cause project failure; lacking strong engineering practices and effective retrospectives leads to technical debt and poor Agile outcomes. https://engineering-leadership.hinshelwood.com/signals/why-slow-processes-impact-developer-productivity-and-performance/ Fri, 14 Mar 2025 16:30:02 +0000 https://engineering-leadership.hinshelwood.com/signals/why-slow-processes-impact-developer-productivity-and-performance/ Developer performance issues are often caused by slow or broken processes, not individual shortcomings. Focusing on improving systems like training, reviews, and team handoffs leads to better results than blaming people. To boost productivity, address process bottlenecks rather than targeting individuals. https://engineering-leadership.hinshelwood.com/videos/overview-of-'applying-flow-metrics-for-scrum'-course/ Mon, 19 Feb 2024 07:00:09 +0000 https://engineering-leadership.hinshelwood.com/videos/overview-of-'applying-flow-metrics-for-scrum'-course/ The “Applying Flow Metrics for Scrum” course teaches Scrum teams how to use Kanban metrics to improve value delivery, transparency, and continuous improvement. Key benefits include better visibility into workflow, data-driven decision-making, and more predictable outcomes for stakeholders. Development managers should consider this course if their teams need to deliver value more consistently and want practical tools for ongoing improvement. https://engineering-leadership.hinshelwood.com/articles/estimating-better-in-an-overloaded-system-is-a-poor-man-s-strategy/ Mon, 08 Sep 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/estimating-better-in-an-overloaded-system-is-a-poor-man-s-strategy/ Trying to improve estimates in an overloaded system is ineffective because high work in progress causes delays and unpredictability, regardless of estimation accuracy. Real improvements in predictability and throughput come from limiting work in progress, fostering collaboration, and focusing on finishing work rather than starting more. To achieve reliable delivery, reduce WIP and prioritize flow over planning. https://engineering-leadership.hinshelwood.com/signals/best-branching-strategies-for-development-teams-explained/ Tue, 25 Feb 2025 16:30:02 +0000 https://engineering-leadership.hinshelwood.com/signals/best-branching-strategies-for-development-teams-explained/ Using separate branches for each environment increases complexity and slows feedback, making it harder to deliver value quickly. Teams should use branches to manage work in progress and rely on feature flags and progressive rollouts to control what users see. Review your current branching approach and consider simplifying it to speed up delivery and reduce risk. https://engineering-leadership.hinshelwood.com/videos/the-crucial-role-of-competence-how-knowledgeable-scrum-masters-drive-team-success/ Mon, 21 Oct 2024 05:32:11 +0000 https://engineering-leadership.hinshelwood.com/videos/the-crucial-role-of-competence-how-knowledgeable-scrum-masters-drive-team-success/ Scrum Masters need deep knowledge of both agile practices and the technical work of their teams to drive real improvement in product delivery. Without this competence, teams stagnate and fail to deliver business value, while skilled Scrum Masters elevate team capabilities and outcomes. Development managers should ensure their Scrum Masters have practical expertise, not just facilitation skills, to maximize team impact. https://engineering-leadership.hinshelwood.com/videos/avoiding-agile-banditry-why-story-points-and-velocity-are-misleading-metrics/ Mon, 08 Jan 2024 07:00:06 +0000 https://engineering-leadership.hinshelwood.com/videos/avoiding-agile-banditry-why-story-points-and-velocity-are-misleading-metrics/ Story points and velocity often distract teams from delivering real customer value and can lead to counterproductive behaviors, especially when used as performance measures or written into contracts. Instead, focus on metrics like throughput and cycle time, which better reflect actual progress and value delivery. Use story points only for internal team discussions, then discard them, and never include them in contracts or external reporting. https://engineering-leadership.hinshelwood.com/videos/rethinking-agile-why-story-points-team-sizes-and-emergent-architecture-need-a-fresh-perspective/ Wed, 13 May 2020 05:03:57 +0000 https://engineering-leadership.hinshelwood.com/videos/rethinking-agile-why-story-points-team-sizes-and-emergent-architecture-need-a-fresh-perspective/ Story points often create confusion and unpredictability, so focusing on throughput and cycle time gives teams clearer insights and better delivery. Slightly larger teams with diverse roles can handle complex work and maintain quality more effectively. Embracing emergent architecture helps teams stay flexible and competitive, so consider shifting your metrics and team structures to support adaptability and faster value delivery. https://engineering-leadership.hinshelwood.com/signals/a-changing-definition-of-done-undermines-quality-and-predictability-in-teams/ Fri, 04 Apr 2025 15:30:02 +0100 https://engineering-leadership.hinshelwood.com/signals/a-changing-definition-of-done-undermines-quality-and-predictability-in-teams/ Frequently changing the Definition of Done makes it hard for teams to deliver predictable results and maintain quality. The Definition of Done should only evolve to raise standards, not lower them. To improve predictability and quality, keep your Definition of Done consistent and ensure it is followed. https://engineering-leadership.hinshelwood.com/articles/deciphering-the-enigma-of-story-points-across-teams/ Thu, 21 Sep 2023 08:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/deciphering-the-enigma-of-story-points-across-teams/ Story Points are useful for team discussions and backlog refinement but are too subjective for comparing teams or predicting delivery. Focus instead on objective metrics like throughput, cycle time, and work in process to measure and improve team performance, while also considering value delivered using evidence-based management practices. Shift your attention from normalising Story Points to tracking flow metrics and value to make better decisions and optimise outcomes. https://engineering-leadership.hinshelwood.com/articles/hiring-a-professional-scrum-master/ Mon, 15 Mar 2021 14:11:00 +0000 https://engineering-leadership.hinshelwood.com/articles/hiring-a-professional-scrum-master/ Hiring a Scrum Master is challenging and requires someone who can lead, coach, and support both the team and organization to improve effectiveness and adopt Scrum practices. Key requirements include strong leadership, facilitation, and communication skills, a servant leadership mindset, and relevant certifications, with technical or business domain knowledge as a plus. Focus on candidates who can foster a safe, collaborative environment and drive continuous improvement for reliable product delivery. https://engineering-leadership.hinshelwood.com/signals/if-every-release-feels-high-risk-you-lack-a-true-definition-of-done/ Sat, 05 Apr 2025 15:30:00 +0100 https://engineering-leadership.hinshelwood.com/signals/if-every-release-feels-high-risk-you-lack-a-true-definition-of-done/ If every release feels risky and stressful, your team likely lacks a clear Definition of Done that ensures software is truly ready for production. A strong Definition of Done means releases are routine, with quality, security, and compliance built in, so there are no last-minute scrambles. Review your team’s process to make releases predictable and low-stress. https://engineering-leadership.hinshelwood.com/videos/special-sprints-agile-banditry-or-risk-management/ Thu, 04 Jan 2024 11:09:15 +0000 https://engineering-leadership.hinshelwood.com/videos/special-sprints-agile-banditry-or-risk-management/ Special sprints like bug-fix or hardening sprints undermine Agile by encouraging teams to defer work and accumulate risk, rather than delivering usable products every sprint. The Azure DevOps team found that relying on a safety net led to overwhelming undone work, but shifting to shipping every sprint improved quality and reduced technical debt. Development managers should eliminate special sprints, ensure each sprint delivers a shippable product, and address issues as they arise to maintain true agility and reduce risk. https://engineering-leadership.hinshelwood.com/signals/let-us-do-the-maths/ Wed, 30 Apr 2025 15:30:52 +0100 https://engineering-leadership.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.hinshelwood.com/videos/cloud-migration-without-the-mayhem-how-to-move-legacy-systems-safely-and-set-your-teams-up-for-success/ Mon, 05 May 2025 06:00:53 +0000 https://engineering-leadership.hinshelwood.com/videos/cloud-migration-without-the-mayhem-how-to-move-legacy-systems-safely-and-set-your-teams-up-for-success/ Cloud migration works best when approached gradually, using a hybrid model to reduce risk and avoid simply moving existing problems to the cloud. Success depends on understanding both your technology and how your teams work, aligning people and processes, and focusing on long-term maintainability. Treat migration as an ongoing journey, not a rushed project, and invest in shared understanding and continuous improvement to ensure a smooth transition. https://engineering-leadership.hinshelwood.com/videos/the-importance-of-visualizing-your-work-in-a-kanban-strategy/ Thu, 07 Mar 2024 07:00:10 +0000 https://engineering-leadership.hinshelwood.com/videos/the-importance-of-visualizing-your-work-in-a-kanban-strategy/ Visualizing work in Kanban is essential for team clarity, transparency, and accountability, but its real value comes from aligning everyone on shared workflows and rules. Teams should collaboratively define what gets visualized, map out each workflow stage, and document these agreements to avoid misalignment and inefficiencies. Prioritize team alignment over optimization, and consider using flow metrics and workshops to continuously improve your process. https://engineering-leadership.hinshelwood.com/videos/the-power-of-kaizen-continuous-improvement-in-scrum-and-beyond/ Sun, 25 Aug 2024 22:00:34 +0000 https://engineering-leadership.hinshelwood.com/videos/the-power-of-kaizen-continuous-improvement-in-scrum-and-beyond/ Kaizen means making small, ongoing improvements that add up to big results over time, and it fits naturally into Scrum through practices like Sprint Retrospectives and workflow optimization. Focusing on incremental changes, measuring their impact, and fostering a culture of continuous improvement can lead to better team collaboration, reduced cycle times, and higher efficiency. Start by encouraging your team to identify and act on small improvements each sprint, measure outcomes, and celebrate progress to build momentum. https://engineering-leadership.hinshelwood.com/articles/you-are-doing-scrum-but-the-scrum-master-tells-the-team-what-to-do/ Tue, 13 Sep 2011 20:40:07 +0000 https://engineering-leadership.hinshelwood.com/articles/you-are-doing-scrum-but-the-scrum-master-tells-the-team-what-to-do/ Explains why Scrum Masters should not direct teams, emphasising self-organisation, shared responsibility, and the importance of team autonomy in Scrum practices. https://engineering-leadership.hinshelwood.com/articles/pragmatism-crushes-dogma-in-the-wild/ Thu, 21 Mar 2024 09:30:00 +0000 https://engineering-leadership.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.hinshelwood.com/videos/mastering-agile-3-essential-strategies-to-boost-your-team's-sprint-success/ Thu, 16 Nov 2023 07:00:16 +0000 https://engineering-leadership.hinshelwood.com/videos/mastering-agile-3-essential-strategies-to-boost-your-team's-sprint-success/ To improve your team’s Sprint outcomes, clearly define what “done” means for every task, avoid overcommitting by leaving room for technical debt and unexpected issues, and make backlog refinement a regular priority to catch blockers early. These steps help align expectations, reduce surprises, and create a smoother workflow. Review your current practices and adjust to ensure these strategies are in place. https://engineering-leadership.hinshelwood.com/videos/transforming-scrum-training-how-real-world-insights-empower-agile-teams-at-great-calm/ Thu, 27 Jul 2017 18:16:30 +0000 https://engineering-leadership.hinshelwood.com/videos/transforming-scrum-training-how-real-world-insights-empower-agile-teams-at-great-calm/ Great Calm improved team alignment and agility by investing in Scrum training led by a trainer with real engineering experience, which fostered open dialogue and practical learning. The training is expected to enhance communication, align teams with business goals, and empower them to own their processes. Development managers should consider similar real-world-focused training to drive meaningful change and continuous improvement in their teams. https://engineering-leadership.hinshelwood.com/signals/frequent-releases-are-not-just-a-technical-strategy/ Fri, 07 Feb 2025 16:30:01 +0000 https://engineering-leadership.hinshelwood.com/signals/frequent-releases-are-not-just-a-technical-strategy/ Frequent releases help teams learn from real users and avoid wasting effort on features that may not work, as shown by Microsoft’s costly Windows 8 failure. Research shows that teams releasing often recover faster and reduce costs. To reduce risk and improve outcomes, prioritize frequent releases and adapt based on user feedback. https://engineering-leadership.hinshelwood.com/videos/the-problem-with-incompetent-scrum-masters-why-lack-of-skills-in-team-context-results-in-poor-roi/ Tue, 22 Oct 2024 07:00:08 +0000 https://engineering-leadership.hinshelwood.com/videos/the-problem-with-incompetent-scrum-masters-why-lack-of-skills-in-team-context-results-in-poor-roi/ Hiring Scrum Masters without the right skills leads to poor returns because they fail to drive team focus, innovation, and product quality. Key metrics like innovation rate, on-product index, usage index, and installed version index reveal how much value your teams actually deliver, often much less than assumed. To improve ROI, measure these metrics regularly and hold Scrum Masters accountable for tangible progress. https://engineering-leadership.hinshelwood.com/videos/unlocking-team-potential-the-essential-role-of-a-scrum-master-in-agile-success/ Mon, 22 May 2023 14:00:41 +0000 https://engineering-leadership.hinshelwood.com/videos/unlocking-team-potential-the-essential-role-of-a-scrum-master-in-agile-success/ A Scrum Master is essential for team effectiveness because they guide teams by understanding business needs, technical practices like DevOps, and organisational change. Without this role, teams often struggle to deliver value quickly and improve continuously. Development managers should ensure their teams have access to a skilled Scrum Master or equivalent expertise to maximize productivity and quality. https://engineering-leadership.hinshelwood.com/signals/understanding-blocked-columns-and-stalled-work-in-project-boards/ Tue, 04 Mar 2025 16:30:01 +0000 https://engineering-leadership.hinshelwood.com/signals/understanding-blocked-columns-and-stalled-work-in-project-boards/ Using a separate “Blocked” column on project boards makes stalled work seem normal, leading to forgotten tasks, inflated work-in-progress, and lost context. Instead, keep blocked items visible in their current workflow state and highlight or tag them so the team addresses issues quickly. Review your process to ensure blocked work is surfaced and resolved without becoming invisible. https://engineering-leadership.hinshelwood.com/signals/too-many-teams-overcomplicate-their-branching-strategies/ Thu, 06 Feb 2025 09:38:01 +0000 https://engineering-leadership.hinshelwood.com/signals/too-many-teams-overcomplicate-their-branching-strategies/ Many teams make branching too complex, which slows delivery and adds risk. Simple models like GitHub Flow or Release Flow help teams move faster and deliver value more consistently. Focus on minimizing branching complexity to improve speed and reliability. https://engineering-leadership.hinshelwood.com/signals/we-don-t-have-time-for-automation-but-manual-testing-slows-releases-and-quality/ Mon, 07 Apr 2025 15:30:01 +0100 https://engineering-leadership.hinshelwood.com/signals/we-don-t-have-time-for-automation-but-manual-testing-slows-releases-and-quality/ Relying on manual testing slows releases, overwhelms testers, and lets bugs slip through, making it impossible to keep up with rapid changes. Automation is essential for maintaining both speed and quality in software development. Teams should prioritize moving to automated testing to avoid bottlenecks and improve release reliability. https://engineering-leadership.hinshelwood.com/signals/not-all-delays-are-the-same/ Sat, 15 Feb 2025 16:30:01 +0000 https://engineering-leadership.hinshelwood.com/signals/not-all-delays-are-the-same/ Not all delays are equal; waiting for approval is different from being blocked by missing dependencies. Treating all delays as blocks hides real workflow issues and reduces accountability. Make delay sources explicit, track idle time, and highlight true blockers to identify and fix underlying problems. https://engineering-leadership.hinshelwood.com/videos/the-pitfalls-of-routine-agile-questions-avoiding-the-ghosts-of-agile-past/ Wed, 03 Jan 2024 07:00:13 +0000 https://engineering-leadership.hinshelwood.com/videos/the-pitfalls-of-routine-agile-questions-avoiding-the-ghosts-of-agile-past/ Focusing daily meetings on routine status questions leads to disengagement and distracts from delivering real value. Instead, teams should use these meetings to track progress toward sprint goals, manage aging tasks before they become bottlenecks, and adapt ceremonies to support value delivery and continuous improvement. Review your Agile practices and shift the focus from individual updates to team outcomes for better results. https://engineering-leadership.hinshelwood.com/articles/getting-started-with-a-definition-of-done-dod/ Mon, 14 Dec 2020 13:03:00 +0000 https://engineering-leadership.hinshelwood.com/articles/getting-started-with-a-definition-of-done-dod/ A clear Definition of Done (DoD) is essential for ensuring software quality and predictable delivery, as it sets shared criteria for what “done” means for every increment. Involve the whole Scrum Team and relevant experts to create a short, measurable checklist that covers code quality, testing, security, and usability, and review it regularly to keep raising the quality bar. Before starting sprints, make sure your current increment meets the DoD, and continuously improve both your software and your DoD to maintain a working, shippable product. https://engineering-leadership.hinshelwood.com/signals/if-software-is-not-delivered-it-is-not-valuable/ Sat, 01 Mar 2025 16:30:03 +0000 https://engineering-leadership.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.hinshelwood.com/signals/every-unreleased-feature-is-a-cost/ Wed, 05 Feb 2025 16:30:01 +0000 https://engineering-leadership.hinshelwood.com/signals/every-unreleased-feature-is-a-cost/ Unreleased features create hidden costs and risks, as work that is not delivered provides no real value. Evidence shows that frequent releases reduce failure rates and improve stability, while long cycles lead to more rework and missed opportunities. Focus on shipping regularly to ensure your team’s efforts translate into actual value. https://engineering-leadership.hinshelwood.com/videos/transforming-chaos-into-collaboration-how-a-common-framework-can-revolutionise-your-team's-dynamics/ Fri, 28 Jul 2017 11:55:30 +0000 https://engineering-leadership.hinshelwood.com/videos/transforming-chaos-into-collaboration-how-a-common-framework-can-revolutionise-your-team's-dynamics/ Introducing a common framework and structured backlog helped transform a chaotic team environment into one marked by better collaboration, clearer communication, and increased trust. Teams benefited from a shared language, improved confidence, and more effective problem-solving, while regular feedback channels boosted morale and engagement. Development managers should consider adopting structured frameworks and open communication practices to drive positive change and sustain team momentum. https://engineering-leadership.hinshelwood.com/videos/empowering-teams-to-tailor-their-processes-a-path-to-true-agility/ Fri, 26 Jul 2024 06:45:00 +0000 https://engineering-leadership.hinshelwood.com/videos/empowering-teams-to-tailor-their-processes-a-path-to-true-agility/ Empowering teams to adapt their processes to their specific needs leads to greater value, less waste, and more innovation, while rigid, one-size-fits-all processes can cause delays, unnecessary costs, and frustration. Development managers should assess whether their teams have the freedom to experiment, minimize bureaucracy, and focus on delivering customer value rather than just following procedures. To achieve true agility, encourage teams to tailor their ways of working and continuously improve based on what they learn. https://engineering-leadership.hinshelwood.com/videos/scrum-is-like-communism-it-doesn't-work-myth-3/ Wed, 25 Oct 2023 07:00:09 +0000 https://engineering-leadership.hinshelwood.com/videos/scrum-is-like-communism-it-doesn't-work-myth-3/ Scrum does not inherently lead to micromanagement; this misconception arises when organizations misapply Scrum by imposing top-down control instead of empowering teams. True Scrum gives developers autonomy over their work, encourages open collaboration, and relies on trust and technical expertise. Development managers should focus on enabling team decision-making and fostering a culture of trust to realize the full benefits of Agile. https://engineering-leadership.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.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.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.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.hinshelwood.com/videos/empowering-teams-to-maximize-value-and-return-on-investment/ Wed, 24 Jul 2024 06:45:04 +0000 https://engineering-leadership.hinshelwood.com/videos/empowering-teams-to-maximize-value-and-return-on-investment/ Empowering teams to adapt their own processes is essential for maximizing value and return on investment in Agile environments. Teams that have autonomy, leadership support, and a culture of continuous improvement consistently outperform those forced to follow rigid, standardized processes. Development managers should trust teams to tailor their workflows, provide the necessary tools and support, and focus on outcomes rather than strict process adherence. https://engineering-leadership.hinshelwood.com/articles/professional-scrum-developer-net-training-in-london/ Fri, 18 Jun 2010 15:53:27 +0000 https://engineering-leadership.hinshelwood.com/articles/professional-scrum-developer-net-training-in-london/ Intensive five-day course for software developers covering Scrum, Visual Studio 2010, .NET, and Agile practices through hands-on team sprints and real-world case studies. https://engineering-leadership.hinshelwood.com/signals/scrum-masters-enabling-teams-fostering-agility-removing-blockers/ Wed, 05 Mar 2025 16:30:00 +0000 https://engineering-leadership.hinshelwood.com/signals/scrum-masters-enabling-teams-fostering-agility-removing-blockers/ Scrum Masters are responsible for ensuring teams deliver effectively by creating the right conditions for success, not just facilitating meetings or shielding teams from pressure. Their accountability lies in identifying and addressing blockers, improving team effectiveness, and ensuring consistent delivery each sprint. Development managers should hold Scrum Masters accountable for team delivery outcomes, not just process adherence. https://engineering-leadership.hinshelwood.com/videos/overcoming-the-plague-of-rigidity-embracing-true-agility-in-your-team/ Wed, 08 Nov 2023 11:00:53 +0000 https://engineering-leadership.hinshelwood.com/videos/overcoming-the-plague-of-rigidity-embracing-true-agility-in-your-team/ Rigidly sticking to tools and processes can cause teams to stagnate, resist change, and miss out on innovation. True agility comes from regularly reassessing practices, encouraging experimentation, and focusing on outcomes rather than methods. Development managers should foster a culture of continuous improvement and adaptability to keep their teams responsive and effective. https://engineering-leadership.hinshelwood.com/videos/what-are-the-top-3-things-a-scrum-master-needs-to-bear-in-mind-when-adopting-the-coaching-stance/ Mon, 18 Sep 2023 07:00:32 +0000 https://engineering-leadership.hinshelwood.com/videos/what-are-the-top-3-things-a-scrum-master-needs-to-bear-in-mind-when-adopting-the-coaching-stance/ A Scrum Master adopting a coaching stance should focus on guiding teams toward self-organisation, building trust and influence through expertise and empathy, and adapting their approach to the team’s unique context and culture. Key outcomes include stronger collaboration, empowered decision-making, and higher team satisfaction. To be effective, Scrum Masters should actively listen, foster a positive environment, and continuously develop their own skills. https://engineering-leadership.hinshelwood.com/articles/decoding-scrum-team-work-balancing-sprint-and-refinement-work/ Thu, 14 Sep 2023 14:25:00 +0000 https://engineering-leadership.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.hinshelwood.com/videos/stop-starting-and-start-finishing-the-key-to-team-success/ Wed, 31 Jan 2024 14:26:11 +0000 https://engineering-leadership.hinshelwood.com/videos/stop-starting-and-start-finishing-the-key-to-team-success/ Trying to do too many tasks at once reduces team productivity due to context switching and leads to slower delivery and burnout. Focusing on finishing work before starting new tasks, limiting work in progress, and prioritizing by business value helps teams deliver faster and more predictably. Development managers should ensure their teams complete current work before taking on new tasks to maximize efficiency and business impact. https://engineering-leadership.hinshelwood.com/videos/how-does-a-scrum-team-decide-on-a-sprint-goal/ Fri, 02 Jun 2023 07:00:09 +0000 https://engineering-leadership.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.hinshelwood.com/guides/scrum-guide/ Mon, 01 Feb 2010 00:00:00 +0000 https://engineering-leadership.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.hinshelwood.com/videos/how-does-a-scrum-master-or-agile-coach-motivate-a-scrum-team/ Mon, 11 Sep 2023 07:00:17 +0000 https://engineering-leadership.hinshelwood.com/videos/how-does-a-scrum-master-or-agile-coach-motivate-a-scrum-team/ Scrum Masters and Agile coaches play a key role in keeping teams motivated by aligning goals with stakeholder value, celebrating achievements, and fostering open communication. Teams lose motivation when goals are misaligned or stakeholder engagement is lacking, so it is important to set achievable objectives, involve stakeholders, and encourage autonomy and continuous learning. Regularly review team morale, connect work to its broader impact, and create feedback loops to maintain a resilient and high-performing team. https://engineering-leadership.hinshelwood.com/videos/what-would-you-advise-a-scrum-team-to-do-in-their-first-4-weeks/ Thu, 16 Feb 2023 07:00:01 +0000 https://engineering-leadership.hinshelwood.com/videos/what-would-you-advise-a-scrum-team-to-do-in-their-first-4-weeks/ In the first four weeks, a scrum team should focus on practicing scrum correctly, learning both what works and what does not, and experimenting to find the best fit for their context. Teams should document obstacles and improvements, address one key change per sprint, and use retrospectives to drive continuous improvement. This approach builds a strong foundation and helps make organizational issues visible for future action. https://engineering-leadership.hinshelwood.com/videos/avoiding-the-seven-deadly-sins-of-agile-transform-your-organisation-for-true-agility/ Sun, 14 Apr 2024 12:17:16 +0000 https://engineering-leadership.hinshelwood.com/videos/avoiding-the-seven-deadly-sins-of-agile-transform-your-organisation-for-true-agility/ Achieving true agility requires more than adopting Agile practices; organisations often fall into seven common traps such as seeking quick fixes, overloading backlogs, focusing on resource utilisation over value, lacking accountability, fostering blame, copying others blindly, and letting pride block learning. These behaviours hinder innovation, value delivery, and team effectiveness. Development managers should regularly assess and address these pitfalls, tailor Agile to their context, and foster a culture of continuous improvement and honest reflection. https://engineering-leadership.hinshelwood.com/videos/why-every-scrum-master-needs-an-immersive-training-experience/ Tue, 21 Nov 2023 07:00:21 +0000 https://engineering-leadership.hinshelwood.com/videos/why-every-scrum-master-needs-an-immersive-training-experience/ Immersive training is essential for Scrum Masters who already have hands-on experience, as it deepens practical skills, sharpens leadership abilities, and drives better team outcomes. Unlike standard courses, immersive classes focus on real-world challenges, immediate feedback, and peer learning, helping Scrum Masters maximize team value and effectiveness. Development managers should encourage experienced Scrum Masters to pursue immersive training to foster continuous improvement and stronger team leadership. https://engineering-leadership.hinshelwood.com/videos/what-is-the-hardest-part-of-working-with-a-brand-new-scrum-team/ Fri, 03 Feb 2023 07:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/what-is-the-hardest-part-of-working-with-a-brand-new-scrum-team/ The hardest part of working with a new scrum team is overcoming their misconceptions about scrum and their focus on superficial practices instead of core principles. Teams often concentrate on the mechanics rather than embracing empiricism and rapid feedback loops, which are essential for high performance. Development managers should guide teams to master foundational agile concepts and use evidence-based learning to drive improvement. https://engineering-leadership.hinshelwood.com/signals/what-makes-an-effective-scrum-master-beyond-meeting-facilitation/ Sun, 23 Feb 2025 16:30:01 +0000 https://engineering-leadership.hinshelwood.com/signals/what-makes-an-effective-scrum-master-beyond-meeting-facilitation/ An effective Scrum Master builds a self-sustaining team that consistently delivers valuable, high-quality products by enabling data-driven planning, supporting meaningful backlog management, removing organizational obstacles, and fostering true cross-team collaboration. Their real value is seen when the team thrives independently rather than relying on constant guidance. If your team would struggle without the Scrum Master, it may be time to reassess their approach. https://engineering-leadership.hinshelwood.com/videos/the-future-of-scrum-training-immersive-learning-for-lasting-change/ Thu, 23 Nov 2023 08:30:06 +0000 https://engineering-leadership.hinshelwood.com/videos/the-future-of-scrum-training-immersive-learning-for-lasting-change/ Immersive learning is more effective than traditional Scrum training because it provides ongoing support, real-time problem solving, and peer collaboration over several weeks, helping participants apply new skills in real situations. This approach leads to gradual, sustainable change and builds confidence through shared learning and continuous improvement. Development managers should consider immersive learning to achieve lasting transformation in their teams and organizations. https://engineering-leadership.hinshelwood.com/videos/how-does-the-aps-course-help-people-apply-scrum-effectively/ Wed, 18 Jan 2023 08:57:16 +0000 https://engineering-leadership.hinshelwood.com/videos/how-does-the-aps-course-help-people-apply-scrum-effectively/ The APS course uses hands-on simulations to help participants deeply understand scrum, recognize common dysfunctions in traditional and current agile practices, and learn how to apply scrum effectively even within organizational constraints. It highlights how traditional mindsets and policies can block team success and shows the value of aligning with scrum principles for better problem-solving and outcomes. Managers are encouraged to attend so they can see firsthand how their decisions impact teams and identify changes needed to support effective scrum adoption. https://engineering-leadership.hinshelwood.com/workshops/sprint-review-1/ Tue, 17 Sep 2024 00:00:00 +0000 https://engineering-leadership.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.hinshelwood.com/videos/transform-your-leadership-the-power-of-evidence-based-management-in-agile/ Wed, 29 Nov 2023 11:00:03 +0000 https://engineering-leadership.hinshelwood.com/videos/transform-your-leadership-the-power-of-evidence-based-management-in-agile/ Evidence-based management helps Agile leaders make better decisions by using data on team performance, customer satisfaction, and product quality, leading to continuous improvement and stronger collaboration. Real-world examples show that adopting EBM can improve delivery times, morale, and outcomes. Development managers should invest in EBM training, encourage data-driven practices, and support experimentation to drive team success. https://engineering-leadership.hinshelwood.com/signals/teams-are-self-managing/ Fri, 21 Mar 2025 16:30:04 +0000 https://engineering-leadership.hinshelwood.com/signals/teams-are-self-managing/ Self-managing teams still need structure and boundaries to be effective, which is where the Scrum Master plays a key role by ensuring clarity, alignment, and accountability. Without this support, autonomy can lead to chaos and poor delivery. Development managers should balance team autonomy with proactive leadership to maintain high performance. https://engineering-leadership.hinshelwood.com/videos/ditch-the-agile-bandit-mentality-how-to-prioritise-value-over-estimates-for-team-success/ Fri, 05 Jan 2024 11:00:32 +0000 https://engineering-leadership.hinshelwood.com/videos/ditch-the-agile-bandit-mentality-how-to-prioritise-value-over-estimates-for-team-success/ Focusing on estimates instead of value delivery can harm team morale and undermine Agile principles. Shifting attention to outcomes, fostering psychological safety, and using metrics that reflect real customer impact lead to better products and a more engaged team. Development managers should prioritise value and team well-being over tracking estimates to achieve lasting success. https://engineering-leadership.hinshelwood.com/signals/agile-without-a-usable-working-product-is-just-expensive-theatre/ Sun, 20 Apr 2025 15:30:27 +0100 https://engineering-leadership.hinshelwood.com/signals/agile-without-a-usable-working-product-is-just-expensive-theatre/ Agile only delivers value if each sprint results in a usable working product; focusing on rituals, documentation, or velocity without real output wastes time and resources. The key measure of success is having something shippable at the end of every sprint, which enables feedback and reduces risk. Development managers should ensure their teams are consistently delivering usable products rather than just going through the motions. https://engineering-leadership.hinshelwood.com/videos/taming-the-chaos-factor-how-to-align-your-agile-teams-for-success/ Thu, 09 Nov 2023 10:45:01 +0000 https://engineering-leadership.hinshelwood.com/videos/taming-the-chaos-factor-how-to-align-your-agile-teams-for-success/ Chaos in Agile teams often results from unclear goals, poor communication, and lack of alignment, leading to disjointed work, low morale, and ineffective decisions. To address this, set clear objectives, ensure open communication, and align teams with the organisation’s vision. Focus on fostering collaboration and regularly reinforcing shared goals to create a more productive and unified environment. https://engineering-leadership.hinshelwood.com/videos/combatting-the-agile-apocalypse-how-to-overcome-the-famine-of-feedback-and-engagement/ Wed, 08 Nov 2023 06:45:00 +0000 https://engineering-leadership.hinshelwood.com/videos/combatting-the-agile-apocalypse-how-to-overcome-the-famine-of-feedback-and-engagement/ A lack of feedback and engagement from stakeholders, especially the product owner, leads to disengaged teams, poor product alignment, and increased risk of failure. Regular feedback sessions, open communication, and early stakeholder involvement are essential to keep teams motivated and ensure products meet business needs. Development managers should prioritise active stakeholder participation to maintain team morale and deliver better outcomes. https://engineering-leadership.hinshelwood.com/videos/7-deadly-sins-of-agile-greed/ Wed, 11 Oct 2023 12:00:36 +0000 https://engineering-leadership.hinshelwood.com/videos/7-deadly-sins-of-agile-greed/ Focusing on resource utilisation over value in Agile leads to busywork, burnout, and reduced innovation, undermining true productivity. Teams should prioritise delivering customer value, balance workloads, and foster open communication and trust to enable creativity and continuous improvement. Development managers should shift from maximising activity to nurturing a value-driven, healthy Agile culture that supports learning and adaptation. https://engineering-leadership.hinshelwood.com/articles/balance-of-leadership-and-control-in-scrum/ Mon, 17 Mar 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/articles/balance-of-leadership-and-control-in-scrum/ Scrum Masters and Product Owners are expected to deliver results, so they need both influence and enough authority to remove obstacles, enforce alignment, and ensure accountability. Too much control stifles team autonomy, but too little makes teams ineffective; the right balance depends on the organisation and situation. Development managers should empower these roles with the authority needed to drive change while maintaining team ownership and continuous improvement. https://engineering-leadership.hinshelwood.com/videos/cultivating-patience-the-secret-ingredient-for-thriving-agile-teams/ Fri, 08 Dec 2023 11:00:09 +0000 https://engineering-leadership.hinshelwood.com/videos/cultivating-patience-the-secret-ingredient-for-thriving-agile-teams/ Patience is essential for agile teams to build trust, avoid blame, and support growth, leading to better collaboration and outcomes. Leaders should set realistic expectations, encourage open communication, and model patient behavior to foster a healthy team environment. Take time to invest in team development and celebrate progress to enable long-term success. https://engineering-leadership.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.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.hinshelwood.com/recipes/sprint-review-recipe/ Tue, 17 Sep 2024 00:00:00 +0000 https://engineering-leadership.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.hinshelwood.com/videos/scrum-doesn't-solve-problems-it-reveals-them-how-and-why-is-that-valuable/ Wed, 27 Sep 2023 07:00:29 +0000 https://engineering-leadership.hinshelwood.com/videos/scrum-doesn't-solve-problems-it-reveals-them-how-and-why-is-that-valuable/ Scrum does not fix problems but makes them visible, helping teams identify bottlenecks, communication gaps, and inefficient processes. This transparency enables continuous learning and improvement, encourages collaboration, and prompts organizations to address root causes. Development managers should use Scrum’s insights to drive real change and foster a culture of problem-solving and adaptation. https://engineering-leadership.hinshelwood.com/signals/scrum-is-not-a-process-it-is-a-social-technology-designed-to-expose-dysfunction/ Sat, 29 Mar 2025 16:30:02 +0000 https://engineering-leadership.hinshelwood.com/signals/scrum-is-not-a-process-it-is-a-social-technology-designed-to-expose-dysfunction/ Scrum is meant to reveal problems in how teams work, not just provide a set process. If the Scrum Master, Product Owner, or Developers avoid their core responsibilities, the team will struggle to deliver value. Development managers should ensure their teams use Scrum to identify and address issues, not just go through the motions. https://engineering-leadership.hinshelwood.com/videos/mastering-sprint-planning-key-principles-for-agile-success/ Fri, 26 May 2023 14:00:37 +0000 https://engineering-leadership.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.hinshelwood.com/videos/is-a-scrum-master-an-agile-micromanager/ Tue, 25 Apr 2023 07:00:06 +0000 https://engineering-leadership.hinshelwood.com/videos/is-a-scrum-master-an-agile-micromanager/ A Scrum Master is not meant to micromanage but to facilitate, support, and empower the team to make decisions and own their work. When Scrum Masters focus on mentoring and creating a culture of trust and continuous improvement, teams become more effective and innovative. Development managers should ensure Scrum Masters act as catalysts for growth rather than as traditional project managers who direct every detail. https://engineering-leadership.hinshelwood.com/videos/unlocking-naked-agility-how-happy-teams-drive-exceptional-products/ Fri, 10 May 2024 06:45:01 +0000 https://engineering-leadership.hinshelwood.com/videos/unlocking-naked-agility-how-happy-teams-drive-exceptional-products/ Happy, engaged teams are essential for building exceptional products; when people have autonomy, opportunities for growth, and a clear sense of purpose, their motivation and output improve significantly. Managers should empower decision-making, invest in skill development, and clearly communicate the vision to foster this environment. Prioritising team well-being leads to better products and more satisfied customers, so focus on creating a culture where your teams can thrive. https://engineering-leadership.hinshelwood.com/videos/the-power-of-immersive-learning-elevating-scrum-mastery-in-your-organization/ Wed, 22 Nov 2023 07:00:18 +0000 https://engineering-leadership.hinshelwood.com/videos/the-power-of-immersive-learning-elevating-scrum-mastery-in-your-organization/ Immersive learning is more effective than traditional training for developing Scrum Masters because it emphasizes hands-on assignments, real-world application, and knowledge sharing, which lead to lasting improvements in team performance. Teams immediately apply what they learn, receive real-time feedback, and benefit from collective insights, making Scrum practices like the Definition of Done part of daily work. To boost Scrum mastery and see real impact, prioritize immersive learning for your organization’s training programs. https://engineering-leadership.hinshelwood.com/videos/why-the-scrum-master-s-true-power-lies-in-influence-not-authority/ Fri, 15 Sep 2023 07:00:06 +0000 https://engineering-leadership.hinshelwood.com/videos/why-the-scrum-master-s-true-power-lies-in-influence-not-authority/ The Scrum Master’s effectiveness comes from their ability to influence and build trust within the team, not from formal authority. By consistently providing value and fostering a collaborative environment, they help teams thrive and drive continuous improvement. Development managers should focus on supporting Scrum Masters in developing their leadership and relationship-building skills rather than granting them traditional authority. https://engineering-leadership.hinshelwood.com/recipes/daily-scrum-recipe/ Tue, 17 Sep 2024 00:00:00 +0000 https://engineering-leadership.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.hinshelwood.com/videos/understanding-the-true-role-of-a-scrum-master/ Tue, 28 Nov 2023 07:00:15 +0000 https://engineering-leadership.hinshelwood.com/videos/understanding-the-true-role-of-a-scrum-master/ The true role of a Scrum Master is to maximize the effectiveness of the Scrum team, which may differ from how organizations define the job. Key to success are teaching the team Scrum principles and empiricism, using complementary practices, and actively working with the wider organization to remove obstacles. Development managers should ensure Scrum Masters are empowered to focus on these priorities and invest in ongoing training to drive both team and organizational improvement. https://engineering-leadership.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-silence/ Mon, 23 Oct 2023 11:00:23 +0000 https://engineering-leadership.hinshelwood.com/videos/7-harbingers-of-the-agile-apocalypse-silence/ Silence during agile sprint reviews signals deeper issues like lack of engagement, unclear goals, and poor product ownership, which can derail team effectiveness. To address this, focus on building trust, communicating clear objectives, and actively involving all stakeholders through inclusive practices and open discussions. Development managers should ensure product owners foster transparency and engagement to transform passive meetings into collaborative, value-driven sessions. https://engineering-leadership.hinshelwood.com/videos/7-deadly-sins-of-agile-wrath/ Mon, 16 Oct 2023 11:00:31 +0000 https://engineering-leadership.hinshelwood.com/videos/7-deadly-sins-of-agile-wrath/ Wrath in Agile teams shows up as blame and fear of mistakes, which stifles innovation and learning. Shifting from blame to shared accountability creates a safer environment for risk-taking and continuous improvement. Development managers should encourage open discussion of mistakes and support a culture where learning from errors is valued over perfection. https://engineering-leadership.hinshelwood.com/articles/does-your-company-culture-resemble-survivor/ Wed, 10 Jul 2013 19:37:00 +0000 https://engineering-leadership.hinshelwood.com/articles/does-your-company-culture-resemble-survivor/ Explores how individualistic, competitive company cultures hinder collaboration and agility, and highlights the benefits of fostering teamwork in software development. https://engineering-leadership.hinshelwood.com/videos/what-should-you-do-if-your-sprint-review-delivers-harsh-scathing-feedback/ Fri, 08 Sep 2023 07:00:07 +0000 https://engineering-leadership.hinshelwood.com/videos/what-should-you-do-if-your-sprint-review-delivers-harsh-scathing-feedback/ Harsh feedback in Sprint reviews signals a need for immediate attention and should be seen as an opportunity to realign with stakeholder needs. Investigate the root causes, engage stakeholders more effectively, and be ready to halt, pivot, or persevere based on what you learn. Use open communication and flexibility to turn negative feedback into actionable improvements for your product and process. https://engineering-leadership.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.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.hinshelwood.com/videos/what-does-a-poor-scrum-team-look-act-and-feel-like/ Fri, 27 Jan 2023 07:00:16 +0000 https://engineering-leadership.hinshelwood.com/videos/what-does-a-poor-scrum-team-look-act-and-feel-like/ Poor scrum teams are marked by autocratic leadership, dysfunctional product ownership, lack of trust, and absence of transparency, which lead to low morale and failure to deliver value. High-performing teams are rare because most organizations create barriers that prevent true collaboration and growth. To improve outcomes, focus on removing organizational obstacles and fostering an environment where teams can develop trust, openness, and shared ownership. https://engineering-leadership.hinshelwood.com/videos/does-your-team-truly-understand-your-product-vision-and-goals/ Fri, 12 Jul 2024 06:45:00 +0000 https://engineering-leadership.hinshelwood.com/videos/does-your-team-truly-understand-your-product-vision-and-goals/ Many teams lack a true understanding of the product vision and strategic goals, which leads to misaligned decisions and reduced value for customers. Regularly communicating and reinforcing these goals helps team members see how their work contributes to the bigger picture, improving collaboration and decision-making. Development managers should frequently check team alignment and use practical strategies like workshops, visual roadmaps, and leadership engagement to ensure everyone is working toward shared objectives. https://engineering-leadership.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-don't-have-a-working-agreement/ Fri, 01 Mar 2024 07:00:17 +0000 https://engineering-leadership.hinshelwood.com/videos/3-best-ways-to-wreck-kanban-don't-have-a-working-agreement/ Not having a working agreement causes chaos, misalignment, and inefficiency in teams using Kanban or similar frameworks. Clear agreements on roles, goals, processes, and workflows are essential for team alignment and success. Development managers should ensure their teams regularly create and review working agreements to avoid confusion and improve outcomes. https://engineering-leadership.hinshelwood.com/articles/what-is-your-perspective-on-collocation/ Mon, 21 Oct 2019 13:05:00 +0000 https://engineering-leadership.hinshelwood.com/articles/what-is-your-perspective-on-collocation/ Collocation, where all team members work together in the same space, is not required for Scrum but is strongly recommended, especially for new teams, as it improves communication, focus, and team ownership. While remote work is possible with the right technology, it often requires extra effort to replicate the benefits of in-person interaction. If collocation is not feasible, managers should support teams with tools and practices to minimize communication challenges and continuously improve team effectiveness. https://engineering-leadership.hinshelwood.com/videos/navigating-the-judgment-trap-how-to-foster-a-healthy-agile-environment/ Thu, 09 Nov 2023 06:45:04 +0000 https://engineering-leadership.hinshelwood.com/videos/navigating-the-judgment-trap-how-to-foster-a-healthy-agile-environment/ Judgment in Agile teams, such as rigid rules and unhealthy metric comparisons, can lower morale, stifle innovation, and create a culture of blame. To avoid this, set meaningful goals, use adaptive metrics that encourage improvement, and foster open dialogue focused on learning. Development managers should prioritize creating a safe, collaborative environment where teams feel empowered to innovate and grow. https://engineering-leadership.hinshelwood.com/videos/breaking-the-silence-how-to-combat-communication-gaps-in-agile-teams/ Thu, 02 Nov 2023 11:30:10 +0000 https://engineering-leadership.hinshelwood.com/videos/breaking-the-silence-how-to-combat-communication-gaps-in-agile-teams/ Communication gaps in Agile teams can lead to stagnation, loss of trust, and failure to deliver value. Silence often shows up as avoiding tough conversations, ignoring misalignment, withholding feedback, or making false promises. Development managers should actively foster open dialogue, model transparent communication, and create safe channels for feedback to keep teams aligned and effective. https://engineering-leadership.hinshelwood.com/videos/unlocking-scrum-success-a-comprehensive-guide-to-values-roles-artifacts-and-events/ Tue, 18 Oct 2022 16:13:02 +0000 https://engineering-leadership.hinshelwood.com/videos/unlocking-scrum-success-a-comprehensive-guide-to-values-roles-artifacts-and-events/ Scrum is a flexible framework that helps teams deliver value through transparency, clear roles, and structured events, all grounded in trust and five core values. Key elements include defined accountabilities, essential artifacts for decision-making, and regular events to inspect and adapt work. To get the most from Scrum, focus on building trust, maintaining transparency, and continuously improving team processes. https://engineering-leadership.hinshelwood.com/videos/how-to-tackle-the-challenge-of-an-ineffective-product-owner-in-agile-teams/ Fri, 27 Oct 2023 14:30:10 +0000 https://engineering-leadership.hinshelwood.com/videos/how-to-tackle-the-challenge-of-an-ineffective-product-owner-in-agile-teams/ Ineffective Product Owners, whether due to lack of skills or organisational constraints, can hinder team performance and product success. Development managers should support Product Owners through relationship-building, organisational education, and open dialogue, while ensuring the team continues to deliver quality work. Take action by fostering collaboration and advocating for clear role expectations to help Product Owners and teams succeed. https://engineering-leadership.hinshelwood.com/videos/is-your-scrum-master-struggling-discover-when-to-choose-an-agile-process-simulation-workshop/ Wed, 05 Apr 2023 07:00:03 +0000 https://engineering-leadership.hinshelwood.com/videos/is-your-scrum-master-struggling-discover-when-to-choose-an-agile-process-simulation-workshop/ If your Scrum Master is struggling with the team, first assess whether the issue is with their approach or deeper team dynamics. An Agile Process Simulation workshop can help by engaging the team in open dialogue and tailored learning, empowering them to decide if Scrum fits their needs. Prioritize collaboration and self-discovery over imposing solutions to achieve better team outcomes. https://engineering-leadership.hinshelwood.com/signals/maximising-value-from-applying-professional-scrum-training/ Mon, 09 Jun 2025 15:30:34 +0100 https://engineering-leadership.hinshelwood.com/signals/maximising-value-from-applying-professional-scrum-training/ The main benefit of Professional Scrum training is not just learning Scrum, but creating a clear list of organisational obstacles that slow delivery. When teams are empowered to identify these issues and leadership commits to addressing them, real transformation can begin. Development managers should ensure their teams have a change backlog and actively work with leadership to remove barriers. https://engineering-leadership.hinshelwood.com/signals/at-the-end-of-the-day-kanban-is-about-improving-flow/ Mon, 03 Mar 2025 15:46:26 +0000 https://engineering-leadership.hinshelwood.com/signals/at-the-end-of-the-day-kanban-is-about-improving-flow/ Kanban focuses on improving workflow by removing constraints and bottlenecks, not by pushing people to work harder or longer. Key to better delivery is reducing work in progress and identifying blockers to increase efficiency. Managers should identify and address the biggest constraint in their current workflow to see meaningful improvements. https://engineering-leadership.hinshelwood.com/videos/navigating-team-conflict-from-healthy-disagreement-to-agile-harmony/ Tue, 07 Nov 2023 11:30:07 +0000 https://engineering-leadership.hinshelwood.com/videos/navigating-team-conflict-from-healthy-disagreement-to-agile-harmony/ Team conflict is normal and can drive innovation, but if disagreements escalate unchecked, they can harm team dynamics and project outcomes. Managers should watch for signs of unhealthy conflict and use open communication, objective discussions, mediation, and clear team norms to de-escalate issues early. Addressing conflict directly helps maintain productivity and keeps teams focused on delivering value together. https://engineering-leadership.hinshelwood.com/videos/7-deadly-sins-of-agile-gluttony/ Wed, 11 Oct 2023 11:35:09 +0000 https://engineering-leadership.hinshelwood.com/videos/7-deadly-sins-of-agile-gluttony/ Excessive backlog items, overambitious sprint plans, and unnecessary product features can slow teams down and reduce focus. Regularly prioritise and trim the backlog, set realistic sprint goals, and remove unused features to keep the team agile and deliver real value. Focus on quality and relevance rather than quantity to improve productivity and morale. https://engineering-leadership.hinshelwood.com/videos/say-do-metrics-avoiding-agile-banditry-in-your-organization/ Fri, 05 Jan 2024 07:00:28 +0000 https://engineering-leadership.hinshelwood.com/videos/say-do-metrics-avoiding-agile-banditry-in-your-organization/ Relying on say-do metrics, which compare what teams promise to what they deliver, often leads to manipulated data, vanity metrics, and a focus on outputs instead of real value. This undermines psychological safety, encourages gaming the system, and disconnects leadership from actual progress. Development managers should shift their focus to measuring outcomes and value delivered, foster transparency, and create an environment where teams can be honest and adapt to change. https://engineering-leadership.hinshelwood.com/articles/how-do-you-handle-conflict-in-a-scrum-team/ Mon, 07 Oct 2019 16:32:19 +0000 https://engineering-leadership.hinshelwood.com/articles/how-do-you-handle-conflict-in-a-scrum-team/ When conflict arises in a Scrum Team, first encourage the team to resolve it themselves and use facilitation techniques that ensure everyone is heard, such as structured group discussions. The Scrum Master should coach team members and escalate only if necessary, involving HR or considering team changes as a last resort. Focus on building conflict resolution skills within the team and iteratively adapt your approach to find the best solution. https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-double-loop-learning-transform-your-scrum-master-journey-with-immersive-training/ Mon, 20 Nov 2023 07:51:59 +0000 https://engineering-leadership.hinshelwood.com/videos/unlocking-the-power-of-double-loop-learning-transform-your-scrum-master-journey-with-immersive-training/ Immersive Professional Scrum Master training enables deeper learning by encouraging participants to question existing practices, apply new strategies, and collaborate with peers from diverse backgrounds. This approach helps Scrum Masters tackle real-world challenges, uncover organisational barriers, and continuously improve their methods. Consider enrolling in immersive training to foster a culture of reflection and shared problem-solving within your teams. https://engineering-leadership.hinshelwood.com/videos/turning-user-feedback-into-actionable-work-a-guide-to-maximizing-product-value/ Wed, 10 Jul 2024 06:45:01 +0000 https://engineering-leadership.hinshelwood.com/videos/turning-user-feedback-into-actionable-work-a-guide-to-maximizing-product-value/ Turning user feedback into actionable work quickly is essential for delivering real product value and staying truly agile. Teams that engage users regularly, prioritize feedback effectively, and integrate it into each Sprint see higher satisfaction and better business results. Review feedback weekly, involve stakeholders, and empower your team to act fast so your product evolves in line with user needs. https://engineering-leadership.hinshelwood.com/videos/unlocking-trust-in-scrum-the-power-of-openness-and-transparency/ Fri, 28 Apr 2023 07:00:30 +0000 https://engineering-leadership.hinshelwood.com/videos/unlocking-trust-in-scrum-the-power-of-openness-and-transparency/ Openness is essential in Scrum because it builds trust and transparency, which are necessary for effective teamwork. Key practices include clear communication, making information easily accessible, and encouraging emotional honesty within the team. Development managers should foster an open environment to improve collaboration and address issues early. https://engineering-leadership.hinshelwood.com/articles/delivering-live-virtual-classes-in-microsoft-teams-and-mural/ Sun, 21 Jun 2020 21:40:00 +0000 https://engineering-leadership.hinshelwood.com/articles/delivering-live-virtual-classes-in-microsoft-teams-and-mural/ Delivering live virtual classes using Microsoft Teams and Mural offers strong security, flexibility, and features that support self-organising teams and foster a safe, collaborative learning environment. Running a tech check before classes saves time and sets expectations, while Teams enables students to manage their own breakout sessions and resources, promoting autonomy and engagement. For best results, set up Teams in advance and use Mural to create structured, interactive exercises that mirror in-person collaboration. https://engineering-leadership.hinshelwood.com/videos/boosting-team-morale-and-engagement-through-effective-mentorship-programs/ Mon, 02 Sep 2024 07:00:19 +0000 https://engineering-leadership.hinshelwood.com/videos/boosting-team-morale-and-engagement-through-effective-mentorship-programs/ Long-term mentorship programs that focus on intrinsic motivation, such as autonomy, mastery, and purpose, significantly boost team morale and engagement, leading to better collaboration, problem-solving, and alignment with business goals. Unlike short-term training, these programs create lasting improvements in performance and excitement across both product and engineering teams. Development managers should consider investing in ongoing mentorship to drive sustained team success and value delivery. https://engineering-leadership.hinshelwood.com/articles/professional-scrum-in-immingham-uk/ Wed, 11 Dec 2013 09:34:45 +0000 https://engineering-leadership.hinshelwood.com/articles/professional-scrum-in-immingham-uk/ Summary of a multi-team Professional Scrum training at DFDS Seaways in Immingham, UK, highlighting co-located learning, cross-team collaboration, and agile best practices. https://engineering-leadership.hinshelwood.com/articles/what's-in-a-burndown/ Wed, 28 Mar 2012 03:52:22 +0000 https://engineering-leadership.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.hinshelwood.com/articles/my-first-scrum-team-in-the-wild/ Sun, 03 Apr 2011 21:44:22 +0000 https://engineering-leadership.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.hinshelwood.com/videos/what-is-empiricism-and-why-is-it-so-critical-to-great-agile/ Wed, 30 Aug 2023 07:00:05 +0000 https://engineering-leadership.hinshelwood.com/videos/what-is-empiricism-and-why-is-it-so-critical-to-great-agile/ Empiricism is essential to Agile because it drives teams to observe real project data, inspect outcomes, and adapt quickly, ensuring alignment with changing needs. Key practices like transparency, regular feedback loops, and continuous improvement help teams stay responsive and deliver real value. Development managers should foster a culture of inspection and adaptation, using data and feedback to guide decisions and refine both processes and product backlogs. https://engineering-leadership.hinshelwood.com/videos/can-organisations-run-an-applying-professional-scrum-workshop-how-would-that-help-them/ Wed, 29 Mar 2023 07:00:17 +0000 https://engineering-leadership.hinshelwood.com/videos/can-organisations-run-an-applying-professional-scrum-workshop-how-would-that-help-them/ Running an Applying Professional Scrum workshop with your whole team creates a safe space for honest discussion, practical problem-solving, and shared learning tailored to your organisation. This approach helps teams understand their current ways of working, experience the benefits of Scrum firsthand, and fosters alignment across roles, leading to improved agility and productivity. Consider organising a private workshop to accelerate your Agile transformation and build a stronger, more collaborative workforce. https://engineering-leadership.hinshelwood.com/videos/why-the-concept-of-a-junior-scrum-master-is-a-misguided-myth/ Mon, 24 Feb 2025 07:26:46 +0000 https://engineering-leadership.hinshelwood.com/videos/why-the-concept-of-a-junior-scrum-master-is-a-misguided-myth/ The idea of a “junior Scrum Master” is misleading because the role demands significant experience, technical knowledge, and the ability to navigate complex team and organisational dynamics. Assigning this responsibility to inexperienced team members undermines both individual growth and team effectiveness. Development managers should ensure that Scrum Masters are chosen based on proven competence and relevant experience, not as entry-level positions. https://engineering-leadership.hinshelwood.com/videos/unlocking-team-potential-how-measurement-influences-engagement-and-collaboration/ Wed, 11 Sep 2024 13:45:58 +0000 https://engineering-leadership.hinshelwood.com/videos/unlocking-team-potential-how-measurement-influences-engagement-and-collaboration/ How you measure people shapes their behaviour, so focusing on individual output can reduce collaboration and engagement. Aligning metrics with team goals, encouraging open discussion about measures, and rewarding collective outcomes can boost teamwork and morale. Review your current metrics to ensure they promote the behaviours you want to see in your teams. https://engineering-leadership.hinshelwood.com/videos/the-power-of-humility-in-agile-a-core-virtue-for-success/ Tue, 12 Dec 2023 07:00:02 +0000 https://engineering-leadership.hinshelwood.com/videos/the-power-of-humility-in-agile-a-core-virtue-for-success/ Humility is crucial for Agile teams because it enables better collaboration, trust, and openness to feedback, leading to stronger products and happier teams. Recognizing that not all ideas are right, listening to others, and being willing to change course based on data and feedback are key to success. Development managers should foster a culture where team members check their egos, seek diverse perspectives, and use data thoughtfully to continuously improve. https://engineering-leadership.hinshelwood.com/videos/transforming-technical-debt-unlocking-opportunities-for-innovation-and-value/ Wed, 20 Nov 2024 16:53:31 +0000 https://engineering-leadership.hinshelwood.com/videos/transforming-technical-debt-unlocking-opportunities-for-innovation-and-value/ Technical debt is more than just a cost; it represents missed opportunities for innovation and value. Allowing technical debt to accumulate slows delivery, increases maintenance costs, and lowers team morale, while proactively addressing it empowers teams, improves agility, and enhances value delivery. Make technical debt management a regular part of your workflow and educate stakeholders to unlock your team’s full potential. https://engineering-leadership.hinshelwood.com/videos/maximise-your-scrum-process-leveraging-azure-devops-for-agile-success/ Wed, 03 Apr 2024 17:21:43 +0000 https://engineering-leadership.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.hinshelwood.com/videos/ditching-agile-banditry-why-story-points-and-velocity-metrics-are-undermining-your-team's-success/ Mon, 08 Jan 2024 11:00:37 +0000 https://engineering-leadership.hinshelwood.com/videos/ditching-agile-banditry-why-story-points-and-velocity-metrics-are-undermining-your-team's-success/ Relying on story points and velocity as performance metrics creates mistrust and pressure, undermining team collaboration and the core values of Agile. Instead, focus on objective measures like cycle time and throughput to better understand team efficiency and foster a healthier, more productive environment. Shift your metrics to support transparency and continuous improvement rather than arbitrary targets. https://engineering-leadership.hinshelwood.com/videos/unpacking-the-scrum-master-myth-why-servant-leadership-is-key-to-team-success/ Wed, 21 Jun 2023 11:00:52 +0000 https://engineering-leadership.hinshelwood.com/videos/unpacking-the-scrum-master-myth-why-servant-leadership-is-key-to-team-success/ The Scrum Master is not a manager or authority figure but a servant leader who facilitates team processes, removes obstacles, and encourages autonomy. Misconceptions like expecting status updates or report writing from the Scrum Master undermine team ownership and collaboration. Development managers should empower Scrum Masters to support teams rather than control them, fostering a culture of trust and shared responsibility. https://engineering-leadership.hinshelwood.com/articles/searching-for-self-organisation/ Wed, 31 Jul 2013 09:38:34 +0000 https://engineering-leadership.hinshelwood.com/articles/searching-for-self-organisation/ Explores the challenges and benefits of self-organising teams, highlighting key factors like team accountability, identity, size, and consistency for effective collaboration. https://engineering-leadership.hinshelwood.com/videos/the-open-guide-to-kanban-unlocking-collaborative-flow-and-real-world-value-for-every-team/ Thu, 03 Jul 2025 05:22:41 +0000 https://engineering-leadership.hinshelwood.com/videos/the-open-guide-to-kanban-unlocking-collaborative-flow-and-real-world-value-for-every-team/ The Open Guide to Kanban is a collaborative, community-driven resource that makes Kanban accessible and practical for all teams, focusing on real-world value rather than rigid rules or jargon. It encourages managers and teams to start small, visualize work, and continuously improve by contributing to and adapting the guide. Managers should engage directly with their teams, use the guide to enhance visibility and flow, and participate in the community to solve real problems together. https://engineering-leadership.hinshelwood.com/videos/how-to-overcome-agile-banditry-a-product-owner-s-journey/ Wed, 10 Jan 2024 07:00:11 +0000 https://engineering-leadership.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.hinshelwood.com/videos/mastering-kanban-a-simple-guide-to-its-core-principles/ Mon, 01 Jul 2024 07:00:24 +0000 https://engineering-leadership.hinshelwood.com/videos/mastering-kanban-a-simple-guide-to-its-core-principles/ Kanban helps teams boost productivity by visualizing their workflow, actively managing tasks, and continuously improving processes. Key benefits include increased transparency, better communication, and faster delivery through proactive management and small, ongoing improvements. Start by mapping your workflow, then focus on daily task management and regular process reviews to drive efficiency. https://engineering-leadership.hinshelwood.com/videos/understanding-the-power-of-kanban-in-scrum/ Mon, 05 Aug 2024 06:45:00 +0000 https://engineering-leadership.hinshelwood.com/videos/understanding-the-power-of-kanban-in-scrum/ Kanban is not a replacement for Scrum but a complementary strategy that increases transparency, helps teams visualize workflow, and manage work in progress, leading to better focus and faster feedback. Integrating Kanban with Scrum enables teams to identify bottlenecks, improve efficiency, and consistently meet sprint goals. Development managers should consider adding Kanban boards and WIP limits to their Scrum process to enhance team performance and value delivery. https://engineering-leadership.hinshelwood.com/videos/understanding-kanban-a-tool-for-transparency-and-continuous-improvement/ Mon, 24 Jun 2024 06:48:02 +0000 https://engineering-leadership.hinshelwood.com/videos/understanding-kanban-a-tool-for-transparency-and-continuous-improvement/ Kanban is a tool that helps teams visualize their workflow, track key metrics, and identify bottlenecks, leading to greater transparency and continuous improvement without changing existing processes. By starting with a simple board, setting work-in-progress limits, and regularly reviewing metrics, teams can quickly spot issues and make data-driven improvements. Development managers should consider implementing Kanban to gain clearer insights into team performance and drive ongoing process enhancements. https://engineering-leadership.hinshelwood.com/signals/measuring-worker-speed-in-manufacturing-plant-operations/ Tue, 11 Mar 2025 16:30:01 +0000 https://engineering-leadership.hinshelwood.com/signals/measuring-worker-speed-in-manufacturing-plant-operations/ Focusing on individual worker speed in manufacturing or knowledge work does not improve overall delivery if the system has bottlenecks or delays. True speed comes from addressing system-wide issues, not by pushing individuals to work faster. Development managers should prioritize fixing process bottlenecks rather than measuring or incentivizing individual task completion speed. https://engineering-leadership.hinshelwood.com/videos/the-power-of-charity-in-agile-how-helping-others-elevates-teams-and-organizations/ Wed, 06 Dec 2023 07:00:08 +0000 https://engineering-leadership.hinshelwood.com/videos/the-power-of-charity-in-agile-how-helping-others-elevates-teams-and-organizations/ Charity, or helping others without expecting anything in return, is a key driver of Agile team and organizational success because it builds trust, collaboration, and a shared sense of purpose. Encouraging this behavior leads to higher motivation, better product quality, and long-term growth. Development managers should actively foster a culture of giving and collective achievement to unlock these benefits. https://engineering-leadership.hinshelwood.com/articles/how-to-set-and-achieve-effective-sprint-goals/ Fri, 29 Sep 2023 12:12:59 +0000 https://engineering-leadership.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.hinshelwood.com/recipes/sprint-planning-recipe/ Tue, 17 Sep 2024 00:00:00 +0000 https://engineering-leadership.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.hinshelwood.com/videos/why-limiting-work-in-progress-is-key-to-success-in-kanban/ Mon, 22 Jul 2024 06:00:19 +0000 https://engineering-leadership.hinshelwood.com/videos/why-limiting-work-in-progress-is-key-to-success-in-kanban/ Limiting work in progress is essential for effective Kanban because it helps teams focus, exposes bottlenecks, and supports a sustainable pace, leading to higher quality and faster delivery. Teams that set and adjust WIP limits based on capacity see improved productivity and less stress. To get the benefits, involve your team in setting WIP limits and regularly review them to keep your workflow smooth and predictable. https://engineering-leadership.hinshelwood.com/videos/why-is-kanban-such-a-popular-approach-for-people-in-creative-industries/ Fri, 25 Aug 2023 07:00:00 +0000 https://engineering-leadership.hinshelwood.com/videos/why-is-kanban-such-a-popular-approach-for-people-in-creative-industries/ Kanban is popular in creative industries because it adapts to existing workflows, reduces chaos, and helps teams align on priorities without stifling creativity. It improves efficiency by visualising work, shortening cycle times, and encouraging collective decision-making. Development managers should consider mapping their team’s current process with Kanban to enhance collaboration and deliver creative work more predictably. https://engineering-leadership.hinshelwood.com/videos/the-importance-of-product-backlog-management-in-today's-agile-landscape/ Fri, 01 Dec 2023 07:00:11 +0000 https://engineering-leadership.hinshelwood.com/videos/the-importance-of-product-backlog-management-in-today's-agile-landscape/ Effective product backlog management is essential for team focus, stakeholder alignment, and delivering real value, yet many organizations neglect it, leading to confusion and wasted effort. Key issues include oversized or outdated backlogs, lack of regular refinement, insufficient detail, and poor stakeholder involvement. To improve, keep the backlog lean, refine it regularly with the whole team, ensure transparency and clarity, and use data to guide priorities; making this a priority will boost team performance and stakeholder satisfaction. https://engineering-leadership.hinshelwood.com/videos/the-power-of-peer-feedback-in-immersive-learning/ Wed, 07 Feb 2024 07:00:27 +0000 https://engineering-leadership.hinshelwood.com/videos/the-power-of-peer-feedback-in-immersive-learning/ Peer feedback in immersive learning accelerates skill development by enabling participants to apply Scrum techniques in real situations, share experiences, and collaboratively solve problems. Facilitated debriefs deepen understanding and build a shared knowledge base, leading to better retention and real-world results. Encourage your teams to actively engage in peer feedback during training to drive continuous improvement and more effective Scrum adoption. https://engineering-leadership.hinshelwood.com/articles/adventures-in-scrum-lesson-1-%E2%80%93-the-failed-sprint/ Mon, 15 Mar 2010 13:08:59 +0000 https://engineering-leadership.hinshelwood.com/articles/adventures-in-scrum-lesson-1-%E2%80%93-the-failed-sprint/ Explores common pitfalls in early Scrum adoption, highlighting why full team involvement in sprint planning is crucial and lessons learned from a failed first sprint. https://engineering-leadership.hinshelwood.com/videos/mastering-your-kanban-board-a-practical-guide-to-visualising-workflows-for-maximum-efficiency/ Mon, 08 Jul 2024 06:00:07 +0000 https://engineering-leadership.hinshelwood.com/videos/mastering-your-kanban-board-a-practical-guide-to-visualising-workflows-for-maximum-efficiency/ A clear and accurate Kanban board is essential for understanding and improving your team’s workflow. Map your actual process, adjust columns to reflect real work stages, and use visual cues to highlight priorities and bottlenecks. Regularly review and adapt your board to boost team collaboration, identify issues early, and drive continuous improvement. https://engineering-leadership.hinshelwood.com/videos/empathy-in-agile-building-trust-and-stronger-relationships-for-success/ Tue, 12 Dec 2023 11:00:04 +0000 https://engineering-leadership.hinshelwood.com/videos/empathy-in-agile-building-trust-and-stronger-relationships-for-success/ Empathy, modesty, and respect are essential for building trust and strong relationships in agile teams, leadership, and with customers, leading to better collaboration and outcomes. Avoiding assumptions and seeking diverse perspectives through open questions and feedback helps prevent bias and supports continuous improvement. Development managers should prioritise empathy and active listening to create a culture where everyone feels valued and engaged. https://engineering-leadership.hinshelwood.com/tags/sprint-review/ Sun, 11 May 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/sprint-review/ The Sprint Review is a fundamental event within the Scrum framework, aimed at evaluating the work completed during a sprint and refining the product backlog based on feedback from stakeholders. This collaborative meeting involves the Scrum Team and key stakeholders, promoting transparency and open communication regarding the product’s progress and future direction. By presenting the increment, teams can assess their achievements against the sprint goal, ensuring alignment with customer needs and expectations. This practice is crucial for enabling teams to deliver value consistently and sustainably, as it fosters continuous improvement through real-time feedback, which is essential in a rapidly changing market. The Sprint Review enhances accountability and nurtures a culture of collaboration and shared ownership among team members and stakeholders. Additionally, it provides a forum for discussing future priorities, ensuring that the product evolves to maximise value delivery. By incorporating stakeholder insights, teams can make informed decisions that improve the product’s development trajectory, ultimately leading to a more resilient and adaptive process. The Sprint Review is not just a routine check; it is a vital tool for promoting innovation and responsiveness within the organisation, contributing to long-term success and customer satisfaction through a commitment to ongoing learning and adaptation. https://engineering-leadership.hinshelwood.com/tags/site-reliability-engineering/ Mon, 05 May 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/site-reliability-engineering/ Site Reliability Engineering (SRE) is a discipline that utilises software engineering principles to develop scalable and reliable systems, effectively bridging the gap between development and operations. Originating from the need to embed reliability within the software development lifecycle, SRE ensures that systems maintain functionality and resilience under diverse conditions. This methodology prioritises automation, monitoring, and incident response, which allows teams to deliver consistent value in a sustainable manner. SRE teams establish service level objectives (SLOs) and service level indicators (SLIs) to create clear performance and reliability metrics, fostering a culture of accountability and continuous improvement. This proactive approach to problem-solving and engineering solutions to operational challenges enhances overall system performance, distinguishing SRE from traditional operations roles. By promoting shared responsibility for reliability across teams, SRE encourages collaboration and knowledge sharing, which not only improves user satisfaction but also drives positive business outcomes. Ultimately, the integration of reliability into the development process supports organisational strategic goals and enhances competitive advantage, making SRE a vital component in agile, DevOps, and product development frameworks. https://engineering-leadership.hinshelwood.com/tags/service-level-expectation/ Mon, 05 May 2025 09:46:11 +0000 https://engineering-leadership.hinshelwood.com/tags/service-level-expectation/ A Service Level Expectation (SLE) is a forecast used by Scrum Teams to estimate the time it should take for a work item to move from initiation to completion within their workflow. Originating from practices that combine elements of Scrum and Kanban, the SLE is defined by two components: a specific range of elapsed days and the probability that work items will be completed within that timeframe, such as stating that 85 percent of items should be finished in eight days or less. The SLE is calculated using the team’s historical cycle time data, which measures how long work items have taken to complete in the past. If such data is not yet available, teams are encouraged to make an informed estimate and refine it as more data becomes available. The SLE is made transparent to all team members and stakeholders, serving as a tool for identifying flow issues and prompting inspection and adaptation when expectations are not met. In agile and DevOps contexts, the SLE is valuable because it enhances predictability, supports continuous improvement, and helps teams manage stakeholder expectations by providing a clear, data-driven understanding of delivery timelines. Keeping the SLE shorter than the length of a Sprint further improves the team’s ability to deliver reliably and respond to change. https://engineering-leadership.hinshelwood.com/tags/definition-of-done/ Mon, 05 May 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/tags/definition-of-done/ The Definition of Done (DoD) is a critical framework that establishes a shared understanding of what constitutes a completed and releasable product increment within agile and DevOps environments. Originating from the need for clarity in product development, the DoD serves as an organisational standard that all teams must adhere to, ensuring that every increment meets minimum quality criteria before it can be considered complete. This framework is vital for fostering transparency and consistency across teams, enabling empirical decision-making based on real-world feedback. By defining specific criteria, such as deployment in production, telemetry collection, and validation of initial hypotheses, the DoD helps mitigate risks associated with incomplete or subpar work, thereby reducing technical debt and enhancing the overall quality of deliverables. Furthermore, it facilitates faster feedback loops and iterative learning, allowing teams to adapt their processes based on actual performance data. The DoD not only clarifies expectations for stakeholders but also protects the integrity of the product, ensuring that increments are valuable, verifiable, and ready for real-world use. In essence, the Definition of Done is foundational to maintaining high standards in product development, promoting alignment among teams, and ultimately driving successful outcomes in organisational design and delivery. https://engineering-leadership.hinshelwood.com/tags/definition-of-workflow/ Mon, 05 May 2025 09:00:00 +0000 https://engineering-leadership.hinshelwood.com/tags/definition-of-workflow/ The Definition of Workflow in the context of Kanban is a dynamic and explicit model that outlines how work progresses through a value stream, making the flow of work visible and understandable. Rather than being a fixed checklist, it consists of clear agreements and policies that determine how work is selected, initiated, managed, and completed. Key elements include entry criteria, which specify when work is ready to begin; limits on work in progress, which help manage capacity and focus; and exit policies, which define what it means for work to be considered finished at each stage. This approach is not intended for micromanagement but to enhance the transparency and legibility of the system, enabling teams to inspect and continuously improve their processes. In Kanban, the Definition of Workflow is central to making work explicit and fostering a culture of ongoing refinement. While Scrum does not formally define a Definition of Workflow, it incorporates related concepts such as the Definition of Done and encourages teams to visualise their work. Understanding and applying a Definition of Workflow is valuable in agile, DevOps, and product development environments because it clarifies expectations, supports collaboration, and provides a foundation for process improvement and adaptability. https://engineering-leadership.hinshelwood.com/tags/lead-time/ Fri, 11 Apr 2025 06:00:00 +0100 https://engineering-leadership.hinshelwood.com/tags/lead-time/ Lead Time is an essential observability metric that quantifies the duration from the initiation of a work item to its delivery to the customer. It is a practical implementation of Cycle Time often used in flow-based systems such as Kanban. This metric provides end-to-end visibility into workflow performance, helping teams identify inefficiencies and optimise delivery for improved predictability and responsiveness. By exposing how long it takes to deliver value, Lead Time enables real-time insight into system health and team effectiveness, supporting continuous improvement across Agile, Lean, and DevOps environments. https://engineering-leadership.hinshelwood.com/tags/throughput/ Wed, 09 Apr 2025 14:41:23 +0000 https://engineering-leadership.hinshelwood.com/tags/throughput/ Throughput is a critical observability metric that quantifies the volume of work completed by a system within a defined timeframe, serving as an indicator of the flow of value delivered by teams. Originating from Agile and Lean methodologies, throughput is utilised to assess system performance holistically rather than focusing on individual contributions. By monitoring throughput, teams can uncover trends, pinpoint bottlenecks, and evaluate the impact of workflow modifications on overall efficiency. Visualisation tools such as cumulative flow diagrams and flow analytics facilitate real-time tracking of throughput data, enabling teams to inspect flow health alongside other metrics like lead time and cycle time. This empirical approach fosters informed decision-making, guiding adjustments in work-in-progress limits, team structures, and planning processes. Ultimately, throughput enhances transparency and supports a culture of continuous improvement, allowing organisations to optimise their processes without relying on subjective evaluations of performance. https://engineering-leadership.hinshelwood.com/concepts/practice/ Wed, 09 Apr 2025 14:00:00 +0100 https://engineering-leadership.hinshelwood.com/concepts/practice/ Practice refers to the consistent and repeatable techniques or habits that teams employ to improve their effectiveness, collaboration, and value delivery. Originating from Agile, Lean, and DevOps methodologies, practices such as Pair Programming, Continuous Deployment, and Retrospectives are integral to fostering ongoing, systematic routines that enhance team dynamics and performance. Unlike structured methods, which provide defined steps, practices focus on the habitual actions that teams incorporate into their workflows. For instance, Pair Programming not only boosts code quality but also promotes knowledge sharing, while Retrospectives allow teams to reflect on their processes and identify areas for improvement, thus supporting continuous enhancement. Although tools like Kanban boards can facilitate these practices, the essence lies in how teams manage their workflows and adapt their routines to evolving challenges. The long-term value of practices is evident in their ability to embed behaviours that lead to predictable and sustainable outcomes, such as the frequent and reliable software releases enabled by Continuous Deployment. Ultimately, practices are crucial for effective teamwork, as they shape collaboration, drive continuous improvement, and ensure responsiveness to both internal and external demands, making them essential in the fast-paced environments characteristic of modern product development and organisational design. https://engineering-leadership.hinshelwood.com/tags/scrum-master/ Tue, 25 Mar 2025 07:35:53 +0000 https://engineering-leadership.hinshelwood.com/tags/scrum-master/ The Scrum Master is an accountability within Scrum, serving as a change agent who enables team effectiveness and organizational transformation. Far from a passive facilitator, they are accountable for creating conditions where delivery becomes inevitable through technical, business, and organizational mastery. They teach, coach, mentor, and facilitate while ensuring teams consistently deliver valuable increments every Sprint. https://engineering-leadership.hinshelwood.com/tags/shift-left-strategy/ Mon, 17 Mar 2025 14:46:11 +0000 https://engineering-leadership.hinshelwood.com/tags/shift-left-strategy/ The Shift-Left Strategy is a proactive approach in modern software development that emphasises the integration of testing, security, and compliance activities early in the development lifecycle, rather than deferring them to the end. Originating from the need to mitigate risks associated with late-stage defect detection, this strategy allows teams to identify and address issues sooner, thereby reducing the amount of rework required and accelerating feedback loops. By implementing practices such as automated testing, security as code, and continuous integration, organisations can enhance software quality and reliability from the outset. This approach is particularly valuable in agile and DevOps environments, where rapid delivery and high performance are critical. Ultimately, the Shift-Left Strategy fosters a culture of quality and efficiency, ensuring that products are not only delivered faster but also meet the necessary standards for security and compliance, making it an essential component of effective organisational design and product development. https://engineering-leadership.hinshelwood.com/tags/agile-frameworks/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/agile-frameworks/ Agile frameworks are structured methodologies designed to implement Agile principles within organisations, allowing teams to deliver value in a predictable and sustainable manner. Originating from the need for more flexible and responsive approaches to project management, frameworks such as Scrum, Kanban, and Lean provide defined roles, events, and artefacts that enhance collaboration, transparency, and continuous improvement among team members. The importance of these frameworks lies in their ability to help organisations adapt to changing market demands and customer needs, thereby maintaining competitiveness and relevance. By fostering a culture of experimentation and learning, Agile frameworks enable teams to iterate on processes and products, identify inefficiencies, and optimise workflows, which ultimately enhances value delivery. Additionally, they promote cross-functional collaboration, breaking down silos and leveraging diverse skill sets towards common objectives. This holistic approach not only improves team dynamics but also aligns organisational goals with customer satisfaction, leading to better outcomes. By integrating Agile frameworks into their operations, organisations can create an environment that prioritises responsiveness and innovation, equipping them to navigate the complexities of modern product development and market dynamics. The emphasis on continuous delivery and improvement cultivates resilience, empowering teams to thrive in an ever-evolving landscape. https://engineering-leadership.hinshelwood.com/tags/agile-planning-tools/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/agile-planning-tools/ Agile Planning Tools are vital resources that support effective backlog management, forecasting, and collaboration within Agile teams. Originating from the principles of Agile methodology, these tools enable teams to visualise their work, prioritise tasks, and monitor progress in real-time, ensuring alignment and focus on delivering value. Their importance lies in enhancing predictability and sustainability in value delivery, allowing teams to make informed decisions based on empirical data, which fosters a culture of continuous improvement and adaptability in dynamic environments. By providing a structured approach to planning, Agile Planning Tools help teams anticipate challenges and respond to changing requirements, streamlining workflows and promoting a collaborative atmosphere. Unlike Agile Project Management or Agile Product Management, which target specific project execution or product lifecycle aspects, these tools form the foundational layer that underpins all Agile practices. They facilitate not just task management but also the creation of an environment conducive to team innovation and customer satisfaction through effective planning and execution. Integrating Agile Planning Tools into daily operations enhances organisational agility and resilience, ultimately leading to improved outcomes and sustained success. https://engineering-leadership.hinshelwood.com/tags/asynchronous-development/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/asynchronous-development/ Asynchronous Development is a collaborative approach that enables team members to work independently and at different times, rather than depending on real-time interactions. This method is particularly advantageous for distributed teams, as it accommodates diverse time zones and personal schedules, facilitating continuous progress without the limitations of synchronous communication. By utilising tools and practices that support asynchronous workflows, teams can improve their efficiency and flexibility, leading to more predictable and sustainable value delivery. This concept is vital in contemporary product development, where rapid adaptation and responsiveness are essential. Asynchronous Development creates an environment where team members can contribute insights and work at their own pace, minimising bottlenecks caused by waiting for others. It fosters a culture of ownership and accountability, encouraging individuals to take responsibility for their tasks while remaining aligned with team objectives. Additionally, this approach aligns with Lean and Agile principles, promoting continuous improvement and learning. By allowing teams to operate asynchronously, organisations can better manage complexity and enhance collaboration, ensuring consistent value delivery to customers without the friction of traditional synchronous methods. This systemic shift not only boosts productivity but also nurtures a more engaged and motivated workforce, ultimately driving long-term success and innovation. https://engineering-leadership.hinshelwood.com/tags/automated-testing/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/automated-testing/ Automated Testing is a vital practice in software development that utilises automation tools to execute tests systematically, thereby enhancing the quality and reliability of software products. Originating from the need to streamline the testing process, this approach allows development teams to identify and address issues early, significantly minimising manual testing efforts and expediting the delivery of high-quality software. The significance of Automated Testing lies in its capacity to facilitate predictable and sustainable value delivery, fostering a culture of continuous improvement through shortened feedback loops. This practice aligns with Agile and DevOps principles by promoting a shift-left strategy, which encourages earlier testing in the development cycle, enhancing collaboration among cross-functional teams. Furthermore, Automated Testing serves as a long-term enabler of organisational agility, embedding quality assurance within the development workflow. This integration leads to increased throughput and a sustained focus on customer value, ultimately resulting in improved customer satisfaction and retention. By adopting this proactive approach, organisations empower their teams to innovate and adapt, ensuring competitiveness in a fast-paced market environment. https://engineering-leadership.hinshelwood.com/tags/azure-boards/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/azure-boards/ Azure Boards is an integral component of the Azure DevOps suite, specifically designed to enhance the management of Agile projects. It provides teams with tools to track work items, manage backlogs, and optimise planning through visual boards that accommodate methodologies such as Scrum and Kanban. By offering a comprehensive view of tasks, progress, and team capacity, Azure Boards promotes collaboration and communication, ensuring that all team members are aligned on priorities and deliverables. Its importance lies in fostering transparency and accountability within teams, enabling them to deliver value in a predictable and sustainable manner. The tool supports continuous improvement by allowing teams to analyse workflows, identify bottlenecks, and adapt processes based on real-time data, which streamlines project management and enhances responsiveness to changing requirements and customer feedback. Unlike other tools that may focus solely on task management, Azure Boards integrates seamlessly with other Azure DevOps services, creating a unified environment for development, testing, and deployment. This integration is vital for maintaining a consistent workflow and ensuring that all facets of product development are interconnected, ultimately leading to improved outcomes and greater organisational agility. The long-term advantages of adopting Azure Boards extend beyond immediate project needs, as it fosters a culture of continuous delivery and improvement, reinforcing the principles of Agile and Lean methodologies across the organisation. https://engineering-leadership.hinshelwood.com/tags/backlog-refinement/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/backlog-refinement/ Backlog Refinement is a fundamental practice within Agile methodologies that focuses on ensuring the product backlog is clearly defined, prioritised, and prepared for execution. Originating from the need for effective collaboration between product owners and development teams, this ongoing process involves clarifying requirements, estimating effort, and adjusting priorities based on evolving insights and stakeholder feedback. The importance of Backlog Refinement lies in its ability to enhance focus and alignment on delivering value, thereby enabling teams to deliver outcomes predictably and sustainably. By regularly refining the backlog, teams can reduce risks associated with ambiguity and miscommunication, facilitating smoother sprint planning and execution. This practice promotes a culture of continuous improvement, allowing teams to adapt to changing circumstances and customer needs while maintaining momentum. Additionally, it supports long-term planning by prioritising the most valuable items, optimising resource allocation, and enhancing overall productivity. By integrating Backlog Refinement into their workflows, organisations can foster a more responsive and agile environment, leading to improved product outcomes and greater stakeholder satisfaction. This systemic approach not only streamlines the development process but also encourages a proactive mindset among team members, empowering them to take ownership of their work and align with the organisation’s strategic objectives. https://engineering-leadership.hinshelwood.com/tags/cross-functional-teams/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/cross-functional-teams/ Cross Functional Teams are essential components in Agile, Lean, and DevOps frameworks, designed to deliver comprehensive value throughout the project lifecycle, from initial conception to final delivery. These teams consist of individuals with varied skills and expertise, enabling them to independently manage all project facets without external dependencies. This integrated approach enhances collaboration and communication, facilitating quicker decision-making and responsiveness to evolving requirements and customer feedback. The importance of Cross Functional Teams lies in their capacity to establish a sustainable workflow focused on value delivery by merging different disciplines, such as development, testing, design, and operations, thereby streamlining processes, minimising handoffs, and reducing bottlenecks. This not only boosts efficiency but also improves product quality, as team members collaborate closely to align on objectives. Additionally, the systemic nature of these teams fosters a culture of continuous improvement and knowledge sharing, creating an environment conducive to innovation. This collaborative ethos is vital for organisations seeking to maintain a competitive advantage in fast-changing markets, empowering teams to experiment and adapt based on real-time insights. Ultimately, the long-term advantages of Cross Functional Teams extend beyond immediate project results, contributing to a resilient organisational culture that embraces change and values collective expertise. https://engineering-leadership.hinshelwood.com/tags/cycle-time/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/cycle-time/ Cycle time is a key performance metric that measures the total duration required to complete a unit of work, from initiation to delivery. It is widely used in agile and DevOps methodologies to enhance team efficiency and predictability in value delivery. By monitoring cycle time, organisations can pinpoint bottlenecks, streamline processes, and optimise workflows, which leads to quicker product and service delivery. Understanding cycle time empowers teams to make data-driven decisions, fostering a culture of continuous improvement and enabling better forecasting and planning based on historical data. This predictability is crucial for aligning stakeholder expectations and meeting customer needs promptly. Furthermore, cycle time promotes a holistic view of value delivery, encouraging teams to consider the entire workflow rather than focusing on individual tasks. By minimising cycle time, organisations can improve their responsiveness to market dynamics and customer feedback, thereby gaining a competitive edge. In an era where rapid and sustainable value delivery is essential, the emphasis on cycle time is vital for organisational success. https://engineering-leadership.hinshelwood.com/tags/daily-scrum/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/daily-scrum/ The Daily Scrum is a fundamental practice within the Scrum framework that aims to improve team alignment and adaptability. Originating from agile methodologies, this brief, time-constrained meeting, usually lasting 15 minutes, provides an opportunity for team members to synchronise their activities, review progress towards the Sprint Goal, and adjust their plans as necessary. During the meeting, participants discuss their accomplishments since the last session, outline their next steps, and highlight any obstacles they are encountering. This structured yet adaptable format promotes transparency and accountability, allowing teams to respond effectively to changes and challenges. By fostering regular communication, the Daily Scrum helps maintain a focus on delivering value and ensures that the team remains aligned with the Sprint’s overall objectives. It also encourages a culture of continuous improvement, enabling team members to swiftly identify and resolve issues that may impede progress. Beyond addressing immediate project needs, the Daily Scrum nurtures long-term habits of collaboration and self-organisation, which are crucial for sustainable success in agile environments. Ultimately, the Daily Scrum serves as a powerful facilitator of team dynamics and performance, driving collective efforts towards shared goals and enhancing overall productivity. https://engineering-leadership.hinshelwood.com/tags/deployment-frequency/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/deployment-frequency/ Deployment Frequency is a key metric that measures the rate at which software is released into production, playing a vital role in contemporary product development. It originates from the need for organisations to enhance their responsiveness to customer needs by facilitating quicker feedback loops and adjustments. By optimising deployment frequency, teams can not only release features and fixes more frequently but also validate their assumptions and learn from real-world usage promptly. This concept is crucial for cultivating a culture of continuous improvement and innovation, allowing teams to experiment, iterate, and adapt to market changes effectively. A high deployment frequency reflects a mature DevOps practice characterised by automation, collaboration, and efficient processes that enable rapid delivery without sacrificing quality. Additionally, it fosters a sense of accountability and ownership among team members, as they can directly observe the impact of their contributions on end-users. By prioritising deployment frequency, organisations can establish a sustainable delivery rhythm that enhances customer satisfaction and drives long-term business success through consistent value delivery and adaptability. This systemic approach not only promotes resilience and agility but also ensures that teams remain competitive in an ever-evolving digital landscape. https://engineering-leadership.hinshelwood.com/tags/experimentation/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/experimentation/ Experimentation is a fundamental practice within agile workflows that utilises hypothesis-driven methods to test ideas and validate assumptions. Originating from the need to systematically address uncertainties, this approach enables teams to make informed decisions based on empirical evidence rather than relying solely on intuition. The importance of experimentation is underscored by its ability to facilitate predictable and sustainable value delivery, fostering a culture where failure is perceived as a learning opportunity that drives continuous improvement and resilience. Through iterative testing and feedback loops, teams can refine their products and processes, ensuring they align with customer needs and organisational objectives. Furthermore, experimentation promotes long-term systemic change by integrating a scientific mindset into the organisational culture, enhancing collaboration among cross-functional teams and boosting engagement as team members witness the direct impact of their efforts. By prioritising experimentation, organisations can create an environment that values learning and adaptability, which is essential for effective and innovative product development in today’s complex and rapidly changing landscape. This practice serves not just as a tactic but as a foundational element that influences how teams operate and evolve. https://engineering-leadership.hinshelwood.com/tags/forecasting/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/forecasting/ Forecasting is the practice of utilising empirical data to predict delivery timelines, manage risks, and optimise value delivery within Agile and Scrum frameworks. It draws from historical performance and current capacity metrics, such as cycle time, lead time, and throughput, enabling teams to make informed decisions that lead to a more predictable and sustainable approach to product development. This practice is vital for promoting transparency and accountability, as it encourages teams to reflect on their processes and outcomes, moving beyond subjective estimations to data-driven insights that enhance decision-making. By anticipating challenges and adapting proactively, teams can improve overall efficiency and effectiveness. Integrating forecasting into Agile practices not only aids in achieving immediate project goals but also fosters long-term organisational agility, creating a resilient environment that can adapt to changing market demands. This systemic approach ultimately enhances the ability to deliver high-quality products that align with customer needs and business objectives, thereby cultivating a culture of continuous improvement and innovation. https://engineering-leadership.hinshelwood.com/tags/frequent-releases/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/frequent-releases/ Frequent releases are the practice of delivering small, incremental updates to products or services on a regular basis, originating from agile methodologies and widely adopted in DevOps environments. This approach is essential for organisations seeking to swiftly respond to user feedback and market dynamics, ensuring consistent value delivery to stakeholders. By segmenting larger projects into manageable releases, teams can mitigate deployment risks, as smaller updates are easier to test and validate. This practice cultivates a culture of continuous improvement, enabling teams to iterate based on real-world usage and feedback, which is vital for maintaining a competitive edge in adapting to evolving customer needs and technological advancements. Additionally, frequent releases promote collaboration among developers, testers, and product owners, fostering a cohesive environment for product enhancement. They also contribute to a sustainable development pace, reducing the risk of burnout associated with large, infrequent releases, which in turn boosts team morale and builds stakeholder trust through visible progress and tangible outcomes. By integrating frequent releases into their operational frameworks, organisations can ensure they remain responsive and relevant in a rapidly changing market landscape. https://engineering-leadership.hinshelwood.com/tags/operational-practices/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/operational-practices/ Operational Practices refer to the techniques and strategies that organisations implement to improve their operational efficiency and delivery capabilities. Originating from methodologies such as Lean, Agile, and DevOps, these practices are utilised to streamline workflows, minimise waste, and optimise resource allocation. Their importance lies in fostering a culture of continuous improvement, enabling teams to swiftly adapt to changing demands while ensuring high-quality outputs. By establishing clear processes and enhancing collaboration, Operational Practices empower teams to make data-driven decisions, which collectively enhance performance and customer satisfaction. This systemic approach ensures that operational improvements are ingrained within the organisational culture, promoting resilience and adaptability rather than being merely reactive. Furthermore, Operational Practices align team efforts with strategic goals, ensuring that every action contributes to the organisation’s overarching mission. By prioritising these practices, organisations can create an environment conducive to innovation and consistent value delivery, ultimately leading to a more agile and responsive structure capable of navigating the complexities of modern product development and market dynamics. https://engineering-leadership.hinshelwood.com/tags/self-organisation/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/self-organisation/ Self-organisation is the capacity of teams to independently manage their work, make decisions, and adapt to evolving circumstances without external oversight. Originating from principles in Agile, Lean, and DevOps methodologies, this concept is vital for fostering a culture of ownership and accountability within teams. By empowering individuals to take initiative, self-organisation enhances collaboration and innovation, leading to improved problem-solving and value delivery. In such environments, teams leverage their collective skills and insights, which boosts engagement and drives continuous improvement through experimentation and learning from failures. This autonomy not only enhances productivity but also contributes to long-term organisational resilience, enabling teams to thrive in dynamic contexts. Unlike traditional hierarchical structures, self-organisation aligns with the need for adaptability and responsiveness, creating a framework that optimises workflows and ensures that organisations remain competitive and responsive to market demands. Ultimately, this approach cultivates an environment where innovation can flourish, equipping teams to navigate complexity with confidence and agility. https://engineering-leadership.hinshelwood.com/tags/team-performance/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/team-performance/ Team performance is the consistent ability of a team to deliver outcomes through its established system of work, reflecting delivery capability over time as indicated by observable patterns in flow, responsiveness, and quality. This concept originates from the understanding that performance is shaped by the structure and constraints of the operational system, influenced by factors such as team composition, collaboration habits, skill alignment, and clarity of purpose. As a system-level capability, team performance transcends individual or cultural traits, making it crucial for organisations aiming to enhance their agile and DevOps practices. By employing flow metrics, retrospectives, and empirical signals to evaluate performance, organisations can discern whether teams are improving, stagnating, or hindered by external dependencies. High-performing teams demonstrate both consistency and adaptability in their delivery, even amidst change. Enhancing team performance involves a focus on system design, which includes limiting work in progress, refining collaboration patterns, and increasing visibility into obstacles. This systemic approach ensures that improvements are not only effective but also sustainable and repeatable across the organisation, ultimately contributing to more efficient product development and organisational design. https://engineering-leadership.hinshelwood.com/tags/technical-debt/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/technical-debt/ Technical debt is the concept that encapsulates the hidden costs associated with opting for quick, suboptimal solutions in software development rather than investing time in more effective, long-term strategies. It often emerges from factors such as hurried development processes, insufficient documentation, or reliance on outdated technologies. Recognising and managing technical debt is essential for teams striving to deliver consistent and sustainable value, as its accumulation can impede innovation and responsiveness to market changes, ultimately compromising product quality and delivery timelines. Addressing technical debt requires a commitment to refactoring, enhancing code quality, and adopting superior tools and practices, which not only boosts team efficiency but also cultivates a culture of continuous improvement. By systematically tackling technical debt, organisations can sustain a healthy development pace, ensuring competitiveness and responsiveness to customer demands. This strategic focus on technical debt is crucial for fostering organisational agility, as it directly impacts the ability to innovate and adapt in a fast-evolving landscape. https://engineering-leadership.hinshelwood.com/tags/test-driven-development/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/test-driven-development/ Test Driven Development (TDD) is a software development methodology that prioritises the creation of automated tests prior to writing the actual code. Originating from the need for a structured approach to software design, TDD ensures that development is guided by the requirements specified in the tests, which clarifies the intended functionality of the software. This practice is crucial in the context of Agile and DevOps as it promotes a culture of quality and accountability, allowing teams to deliver consistent and sustainable value. By embedding testing into the development lifecycle from the beginning, TDD significantly reduces the risk of defects and simplifies the process of refactoring, with tests acting as a safety net. The long-term advantages of TDD extend beyond immediate improvements in code quality; it fosters a mindset of continuous improvement and adaptability among team members. This approach aligns seamlessly with Agile principles, enhancing collaboration and responsiveness to change while supporting technical excellence. By focusing on test coverage, teams can confidently introduce new features and enhancements, ensuring that existing functionalities remain intact. Ultimately, TDD not only improves individual projects but also cultivates a culture of reliability and trust within the organisation, leading to better outcomes for stakeholders and customers. https://engineering-leadership.hinshelwood.com/tags/transparency/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/transparency/ Transparency is the practice of fostering openness and visibility within agile processes, which is essential for building trust and accountability among team members. Originating from agile methodologies, transparency enables teams to share information freely, allowing all members to grasp project status, challenges, and progress. This clarity is vital for effective collaboration, empowering individuals to make informed decisions and contribute significantly to team objectives. By promoting transparency, organisations can more easily identify bottlenecks and inefficiencies, facilitating continuous improvement and creating a culture that values feedback and adaptability. This openness not only enhances team dynamics but also aligns efforts towards common goals, ensuring that all members work together to deliver value in a predictable and sustainable manner. Furthermore, transparency supports a long-term approach to organisational health by cultivating an environment of psychological safety, where team members feel secure in expressing concerns and proposing innovations without fear of retribution. This ultimately results in a more resilient organisation, capable of navigating the complexities and uncertainties inherent in product development. By embedding transparency into daily operations, teams can improve their performance and achieve meaningful outcomes that resonate with stakeholders and customers. https://engineering-leadership.hinshelwood.com/tags/value-stream-mapping/ Tue, 11 Feb 2025 10:17:24 +0000 https://engineering-leadership.hinshelwood.com/tags/value-stream-mapping/ Value Stream Mapping is a visual tool designed to analyse and optimise workflows within an organisation by focusing on the flow of materials and information necessary for delivering a product or service. This method involves mapping each step of the process to identify inefficiencies, bottlenecks, and areas of waste, thereby enabling teams to streamline operations and enhance value delivery. Its importance lies in facilitating predictable and sustainable value delivery, empowering teams to make informed decisions based on empirical data, and allowing for adjustments that improve overall performance. By aligning processes with customer needs, Value Stream Mapping ensures that every step adds value towards the end goal. It is not a one-time exercise but a long-term, systemic practice that promotes ongoing reflection and adaptation, helping teams remain agile in response to changing demands and market conditions. This ultimately leads to improved customer satisfaction and organisational resilience. The insights gained from Value Stream Mapping can drive strategic initiatives and foster a culture of collaboration and shared understanding across cross-functional teams, which is essential for achieving sustained success in modern product development. https://engineering-leadership.hinshelwood.com/tags/flow-efficiency/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership.hinshelwood.com/tags/flow-efficiency/ Flow efficiency is the optimisation of work throughput within a value stream, aimed at minimising waste and reducing bottlenecks. This concept is essential for organisations seeking to deliver value in a predictable and sustainable manner, as it significantly influences the speed at which teams can respond to customer demands and market fluctuations. By examining and enhancing flow efficiency, teams can pinpoint delays and implement targeted improvements that boost overall performance. This methodology is closely aligned with Lean principles, which emphasise the removal of non-value-adding activities. Unlike metrics such as cycle time or lead time that focus on specific durations, flow efficiency offers a comprehensive view of how effectively work progresses through the system, promoting collaboration across various teams and disciplines to ensure seamless operation throughout the value stream. By emphasising flow efficiency, organisations foster a culture of continuous improvement, empowering teams to innovate and experiment. This not only increases productivity but also enhances resilience, allowing teams to adapt to evolving circumstances while consistently delivering value. Ultimately, the focus on flow efficiency nurtures an environment conducive to sustainable practices, leading to long-term success and heightened customer satisfaction. https://engineering-leadership.hinshelwood.com/categories/kanban/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership.hinshelwood.com/categories/kanban/ Kanban is a change management strategy that focuses on improving workflow and value delivery within organisations, rather than being merely a tool or visual board. Originating from Lean principles and systems thinking, Kanban encourages teams to begin with their current processes, fostering an understanding of existing systems to facilitate evolutionary improvements. Unlike prescriptive frameworks that dictate roles or time constraints, Kanban emphasises observability through visualisation of work, limiting work in progress, managing flow, and making policies explicit. This approach helps identify bottlenecks and supports evidence-based enhancements without necessitating major organisational changes. By complementing methodologies like Scrum and DevOps, Kanban enhances transparency and decision-making, allowing teams to adapt their practices over time based on feedback and performance metrics such as lead time and throughput. While often misconceived as merely a visual task management tool, the true strength of Kanban lies in its ability to create a shared understanding of system dynamics, enabling strategic improvements. This empowers teams to deliver value in a predictable, sustainable manner, making Kanban a vital strategy for organisations operating in complex and rapidly changing environments. https://engineering-leadership.hinshelwood.com/categories/lean/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership.hinshelwood.com/categories/lean/ Lean is a strategic methodology focused on maximising value while minimising waste, originating from the principles of the Toyota Production System. It is utilised to enhance organisational efficiency by delivering customer value through streamlined processes and fostering a culture of continuous improvement and respect for individuals. By systematically identifying and eliminating non-value-adding activities, Lean enables teams to optimise workflows, boost productivity, and swiftly adapt to changing market conditions. This approach transcends mere tools, embodying a mindset that prioritises long-term sustainability and systemic transformation. Techniques such as value stream mapping and flow efficiency allow teams to visualise their processes, pinpoint bottlenecks, and improve resource allocation, leading to the reliable delivery of high-quality products and services, which in turn enhances customer satisfaction and loyalty. Lean’s focus on empirical decision-making and iterative learning aligns seamlessly with Agile and DevOps principles, creating a collaborative environment that fosters rapid innovation while maintaining a commitment to value delivery. By promoting a culture of experimentation and feedback, Lean equips organisations to navigate and thrive in a dynamic landscape, ensuring their competitiveness and relevance in the market. https://engineering-leadership.hinshelwood.com/tags/one-engineering-system/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership.hinshelwood.com/tags/one-engineering-system/ The One Engineering System (1ES) is a strategic framework designed to unify engineering tools and practices across various teams, aiming to reduce friction, enhance collaboration, and ensure consistency at scale. Originating from the need to streamline workflows in software development, 1ES focuses on establishing a shared engineering backbone that allows teams to operate more efficiently by eliminating the chaos associated with disparate toolchains and ad hoc processes. This approach is crucial in agile and DevOps environments, as it promotes a common set of engineering standards that facilitate planning, coding, testing, deployment, and production support. By reducing cognitive overhead and simplifying integration, 1ES enables teams to deliver high-quality outcomes more reliably. Importantly, the framework emphasises that tools should adapt to the teams’ workflows rather than impose rigid structures, allowing for flexibility and coherence rather than uniformity. Successful implementation of 1ES necessitates investment in team enablement, including guidance, training, and support, to ensure effective adoption. When executed properly, 1ES fosters scalable engineering excellence, characterised by clear communication, consistent processes, and a resilient development lifecycle across the organisation. https://engineering-leadership.hinshelwood.com/tags/sociotechnical-systems/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership.hinshelwood.com/tags/sociotechnical-systems/ Sociotechnical systems encompass the complex interactions between social and technical components within an organisation, particularly relevant to software delivery and team performance. This concept highlights that technology is not an isolated entity; rather, it is intricately linked to the organisational culture, structures, and processes. Understanding this duality allows teams to recognise how their workflows, communication styles, and tools impact overall effectiveness. The importance of sociotechnical systems lies in their capacity to create environments where teams can deliver value in a predictable and sustainable manner. When social factors, such as collaboration, trust, and motivation, are harmonised with technical capabilities, including tools and processes, organisations can enhance efficiency and foster innovation. This alignment equips teams to swiftly adapt to evolving market demands and customer expectations, thereby improving agility. Furthermore, sociotechnical systems advocate for a long-term, systemic approach to problem-solving, promoting continuous improvement and learning. By concentrating on the interplay between human and technological elements, organisations can establish resilient frameworks that facilitate ongoing adaptation and growth, ensuring optimal utilisation of both human and technical resources to drive value creation. This comprehensive perspective is crucial for navigating the complexities of contemporary product development and achieving sustained success in a competitive environment. https://engineering-leadership.hinshelwood.com/tags/value-stream-management/ Tue, 11 Feb 2025 10:16:54 +0000 https://engineering-leadership.hinshelwood.com/tags/value-stream-management/ Value Stream Management is a strategic methodology aimed at improving the flow of value within an organisation by optimising processes, reducing waste, and aligning efforts with customer outcomes. Originating from the need to enhance operational efficiency, it involves mapping the entire value stream from ideation to delivery, enabling teams to identify and address bottlenecks and inefficiencies that impede performance. This approach is vital in the context of agile, DevOps, and product development, as it fosters a culture of continuous improvement and responsiveness to market changes. By promoting collaboration across departments and breaking down silos, Value Stream Management ensures a shared understanding of how work contributes to overarching business goals. It empowers teams to focus on delivering high-quality products that satisfy customer needs while balancing speed and efficiency. Unlike specific Agile frameworks or Lean principles that concentrate on particular practices, Value Stream Management offers a comprehensive perspective on the entire process, ensuring that each step adds value. This long-term, systemic approach not only enhances operational performance but also nurtures an environment conducive to innovation, ultimately leading to greater organisational resilience and adaptability in a fast-changing landscape.