For those not familiar with agile development and Scrum, a ScrumMaster may sound like a new term for project manager.
Those familiar with Scrum, however, know that the truth is very different. In many ways, a ScrumMaster is the antithesis of an old-school project manager. Instead of telling, the ScrumMaster coaches. Instead of directing, the ScrumMaster guides. Instead of being the authority, the ScrumMaster serves.
User stories are a fundamental component of any agile development. They’re the building blocks that get prioritized on the product backlog and brought into sprints, they capture what needs to be done to officially “sign off,” and they focus the development team’s discussion on how to do it.
So what’s an epic?
User Stories are one of the most important parts of agile development.
Yes, user stories replace those traditional requirements and specifications docs. But they do it in such a different manner that casual observers wouldn’t even recognize the relationship.
User stories are a critical element of the agile software development process. But they're so different from traditional software requirement documents that many Scrum teams struggle to get them right.