Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
kamen327569dAre these ordered by importance?
We use pie scoring (potential/impact/ease), so a task is rated based on much it improves the product, how many people would be positively affected by the change, and how difficult the change is to implement.
We use Scrum story points for "ease", those are decided upon by devs + Scrum Master.
The other two values are assigned by product owner + stake holders.
Then you just multiply the numbers, sort from high to low, and fill up a two-week sprint based on the average team velocity.
In case of incidents, then sprint can be adjusted, but the person breaking our cadence is then responsible for informing the other stake holders why his/her incident had such a sudden priority change.
Devs don't do anything other than grab the next task from the top of the stack — although some minor shuffling is allowed to accommodate for specialisms and personal preferences.
lyxsus2468dIt's easy :)
1. I Need That Now – like right now, right?
2. ASAP – the soonest possible after now
3. Urgent – now we can deal with urgent problems
4. Rush – nobody will die because of it just yet, but you'd better rush, things can change
5. Priority – the most important among important
6. Important – because they won't ask you to do anything that's not important
But really, there should be just 2 separated scopes of priority levels never to be mixed up.
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job
M-Arcus18Never let customers define the priority levels. It will end in: - Normal (never used) - High (used for small...
dvncoder183Something I ensure stays on the whiteboard at my company 24/7
k0pernikus13Manager: The thing you working on. We need this now! Like end of the week. Me: Desirability is not do-ability...