Priority should play some role in how you organize a product backlog
but often times people would like to follow the MoSCoW principle. The
have items that they:
Must do
Should do
Could do and
Would like
Agile teaches us to always do the items of critical nature first,
however, we do not want to restrict ourselves from ever getting to the
features a customer would like to have. In a real world example, two
releases are contained in the same product backlog and are being
worked by the sae development team. One release is winding down with
low to medium priority workitems, the other is just ramping up and has
high pririty work to do.
Those can be mixed in the backlog in order to eet what you have
promised the customer without being restricted by pririty placement.
I hope this helps!
Regards,
V. Lee Henson CST (The Narrator on the Video)
VersionOne Trainer / Certified Agile Enthusiast
http://agiledad.blogspot.com