Basic Agile principles can be fully applied in highly professional teams only, when you have no problems with competencies and commitment. "People over processes" principle works only when people know what to do without much coaching. Only professional has skills and expirience to own the problem, commit into it, choose right tools/methodics from his portfollio, find optimal solution himself. Only professional has built-in internal "common sence" that is required to be agile and "self organized".
As soon as team is not skilled enouth you have no choice but setup a PROCESS to secure some level of success in the project and make success repeatable.
It seems to me that many cases when organization tries to go "agile" but do "traditional" instead is about people that are not skilled enougth. Often they do understand princeples and practices, but can't follow them just because people need more precise guidance.
"Disciplined agile" term is just about that. Professional developer is disciplined by nature, he/she don't need additional quidance to be "disciplined". For less skilled team you need to define "minimum precess requirements", "required practices" etc. but this is already not agile, you put process over people!
This is just as in any art you have to learn basics first in order to become a Master. Agility is for Masters.
The main goal of "Scrum Master" is to train "masters" that can be "self-organized". unfortunatelly it is rarely possible to do in a resonable timeframe with the "random" team. Team has to be formed already with this goal in mind: talanted people, not jouniors.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment