Member Articles

Enjoy our extensive collection of member-contributed articles to learn how other Scrum practitioners use Scrum in the workplace.

Read about the experiences and ideas of Agile colleagues around the world, and share your own thoughts here. You can also visit Spotlight, which features blogs by experts in the fields of Scrum, Agile, and the broader business world.

Opinions represent those of the authors and not of Scrum Alliance. The sharing of member-contributed content on this site does not imply endorsement of specific Scrum methods or practices beyond those taught by Scrum Alliance Certified Trainers and Coaches.

What I have experienced is that there is a very thin line between changing requirements versus lack of proper definition of stories and acceptance criteria that can lead to scope creep, even in an Agile environment.

The difference between user stories and use cases can be challenging to understand and explain, especially if your team is making a transition from a Waterfall software development environment to Agile and Scrum.

Having been in the outsourcing industry for several years, the most challenging issue I have encountered is formalizing service level agreements (SLAs) or key performance indicators (KPIs) as part of the contractual agreement for adopting Agile.

To remain competitive, we must innovate. A product owner is always challenged to satisfy innovation needs while simultaneously handling current requirements. Can innovation become another item in the product owner's backlog?

A self-organizing Scrum team is really a great team. In fact, it is an ideal condition that not every team reaches -- so it is no wonder that some people call it a myth. What are some keys to making it a reality?