From the course: Getting Started with Azure DevOps for Non-Programmers

Unlock this course with a free trial

Join today to access over 25,600 courses taught by industry experts.

Prioritizing work items in the backlog

Prioritizing work items in the backlog - Azure Tutorial

From the course: Getting Started with Azure DevOps for Non-Programmers

Start my 1-month free trial Buy for my team

Prioritizing work items in the backlog

“

- [Instructor] A key way in which business should be involved in Azure DevOps is prioritization. Ideally, the business ultimately owns the software, particularly if it is client facing and even if it's internally focused, unless it's for managing software or servers, the software should still be owned by the business because they have to ensure it's developed in a way that will pay for itself by raising funds or reducing risk. It makes sense then that only the business can specify what changes should happen to the software. And in the case where not all requirements can be met, that the business define which are the key deliverables and which can slide. Now, the business can prioritize the work directly in ADO by dragging and dropping. Let's change this to feature so we see a few more things and let's remove that sort of hierarchical view and get rid of mapping. Now, I can drag that up. Did you see that? So I'm taking the…

Contents