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.

Traditionally, release planning is done based on effort estimations of the requirements. But in projects for which the requirements are at a high level without enough details, it becomes difficult to create a high-level release plan.

I asked my Scrum Team to estimate user story A, and after a good game of Planning Poker, they came up with a number that was accurate and achieved. It felt like a great success — and that was when I woke up.

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.