Because the rank is what determines what you need to be pulling into the next sprint. It encourages iterative development because you can draw in what you need to do based on all the data,not just one aspect of it. You might think ranking by age or priority are useful. They can be, but only when you start out with a new backlog. They're not a lot of use once you start to work iteratively, and they're certainly no good on their own. If you sort by age or priority, you simply can't account for dependencies or other work. If, for example ABC-234 is urgent, but ABC-123 is trivial, the priority is fine. Until you realise you can't do ABC-234 until ABC-123 is complete. The way around broken sort orders like that - rank them.
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG