Menu
What's stack rank mean for a work item in Team Foundation Server 2010? Is it a user characteristic of some kind?
738
Stacked ranking is an employee evaluation method that slots a certain percentage of employees into each of several levels of performance. Because the ranking is inherently somewhat arbitrary, the model is also sometimes referred to as a forced distribution.
Stack ranking is a pretty simple system. Every manager ranks their employees into buckets of a certain size. X percent are top performers, Y percent are the next tier down, and so on. On a team of 15 people, there might be three top tier slots, eight middle tier slots, and four bottom tier slots.
Stack Ranking (forced ranking) is a prioritization technique which involves taking a list of options (ideas, problems, stories, etc.) and ordering them along an axis according to a single criterion (e.g. value, importance, cost, complexity, risk, etc.)
In most cases priority and stack rank are aligned i.e. on average higher priority items will have lower/earlier rank... BUT
Stack Rank is not priority. It is just the order in which your team will work i.e. Rank 1 is the item on which your team will work first, Rank 2 is the second and so on...
so when does a lower priority item get an earlier/lower rank..
Example 1 Let's say you choose 3 bugs to fix in the current iteration.. 1 is high priority and 2 are medium priority.. but, lets assume, fixing one of the medium priority bug means regression testing.. so you will like to fix it at the earliest so that regression effects are visible at the earliest..
Example 2 a higher priority item needs more info before you can start working on it.. so you will keep its priority high but will move some lower priority item to earlier rank so that your team can continue working...
172
It assigns a priority to a requirement.
40
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
