This document discusses Scrum, including both myths and best practices. It begins by questioning whether Scrum is a "holy grail" or "holy s#!?". It then debunks the myth that Scrum means rapid development and clarifies that agility is about flexibility, not speed. The document also outlines what Scrum focuses on and provides examples of pitfalls seen in Scrum teams, such as when the Product Owner acts as a developer or the definition of done is changed at the end of a sprint. It shares tips for running effective Scrums through retrospective meetings, reasonable 'sprints, and keeping things simple. In the end, it emphasizes self-learning, agility and control, and continual improvement
Related topics: