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.
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!
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.
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.
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.
Many organizations transitioning to Agile Development suffer from a preconceived idea that coding tasks and testing tasks should be seen as separate activities.