The strongest signals on engineering excellence and technical leadership — ranked by substance, not recency. How this is ranked
Velocity isn’t how many story points a team burns down
Velocity measures how quickly teams turn ideas into value, using build, test, deploy, and feedback times, not just story points, to track …
Scrum Masters are not glorified meeting schedulers
Scrum Masters must have technical and business expertise to guide teams, improve code quality, and drive real agility, not just schedule …
There no such thing as "good" technical debt
Technical debt always harms productivity and system stability. Ignoring it leads to inefficiency and risk, making it essential to address …
Engineering can fix technical debt, but leadership has to invest in it
Technical debt requires leadership investment to resolve; without support for automation and quality improvements, continuous delivery is …
Scrum Teams don’t set the bar for quality, they meet it
Scrum Teams must consistently meet a clear, non-negotiable Definition of Done to ensure quality, manage risk, and prevent technical debt in …
Do More Staging Environments Really Reduce Deployment Risk
Adding more staging environments does not reduce deployment risk; true safety comes from automated testing, continuous integration, and …
Every delay increases the risk of failure
Delaying software releases increases failure risk. Frequent, small releases improve success rates, adaptability, and recovery, as shown by …
Scrum doesn’t stop you from optimising flow
Explains how Scrum supports continuous flow and agility by prioritising Sprint Goals, Done increments, CI/CD practices, and outcomes over …
Technical debt isn’t just messy code
Technical debt includes slow feedback, fragile systems, and manual processes that hinder progress. Addressing it early with automation and …
The signals that speak most directly to technical leadership — ranked by that classification’s score alone.
The True Role of a Scrum Master Beyond Facilitation
Explains how a Scrum Master drives team improvement, removes obstacles, and leads organisational change, going far beyond basic facilitation …
How Top Scrum Masters Are Selected by Their Teams
Explains how Scrum Masters are naturally chosen by teams based on trust, experience, and leadership, highlighting the importance of peer …
Scrum Masters are not glorified meeting schedulers
Scrum Masters must have technical and business expertise to guide teams, improve code quality, and drive real agility, not just schedule …
Velocity isn’t how many story points a team burns down
Velocity measures how quickly teams turn ideas into value, using build, test, deploy, and feedback times, not just story points, to track …
The fastest way to cripple a Scrum Team? Hire the wrong Scrum Master
Hiring an unqualified Scrum Master limits team growth, reduces agility, and hinders value delivery. Effective Scrum Masters drive change, …
let-us be blunt
Accountability in Scrum requires real agency; without the power to act, roles like Product Owner and Scrum Master become ineffective and …
Scrum Masters: Enabling Teams, Fostering Agility, Removing Blockers
Explains the Scrum Master's role in ensuring team delivery by fostering agility, removing blockers, and being accountable for improving team …
There no such thing as "good" technical debt
Technical debt always harms productivity and system stability. Ignoring it leads to inefficiency and risk, making it essential to address …
Engineering can fix technical debt, but leadership has to invest in it
Technical debt requires leadership investment to resolve; without support for automation and quality improvements, continuous delivery is …
The signals that speak most directly to engineering excellence — ranked by that classification’s score alone.
Do More Staging Environments Really Reduce Deployment Risk
Adding more staging environments does not reduce deployment risk; true safety comes from automated testing, continuous integration, and …
Scrum doesn’t stop you from optimising flow
Explains how Scrum supports continuous flow and agility by prioritising Sprint Goals, Done increments, CI/CD practices, and outcomes over …
Velocity isn’t how many story points a team burns down
Velocity measures how quickly teams turn ideas into value, using build, test, deploy, and feedback times, not just story points, to track …
Evolving Engineering Practices to Improve Sprint Workflow in Scrum
Learn how evolving engineering practices like Feature Flags, TDD, and refactoring enable smoother Sprint workflows and reduce technical debt …
Rethinking Dev-Test-Staging-Production Pipelines for Safety
Explores why traditional Dev-Test-Staging-Production pipelines fall short and highlights audience-based deployment for safer, faster …
Scrum Teams don’t set the bar for quality, they meet it
Scrum Teams must consistently meet a clear, non-negotiable Definition of Done to ensure quality, manage risk, and prevent technical debt in …
Technical debt isn’t just messy code
Technical debt includes slow feedback, fragile systems, and manual processes that hinder progress. Addressing it early with automation and …
Technical debt cripples business agility and slows engineers down
Technical debt limits business agility, slows engineering, and hinders innovation. Managing it with automation and transparency is key to …
The Hidden Costs of Supporting Multiple Versions in Production
Maintaining multiple production versions increases bugs, merge conflicts, and technical debt, making development harder and less efficient …
132 resources, newest first
Detecting agile theatre with real delivery signals
Bonuses are not incentives
Bonuses reflect mistrust, not motivation. True engagement in knowledge work comes from purpose, autonomy, and meaningful challenges, not …
Why Most Transformations Fail Without Honest Conversations
Most transformations fail without open, honest conversations that address real issues, making transparency and tough dialogue essential for …
The Myth of Knowing Everything Upfront in Software Development
Software development thrives on continuous discovery and adaptation; upfront planning can’t predict everything. Embrace uncertainty, deliver …
AI isn’t coming for your job
AI is automating repetitive tasks, freeing people to focus on creative, strategic, and empathetic work that technology can’t replace. It’s a …
The Hidden Impact of Routine Jobs on Worker Dignity
Explores how routine, repetitive jobs affect worker dignity, questioning their value as automation rises and urging a shift toward …
In Scrum, we don’t do UX separately
UX is integrated into Scrum, not handled separately. Design and validation happen within Sprints and backlog refinement, supporting …
The FBI Sentinel project was textbook waterfall
The FBI Sentinel project failed with a waterfall approach, wasting years and budget, but succeeded rapidly after switching to Agile and …
Why Copying Scaled Agile Frameworks Fails in Your Business
Copying scaled agile frameworks fails because each business needs a tailored, evidence-based approach to agility that fits its unique …
Maximising Value from Applying Professional Scrum Training
Learn how Professional Scrum training empowers teams to identify organisational blockers, create actionable change backlogs, and drive real …
US Department of Defence and the History of Waterfall Delivery
Explores the US Department of Defence’s shift from traditional waterfall delivery to lean-agile methods, highlighting new procurement rules …
Too many organisations hide behind excuses:"
Many organisations use excuses to avoid Agile, but even large, regulated bodies can adopt iterative delivery to reduce risk and deliver …
FBI Launched Outdated Criminal Records System in 1995
The FBI’s 1995 criminal records system was outdated at launch, showing how slow, waterfall methods can leave technology obsolete and users …
Stop treating the end of the Sprint like a finish line
The end of a Sprint is a checkpoint for review and adaptation, not a deadline. Focus on flow, learning, and continuous improvement over …
Design Sprints in Scrum: Common Questions and Practical Insights
Answers common questions about integrating design and UX work into Scrum Sprints, clarifying why dedicated Design Sprints aren’t needed and …
You can’t deliver change through memos
Change succeeds when everyone understands and engages with it. Broad Scrum training empowers all roles to identify blockers and drive real, …
Scrum isn’t limited to building features
Scrum can drive organisational change, not just product features, by using backlogs, teams, and feedback to enable real, evidence-based …
Evolving Engineering Practices to Improve Sprint Workflow in Scrum
Learn how evolving engineering practices like Feature Flags, TDD, and refactoring enable smoother Sprint workflows and reduce technical debt …
Why Frameworks Alone will-not Transform Your Team Culture
Explains why frameworks alone can't shift team culture, emphasizing clear vision, leadership commitment, and empowering teams to drive …
When you scale Scrum, the challenge isn’t just delivery, it coherence
Explains how scaling Scrum requires UX coherence through Communities of Practice, shared frameworks, and collaboration, not central control, …
David thought he already knew Scrum
Discover why experienced Scrum practitioners often misunderstand core principles, and how revisiting Scrum fundamentals restores clarity, …
Scrum doesn’t stop you from optimising flow
Explains how Scrum supports continuous flow and agility by prioritising Sprint Goals, Done increments, CI/CD practices, and outcomes over …
Scrum Myth Debunked: Unfinished Work is Allowed in Scrum
Clarifies Scrum guidelines on unfinished work, explaining that items can span multiple Sprints if the Sprint Goal and Done Increment remain …
AI won’t replace humans
Explores how AI automates repetitive tasks, enabling humans to focus on creative, strategic, and empathetic work, and challenges fears about …
Scrum is not an engineering process
Explains why Scrum is a social framework, not just engineering, emphasizing inclusive training, alignment, collaboration, and breaking …
Frederick Taylor Legacy: Why it-is Still Problematic Today
Examines how Frederick Taylor’s management ideas still shape workplaces today, highlighting their impact on motivation, job design, and the …
Resilience is not a department
Resilience must be built into products from the start, ensuring they withstand failures like outages or network loss, rather than being …
During a massive flood in London, nearly every datacentre went down."
A London flood shut down most datacentres, but Rackspace stayed online by regularly live-testing failures, proving true resilience comes …
When Heathrow went down, they blamed the power supplier
Heathrow’s outage was caused by an over-sensitive disaster recovery system, not a power loss, highlighting the risks of untested resilience …
Everyone has a disaster recovery plan, on paper
Most disaster recovery plans fail in practice due to overlooked dependencies and lack of real-world testing, leaving organisations …