Wondering where to start with agile transformation? Do you pick a single project? Or a specific team? Train everyone and run with it? Here's some guidance.
As a ScrumMaster and organizational change advocate, here's 7 things you can do to help your organization embrace change as a normal way of life.
Change usually creates conflict, but a good ScrumMaster knows what types of conflict to expect and is prepared to handle it with correct conflict responses.
One small change can make a BIG difference to your Product Owner success. Before worrying about putting value on backlog items, here's some simple tips.
With the Agility mindset, it's critical to understand the concept of "being" Agile. Some people want "to do Agile", but you don't DO Agile, you must BE Agile.
Should Scrum teams be dedicated to a single product? The truth is, there's times when you want a dedicated team and times when you don't. Let me explain!
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.
Although the Scrum Guide defines the ScrumMaster at length, here we're going to dissect that description and take a much closer look at what a ScrumMaster is.
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.
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!