[teampractices] how to mark tasks as high, but not immediate, priority
Rob Lanphier
robla at wikimedia.org
Mon Feb 9 19:18:28 UTC 2015
On Mon, Feb 9, 2015 at 10:00 AM, S Page <spage at wikimedia.org> wrote:
> Leave it Normal priority but move the task near the top of its column in the
> backlog or next sprint workboard.
I agree with this. For what it's worth, I think "Low" and "Needs
Volunteer" priority are severely underutilized. "Normal" should mean
"this is important enough to explicitly revisit at every sprint
planning meeting, or at least every quarter". If it's not important
enough for that level of fussing, then it seems to be low priority and
should be marked as such.
Rob
More information about the teampractices
mailing list