Prioritization Techniques: Lets move beyond MoSCoW!!
- Have you been in a situation where everything gets prioritized as MUST HAVE?
- Have you been in a situation where you have find it difficult to get different stake holders to agree on relative priority of different features?
- Most of the time is spent in discussiing low value features?
- Whoever screams the loudest, gets their pet features prioritixed high?
- Do you want to learn some more prioritization games/techniques that can be used to start prioritizing at Feature level and subsequently refine it to story level?
- You feel the current technique(s) you use for prioritization are time consuming and ineffective?
If answer to any of the above questions is yes, this is the workshop for you to attend
Customers are never thrilled to find out they can’t get all the features they want in release 1.0 of a new software product. In reality, customer expectations are high, timelines are short, and resources are limited. Any project with resource limitations has to establish the relative priorities of the requested features, use cases, or functional requirements. Prioritization helps the project manager resolve conflicts, plan for staged deliveries, and make the necessary trade-off decisions. Thus, requirement prioritization is used in Software development for determining which requirements of the software product/application should be included in a certain release. Requirements are also prioritized to minimize risk during development so that the most important or high risk requirements are implemented first.
Several methods for assessing a prioritization of software requirements exist. In this workshop we are going show some of techniques/games we have used for feature prioritization.