JavaZone 2009 - Unconscious Taylorism - Why Old Thinking Hinders Agile Adoption
- Why do we separate Java and .Net developers?
- Why do system architects choose frameworks and write UML diagrams but do not write any code?
- Why do we measure how many lines of code a developer writes?
- Why is agile adoption in traditional organizations hard?
The theories of Frederick Taylor and those that followed today still sets the norm for how organizations are managed. What we see as normal and common ways to organize work is in fact making agile adoption difficult, hindering empirical processes and self organizing teams. The talk points these patterns and their effects and shows how to avoid the to not miss the benefits of an agile development process.
Marcus Ahnve
Marcus Ahnve heads the Stockholm office of ThoughtWorks, a global IT consultancy aiming to revolutionize the IT industry and the way software is delivered. He specializes in agile methodologies and web development.
Marcus experience with agile development dates back to 1996 and his first professional project which was done is Smalltalk. In 2001 he got hooked on XP and has since then explored new ways to make development more effective, valuable and fun. Marcus is one of the founders of the conference Agila Sverige which is held yearly in Stockholm.