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.

Organizations adopting Scrum have business analysts, business systems analysts, systems analysts, and architects, among many other titles. Who among these is best suited for a delivery team's product owner role?

A retrospective is one of the core events of Agile practices. But for most teams, retrospectives are not as effective as they should be. Here are the five major symptoms of ineffective or dysfunctional retrospectives.

Why should we have retrospective meetings after every sprint or iteration? I have observed that some project teams skip the retrospective process, thinking that they save time by doing so. However, this only creates adverse effects.

In Scrum, challenges arise when we must perform evaluations. Scrum teams work together to complete the commitments they have made collectively for a sprint. Therefore, evaluating an individual becomes difficult.