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
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 …
Who signed off on cutting quality?
Cutting quality to hit a date is not a delivery problem but a risk decision on contractual penalties, customer trust, and accounts that the …
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 …
You can not implement Agile or Scrum successfully by decree
Mandating Agile or Scrum fails without cultural change; true agility requires trust, transparency, and a supportive environment, not just …
Toyota "andon" cord lets any worker stop production to fix defects
Explains how true quality improvement needs both tools and a culture of safety, using Toyota’s andon cord as a lesson for Agile and Scrum …
You want speed, adaptability, resilience
Explores why true organisational agility depends on empowering teams with agency, not just adopting frameworks like Scrum, Kanban, or …
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 …
We hear self-managing teams so often it become a cliché
Explains how true self-management in Scrum requires active, disciplined effort from Product Owners, Scrum Masters, and Developers, not chaos …
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 …
Fear is the real enemy of agility
Explores how fear hinders true agility in teams, emphasising the need to foster courage and trust for effective Agile, Scrum, and DevOps …
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 …
Most teams don’t fail because they lack frameworks
Teams struggle not from lacking frameworks, but from ignoring feedback. Success depends on acting on signals, fostering safety, and …
Agile and Scrum are often misunderstood
Agile and Scrum expose underlying team and workflow issues, helping organisations address real problems rather than masking dysfunction with …
A certification proves you’ve passed a test
Certifications show test-passing ability but don’t prove real-world product skills. Experience, judgement, and stakeholder influence matter …
Here the dirty secret behind many agile transformations
Many agile transformations restrict team autonomy, leading to control and compliance instead of true ownership, adaptability, and meaningful …
I’ll never understand teams that manage bugs instead of fixing them
Highlights the importance of promptly fixing software bugs instead of managing backlogs, arguing that unresolved defects harm product …
let-us do the maths
Explains how slow product release cycles delay feature delivery, risk losing relevance, and create competitive disadvantages, highlighting …
Too much refinement wastes time
Balancing backlog refinement prevents wasted effort and chaos. Aim for just enough detail so developers can plan sprints confidently without …
Not all surprises in product development are true unknowns
Many product development surprises stem from poor backlog management, not true unknowns. Regular refinement and reflection help teams …
Innovation graveyards: Where great ideas die in slow organisations
Explores how slow organisational processes, risk aversion, and excessive alignment cause promising ideas to stall, leading to lost …
No successful company thrives by copying others’ ways of working
Successful companies thrive by creating unique ways of working, not by copying frameworks. Tailor your approach to fit your organisation’s …