https://engineering.hinshelwood.com/signals/ Recent content in Signals on Engineering as a Leadership System Hugo en Mon, 25 May 2026 00:00:00 +0000 https://engineering.hinshelwood.com/signals/velocity-isn-t-how-many-story-points-a-team-burns-down/ Mon, 10 Mar 2025 16:30:02 +0000 https://engineering.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.hinshelwood.com/signals/scrum-masters-are-not-glorified-meeting-schedulers/ Sun, 09 Mar 2025 16:30:01 +0000 https://engineering.hinshelwood.com/signals/scrum-masters-are-not-glorified-meeting-schedulers/ Scrum Masters must have strong technical and business skills, including coding knowledge and expertise in modern engineering practices, to effectively lead software teams. They should be able to challenge teams, identify technical debt, and promote quality, not just schedule meetings. Ensure your Scrum Master can engage with developers on technical topics to achieve real agility. https://engineering.hinshelwood.com/signals/there-no-such-thing-as-good-technical-debt/ Sat, 19 Apr 2025 15:30:34 +0100 https://engineering.hinshelwood.com/signals/there-no-such-thing-as-good-technical-debt/ Technical debt is always harmful and should not be considered acceptable; it slows onboarding, increases errors, and creates inefficiency. It accumulates quickly and can suddenly halt delivery, as seen in Microsoft’s experience before they overhauled their processes and addressed their debt. Development managers should prioritize identifying and reducing technical debt now rather than accepting it as normal. https://engineering.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.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.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.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.hinshelwood.com/signals/do-more-staging-environments-really-reduce-deployment-risk/ Wed, 26 Feb 2025 16:30:31 +0000 https://engineering.hinshelwood.com/signals/do-more-staging-environments-really-reduce-deployment-risk/ Adding more staging environments does not actually reduce deployment risk; it only delays issue discovery and creates a false sense of security. Real risk reduction comes from investing in automated testing, continuous integration, and quality practices built into the development process. To minimize downtime and deployment risk, focus on modern engineering practices rather than adding more pre-production gates. https://engineering.hinshelwood.com/signals/every-delay-increases-the-risk-of-failure/ Mon, 10 Feb 2025 11:00:51 +0000 https://engineering.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.hinshelwood.com/signals/scrum-doesn-t-stop-you-from-optimising-flow/ Sun, 25 May 2025 15:30:23 +0100 https://engineering.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.hinshelwood.com/signals/technical-debt-isn-t-just-messy-code/ Thu, 13 Mar 2025 16:30:02 +0000 https://engineering.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.hinshelwood.com/signals/technical-debt-cripples-business-agility-and-slows-engineers-down/ Tue, 06 May 2025 15:30:42 +0100 https://engineering.hinshelwood.com/signals/technical-debt-cripples-business-agility-and-slows-engineers-down/ Technical debt severely limits business agility and slows down engineering teams, making it harder to respond to market opportunities and innovate. This is a real risk seen in major companies and happens when technical debt is ignored. To stay competitive, focus on shortening feedback loops, automating processes, increasing transparency, and actively managing technical debt rather than accepting it. https://engineering.hinshelwood.com/signals/if-teams-struggle-with-quality-or-delivery-the-problem-is-often-the-system/ Wed, 02 Apr 2025 15:30:05 +0100 https://engineering.hinshelwood.com/signals/if-teams-struggle-with-quality-or-delivery-the-problem-is-often-the-system/ When teams face issues with quality or delivery, the root cause is often the broader system, not just the team itself. Consistent quality requires clear engineering standards, automation, and strong leadership support, not just team-level efforts. Leaders should ensure these foundations are in place rather than simply demanding results. https://engineering.hinshelwood.com/signals/the-hidden-costs-of-supporting-multiple-versions-in-production/ Thu, 06 Feb 2025 16:30:01 +0000 https://engineering.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.hinshelwood.com/signals/why-organisations-believe-their-software-is-too-complex-for-cd/ Mon, 24 Feb 2025 10:51:31 +0000 https://engineering.hinshelwood.com/signals/why-organisations-believe-their-software-is-too-complex-for-cd/ Software complexity is often used as an excuse to avoid continuous delivery, but real-world examples like Microsoft’s Azure DevOps team show that even large, complex systems can achieve frequent releases by investing in quality practices and addressing technical debt. The main barrier is not complexity but the willingness to make necessary improvements. Development managers should focus on fixing underlying issues rather than blaming complexity. https://engineering.hinshelwood.com/signals/rethinking-dev-test-staging-production-pipelines-for-safety/ Fri, 21 Feb 2025 16:30:30 +0000 https://engineering.hinshelwood.com/signals/rethinking-dev-test-staging-production-pipelines-for-safety/ Traditional Dev-Test-Staging-Production pipelines give a false sense of security because staging environments do not truly reflect production, leading to missed issues and wasted resources. Modern teams should focus on releasing to small user groups in production and using real feedback to guide rollouts. Consider shifting from heavy pre-release testing to faster, data-driven feedback in production to improve safety and efficiency. https://engineering.hinshelwood.com/signals/why-measuring-individual-cycle-time-fails-to-help-teams/ Sat, 15 Mar 2025 16:30:02 +0000 https://engineering.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.hinshelwood.com/signals/evolving-engineering-practices-to-improve-sprint-workflow-in-scrum/ Thu, 29 May 2025 15:30:45 +0100 https://engineering.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.hinshelwood.com/signals/why-tracking-individual-cycle-time-distorts-team-behaviour/ Wed, 12 Mar 2025 16:30:03 +0000 https://engineering.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.hinshelwood.com/signals/toyota-andon-cord-lets-any-worker-stop-production-to-fix-defects/ Mon, 12 May 2025 15:30:50 +0100 https://engineering.hinshelwood.com/signals/toyota-andon-cord-lets-any-worker-stop-production-to-fix-defects/ Giving teams tools like Scrum events or defect reporting only works if you also create a culture where people feel safe to speak up and address problems. Without psychological safety and genuine empowerment, process changes alone will not lead to real improvement. Development managers should focus on building trust and openness so teams feel comfortable raising issues. https://engineering.hinshelwood.com/signals/why-engineering-teams-use-staging-environments-for-risk-reduction/ Fri, 14 Feb 2025 16:30:01 +0000 https://engineering.hinshelwood.com/signals/why-engineering-teams-use-staging-environments-for-risk-reduction/ Staging environments are intended to reduce risk but often lead to wasted time, delayed feedback, and extra costs without truly preventing failures. Modern practices like feature flags, progressive rollouts, and real-time monitoring can help teams deploy safely to production while reducing waste. Consider whether maintaining staging environments is actually benefiting your team or just adding unnecessary overhead. https://engineering.hinshelwood.com/signals/executives-want-predictability/ Mon, 31 Mar 2025 15:30:08 +0100 https://engineering.hinshelwood.com/signals/executives-want-predictability/ If your teams do not have a clear, enforced Definition of Done, you are creating hidden risks and unreliable forecasts, which leads to missed deadlines and frustrated customers. Treating “Done” as negotiable means you are not delivering real value or predictability. Make sure your teams only mark work as done when it meets objective, enforceable standards to ensure true progress and trustworthy commitments. https://engineering.hinshelwood.com/signals/why-scrum-masters-need-technical-expertise-to-guide-teams/ Fri, 28 Mar 2025 16:30:04 +0000 https://engineering.hinshelwood.com/signals/why-scrum-masters-need-technical-expertise-to-guide-teams/ Scrum Masters are most effective when they have hands-on experience and technical understanding relevant to their team’s work, such as development practices or domain-specific knowledge. This expertise helps them guide teams toward improvement without doing the work themselves. Development managers should ensure Scrum Masters have sufficient technical background to enable, not just facilitate, their teams. https://engineering.hinshelwood.com/signals/why-slow-processes-impact-developer-productivity-and-performance/ Fri, 14 Mar 2025 16:30:02 +0000 https://engineering.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.hinshelwood.com/signals/understand-the-true-risk-of-technical-debt-in-your-business/ Thu, 24 Apr 2025 15:30:48 +0100 https://engineering.hinshelwood.com/signals/understand-the-true-risk-of-technical-debt-in-your-business/ Technical debt is pure risk with no upside, leading to lost time, reduced agility, and missed opportunities. Microsoft’s experience shows that unchecked technical debt can severely slow delivery, but addressing it directly restores speed and flexibility. Development managers should treat technical debt as a critical business issue and take proactive steps to reduce it. https://engineering.hinshelwood.com/signals/best-branching-strategies-for-development-teams-explained/ Tue, 25 Feb 2025 16:30:02 +0000 https://engineering.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.hinshelwood.com/signals/i-ll-never-understand-teams-that-manage-bugs-instead-of-fixing-them/ Thu, 01 May 2025 15:30:38 +0100 https://engineering.hinshelwood.com/signals/i-ll-never-understand-teams-that-manage-bugs-instead-of-fixing-them/ Teams should focus on fixing bugs as soon as they are found instead of managing or prioritising them in backlogs or meetings. Delaying bug fixes leads to bigger problems and undermines the goal of delivering working software. Development managers should ensure their teams address defects promptly rather than letting them accumulate. https://engineering.hinshelwood.com/signals/microsoft-shift-from-2-year-cycles-to-3-week-sprints-caused-team-anxiety/ Wed, 23 Apr 2025 15:30:47 +0100 https://engineering.hinshelwood.com/signals/microsoft-shift-from-2-year-cycles-to-3-week-sprints-caused-team-anxiety/ When Microsoft switched from two-year release cycles to three-week Sprints, teams initially felt anxious because increased transparency exposed inefficiencies and technical debt. However, teams that embraced this openness improved dramatically, moving from delivering 24 features a year to shipping multiple times daily. Development managers should consider whether their teams are ready to use transparency as a tool for continuous improvement. https://engineering.hinshelwood.com/signals/a-changing-definition-of-done-undermines-quality-and-predictability-in-teams/ Fri, 04 Apr 2025 15:30:02 +0100 https://engineering.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.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.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.hinshelwood.com/signals/let-us-do-the-maths/ Wed, 30 Apr 2025 15:30:52 +0100 https://engineering.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.hinshelwood.com/signals/there-a-common-belief-that-rollback-is-the-ultimate-safety-net/ Thu, 13 Feb 2025 15:53:38 +0000 https://engineering.hinshelwood.com/signals/there-a-common-belief-that-rollback-is-the-ultimate-safety-net/ Relying on rollback as a safety net is risky, especially for stateful applications where it can cause data issues and failures. Safer approaches include progressive delivery methods like feature flags and canary releases, which help detect and limit problems early. Teams should focus on making deployments safe to fail rather than assuming rollback will fix mistakes. https://engineering.hinshelwood.com/signals/why-compromising-on-software-quality-is-a-leadership-decision/ Tue, 01 Apr 2025 15:30:02 +0100 https://engineering.hinshelwood.com/signals/why-compromising-on-software-quality-is-a-leadership-decision/ Compromising on software quality is a leadership decision, not a team one, and lowering standards to meet deadlines carries business risks that should be explicitly approved by leadership. A clear Definition of Done helps maintain consistent quality, and any decision to reduce it should be transparent and deliberate. Development managers should ensure quality expectations are set and upheld at the leadership level, not left to teams under delivery pressure. https://engineering.hinshelwood.com/signals/the-fastest-way-to-cripple-a-scrum-team-hire-the-wrong-scrum-master/ Mon, 17 Feb 2025 16:30:17 +0000 https://engineering.hinshelwood.com/signals/the-fastest-way-to-cripple-a-scrum-team-hire-the-wrong-scrum-master/ Hiring the wrong Scrum Master, especially one who acts as a process admin rather than a true agile leader, can seriously harm a Scrum Team. Effective Scrum Masters coach teams toward self-management, challenge obstacles, and connect engineering with business goals. To enable real agility and high performance, hire Scrum Masters who drive change and value, not just manage meetings. https://engineering.hinshelwood.com/signals/why-using-a-blocked-column-in-azure-devops-is-a-mistake/ Thu, 20 Feb 2025 16:30:01 +0000 https://engineering.hinshelwood.com/signals/why-using-a-blocked-column-in-azure-devops-is-a-mistake/ Using a blocked column in Azure DevOps causes work to stall and be forgotten, rather than resolved. Instead, use a visible blocked tag and keep items in their active state to maintain focus and encourage action. Track blockages to address root causes and keep work moving. https://engineering.hinshelwood.com/signals/deploying-windows-os-directly-to-production-then-vs-now/ Sat, 22 Feb 2025 16:30:00 +0000 https://engineering.hinshelwood.com/signals/deploying-windows-os-directly-to-production-then-vs-now/ Microsoft now deploys Windows updates directly to production using a gradual, ring-based rollout that starts with internal users and expands outward, guided by real-time feedback and telemetry. This approach catches issues early and enables safe, incremental releases even across complex environments. Development managers should consider adopting similar staged deployment strategies to improve release quality and responsiveness. https://engineering.hinshelwood.com/signals/branch-promotion-is-a-relic-of-slow-manual-software-delivery/ Sat, 08 Feb 2025 16:30:00 +0000 https://engineering.hinshelwood.com/signals/branch-promotion-is-a-relic-of-slow-manual-software-delivery/ Branch promotion slows down delivery and adds risk, while modern teams merge changes into the main branch as soon as they are ready and use feature flags to separate deployment from release. Testing in production-like environments and instant rollbacks improve speed and safety. Focus on managing the flow of work, not branches, to streamline delivery. https://engineering.hinshelwood.com/signals/frequent-releases-are-not-just-a-technical-strategy/ Fri, 07 Feb 2025 16:30:01 +0000 https://engineering.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.hinshelwood.com/signals/understanding-blocked-columns-and-stalled-work-in-project-boards/ Tue, 04 Mar 2025 16:30:01 +0000 https://engineering.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.hinshelwood.com/signals/too-many-teams-overcomplicate-their-branching-strategies/ Thu, 06 Feb 2025 09:38:01 +0000 https://engineering.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.hinshelwood.com/signals/we-hear-self-managing-teams-so-often-it-become-a-clich%C3%A9/ Fri, 09 May 2025 15:30:39 +0100 https://engineering.hinshelwood.com/signals/we-hear-self-managing-teams-so-often-it-become-a-clich%C3%A9/ Self-management is essential for all Scrum roles, not just developers, and involves active, disciplined work in how Product Owners, Scrum Masters, and Developers fulfill their responsibilities. Scrum requires clear alignment and adaptive discipline, not a loose or chaotic approach. Development managers should ensure their teams understand and practice self-management as a structured, intentional process rather than mistaking it for a lack of direction. https://engineering.hinshelwood.com/signals/building-the-wrong-thing-is-worse-than-fixing-a-bug/ Mon, 14 Apr 2025 15:30:31 +0100 https://engineering.hinshelwood.com/signals/building-the-wrong-thing-is-worse-than-fixing-a-bug/ Most features built by software teams do not deliver value, with 65 percent considered waste. Shortening feedback loops through frequent reviews and real user input helps teams focus on what matters and avoid building the wrong things. Act now to get faster, actionable feedback and prevent wasted time and resources. https://engineering.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.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.hinshelwood.com/signals/not-all-delays-are-the-same/ Sat, 15 Feb 2025 16:30:01 +0000 https://engineering.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.hinshelwood.com/signals/during-a-massive-flood-in-london-nearly-every-datacentre-went-down/ Fri, 16 May 2025 15:30:31 +0100 https://engineering.hinshelwood.com/signals/during-a-massive-flood-in-london-nearly-every-datacentre-went-down/ Rackspace was the only London datacentre to stay online during a major flood because they regularly tested their backup systems by simulating real failures. Practising failure recovery under controlled but challenging conditions built true resilience in their operations. Development managers should regularly test their systems and teams under realistic failure scenarios to ensure they can recover when it matters most. https://engineering.hinshelwood.com/signals/if-software-is-not-delivered-it-is-not-valuable/ Sat, 01 Mar 2025 16:30:03 +0000 https://engineering.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.hinshelwood.com/signals/a-two-day-scrum-master-certification-doesn-t-make-you-a-scrum-master/ Thu, 27 Feb 2025 16:30:31 +0000 https://engineering.hinshelwood.com/signals/a-two-day-scrum-master-certification-doesn-t-make-you-a-scrum-master/ A two-day Scrum Master certification alone is not enough to prepare someone for the real challenges of leading Scrum Teams and delivering value. Effective Scrum Masters have hands-on experience, understand code quality and DevOps, and have navigated real-world obstacles. Companies should prioritize hiring or developing Scrum Masters with proven experience rather than relying solely on certifications. https://engineering.hinshelwood.com/signals/staging-environments-do-not-prevent-production-failures/ Fri, 28 Feb 2025 16:30:01 +0000 https://engineering.hinshelwood.com/signals/staging-environments-do-not-prevent-production-failures/ Staging environments do not truly prevent production failures because they cannot fully replicate real-world conditions, often giving teams a false sense of security. Leading teams now deploy changes incrementally to real users in production, using monitoring and automated safeguards to catch issues early. Consider shifting focus from pre-production testing to safer, controlled releases in production to reduce risk and respond faster to problems. https://engineering.hinshelwood.com/signals/every-unreleased-feature-is-a-cost/ Wed, 05 Feb 2025 16:30:01 +0000 https://engineering.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.hinshelwood.com/signals/too-many-scrum-masters-believe-they-don-t-need-technical-skills/ Mon, 24 Mar 2025 16:30:03 +0000 https://engineering.hinshelwood.com/signals/too-many-scrum-masters-believe-they-don-t-need-technical-skills/ Scrum Masters need relevant technical and domain knowledge to effectively support their teams, not just certifications. Without understanding the specific challenges and practices of their team’s work, they cannot truly enable success. Development managers should ensure Scrum Masters have or develop the necessary expertise to make a meaningful impact. https://engineering.hinshelwood.com/signals/scrum-masters-and-product-owners-are-held-accountable-for-results/ Mon, 17 Mar 2025 16:30:03 +0000 https://engineering.hinshelwood.com/signals/scrum-masters-and-product-owners-are-held-accountable-for-results/ Scrum Masters and Product Owners are often held accountable for results without having the authority needed to influence outcomes. This mismatch leads to empty expectations and limits team effectiveness. To achieve better results, organisations should empower Scrum Masters with real authority, not just expect them to coach from the sidelines. https://engineering.hinshelwood.com/signals/agile-is-not-easier-than-traditional-methods-common-misconceptions/ Sat, 08 Mar 2025 16:30:01 +0000 https://engineering.hinshelwood.com/signals/agile-is-not-easier-than-traditional-methods-common-misconceptions/ Agile is often harder than traditional methods because it requires frequent delivery, decision-making with limited information, and handling uncertainty. Success depends on disciplined teams, strong collaboration, and a focus on delivering value, not just following a framework. Development managers should assess whether their teams are truly embracing Agile principles or simply following routines. https://engineering.hinshelwood.com/signals/let-us-be-blunt/ Sat, 10 May 2025 15:30:22 +0100 https://engineering.hinshelwood.com/signals/let-us-be-blunt/ Accountability in Scrum only works if people also have the authority to make decisions and remove obstacles; otherwise, roles become meaningless and teams are set up to fail. To achieve real results, ensure your Product Owners, Scrum Masters, and Developers have both responsibility and the power to act. Review your organisation to identify where you may be limiting agency while still expecting accountability. https://engineering.hinshelwood.com/signals/most-teams-don-t-fail-because-they-lack-frameworks/ Mon, 05 May 2025 15:30:43 +0100 https://engineering.hinshelwood.com/signals/most-teams-don-t-fail-because-they-lack-frameworks/ Teams usually fail not because they lack frameworks like Agile or Scrum, but because they ignore the feedback these frameworks reveal. The real challenge is creating a culture where teams feel safe and empowered to act on what they learn. Development managers should focus on listening to feedback and enabling teams to address issues, which leads to better performance and competitive advantage. https://engineering.hinshelwood.com/signals/here-the-dirty-secret-behind-many-agile-transformations/ Fri, 02 May 2025 15:30:32 +0100 https://engineering.hinshelwood.com/signals/here-the-dirty-secret-behind-many-agile-transformations/ Many agile transformations fail because organizations maintain tight control over how work is done while claiming to empower teams. True agility requires leadership to set clear goals and priorities but let teams decide how to achieve them. To foster commitment and improvement, review where your processes still dictate the how and shift toward real team autonomy. https://engineering.hinshelwood.com/signals/would-your-cfo-approve-misrepresenting-corporate-assets/ Mon, 21 Apr 2025 15:30:34 +0100 https://engineering.hinshelwood.com/signals/would-your-cfo-approve-misrepresenting-corporate-assets/ Ignoring technical debt is like misrepresenting the value of your software assets, which can lead to future losses and operational risks. Most businesses fail to track this risk, even though technical debt reduces asset value and increases costs. Development managers should ensure technical debt is monitored and addressed to protect the true value of software investments. https://engineering.hinshelwood.com/signals/you-can-not-implement-agile-or-scrum-successfully-by-decree/ Tue, 13 May 2025 15:30:47 +0100 https://engineering.hinshelwood.com/signals/you-can-not-implement-agile-or-scrum-successfully-by-decree/ Agile and Scrum cannot be made effective just by issuing mandates or using tools; their success depends on a culture of trust, openness, and willingness to improve. If your team fears blame or resists change, process changes alone will not help. Focus on building a supportive culture before trying to improve processes. https://engineering.hinshelwood.com/signals/fear-is-the-real-enemy-of-agility/ Wed, 07 May 2025 15:30:42 +0100 https://engineering.hinshelwood.com/signals/fear-is-the-real-enemy-of-agility/ Fear blocks true agility and leads to stagnation, regardless of how many Agile practices you follow. The main job of leaders is to remove fear so teams can learn, adapt, and deliver value. Focus on creating an environment where people feel safe to speak up and take risks. https://engineering.hinshelwood.com/signals/too-much-refinement-wastes-time/ Tue, 29 Apr 2025 15:30:43 +0100 https://engineering.hinshelwood.com/signals/too-much-refinement-wastes-time/ Too much backlog refinement wastes time, while too little causes confusion and delays. Aim for just enough detail so developers can start work confidently without needing constant clarification. If Sprint Planning is about making commitments rather than figuring things out, your refinement process is working well. https://engineering.hinshelwood.com/signals/scrum-masters-enabling-teams-fostering-agility-removing-blockers/ Wed, 05 Mar 2025 16:30:00 +0000 https://engineering.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.hinshelwood.com/signals/everyone-loves-to-shout-give-teams-autonomy/ Thu, 08 May 2025 15:30:40 +0100 https://engineering.hinshelwood.com/signals/everyone-loves-to-shout-give-teams-autonomy/ Autonomy alone is not enough; teams need clear alignment with strategic goals to deliver real business outcomes. In Scrum, tools like the Product Goal, Sprint Goal, and Product Backlog are essential for this alignment. Leaders should provide clarity of purpose so teams can be both autonomous and effective, avoiding wasted effort and missed objectives. https://engineering.hinshelwood.com/signals/stop-treating-the-end-of-the-sprint-like-a-finish-line/ Thu, 05 Jun 2025 15:30:54 +0100 https://engineering.hinshelwood.com/signals/stop-treating-the-end-of-the-sprint-like-a-finish-line/ The end of a Sprint is a checkpoint for review and planning, not a finish line where all work must be completed. It is normal for large items to span multiple Sprints; focus on showing progress, adapting plans, and maintaining flow. Managers should move away from rigid project thinking and support teams in embracing continuous delivery and adaptation. https://engineering.hinshelwood.com/signals/the-true-role-of-a-scrum-master-beyond-facilitation/ Tue, 25 Mar 2025 16:30:02 +0000 https://engineering.hinshelwood.com/signals/the-true-role-of-a-scrum-master-beyond-facilitation/ A Scrum Master’s real value is in driving team improvement and organisational change, not just running meetings or handling admin tasks. They should coach teams, remove obstacles, and ensure Scrum is used to deliver value. Development managers should empower Scrum Masters to act as change agents rather than limiting them to facilitation. https://engineering.hinshelwood.com/signals/not-all-surprises-in-product-development-are-true-unknowns/ Mon, 28 Apr 2025 15:30:55 +0100 https://engineering.hinshelwood.com/signals/not-all-surprises-in-product-development-are-true-unknowns/ Many surprises in product development are due to poor backlog management rather than true unknowns. Regularly reviewing and categorizing past surprises helps teams improve their backlog and anticipate issues. Development managers should ensure their teams use backlog refinement to build foresight and reduce avoidable disruptions. https://engineering.hinshelwood.com/signals/what-makes-an-effective-scrum-master-beyond-meeting-facilitation/ Sun, 23 Feb 2025 16:30:01 +0000 https://engineering.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.hinshelwood.com/signals/challenging-misconceptions-about-behaviour-in-agile-teams/ Thu, 13 Feb 2025 16:30:02 +0000 https://engineering.hinshelwood.com/signals/challenging-misconceptions-about-behaviour-in-agile-teams/ Agile is often misused to justify poor planning and lack of accountability, but true agility demands more discipline, professionalism, and clear alignment with the product vision. Teams that fail to deliver usable increments or start work without sufficient understanding are not practicing real Agile. Development managers should ensure their teams uphold high standards and address unprofessional behavior rather than excusing it as Agile. https://engineering.hinshelwood.com/signals/you-want-speed-adaptability-resilience/ Sun, 11 May 2025 15:30:29 +0100 https://engineering.hinshelwood.com/signals/you-want-speed-adaptability-resilience/ Investing in Agile, Scrum, Kanban, and DevOps will not deliver real speed, adaptability, or resilience unless your teams have the agency to truly own their work and outcomes. Without empowering people to take responsibility, you risk superficial processes and disengaged teams. To achieve genuine agility, ensure your system supports team and individual ownership, not just frameworks. https://engineering.hinshelwood.com/signals/let-us-be-blunt-if-a-scrum-team-isn-t-delivering-is-it-effective/ Fri, 07 Mar 2025 16:30:00 +0000 https://engineering.hinshelwood.com/signals/let-us-be-blunt-if-a-scrum-team-isn-t-delivering-is-it-effective/ A Scrum Team is only effective if it consistently delivers usable product increments; without delivery, Scrum practices are just empty rituals. The Scrum Master is accountable for enabling the team to deliver by fixing any issues that block progress. If your team is not delivering, focus on identifying and removing obstacles to restore effectiveness. https://engineering.hinshelwood.com/signals/how-top-scrum-masters-are-selected-by-their-teams/ Wed, 19 Feb 2025 16:30:01 +0000 https://engineering.hinshelwood.com/signals/how-top-scrum-masters-are-selected-by-their-teams/ The most effective Scrum Masters are chosen by their teams based on trust, experience, and proven leadership, not assigned from outside. Teams naturally follow those who have already guided them through challenges and earned their respect. To ensure real impact and avoid resistance, let the team identify who they trust to lead as Scrum Master. https://engineering.hinshelwood.com/signals/everyone-has-a-disaster-recovery-plan-on-paper/ Wed, 14 May 2025 15:30:37 +0100 https://engineering.hinshelwood.com/signals/everyone-has-a-disaster-recovery-plan-on-paper/ Many organizations have disaster recovery plans, but these often fail in real situations because critical dependencies are overlooked and not tested end to end. Successful drills can give a false sense of security if they do not include all essential systems, like authentication services. To ensure true resilience, regularly test your recovery process under real conditions and verify that all dependencies are restored and functional. https://engineering.hinshelwood.com/signals/great-scrum-masters-and-product-owners-don-t-micromanage/ Sun, 23 Mar 2025 16:30:01 +0000 https://engineering.hinshelwood.com/signals/great-scrum-masters-and-product-owners-don-t-micromanage/ Effective Scrum Masters and Product Owners avoid micromanaging by providing clear direction, supporting team autonomy, and ensuring accountability. Teams perform best when they understand the vision and operate within a structured framework that balances freedom with alignment. Leaders should focus on removing obstacles and maintaining this balance to enable true agility; consider how your organization supports both autonomy and structure. https://engineering.hinshelwood.com/signals/hiring-a-scrum-master-is-hard/ Sun, 16 Feb 2025 16:30:01 +0000 https://engineering.hinshelwood.com/signals/hiring-a-scrum-master-is-hard/ Hiring a Scrum Master is challenging because many organizations misunderstand the role and focus on the wrong qualifications. A strong Scrum Master needs deep knowledge of Scrum, the ability to drive team effectiveness, and enough technical understanding to support your teams and foster change. Look for candidates who demonstrate commitment, challenge assumptions, and coach teams to deliver real value, not just those with certifications or project management backgrounds. https://engineering.hinshelwood.com/signals/teams-are-self-managing/ Fri, 21 Mar 2025 16:30:04 +0000 https://engineering.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.hinshelwood.com/signals/agile-without-a-usable-working-product-is-just-expensive-theatre/ Sun, 20 Apr 2025 15:30:27 +0100 https://engineering.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.hinshelwood.com/signals/when-you-scale-scrum-the-challenge-isn-t-just-delivery-it-coherence/ Tue, 27 May 2025 15:30:33 +0100 https://engineering.hinshelwood.com/signals/when-you-scale-scrum-the-challenge-isn-t-just-delivery-it-coherence/ When scaling Scrum, the main challenge is maintaining coherence across teams, not just delivering work. Without coordination, teams create inconsistent user experiences and duplicate efforts. To address this, form a cross-team Community of Practice to develop shared frameworks and include them in your Definition of Done, promoting collaboration and consistency without adding hierarchy. https://engineering.hinshelwood.com/signals/everyone-loves-the-idea-of-self-managing-teams/ Tue, 18 Mar 2025 09:51:08 +0000 https://engineering.hinshelwood.com/signals/everyone-loves-the-idea-of-self-managing-teams/ Self-managing teams need both autonomy and clear structure to be effective; Scrum provides this by allowing teams to decide how to deliver value within defined boundaries and shared goals. Too much control leads to disengagement, while too little causes chaos and lack of direction. Development managers should regularly assess whether their teams have the right balance of freedom and alignment to maintain productivity and adaptability. https://engineering.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.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.hinshelwood.com/signals/overcoming-project-blockers-and-challenging-organisational-inertia/ Sat, 22 Mar 2025 16:30:03 +0000 https://engineering.hinshelwood.com/signals/overcoming-project-blockers-and-challenging-organisational-inertia/ Teams are often held responsible for project outcomes without having the authority to remove blockers or challenge ineffective practices, which leads to frustration and failure. True accountability requires giving teams both autonomy and the power to influence their environment. Development managers should ensure teams have the authority needed to address obstacles and drive results, not just the responsibility. https://engineering.hinshelwood.com/signals/no-one-questions-a-product-owner-authority/ Wed, 19 Mar 2025 16:30:30 +0000 https://engineering.hinshelwood.com/signals/no-one-questions-a-product-owner-authority/ Product Owners are trusted with authority to make decisions that drive product success, but Scrum Masters often lack similar authority despite being responsible for team effectiveness and removing obstacles. Relying only on persuasion limits their impact; Scrum Masters need the power to enforce good practices and address issues directly. Development managers should ensure Scrum Masters have the authority needed to fulfill their role and support team agility. https://engineering.hinshelwood.com/signals/why-teams-claim-self-management-to-avoid-alignment-discussions/ Tue, 18 Mar 2025 16:30:34 +0000 https://engineering.hinshelwood.com/signals/why-teams-claim-self-management-to-avoid-alignment-discussions/ Self-management means taking ownership within agreed boundaries, not avoiding alignment or accountability. Scrum teams must align with business goals, agile practices, and delivery commitments while deciding how to work. Development managers should ensure teams are not using autonomy as an excuse to sidestep necessary alignment and accountability. https://engineering.hinshelwood.com/signals/would-you-hire-a-junior-ciso-a-junior-financial-director/ Mon, 17 Feb 2025 10:06:07 +0000 https://engineering.hinshelwood.com/signals/would-you-hire-a-junior-ciso-a-junior-financial-director/ Hiring a junior Scrum Master is risky because the role requires proven expertise in technical, business, and organisational areas from the start, similar to senior roles like CISO or Financial Director. Scrum Masters must lead teams and drive change, not learn on the job. Only hire experienced Scrum Masters to ensure your team’s success and true agility. https://engineering.hinshelwood.com/signals/scrum-isn-t-limited-to-building-features/ Fri, 30 May 2025 15:30:41 +0100 https://engineering.hinshelwood.com/signals/scrum-isn-t-limited-to-building-features/ Scrum can be used to drive organizational change, not just build software features. By forming a change team, creating a backlog, and using regular feedback, you can make improvements measurable and adaptable. To achieve real agility, apply Scrum practices to your internal processes as well as your products. https://engineering.hinshelwood.com/signals/scrum-master-effectiveness-begins-with-consistent-delivery/ Thu, 06 Mar 2025 16:30:29 +0000 https://engineering.hinshelwood.com/signals/scrum-master-effectiveness-begins-with-consistent-delivery/ Scrum Master effectiveness depends on ensuring teams deliver something every sprint, as delivery enables feedback and improvement. Without delivery, there is no basis for learning or adding value. Development managers should prioritize consistent delivery as the foundation for team effectiveness and continuous improvement. https://engineering.hinshelwood.com/signals/design-sprints-in-scrum-common-questions-and-practical-insights/ Wed, 04 Jun 2025 15:31:05 +0100 https://engineering.hinshelwood.com/signals/design-sprints-in-scrum-common-questions-and-practical-insights/ There are no special Sprints in Scrum for design or other functions; all work needed to meet the Sprint Goal, including UX and design, should happen within the Sprint or during Refinement if it is for future preparation. Segmenting Sprints by function creates silos and goes against Scrum’s purpose of delivering high-quality working software. Development managers should focus on integrating design and architecture work into the regular Sprint flow rather than isolating it. https://engineering.hinshelwood.com/signals/scrum-myth-debunked-unfinished-work-is-allowed-in-scrum/ Sat, 24 May 2025 15:30:17 +0100 https://engineering.hinshelwood.com/signals/scrum-myth-debunked-unfinished-work-is-allowed-in-scrum/ Scrum does not require all work to be finished by the end of a Sprint, only that the Increment is Done and meets the Definition of Done. Unfinished items can carry over as long as the Sprint Goal and Increment are not compromised. Managers should focus on delivering value and avoid forcing work to fit arbitrary Sprint boundaries. https://engineering.hinshelwood.com/signals/empowering-product-owners-as-strategic-leaders-in-scrum-teams/ Wed, 26 Mar 2025 16:30:33 +0000 https://engineering.hinshelwood.com/signals/empowering-product-owners-as-strategic-leaders-in-scrum-teams/ Product Owners should be empowered as strategic leaders who drive product vision and business value, not just manage backlogs. Scrum Masters play a key role in coaching Product Owners to use customer insights and data for better decisions. Development managers should ensure Product Owners have the authority and support to lead effectively, rather than treating them as task managers. https://engineering.hinshelwood.com/signals/key-skills-scrum-masters-need-technical-business-organisational/ Tue, 18 Feb 2025 16:30:30 +0000 https://engineering.hinshelwood.com/signals/key-skills-scrum-masters-need-technical-business-organisational/ Scrum Masters need strong technical, business, and organisational skills to lead teams, align with business goals, and remove obstacles effectively. Experience and real leadership matter more than certifications. To achieve true agility, hire Scrum Masters who demonstrate competence and bold leadership. https://engineering.hinshelwood.com/signals/maximising-value-from-applying-professional-scrum-training/ Mon, 09 Jun 2025 15:30:34 +0100 https://engineering.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.hinshelwood.com/signals/at-the-end-of-the-day-kanban-is-about-improving-flow/ Mon, 03 Mar 2025 15:46:26 +0000 https://engineering.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.hinshelwood.com/signals/realistic-expectations-when-hiring-junior-scrum-masters/ Sun, 02 Mar 2025 16:30:02 +0000 https://engineering.hinshelwood.com/signals/realistic-expectations-when-hiring-junior-scrum-masters/ Hiring inexperienced Scrum Masters to save money often leads to poor team performance, delays, and lower product quality. The cost of inexperience outweighs any salary savings, while experienced Scrum Masters drive better results and team satisfaction. Invest in proven leadership to avoid costly failures and achieve faster, higher-quality delivery. https://engineering.hinshelwood.com/signals/git-flow-should-have-died-years-ago/ Sun, 09 Feb 2025 16:30:00 +0000 https://engineering.hinshelwood.com/signals/git-flow-should-have-died-years-ago/ Git Flow is outdated and causes unnecessary delays and complications for modern software teams. Long-lived branches and complex merges slow down delivery and increase risk. Switch to simpler workflows like GitHub Flow or Release Flow to speed up development and focus on delivering value. https://engineering.hinshelwood.com/signals/detecting-agile-theatre-with-real-delivery-signals/ Mon, 25 May 2026 00:00:00 +0000 https://engineering.hinshelwood.com/signals/detecting-agile-theatre-with-real-delivery-signals/ Agile is measured by delivery, feedback, and decision-making authority in the hands of teams, not by visible ceremonies or tooling. https://engineering.hinshelwood.com/signals/resilience-is-not-a-department/ Sat, 17 May 2025 15:30:21 +0100 https://engineering.hinshelwood.com/signals/resilience-is-not-a-department/ Resilience must be built into your product from the start, not treated as a separate concern or afterthought. Focusing only on performance, cost, or speed can lead to fragile systems that fail in real-world conditions. Make sure your disaster recovery plans are tested under real scenarios, not just documented, to avoid turning your product into a liability. https://engineering.hinshelwood.com/signals/scrum-masters-why-influence-alone-may-not-be-enough/ Thu, 20 Mar 2025 16:30:02 +0000 https://engineering.hinshelwood.com/signals/scrum-masters-why-influence-alone-may-not-be-enough/ Relying only on influence limits a Scrum Master’s ability to drive real change, especially when teams or leaders resist Agile practices. Sustainable agility needs Scrum Masters who can enforce the framework, remove obstacles, and hold teams accountable, not just suggest improvements. Development managers should ensure Scrum Masters have enough authority to lead effectively, not just influence. https://engineering.hinshelwood.com/signals/why-frameworks-alone-will-not-transform-your-team-culture/ Wed, 28 May 2025 15:30:50 +0100 https://engineering.hinshelwood.com/signals/why-frameworks-alone-will-not-transform-your-team-culture/ Relying on frameworks alone will not change your team culture; the main barriers are existing habits and lack of true commitment. Real transformation requires a clear vision, visible leadership support, and active involvement from everyone to identify and address obstacles. As a development manager, focus on building shared understanding and genuine engagement rather than just rolling out new processes. https://engineering.hinshelwood.com/signals/david-thought-he-already-knew-scrum/ Mon, 26 May 2025 15:30:28 +0100 https://engineering.hinshelwood.com/signals/david-thought-he-already-knew-scrum/ Even experienced teams often fall into old habits and misunderstand Scrum, leading to ineffective practices that only look agile on the surface. Regularly revisiting the fundamentals and purpose of Scrum helps prevent complacency and ensures real improvement. Consider challenging your team’s understanding of Scrum to maintain true agility and drive meaningful change. https://engineering.hinshelwood.com/signals/companies-often-say-we-are-going-agile-as-if-declaring-it-makes-it-so/ Fri, 25 Apr 2025 15:30:40 +0100 https://engineering.hinshelwood.com/signals/companies-often-say-we-are-going-agile-as-if-declaring-it-makes-it-so/ Simply declaring an Agile transformation does not make a company truly agile; real agility is about quickly responding to market changes, not just adopting frameworks like SAFe or Scrum@Scale. Successful organisations tailor their ways of working to their unique needs rather than copying others. Development managers should focus on building agility that fits their own business instead of relying on off-the-shelf solutions. https://engineering.hinshelwood.com/signals/the-myth-of-knowing-everything-upfront-in-software-development/ Mon, 16 Jun 2025 15:30:47 +0100 https://engineering.hinshelwood.com/signals/the-myth-of-knowing-everything-upfront-in-software-development/ You cannot know everything upfront in software development, so focus on continuous discovery and adapt as you learn. Scrum supports this by encouraging just enough planning and design to move forward, then delivering and learning from real use. Prioritise delivery and feedback over excessive upfront design to create more value. https://engineering.hinshelwood.com/signals/agile-and-scrum-are-often-misunderstood/ Sun, 04 May 2025 15:30:30 +0100 https://engineering.hinshelwood.com/signals/agile-and-scrum-are-often-misunderstood/ Agile and Scrum do not solve problems by themselves; they expose underlying issues in your team’s processes. The real value comes from addressing these revealed problems directly rather than just following rituals or tools. Managers should focus on actively resolving dysfunctions highlighted by Agile and Scrum to improve team performance. https://engineering.hinshelwood.com/signals/lack-of-authority-blocks-progress-on-critical-projects/ Sun, 16 Mar 2025 16:30:01 +0000 https://engineering.hinshelwood.com/signals/lack-of-authority-blocks-progress-on-critical-projects/ Scrum Masters need real authority to remove obstacles and drive project success, but many are blocked by bureaucracy and lack of support. Without empowerment, they cannot be held accountable for outcomes and become ineffective. Development managers should ensure Scrum Masters have the authority to act if they expect meaningful results. https://engineering.hinshelwood.com/signals/when-heathrow-went-down-they-blamed-the-power-supplier/ Thu, 15 May 2025 15:30:30 +0100 https://engineering.hinshelwood.com/signals/when-heathrow-went-down-they-blamed-the-power-supplier/ Heathrow’s outage was not caused by a power loss but by an overly sensitive internal system that shut everything down in response to a minor fluctuation, revealing that their disaster recovery measures were untested for real-world chaos. Investing in infrastructure does not guarantee true resilience; resilience is proven only when systems are tested against unexpected failures. Development managers should regularly test and challenge their recovery processes to ensure they work under real conditions, not just ideal scenarios. https://engineering.hinshelwood.com/signals/why-copying-scaled-agile-frameworks-fails-in-your-business/ Tue, 10 Jun 2025 15:30:38 +0100 https://engineering.hinshelwood.com/signals/why-copying-scaled-agile-frameworks-fails-in-your-business/ Copying scaled agile frameworks does not work because each organization has unique culture and challenges. Success comes from creating your own vision, identifying real obstacles, and experimenting with solutions tailored to your context. Focus on building your own path to agility using evidence and iteration rather than following someone else’s blueprint. https://engineering.hinshelwood.com/signals/the-fbi-sentinel-project-was-textbook-waterfall/ Wed, 11 Jun 2025 15:30:44 +0100 https://engineering.hinshelwood.com/signals/the-fbi-sentinel-project-was-textbook-waterfall/ The FBI’s Sentinel project failed after years and massive spending using a traditional waterfall approach, delivering nothing. Switching to a small, focused Agile team produced a working product in a year at a fraction of the cost. Consider adopting iterative methods to avoid wasted time and resources and deliver real value sooner. https://engineering.hinshelwood.com/signals/you-can-t-deliver-change-through-memos/ Sat, 31 May 2025 15:30:23 +0100 https://engineering.hinshelwood.com/signals/you-can-t-deliver-change-through-memos/ Change cannot be achieved through memos or top-down mandates; real progress happens when everyone is trained together and understands the reasons behind new approaches. Broad-based training helps people identify problems and suggest improvements, making change more effective and sustainable. To drive meaningful change, involve all stakeholders in learning and improvement, not just managers or specialists. https://engineering.hinshelwood.com/signals/scrum-is-built-on-empiricism-transparency-inspection-and-adaptation/ Mon, 24 Feb 2025 16:30:29 +0000 https://engineering.hinshelwood.com/signals/scrum-is-built-on-empiricism-transparency-inspection-and-adaptation/ Scrum relies on delivering a usable product increment every sprint, and if this does not happen, the team is not truly practicing Scrum. The Scrum Master is accountable for ensuring an environment where delivery is consistent and inevitable, with no excuses for missed increments. Development managers should ensure their Scrum Masters take ownership of delivery and address any barriers to producing usable increments each sprint. https://engineering.hinshelwood.com/signals/why-most-transformations-fail-without-honest-conversations/ Thu, 19 Jun 2025 15:30:37 +0100 https://engineering.hinshelwood.com/signals/why-most-transformations-fail-without-honest-conversations/ Most transformation efforts fail because teams avoid honest conversations about real issues. Creating space for open dialogue leads to genuine improvement and transparency, which are essential for true agility. Development managers should ensure their teams regularly discuss tough topics to drive meaningful change. https://engineering.hinshelwood.com/signals/no-successful-company-thrives-by-copying-others-ways-of-working/ Sat, 26 Apr 2025 15:30:29 +0100 https://engineering.hinshelwood.com/signals/no-successful-company-thrives-by-copying-others-ways-of-working/ Successful companies do not achieve success by copying others’ processes; instead, they create ways of working tailored to their unique challenges, culture, and customers. Relying on packaged frameworks like SAFe or the Spotify Model can hinder genuine growth and adaptation. Development managers should focus on designing and evolving their own approaches to scaling rather than outsourcing this critical work to external models. https://engineering.hinshelwood.com/signals/hybrid-agile-often-combines-the-worst-of-both-traditional-and-agile-methods/ Wed, 09 Apr 2025 15:30:02 +0100 https://engineering.hinshelwood.com/signals/hybrid-agile-often-combines-the-worst-of-both-traditional-and-agile-methods/ Mixing Agile with traditional methods often results in a slow, inefficient process that fails to deliver the benefits of either approach. Simply adding Agile practices to a rigid system does not enable faster adaptation or competitiveness. Development managers should assess whether their processes truly support rapid change rather than just adopting Agile terminology. https://engineering.hinshelwood.com/signals/us-department-of-defence-and-the-history-of-waterfall-delivery/ Sun, 08 Jun 2025 15:30:25 +0100 https://engineering.hinshelwood.com/signals/us-department-of-defence-and-the-history-of-waterfall-delivery/ The US Department of Defence has moved away from traditional waterfall delivery and now requires lean-agile approaches in its procurement rules, recognizing that agility is essential for complex, high-stakes projects. This shift is now mandated, not just recommended, showing that even large, regulated organizations can make the change. Development managers should reconsider stage-gate processes and focus on enabling real agility rather than clinging to outdated controls. https://engineering.hinshelwood.com/signals/scrum-is-not-an-engineering-process/ Wed, 21 May 2025 15:30:39 +0100 https://engineering.hinshelwood.com/signals/scrum-is-not-an-engineering-process/ Scrum is a framework for fostering collaboration across the whole organisation, not just an engineering process for developers. True agility happens when everyone, regardless of role, understands and participates in Scrum, which helps break down silos and exposes issues that slow delivery. To achieve real change, ensure your entire team is aligned and involved in the conversation about how value is delivered. https://engineering.hinshelwood.com/signals/most-companies-still-get-product-ownership-wrong/ Thu, 17 Apr 2025 15:30:37 +0100 https://engineering.hinshelwood.com/signals/most-companies-still-get-product-ownership-wrong/ Many companies misunderstand the Product Owner role, treating it as simple backlog management or assigning it to any business analyst, which leads to weak products and misaligned teams. Effective Product Owners are strategic leaders who own the vision, make tough decisions, and use evidence to guide development. Development managers should ensure they are hiring or empowering true Product Owners with the right skills and authority, not just filling a position. https://engineering.hinshelwood.com/signals/in-scrum-we-don-t-do-ux-separately/ Thu, 12 Jun 2025 15:30:39 +0100 https://engineering.hinshelwood.com/signals/in-scrum-we-don-t-do-ux-separately/ UX should be integrated into regular Scrum work, not handled in separate sprints or phases. Design and validation should happen continuously alongside development to support the Sprint Goal and future planning. Managers should ensure UX is part of the team’s ongoing workflow to improve learning and delivery speed. https://engineering.hinshelwood.com/signals/the-false-claim-that-scrum-is-immutable/ Tue, 25 Jun 2024 11:37:00 +0000 https://engineering.hinshelwood.com/signals/the-false-claim-that-scrum-is-immutable/ Scrum is meant to be flexible and adaptable, not rigid, despite some claims that it is “immutable.” The Scrum Guide’s reference to immutability applies to its definition, not to how teams must implement it, so teams can adapt Scrum as needed as long as they are transparent about changes. Development managers should focus on delivering value, getting feedback, adapting plans, and reflecting regularly rather than debating strict adherence to the Scrum Guide. https://engineering.hinshelwood.com/signals/the-market-isn-t-slowing-down-for-anyone/ Wed, 16 Apr 2025 15:30:49 +0100 https://engineering.hinshelwood.com/signals/the-market-isn-t-slowing-down-for-anyone/ Success in today’s market depends on how quickly your organization can respond and adapt, not on which framework you use. Relying on old control methods with superficial agile practices slows you down and puts you at risk of falling behind. To stay competitive, focus on building a truly responsive system that enables fast, smart decisions and real adaptability. https://engineering.hinshelwood.com/signals/fbi-launched-outdated-criminal-records-system-in-1995/ Fri, 06 Jun 2025 15:30:50 +0100 https://engineering.hinshelwood.com/signals/fbi-launched-outdated-criminal-records-system-in-1995/ The FBI launched a criminal records system in 1995 that was already outdated, and it remained in use for 15 years. Relying on big, infrequent releases means technology and user needs quickly outpace your delivery. To avoid delivering obsolete solutions, shift to frequent, incremental releases so you can keep up with changing requirements and user expectations. https://engineering.hinshelwood.com/signals/a-bloated-backlog-is-not-a-sign-of-good-product-management/ Thu, 10 Apr 2025 15:30:07 +0100 https://engineering.hinshelwood.com/signals/a-bloated-backlog-is-not-a-sign-of-good-product-management/ A backlog packed with every idea signals indecision, not good product management. Overloaded backlogs make it hard to prioritize, confuse stakeholders, and slow teams down. Keep your backlog focused on the most valuable upcoming work and regularly remove items your team cannot realistically address. https://engineering.hinshelwood.com/signals/too-many-organisations-hide-behind-excuses/ Sat, 07 Jun 2025 15:30:25 +0100 https://engineering.hinshelwood.com/signals/too-many-organisations-hide-behind-excuses/ Even large, regulated, and traditionally slow organizations like the DOD and FBI have successfully adopted iterative delivery, showing that excuses for not embracing agile are unfounded. Agile helps reduce risk, increase flexibility, and deliver value incrementally, which is especially important in regulated industries. Development managers should challenge resistance and prioritize agile practices to improve outcomes regardless of organizational constraints. https://engineering.hinshelwood.com/signals/a-great-backlog-isn-t-just-a-list-of-tasks/ Sun, 13 Apr 2025 15:30:17 +0100 https://engineering.hinshelwood.com/signals/a-great-backlog-isn-t-just-a-list-of-tasks/ A backlog should guide strategic decisions and reflect the product vision, not just list tasks. Filling it with unchecked requests leads to loss of focus and unclear priorities. Review your backlog to ensure it highlights what truly matters for delivering value and supports your product strategy. https://engineering.hinshelwood.com/signals/measuring-worker-speed-in-manufacturing-plant-operations/ Tue, 11 Mar 2025 16:30:01 +0000 https://engineering.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.hinshelwood.com/signals/the-majority-of-scrum-masters-are-not-fit-for-their-position/ Mon, 03 Jun 2024 14:44:00 +0000 https://engineering.hinshelwood.com/signals/the-majority-of-scrum-masters-are-not-fit-for-their-position/ Most Scrum Masters lack the necessary knowledge and skills to lead teams effectively, with data showing that only 39 percent meet basic expectations and just 3 percent fully meet the role’s requirements. Many have held these roles for years without competence, which is contributing to job losses as organizations demand higher standards. Development managers should rigorously assess and upskill their Scrum Masters to ensure team success. https://engineering.hinshelwood.com/signals/innovation-graveyards-where-great-ideas-die-in-slow-organisations/ Sun, 27 Apr 2025 15:30:30 +0100 https://engineering.hinshelwood.com/signals/innovation-graveyards-where-great-ideas-die-in-slow-organisations/ Slow organisations kill promising ideas by demanding certainty, avoiding risk, and requiring full alignment before testing anything. Successful companies move quickly, experiment, and improve as they go, understanding that waiting for perfection leads to missed opportunities. To avoid wasting potential, encourage faster testing and learning from new ideas. https://engineering.hinshelwood.com/signals/why-most-companies-fail-at-adopting-agility-beyond-it/ Thu, 27 Mar 2025 16:30:04 +0000 https://engineering.hinshelwood.com/signals/why-most-companies-fail-at-adopting-agility-beyond-it/ Most companies fail to adopt agility beyond IT because the real barriers are organisational, such as rigid hierarchies, inflexible budgeting, and outdated performance reviews. Scrum Masters need to focus on driving broader organisational change, not just team-level practices. Development managers should address systemic blockers and rethink how work is funded and measured to enable true agility. https://engineering.hinshelwood.com/signals/bonuses-are-not-incentives/ Sat, 21 Jun 2025 08:30:44 +0100 https://engineering.hinshelwood.com/signals/bonuses-are-not-incentives/ Bonuses do not truly motivate skilled software engineers; instead, purpose, autonomy, and meaningful challenges drive performance. Relying on traditional incentives signals a lack of trust and leads to outdated, compliance-focused cultures. Development managers should focus on empowering teams and aligning work with meaningful outcomes rather than using bonuses as motivation. https://engineering.hinshelwood.com/signals/every-delay-in-decision-making-taxes-your-organisation-future/ Tue, 22 Apr 2025 15:30:43 +0100 https://engineering.hinshelwood.com/signals/every-delay-in-decision-making-taxes-your-organisation-future/ Delays in decision-making hurt your organisation by slowing progress and letting competitors get ahead. Most delays come from internal bureaucracy and risk-averse processes, which stifle innovation and responsiveness. To stay competitive, streamline approvals and empower teams to act quickly. https://engineering.hinshelwood.com/signals/hiring-a-product-owner-avoid-copying-job-specs-from-the-internet/ Tue, 15 Apr 2025 15:30:50 +0100 https://engineering.hinshelwood.com/signals/hiring-a-product-owner-avoid-copying-job-specs-from-the-internet/ When hiring a Product Owner, do not rely on generic job descriptions; a true Product Owner drives product success by setting vision, prioritizing value, collaborating closely with teams, making data-driven decisions, and maintaining accountability. Delegation is necessary, but the PO must remain responsible for outcomes, not just manage tasks. Review your job specs to ensure they focus on leadership and product impact, not just administrative duties. https://engineering.hinshelwood.com/signals/99-of-all-animal-species-that-ever-existed-are-now-extinct/ Fri, 11 Apr 2025 15:30:00 +0100 https://engineering.hinshelwood.com/signals/99-of-all-animal-species-that-ever-existed-are-now-extinct/ Most animal species have gone extinct because they could not adapt, and the same fate can happen to companies that fail to evolve. Relying on past successes or outdated processes puts your business at risk, as the market changes quickly and does not wait. To stay competitive, focus on true adaptability and regularly assess what is slowing your company down. https://engineering.hinshelwood.com/signals/you-don-t-own-your-market/ Fri, 18 Apr 2025 15:30:32 +0100 https://engineering.hinshelwood.com/signals/you-don-t-own-your-market/ Your customers control the market, not you, so failing to listen or respond quickly means losing them to competitors. Many organizations prioritize internal views over real customer needs, leading to late product launches and missed opportunities. To stay relevant, focus on genuine customer feedback and ensure your teams are closely connected to those you serve. https://engineering.hinshelwood.com/signals/a-great-product-owner-drives-product-strategy-not-just-manages-the-backlog/ Tue, 08 Apr 2025 15:30:02 +0100 https://engineering.hinshelwood.com/signals/a-great-product-owner-drives-product-strategy-not-just-manages-the-backlog/ A great Product Owner shapes product strategy by owning the vision, understanding customers and the market, making tough decisions, aligning stakeholders, and adapting based on evidence. Focusing only on backlog management limits their impact; empowered POs drive real value and influence roadmaps. Ensure your Product Owners have the authority and support to make strategic decisions, not just administrative tasks. https://engineering.hinshelwood.com/signals/a-certification-proves-you-ve-passed-a-test/ Sat, 03 May 2025 15:30:21 +0100 https://engineering.hinshelwood.com/signals/a-certification-proves-you-ve-passed-a-test/ Certification shows someone passed a test but does not prove they can handle real product challenges or make strategic decisions. Experience is a better indicator of true capability, though certifications can help identify knowledge gaps. Hiring managers should prioritize practical experience over credentials when evaluating candidates. https://engineering.hinshelwood.com/signals/most-organisations-waste-their-smartest-people/ Sat, 12 Apr 2025 15:30:27 +0100 https://engineering.hinshelwood.com/signals/most-organisations-waste-their-smartest-people/ Many organisations waste their smartest people by creating environments where decision-making is centralized and ideas are slowed by bureaucracy, leaving those closest to the work powerless. This leads to disengagement or turnover among top talent, not due to lack of motivation but because they are unable to act. To retain and energize your best people, give them real authority to drive change. https://engineering.hinshelwood.com/signals/ai-isn-t-coming-for-your-job/ Sun, 15 Jun 2025 15:30:31 +0100 https://engineering.hinshelwood.com/signals/ai-isn-t-coming-for-your-job/ AI is not replacing people but automating repetitive tasks that never needed human input, such as data entry and routine reporting. This shift exposes the limitations of roles designed for control and repetition, highlighting the need for work that leverages human strengths like empathy and adaptability. Development managers should redesign roles to focus on meaningful, creative tasks that AI cannot perform. https://engineering.hinshelwood.com/signals/frederick-taylor-legacy-why-it-is-still-problematic-today/ Mon, 19 May 2025 15:30:58 +0100 https://engineering.hinshelwood.com/signals/frederick-taylor-legacy-why-it-is-still-problematic-today/ Many organizations still follow Frederick Taylor’s outdated approach of breaking work into repetitive tasks, leading to meaningless titles, ineffective bonuses, and siloed knowledge. With AI and automation revealing how much work is based on repetition, leaders must choose between maintaining the status quo or shifting to a culture focused on mastery, autonomy, and real outcomes. Development managers should reconsider current structures and incentives to ensure their teams are prepared for a future where genuine skills and collaboration matter most. https://engineering.hinshelwood.com/signals/the-hidden-impact-of-routine-jobs-on-worker-dignity/ Fri, 13 Jun 2025 15:30:38 +0100 https://engineering.hinshelwood.com/signals/the-hidden-impact-of-routine-jobs-on-worker-dignity/ Routine jobs were designed for efficiency, not human dignity, and their replacement by automation challenges outdated assumptions about people’s capabilities. Instead of preserving repetitive roles, focus on creating work that values problem-solving and critical thinking. Review your team’s job design to ensure it enables meaningful contributions rather than just compliance. https://engineering.hinshelwood.com/signals/ai-won-t-replace-humans/ Fri, 23 May 2025 15:30:36 +0100 https://engineering.hinshelwood.com/signals/ai-won-t-replace-humans/ AI will not replace people but will automate repetitive and mechanical tasks, freeing humans to focus on creative and strategic work. Companies that use AI to eliminate low-value tasks and empower employees will be more successful. Leaders should assess whether their processes rely too much on dehumanising work and use AI to improve job quality.