The 3rd Agile Gathering was conducted by Agile Ukraine in Kyiv on 9/10. I was participating as humble developer from our team listening to people who have already achievements (or at least pretended to have) in implementing agile technologies.
Being a participant of previous two gatherings I feel some remarkable symptoms, which probably may cause me to review agile technologies in different manner.
Organization crew strongly wants to sell certifications. So, they encourage everybody to become SCRUM certificated master (SCM), to have affiliation of the international agile community. Then you probably gain SCRUM Certificated practitioner. And the third stage of that is to become SCRUM Certificated trainer to be able to provide certification for other people. Capacities are growing: soon one more battalion of SCMs will appear in Kyiv. IMHO, it rather makes SCM devalued than increase percentage of successive projects, but let's see it together in the future.
Reporters lean to tell about their projects and how effective they are with agile. That's great, but why main accent is made "How to make your business applied for agile"? They prefer to answer question: "What kind of project should you manage to implement agile?", not "How to apply agile on some project?":
- How about deadlines? How can you check if you are meeting deadline or not, implied from your estimations?
- We do not operate with term "deadline". We have workflow, sprint, backlog, but do not use deadlines.
Well done. Thanks! Only challenge is to find such brave customer, that doesn't care about deadlines!
As for me, it's pathetic point of view: instead of appling process to business, let's make your business applied to the process. Bringing business to agile is even more ridiculous thing then bringing agile to agile software tool.
Accordingly to report of Adam Byrtek about his company Codesprinters agile techologies can be applied for small teams developing web-based solution on languages like Python. Unfortunatelly, that doesn't impress me much, because I can't drive out requirement of my customer and say: "Dear sirs, instead of delivering desktop client-server application based on Win32, we offer you web portal developed in Java".
Indeed, the most crucial thing is how to convert methodology to something worth to decision making people: would it be customer, headmaster, sales or owner you should represent your approach in his values.
I remember very remarkable book Critical Testing Processes by Rex Black. It impressed me very much because author managed to convert his technology to business benefits. Actually this is essential point of his thinking. Look at the first frame of his presentation here: his approach serves to save money. His listers don't even think what business values will be spent on implementation such QA-driven development. Because his approach is business value itself!
I can see community is progressing comparatively with last year: among people bedazzled with some extra-special-new-super-cool methodology appears essential community of pragmatic specialists, who will probably reenforce agile stronghold. Askhat Urazbaev from Luxsoft Moscow emphasized that agile is implemented not for agile, but to make project successful (in the meaning of business). I strongly belive in that and I also believe that agile will make software industry more successful, but for now I didn't get any good ideas how to make agile benefits evident for business. And this is very disappointing ...