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.

I worked with an awesome development team that had an Agile training budget of zero and a time allowance during business hours for a two-day deep dive. Therefore I put together the following schedule from hours and hours of YouTube viewing, which I hope might help you as well.

Each of my children uses Agile principles and practices in different ways to accomplish his or her goals. To have my children do this, this early in their lives, gives me great satisfaction because they are learning how to make their lives simpler and more efficient.

Whether you are using Scrum or another software delivery method, it is highly likely that you will be working as a group in order to achieve your goals -- you will, in fact, be team workers. What are the necessary traits?

How can we make sprint retrospectives more effective? It takes time to create stable teams, but retrospectives play a major role in shaping the team and in making Scrum the right fit for an organization.

Over the years, I've found that one of the biggest hurdles in getting (and keeping) a team to think in an Agile Scrum manner is the fact that the ScrumMaster is not the boss. As with many things in life, this is easy to say and more difficult to practice.

A ScrumMaster is responsible for removing all impediments that stand in the way of the Scrum team during a sprint. Though the role of a ScrumMaster seems pretty straightforward, there are many aspects to what he or she does.

In software development, the term "quality" has always been an area of concern. Because customers are the entity around which an organization's business strategy grows, they are the driving force that defines quality. This approach basically keeps you focused on "what customers need."

I recently interviewed for a coaching role. The teams were definitely having problems; the good news is that an Agile coach can slowly untangle all the issues. But here's the key: Scrum works, but scrambled Scrum does not.

I was toying with the idea of a game around work in progress (WIP), which can be incredibly stressful for teams. As part of a group effort at a meeting, we came up with a result that covers even more than my original intentions.