Originally published at Paul Henman at henman.ca. You can comment here or there.
How do you identify a high priority task? I like this answer, found on Merlin Mann’s website:
In Scrum we tend to see tasks (the work breakdown that a team deemed necessary in order to deliver a Story or feature) as equal priority because they all need to be completed in order to say we’re Done.
However Scrum also has the concept of a Product Backlog, which is a prioritised list of Stories (or features) which the Product Owner manages; planning for each Sprint (iteration) begins with the Product Owner describing the top priority Stories.
So maybe this card should say “How do you identify a high priority Story? It’s Done.”