Agile Software Development: Prioritization Flashcards
Prioritization
Working on the things that provide value to the customer first.
Lack of priority
Too much Scope
Poor quality
unsatisfied customers
unsuccessful product
Two major perspectives to begin prioritizing
- Business Value
2. Technical Complexity
Determining Business value
- What is most important for our customer?
- Are we building what will make our customer successful?
- Are we building something that our customer will benefit from?
- Are we delivering Value?
- What is not ciritical for success?
- What is the customer asking for that they don’t actually need?
User stories at the top of the team’s to-do list are high-priority and should have what type of details?
Well-defined details so that the team can work on them
Product Backlog
List of all the remaining work for a product
Planning tool for the team developing the product
Contains, user stores, features, and epics for a product
Centralized and prioritized “To DO list” for the product
Who owns the product backlog?
Product Owner
Criteria for a Good Product backlog
Good Product Backlog: DEEP
The key aspects of a good product backlog are being Detailed Appropriately, Estimated, Emergent, and Prioritized.
Which user stories are prioritized in the product backlog?
Highest value and highest Risk
User stories at the top of the product backlog
1 Higher priority user stories
- Well defined user stories
- Higher risk user stories
- REady to be implemented
- INVEST criteria applied to stories
User stories at the bottom of the product backlog
- Lower priority
- Lower risk user stories
- User stories that are not well defined
- Invest Criteria not fully applied
Progressive Elaboration
A techique for prioritizaing the product backlog
Combine the backlog and any new user stories. Then prioritize user stories to the top of the backlog the items of high priority, well defined, and finer granularity. While the low priority, not well defined, and courses granularity user stories will be at the bottom of the backlog.
When are user stories split?
Too complex or too big
Dependencies are present
Not able to estimate
INVEST criteria is not met
Sprint Backlog
Teams backlog of committed work for a sprint
Creating the Sprint Backlog
- PO prioritize the product backlog
- The team commits to as much work as they can deliver.
- The team pulls the work
- The team only focuses on what is in the sprint backlog
- The PO prioritizes the work for the next sprint in the product backlog, while team members are working on the sprint backlog items
Who is responsible for the sprint backlog?
The team
MoSCoW
Backlog prioritization technique
Must have - critical
Should have - important
Could have - nice to have
Won’t have - never
Use Swim lanes or a Matrix
Basic Prioritization
Prioritize user stories based on value alone
User Stories are assigned Priority levels such as P1, P2, P3
High priority user stories are assigned P1 and are implemented first
P2 user stories are implemented next and P3 stores are last
Dot Voting
User stores or features are posted on a board
Dots represent “votes” and are given to each person
Each person receives the same number of dots
The number of dots that are given should be less than the number of user stories being voted on
Each person places their dots on the features or user stories
User stories are prioritized according to the number of dots
Play Money
Prioritization Technique
Each customer gets play money that equals the product budget
Each person distributes or spends their money on the features for the product
Features are prioritized according to the amount of the budget they recieve
