Bindings, Platforms, and Innovation
This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.
Tracking change and innovation in the enterprise software development community
Posted by Abel Avram on Aug 23, 2008 05:31 AM
In this presentation filmed during Agile 2008, David Anderson talks about the history of Agile, the current status of it and his vision for the future. The role of Agile does not stand in just having a practice, but in finding ways to implement the principles contained by the Agile Manifesto.
Watch: Future Directions for Agile (1h 32min).
David presents the paradigms behind the principles of the Agile Manifesto and Lean. He is not content with just doing what the Manifesto says, but he wants to understand why it makes sense doing it. One such example is related to the principle "Working software over comprehensive documentation". In the past, people wanted to document everything ending up with huge amounts of documentation which could not possible be efficiently used. For example, he says that the RUP documentation amounts to 11,000 pages, while the Fujitsu process documentation covers 100,000 pages, all of that in order to create the perfect process. We need to discover processes and practices which do not rely so heavily on documentation.
David discusses a great deal about Lean, Kanban, Real Options, and CMMI, comparing them with Agile. His purpose is to draw attention to other ideas, in an attempt to make the audience aware of other options available to us, so we don't get stuck with some practice, but use new ways to extract more value from the original Agile principles.
5 Ways to Ensure Application Performance
Give-away eBook – Confessions of an IT Manager
The Agile Business Analyst: Skills and Techniques needed for Agile
I liked Anderson's query at the end: when people make proposals to this conference for these new ideas... will we let them in? or not?
Good question.
This is really 4 or 5 presentations in one. Extremely dense and high quality. David explains the real values behind the Agile manifesto (he "modelizes" Agile), compares Agile with Lean, then sells Kanban and finally CMMI. Definitely fine food for thought. I had to listen to it twice to start getting the key messages. Highly recommended presentation for whoever wants to understand where Agile is/should be heading.
Great talk! Would love to work with a David and others to develop these principles, practices, and community and take them to new areas of innovation, leadership and management outside the software practice. Please see a 90% Transcript of David Anderson's Future Directions for Agile.
This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.
This article explores the use of JBoss and jBPM to implement design solutions that effectively address the issue of orchestrating long running activities.
This presentation covers the use of graph databases as an optimal solution for data that is difficult to fit in static tables, rapidly evolving data or data that has a lot of optional attributes.
This session introduces Real Options and shows how it can help in running your project. Real Options is a decision-making process that can be used to manage risk.
This article discusses the use of bindings on services and references (including the instance of non-configured bindings) as the means to implement SCA communications in a Web and SOA environment.
After a short introduction to DSLs, Scott Davis plays with the keyboard showing how to approach the creation of a DSL by typing working snippets of Groovy code that get executed.
IBM Rational and InfoQ present, Scaling Agile with C/ALM, an eBook showing organizations how to become “finely tuned software delivery machines” by enabling team integration and scaling.
Amanda Laucher presents a real life enterprise application written in F#. She shows actual code snippets, explaining design decisions and suggesting how to use some of the F# constructs.
3 comments
Watch Thread Reply