Monday, 28 April 2014

Priority-based project management

So here we have Project 2013, but what do we see:


Exactly, "Hello Windows 3.1"! But why? I remind the same case with having only 16 colors available to style background of a cell until Excel 2007. But, as Joel Spolsky has described, it's intentional. It's a priority-based development: they had this "issue" on the list for years, but got it to be fixed only recently. I suppose that for Project there is the same case.

Is it good or bad? Well, I hope that Microsoft will be capable of finding additional people to fix that minor but disappointing stuff. Certainly, 95% won't notice a problem, but others 5% will, and that can make sense, because those guys/gals are usually early adopters, evangelists and IT decision makers. It's like a debt, but not technical, rather a task-based debt. Sometimes everyone needs to make a cleanup, at least each year before Easter, right? :)