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.

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.

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.

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.

Practical branching strategies and trade-offs for teams struggling with many long-lived branches.

Should you estimate at the subtask level? A pragmatic take on estimation, planning, and focusing on outcomes instead of numbers.

Real-world advice for new Scrum Masters: why experience matters and how to build credibility beyond certifications.

Thinking about becoming a Certified Scrum Master? A deep dive into what it really takes to be a great Scrum Master. Discover why character, experience, and broad knowledge are more important than just a certificate, and why the role is more senior than you might think.

Is your Daily Scrum just a series of status updates? A look at a common misunderstanding of this key Scrum event. Discover why the Daily Scrum is a planning meeting for developers, not a status report, and what it means for team collaboration.

Should you partition your sprint into fixed percentages for features, bugs, and tech debt? An alternative approach to balancing new development with maintenance. Discover why integrating refactoring into your user stories might be a more effective way to improve code quality.

Should we wait until the merge request complies with the DoD? Or are we solving the wrong problem?

Does every agile team need a QA tester? A nuanced look at the role of QA in software development. Discover why testing skills are essential, even if you don’t have a dedicated tester, and how to build quality into your process from the start.

Scrum is fine, but most implementations of it aren’t.