5 Ways to At Least DOUBLE Team Performance
Here's 5 steps you can take as a manager or ScrumMaster to help DOUBLE your Development Team's performance (#5 is a shocker; it's easy but SUPER non-intuitive!)
Here's 5 steps you can take as a manager or ScrumMaster to help DOUBLE your Development Team's performance (#5 is a shocker; it's easy but SUPER non-intuitive!)
When beginning the transformation to Agile Development, it's hard to know exactly what skills the organization needs to adapt to the new way of working.
Effective Scrum use is more than Sprint Planning, Daily Scrums, and so on. To see a big difference in your team's Sprints, make these workflow changes.
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!
If your Scrum teams aren't seeing the quality, value, and productivity improvements you were hoping for, it's possible that they don't understand their roles.
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.