Or, "does the process matter more than the work?"
Maybe I've been in my isolated little work world for too long, where I've had to wear lots of hats, and for the most part, teach myself everything I've needed to know, and just get things done. But apparently that's not important these days. These days, you need to GTD. And agility in your process is not enough, you have to be Agile, and Scrum.
What's all this? Well it seems to me that the process of how work is done, especially software development work, is more important to some people than the work itself.
I've been dismissed from interviews because I couldn't describe the Scrum process, yet I've worked iteratively on software projects, delivered features on deadline, and added features over time. Hmm.
I've read job requirements that include "Must follow GTD process and be Agile". Hmm.
I've watched 'professional developers' fritter away time and money talking about their code sprints while not actually delivering any product (or even product components). Hmm.
I guess it all looks good on a resume, and I may be naive, but when did concentrating time and energy (and money!) on the process become more important than concentrating on building the product/service? When did buzzword compliance become the key criteria for evaluating employee potential?
Where do you draw the line between the effort you spend on organizing your time and the effort you spend actually moving work forward?
Flame me if you must.