In the past there have been many great debates:
Now out of this chaos, a new darker dilemma has risen to challenge all who might stand in its way:
“How does the priority column work?”
The company I work for has been growing, and has recently focus a great deal of attention to improving our software estimation process. So far we have been impressed with Joel Spolsky's Painless Software Schedules.
We didn't want to wait until we were finished with the current project we are working on to start. So we took our task list and added it to the document.
The only thing is half of us think priority works one way, and the other half thinks it works the other way. So at the end of the day, we had a task list that was a little confused. It is easily sorted out, but the greater question remains: “How does the priority column work?”
Consider the following:
Task PriorityBlah 2Bleh 1Bluh 3
Which is the most import task: Blah, Bleh, or Bluh?
In one corner you have the “Bigger is better” team. And in the other corner you have the “First things first”.
“Bigger is better” Pros:
“First things first” Pros:
I guess programmers just like to argue over petty things sometimes, because the sides formed almost instantly and everyone's heals dug in on this one.
So do you find yourself, “thrust upon the horns of dilemma” or do you see an easy way out? I'm hoping for a landslide majority so there can be no question to the truth.
Please comment if you'd like to share your thoughts (or save us from each other).