What Do Testers REALLY Do On a Scrum Team?
Analysis, design, coding, and testing are done constantly rather than in phases, meaning testing ISN'T just a phase but an ongoing part of Agile Development.
Analysis, design, coding, and testing are done constantly rather than in phases, meaning testing ISN'T just a phase but an ongoing part of Agile Development.
When I teach or coach people about Scrum, we talk about self-organization, but the importance of self-organizational principles cannot be understated.
Specialists with a particular skill can get stretched thin! But there's ways to solve this dilemma other than assigning them to ten Scrum teams at once.
Some initial “rules” that everyone agrees to follow will help your team avoid misunderstandings and deliberate misconduct.
What's the one thing YOU could do as a Scrum Master to improve your team's reliability, quality, and productivity? Read on and find out!
In this article, we'll discuss how a team bares responsibility for the Sprint and what should be done if they can’t get everything done they committed to.
One of the worst things we can do to our teams is allow too many changes to the content of the Sprint after the Sprint has been planned.
Scrum Sprints provide empiricism, part of the Agile core beliefs, which is why extending a Sprint is never a good idea!
Many Scrum events seem simple, but aren't. The Daily Scrum seems to be the event that causes the most problems for teams.
Teams that "Swarm" backlog items find it's a better way to get work done than approaches that lead to handoffs and continuity loss.
Measuring Scrum Team productivity is something nearly every organization wants, but performance metrics should really only be created under two conditions.
This blog post seeks to provide some tips you can use to help your teams successfully do large item estimation. Part 6 of my series on Backlog Refinement!