Discover the best ways to customize your agile workflow. Learn how to adapt your process to your team’s needs, and then configure your tools to support your unique workflow.

Should you be sizing bugs found during regression? This post challenges the idea and explores why focusing on ‘shifting quality left’ through automated testing and team collaboration is a more effective approach.

Ever wondered where ‘in-testing’ tickets go in a Trunk-Based Development workflow? Discover why you might not even need that status and how to ship faster with small changes, teamwork, and automation.

Should you schedule backlog refinement meetings? This post explores the pros and cons of different approaches, from scheduled sessions to continuous refinement, and helps you decide which method is right for your team.

Does story size really matter? A developer’s perspective on why breaking down complex stories during the sprint is more important than over-refining them beforehand. Learn how to embrace emergent design and continuous planning.

What do you do with a story that’s too big for a sprint? This post shares a story about a team that ditched Scrum for a more flexible, goal-oriented approach, and why it might be the right move for you.

Is Scrum losing its edge? This post explores the flaws of the popular framework, from its user-unfriendliness and intentional incompleteness to its outdated approach to modern challenges like scaling.

A short argument for why Scrum is a discovery framework, not a traditional project management method.

Why Scrum and project management feel similar — and where Scrum’s focus on empiricism and discovery really differs from traditional project approaches.

A reality check on estimates: why story points are guesses and how to make estimation useful for your team.

Practical guidance on how much analysis a Scrum team should do before a sprint and when to keep planning lightweight.

When managers block testing: how to push for developer-owned quality and get buy-in for writing tests.

Strategies for migrating and testing tangled legacy business logic when documentation and tests are missing.

What to do when new requirements surface during development — prioritize, split work, and avoid perfectionism.

Bugs are inevitable, but how should you schedule time to fix them? This post argues against delaying bug fixes and advocates for prioritizing them immediately to maintain product quality and team efficiency.

Transaction cost matters: reduce build time, manual approvals, and slow tests so you can deliver in small batches and increase flow.

Practical thoughts on remote teams across timezones — when distributed teams work and when they break Scrum.

Why burndown charts can mislead and how the Daily Scrum and Sprint Goal reveal real sprint health.

A reaction to a survey showing most developers don’t practice TDD — why TDD matters and how to make it work in teams.

A defence of the ‘Boy Scout Rule’ — why leaving code better than you found it still makes sense when done intentionally and aligned with business goals.