When prioritizing a Product Backlog, traditional practice is to rank your items by priority levels P1, P2 & P3, and then tackle as many P1s items simultaneously, by distributing your engineering resources. However, if you use the Forced Ranking approach, as described by Scrum, you might find that by resolving just one P1 item, the priorities of the other P1 items change. I have found this to be true from my own Product Management practices!
arjuniyengar11
Comments