From the course: Agile Product Owner Role: Techniques

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Forced ranking prioritization

Forced ranking prioritization

From the course: Agile Product Owner Role: Techniques

Start my 1-month free trial

Forced ranking prioritization

“

- Effective teams and product owners know what their number one and number two priorities are, along with three, four, and five. Their items are ranked. I don't advocate for ranking all of the items in a backlog, but for sure the top 10 priorities in the near future, and top 10 conceptual items that are further out. These should all be known and visible to the team. In our funnel-shaped backlog, this means that we have 10 smaller items of top priority, and 10 items further out that we have yet to be broken down into smaller items. I don't want to rank hundreds of items. That's just too difficult, and quite frankly a waste of time. Priorities change easily, and we want prioritization to be as clean and easy as possible. Stakeholders will have endless battles of their own with priorities, and it's often difficult to figure out what's behind the conflict. Ultimately, we need to align to the business priorities and strategic alignment. One way to get to the top 10 either detailed or…

Contents