InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Presentation: Future Directions for Agile

Posted by Abel Avram on Aug 23, 2008

Sections
Process & Practices,
Architecture & Design
Topics
Delivering Value ,
Agile in the Enterprise ,
Agile
Tags
Agile Manifesto ,
CMM/CMMI ,
agile2008 ,
Lean ,
Behavior Driven Development ,
Kanban

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.

  • This article is part of a featured topic series on Agile
Will we let Agile develop? by Deborah Hartmann Posted
Wow! by Olivier Gourment Posted
Transcript of Future Directions for Agile by Martien van Steenbergen Posted
  1. Back to top

    Will we let Agile develop?

    by Deborah Hartmann

    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.

  2. Back to top

    Wow!

    by Olivier Gourment

    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.

  3. Back to top

    Transcript of Future Directions for Agile

    by Martien van Steenbergen

    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.

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

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.

10 tips on how to prevent business value risk

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.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

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.