The other day I attended a meeting where the main topic was Agile process standardization. During the last 9 years of working with Scrum in particular and Agile in general, I’ve been constantly struggling to understand why certain people think such thing as a fully standardized Agile process has right to exist. Of course on the meeting in the end we agreed that this kind of thing should somehow happen, but that was pure diplomacy on my end (why hurt people’s feelings if they are so obsessed).
See Henrik Kniberg’s illustration for example: http://blog.crisp.se/wp-content/uploads/2014/09/Screen-Shot-2014-09-15-at-13.58.35.png
So here’s my question (or you may call it a research challenge for software engineering methodology scientists if you wish): Is there a way to figure out where to draw the slider regarding these dimensions? In a certain situation, should we do detailed estimations or not? Does sprint planning make sense or we should just kanban our tasks? Should we have more of written specifications or we should have more meetings to clarify what needs to be done? Should we scream to management telling that wanting a detailed plan for the next half year and at the same time always interrupt the team is plain schizophrenia, or just let things flow and let our survival instincts solve the problem? Should we let developers just do things their way (often ending up in perfectionist procrastination) or be pushier (and then see the motivation of the kings of today’s world deteriorate in an instant)?
These daily decisions may depend on many things of course, the main ones probably being actual project situation, company culture and individual people being involved. My theory is that always individual people win, but this is just a highly subjective idea.
So all the people who believe measuring this kind of stuff, come and convince me!