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.

Recently a CEO asked me, "What is the meaning of culture in our organization? Is culture what most areas of the company do? Is it what management says? Is it what I tell people to do?" The answer is rather more exciting than this.

When I first started as a ScrumMaster with my current employer, the team was excited about the concept of rapid and quick development cycles that would provide incremental value to our customers in short development sprints. . . .

Am I able to coach without ruffling some feathers in an organization in which, as an outsider, I am going to bring about change? Here I would like to highlight a particular strategy called GULP, which has helped me lessen the resistance that change agents so often face.

What is the ideal testing strategy for a Scrum team? Having worked with diverse organizations that operate with different styles, I have composed a set of daily tasks and expectations that I have seen to work well for testing in Scrum teams.

Causal loop diagrams provide a great way to graphically illustrate cause-and-effect relationships between various elements of an organizational ecosystem. I have found that they are highly useful in communicating ideas to my customers, particularly to senior leadership.

In any product development, it is often perceived that documentation plays second fiddle to development in Agile. In fact, in today’s world, both these domains play a key role in the success of a product. So, what exactly is this type of documentation?