Prioritization by value (DevOps, Scrum)
Download as PPTX, PDF2 likes702 views
This document by Tommy Quitt outlines the process of building a project backlog through various methods like conversations and research, emphasizing the need for customer feedback and the realization of system value. It discusses project planning with a focus on prioritization factors such as risk, effort, and value. Additionally, it poses critical questions regarding stakeholder importance and feasibility of support for activities.
Prioritization by value (DevOps, Scrum)
- 1. Prioritization byValue This document/presentation was prepared/created byTommy Quitt for his own purposes. All materials contained in this document/presentation are protected by copyright laws, and may not be reproduced, republished, distributed, transmitted, displayed, broadcast or otherwise exploited in any manner without the express prior written permission ofTommy Quitt. 1
- 2. Project Discovery The objective: Build a project backlog The means: Conversation,Questions, Research, Pilots The result: a list of Epics, prioritized and ready to be detailed 2
- 3. Why? Requirements are not fixed (Although the customer “signed off”) Estimations are only estimations We want to get customer’s feedback as soon as possible We want the customer to realize the value from the system as soon as possible 3
- 4. Then, how to plan the project? 4
- 6. ValueVs. Risk 6 High HighLow R I S K Value Avoid Low Priority High Priority Medium Priority
- 7. Priority questions Is it really important that these stakeholders (users) are able to do this? Is it actually possible for us to support this activity currently? Is it important enough to us that we should consider infrastructure / policy changes? Can we meet these goals only in this way? Do we need to meet these goals now? Is this a long term project goal? 7