scrum - Articles explaining anti-AGILE patterns -
The more clients I see, I see that even more bad implementation of the strange herd. Sometimes I just hope that I am misunderstood the basic principles of agile, but as much as I read clearly, I read as clearly what I am really developing, and how it is implemented. .
I'm looking for comics / articles
I personally like this white paper (pdf)
And it is by far the most There are some links to the Scam Alliance below, which do not have an account here, they are cached links, edit
/ P>
This is discussed before and after a lot of observation (articles about ScrumBut and many talks and articles. First by interest Ken Schwaber and Jeff Sutherland)
There are two reasons for this principle, with each set of "smell":
-
No cultural changes - banner Under the blanket, tight and lately, most of the earbers are still old orders and controls, as well as managers still using "point and tell" management techniques (talk to someone and tell them) What should they do and where to end New). Agile will bring a cultural change in this situation, where teams take ownership of the work and manage the technical part while the managers focus on removing the obstacles and driving the entire company / project in the right direction. Where this change is disappearing, then there may be the advantage of the playful methods, even if they are followed.
-
Bad technical practices - Scam does not explicitly say anything about how he can write good, readable codes, how to review and re- Write tests, how to use them after writing them etc. The inclination was made with the notion which is free from the bondage of the command and the waterfall governs the environmental developers that they will work properly. Unfortunately, in many cases they do not do this - in many cases they are not out of self complacency or idleness, but are out of ignorance. It is linked to the fact that many people who develop software have not been educated (formally or otherwise) in basic topics such as algorithms, numerical methods, object modeling etc.
It is worth noting that Ken Schwabber was apparently the only thinker of the drummer who took care of the situation and tried to do something about it. Their answer is improvement in the main Master's education through walking around in depth courses, but also to ensure that the developers should realize that they have to use good technical practices for drums. This is the reason that the curriculum was prepared for developers - both certified scoom developer and professional scrum developer program have been built in an effort to improve the second problem above Ken. Of course, training - regardless of how well prepared and distributed - will not solve it completely, but atleast it shows that Ken recognizes the problem and tries to do something about it
BTW - Ken has published an article on some of the "smell" on his blog: is readable.
Comments
Post a Comment