9 Useful Rules for Prioritizing Use Cases

Type: Rules


Using a smart way of finding the use cases to start with
Note: You may want to replace 'use case' with 'feature'.

Principles and Notes

You should start with a use case that has the following properties:
Note: You are not supposed to use all principles at once. Focus on 1-3 principles. Discuss with your sponsor, which principles you should use. Proposal: use 2 principles to find the initial order. Use a third principle to move use cases forth and back in this order.

R1: a key stakeholder is an actor to the use case

R2: the actor has been determined as 'primary'

R3: the use case's development is particularly risky or it's attainability is uncertain (due to technical or organizational issues, for example)

R4: it is a use cases within a core business process

R5: the use cases yields high business value

R6: the use cases yields high ratio of business value to costs

R7: there is a business related dependency to another use case wich uses the business results of the first

R8: the use case is part of a business process and it makes sense - from a business point of view - to first complete all use cases for this process

R9: the team can gain knowledge (about the domain, the project, the product) from implementing a use case

Related Pages

finding the right size for a use case
how to state the credibility of estimations
go agile, enterprise wide
use case content patterns
10 Deadly Sins of Estimation (on Seer)

rating: +1+x

If you want to know more about a topic, simply tag the article with a 'morePlease' or 'examplesPlease' tag!


Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License