The strongest signals on engineering excellence and technical leadership — ranked by substance, not recency. How this is ranked
Detecting agile theatre with real delivery signals
Just ship it is not sufficient authority
Shipping below an agreed quality standard is a financial, legal and customer risk that only the organisation's accountable leaders can …
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 …
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 …
You want speed, adaptability, resilience
Explores why true organisational agility depends on empowering teams with agency, not just adopting frameworks like Scrum, Kanban, or …
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 …
There a common belief that rollback is the ultimate safety net
Rollback is often riskier than rolling forward, especially for stateful apps. Safer deployment relies on progressive delivery and …
Everyone loves to shout give teams autonomy
Explores why team autonomy in Scrum must be balanced with alignment to strategic goals, highlighting the role of clear objectives and …
Why Tracking Individual Cycle Time Distorts Team Behaviour
Tracking individual cycle time can harm team performance by encouraging task cherry-picking, reduced collaboration, and lower quality, …
134 resources, newest first
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 …
Understanding Blocked Columns and Stalled Work in Project Boards
Explains why using blocked columns for stalled tasks on project boards harms workflow, and suggests better ways to highlight and 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 …
At the end of the day, Kanban is about improving flow
Kanban focuses on improving workflow by removing bottlenecks and constraints, reducing work in progress, and increasing process efficiency, …
Realistic Expectations When Hiring Junior Scrum Masters
Understand the risks of hiring inexperienced junior Scrum Masters, including higher costs, team issues, and project delays, versus investing …
If software is not delivered, it is not valuable
Undelivered software provides no value. Frequent, iterative releases reduce risk, cost, and failure, enabling faster learning and real user …
Staging Environments Do Not Prevent Production Failures
Staging environments can’t fully replicate production, often leading to false confidence. Real risk reduction comes from safe, incremental …
A two-day Scrum Master certification doesn’t make you a Scrum Master
Practical experience is essential for effective Scrum Masters; certification alone is insufficient. True expertise comes from guiding teams, …
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 …
Best Branching Strategies for Development Teams Explained
Explains why environment-based branching slows development, and recommends using feature flags and progressive rollouts for simpler, faster, …
Scrum is built on empiricism, transparency, inspection, and adaptation
Explains why consistent delivery of usable increments is essential in Scrum, highlighting the Scrum Master's accountability for ensuring …
Why Organisations Believe Their Software Is Too Complex for CD
Many organisations cite software complexity as a barrier to continuous delivery, but real obstacles are technical debt and lack of …
What Makes an Effective Scrum Master Beyond Meeting Facilitation
Explores key qualities of an effective Scrum Master, focusing on team empowerment, backlog management, collaboration, and removing …
Deploying Windows OS Directly to Production: Then vs Now
Explains how Windows OS updates shifted from infrequent, risky releases to safe, staged rollouts using ring-based deployment and real-time …
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 …
Why Using a Blocked Column in Azure DevOps Is a Mistake
Explains why a “Blocked” column in Azure DevOps hinders workflow, and suggests using tags and tracking to manage blocked work more …
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 …
Key Skills Scrum Masters Need: Technical, Business, Organisational
Scrum Masters need technical, business, and organisational skills to guide teams, remove obstacles, drive value, and lead effective agile …
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, …
Would you hire a Junior CISO? A Junior Financial Director
Scrum Masters require proven expertise, not entry-level skills. Hiring juniors in this role risks team performance and agile success; …
Hiring a Scrum Master is hard
Finding a skilled Scrum Master is challenging; true effectiveness requires deep Scrum knowledge, coaching ability, and alignment with your …
Not all delays are the same
Explains the difference between waiting and blocked tasks, why clear distinction matters in workflows, and how to track and address sources …
Why Engineering Teams Use Staging Environments for Risk Reduction
Explores how staging environments aim to reduce risk in software development, their hidden costs, and modern alternatives like feature flags …
Challenging Misconceptions About Behaviour in Agile Teams
Explores common misconceptions about Agile teams, clarifying that true agility demands discipline, planning, and professionalism, not chaos …
There a common belief that rollback is the ultimate safety net
Rollback is often riskier than rolling forward, especially for stateful apps. Safer deployment relies on progressive delivery 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 …
Git Flow should have died years ago
Explains why Git Flow is outdated for modern software, highlighting its drawbacks and recommending simpler workflows like GitHub Flow for …
Branch promotion is a relic of slow, manual software delivery
Explains why modern software teams avoid branch promotion, using continuous integration, feature flags, and production-like testing to …
Frequent releases are not just a technical strategy
Frequent software releases reduce risk, enable faster feedback, and help teams adapt to user needs, preventing costly mistakes and improving …
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 …
Too many teams overcomplicate their branching strategies
Learn why simple branching strategies like GitHub Flow and Release Flow help teams deliver faster, reduce risk, and avoid the pitfalls of …
Every unreleased feature is a cost
Unreleased features create hidden costs and risks. Regular software delivery reduces failure rates, rework, and missed opportunities, …
The false claim that Scrum is immutable
Clarifies that Scrum is flexible and adaptable, not strictly immutable, and highlights the importance of transparency when modifying its …
The majority of Scrum Masters are not fit for their position
Most Scrum Masters lack essential Scrum knowledge, with only 39% meeting core standards. Poor competency threatens team success and …