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.

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

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

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

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

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.

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.

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.

What makes a good Scrum Master from a developer’s perspective? A list of expectations that go beyond the textbook definition. Discover the skills and qualities that can make a Scrum Master a true asset to a development team.

Should you include QA time in your story points? A story of a team’s journey from separate estimations to a more agile, continuous process. Discover how their approach to estimation evolved as they embraced practices like Continuous Delivery and smaller stories.

How do you set up an agile team? It’s not just about sprints. Discover why focusing on goals, feedback, and technical excellence is more important than just adopting a framework like Scrum. Learn about the Agile Fluency Model as a guide for your agile journey.

What happens when a team stops doing sprints? A look at a team that ditched traditional Scrum ceremonies for a more continuous workflow. Discover how they handle planning, priorities, and large-scale work without sprints.

Scrum vs. Kanban: which is more agile? A simple answer to a common question. Discover why agility is about culture, not the framework you use, and how you can be agile with or without Scrum.

Is your Daily Scrum a boring status report? Learn the true purpose of this crucial Scrum event. It’s not about standing up or making it ‘fun’ – it’s about effective daily planning for the development team. Discover how to fix a broken Daily Scrum.

Should you re-estimate unfinished tasks from a sprint? A pragmatic take on story points, velocity, and what really matters in agile development. Learn why re-estimation can be a useful tool to encourage your team to ‘start less, finish more’.

Is ‘Scrum Master’ a real job? A controversial take on the role, arguing that it’s a set of responsibilities, not a job title. Read a different perspective on what it means to be a Scrum Master and why having other skills is crucial for career stability.

Is your GitLab workflow too complicated? See a critique of a waterfall-like story progression and discover an alternative approach based on Continuous Delivery and Extreme Programming. Learn how to shorten feedback cycles and build quality into your development process.

Looking for some of the best videos on Agile product development? Check out these two recommendations that can help you, whether you’re a game developer or new to agile.

Are skill gaps creating tension in your development team? Explore a common scenario where senior developers lose trust in the work of their junior colleagues. Discover why this is a whole-team problem and learn practical strategies to foster collaboration, build quality into your process, and turn skill differences into a strength.