Documente Academic
Documente Profesional
Documente Cultură
Product Backlog
Daily Stand-up Meeting
Prioritization
24 hours
Adapt
Inspect 2 to 4 Weeks
Features Epics Stories Stories Iteration Planning Tasks defined / expanded by team
Retrospective
Deliverable*
Release Backlog
2
Iteration Backlog
Iteration
Product Backlog
The Product Backlog is the master list of all functionality desired in the product, that evolves iteratively throughout the entire project.
Product Backlog items, referred to as Stories, are typically user-centric, hence the term User Stories, but will also include technical and other non-functional stories that will need to be developed and delivered. The on-going process of iteratively maintaining the Backlog is referred to as Grooming. As the Project and Backlog evolves, the Product Owner and the Team will collaborate to groom, order and size the Stories. Backlog Order starts with Business Priority/Value, and is then refined based on Risk, Necessity, and any logical or technical dependencies. The Product Owner(s), with the assistance of BAs and/or SMEs, are responsible for writing the Stories, based on the desired functionality.
3
Tasks
Build UI
Setup DB
Update Front-End Build Web Service Update Tech Design DB Testing Front-End Testing
Release
Theme 1 Theme 2 Theme n
Process Level 1 / 2*
i.e. work stream and/or core functionality
Theme
Epic 1 Epic 2 Epic n
Process Level 2
i.e. Sales Order Process
Epic 1
(aka. Feature)
Story 1 Story 2 Story n
Story 1
Task 1 Task 2
Task 1
Unit of Work
i.e. BPxxx_B_001 *May be a Business Requirement, RICEFW, Configuration, etc
Task n
Maintain an iterative process of analysis to continually refine and decompose Requirements into discrete units of work Level of Effort (LOE) estimates are iteratively refined as decomposition reveals new information (gaps, complexities, redundancies, etc)
What is a Story?
The User Story represents customer requirements rather than documents them Provides a simple format to insure consistent, correct communications with the team and stakeholders Serves as a Token for a conversation Feature descriptions from the perspective of the User/Customer Also includes requirements of System or the team - these are referred to as nonfunctional stories Includes "Acceptance Criteria, which are clearly defined conditions, that can be tested and demonstrated, required to be met in order for the Product Owner to accept it Able be completed as a distinct deliverable, within a single iteration, independent of other stories
As a customer service rep , As I need a System to cancel , an order, at the I customers need to Map request, Master Data changes so that I can , so provide that I can quality enable Sales customer Order service Processing . steps.
User stories are increasingly used on Agile projects. This popularity is a very good thing. Goal and business oriented, their simplicity and a immediate focus on acceptance criteria make them terribly effective on design projects.
Negotiable
Valuable Estimable Small Testable
V E
S T
7
Test Cases should be created for each Story, based on defined Acceptance Criteria, that defines the steps necessary to validate the functionality (enables the team to, at a minimum, Unit test and User test. Test Cases (may also be referred to as Use Cases) define the key process steps that need to be satisfied, such as:
CSR selects Sales Order based on Customer Name CSR clicks [Cancel Order] button CSR selects an appropriate Rejection Reason Code CSR clicks [OK] when prompted to confirm cancellation and view confirmation screen
Requirement
Justification
It starts with a very big Story, then we refine and decompose it until it is clear, concise and deliverable as stated
9
-Matching Results -No matching Results -Too many matching Results -By Author Name -By Genre -By most popular -As a New User -As a Registered User -As a Power User
10
As a customer, I want to buy books online so that I dont have to leave my home
As a customer, I want to add books to a shopping cart so that I can compile the list of books to buy
As a customer, I want to buy my books with a credit card so that I can pay for the books I want
11
Wrap-Up
Q&A
12