The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Recorded at:
How would you like to view the presentation?
Case Study: IBM's Agile Transformation
18 agile and lean practices for effective software development governance
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
Sorry for my poor english if ever because I'm not english native.
I have really appreciated this Webminar. I've been a Quality Engineer in traditional Industry myself before going into IT and what Don Reinertsen says about the huge difference between the two is really true. This seems common sense for people operationally involved in software development but not always at the management level, that's at least my experience in France where Management is often about managing people not process (which is in the hand of Governance which mostly do not deal with concrete stuffs) and who have some difficulty to just realize that building a software is not exactly like building a product in a factory especially with the rise of so called "Software Factory". I have created an analogy with Fractal Theory to explain that to Managers here translate.google.com/translate?hl=en&sl=fr&...
As for Deming, I don't agree with Don because it's a very huge misunderstanding about what Deming means by system. I have met a friend of Deming who translated 2 of his Books in French 20 years and so I think I can tell I know Deming's spirit nearly first hand.
Don has probably known Deming through the huge misleading theory of Six Sigma or ISO stuff with which Deming did not welcome www.youtube.com/watch?v=GXVgsPxQR54. Deming Philosophy is more about Psychology of People than about Statistical Systems (see direct testimonies of CEOs from both Fortune 500 US and Japan companies from www.youtube.com/watch?v=GHvnIm9UEoQ www.youtube.com/watch?v=mKFGj8sK5R8 www.youtube.com/watch?v=6WeTaLRb-Bs). Continuously training People for excellency of the system is part of his 14 points of Deming Management www.lii.net/deming.html in his book "Out of the Crisis" www.amazon.com/Out-Crisis-W-Edwards-Deming/dp/0...
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
1 comment
Watch Thread Reply