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.

Though there is lot of bias toward increasing velocity in every iteration (release more features faster), if there is no attention to quality, the system will soon become fragile and will not be able to sustain future scope changes.

Agile development is based on empiricism and thus does not recommend a watertight framework for practice. The learning organization disciplines provide a foundation for practicing Agile software development. We can see a strong correlation between Agile tenets and learning organization disciplines.

At the heart of Agile is delivery of business value. Search for its real meaning has become a sort of Agile Holy Grail. Yet when you step far enough back from any of our software development practices, we still seem to operate in the zone of simply “delivering features the customer likes.”

It seems intuitive that once you have sized your stories and agreed on the sprint backlog, it doesn’t really matter how you do your stories (e.g., in what order, which one’s first, how many you start together). Is this accurate? Let’s examine a few scenarios.