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.

"Quality" is one of the most commonly used terms, and at the same time the most misunderstood. There is a great need to understand it, so let's try to explain quality and how we can ensure the quality of our products.

Being a ScrumMaster requires a complex and varied set of skills, including how to be a coach and facilitator, resolve conflicts, remove impediments and manage stakeholders. These are the topics that I’m going focus on here.

When feedback is a waste of time, those in the session tend to feel rejected, defeated, and hopeless. How do we create a healthy feedback session? Through engagement. Activity-based retrospectives will bring the team life and energy.

Test automation is key to Agile development. And being on an Agile team means that we are always addressing these questions: How far should we automate? What should not be included? How quickly can we develop, test, and deliver?

In looking at a series of team retrospectives, the data told me that the same issues were resurfacing after every other sprint. That is when I realized that the team should have a Retrospective of Retrospectives.

An issue with most IT project teams is that they jump into solution implementation without proper planning. I would like to discuss an important responsibility of a ScrumMaster and a best practice to ensure that proper planning is done.

We have tried the Three Amigos planning process (as shared in an earlier member article), and here I'd like to share my thoughts about it, including how we are using it and what areas we have modified for our team.