Slide Deck 4 - SW Prioritization and Planning Flashcards
What is financial prioritization?
Estimating the money to be made or saved by each theme can be used to prioritize each of the themes
Forecasting the financial value of a theme or decisions on priorities is responsibility of the ___ ?
Product Owner
What are the 4 sources of revenue?
New Revenue, Incremental Revenue Sources, Retained Revenue, Improved Operational Efficiencies (Reduced Cost)
When should you split a story?
When the implementation will take longer than the iteration
Stories can be split in what ways?
Along boundaries of the data, operational boundaries, split into separate CRUD operations, of mixed priorities
Should we keep exception handling or error conditions when a large story could be made smaller?
no
What is it to split on operational boundaries?
Divide the story into different iterations or components that can be implemented or improved on each time
What is splitting via CRUD operations?
Create, Retrieve, Update, and Delete
As a …, I can add…
… I can edit…
… I can delete…
What are “cross-cutting” features? and how are they removed?
Cross-cutting features are things like security, logging-in, error handling, etc. where they each cut across all features of the application.
They are removed by essentially doing an iteration without the features and then another iteration implementing all the features
What is splitting on mixed priorities?
If you have a big user story but somethings that are broken off have a higher importance than others in order for things to work, i.e., you cannot ship the product if it does not have a login screen. You split the smaller stories if they have different priorities
Why do we do release planning?
- Create a high-level plan for a period longer than an iteration
- Helps the product owner and team get an idea of how much work is left
- Conveys expectation of what will be developed by when
- Serves as a guidelines for the team to progress to
What are the 6 steps in release planning?
- Determine conditions of satisfaction
- Estimate the user stories (story points)
- Select an iteration
- Estimate velocity
- Prioritize user stories
- Select stories and a release date
Then go back to (1) until conditions of satisfaction are best met
What are the conditions of satisfaction?
Criteria to be used to determine success or failure
i.e. schedule, scope, resource goals
How is a feature driven project conditions of satisfaction computed?
Sum the estimates of all features and divide by the expected velocity to get iterations needed (and the time)
How is a date driven project conditions of satisfaction computed?
Count the number of iterations to the expected release date, multiply that number by the velocity per iteration to get the total story point to be completed by the specified date.
