Comments on: Agile software development, the principles. Principle 11: The best architectures, requirements, and designs emerge from self-organizing teams. http://technology.amis.nl/2009/12/14/agile-software-principle-11/?utm_source=rss&utm_medium=rss&utm_campaign=agile-software-principle-11 Tue, 11 Jun 2013 22:09:58 +0000 hourly 1 http://wordpress.org/?v=3.5.1 By: Lucas Jellema http://technology.amis.nl/2009/12/14/agile-software-principle-11/#comment-6072 Lucas Jellema Tue, 15 Dec 2009 07:06:21 +0000 http://technology.amis.nl/blog/?p=6724#comment-6072 This is an interesting article. The focus on the responsibility of the team makes a lot of sense. The composition of the team is intriging. I quote from your article: “The team members must be able to cover all aspects of systems development. ” ; when is that the case? How do you determine that? How do you know you can handle all challenges you will encounter? Won’t that involve specialists – depending of course on your definition of specialist? If not – won’t you run the risk of arriving at inferior, incomplete, wanting solutions that will be hard to maintain? Do you bring in specialists from outside the team to verify the solutions created by the non-specialist team? Or is the result of the team judged only on functionality and (short-term) customer satisfaction?

I may sound criticial. To be clear: I am currently involved in an agile project, based on the Scrum method, and compared to our earlier approach, it works miracles. However, the role of specialists is not downplayed as much as you seem to be doing.

best regards,

Lucas

]]>