From the course: Agile at Work: Planning with Agile User Stories
Join today to access over 24,900 courses taught by industry experts.
Develop a product backlog
From the course: Agile at Work: Planning with Agile User Stories
Develop a product backlog
- Back to the voluminous requirements document, oh no. Traditional approaches have many types of requirements documents that may be utilized. A few examples are business requirements document, functional requirements document, software requirements specification. They can take months to complete and reach lengths of 30, 50 or over 100 pages of text. They're challenging to read, comprehend, and create. Agile approaches use a different strategy. Most agile teams have a product backlog that is the primary source of the requirements. The backlog is comprised of small requirements called stories. Although many types of stories are in use today, there are two primary types that I will cover, the user story and the technical story. User stories have been around for more than two decades. Their popularity has remained strong and for good reason. User stories are tiny requirements, often a sentence or two combined with additional details called acceptance criteria. Early in their usage…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.