InfoQ

InfoQ

Presentation

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.

Recorded at:
Recorded at

Technical Lessons Learned Turning the Agile Dials to Eleven

Presented by Craig Smith and Paul King on Oct 30, 2008 Length 00:31:15
Sections
Process & Practices
Topics
Agile ,
Agile Techniques
Tags
agile2008
 

How would you like to view the presentation?

In case you are having issues watching this video, please follow these simple steps to help us investigate the issue:
1. Right click on the video player and select Copy log
2. Paste the copied information in an email to video-issue@infoq.com (clicking this link will fill in the default details in most email clients).
Note: in case your email client hasn't automatically picked up the email subject, please include in your email the URL of the video too.
3. Done.
We will investigate the issue and get back to you as soon as possible. Thanks for helping us improve our site!
Summary
In this presentation filmed during Agile 2008, Craig Smith and Paul King present what happens when one tries to be super Agile. Practically, they employed most currently used Agile practices on several projects, then they experimented with new ideas leading them to better results, increased productivity and quality.

Bio
Paul King has contributed to open source projects and international standards, has won prizes for his research, and is a frequent speaker at international conferences. Paul's special interest areas are Java, Agile development, open source testing tools, XML and Web services, and dynamic languages such as Ruby and Groovy. Craig Smith is a Certified Scrum Master and IT Professional.

About the conference
Agile 2008 is an exciting international industry conference that presents the latest techniques, technologies, attitudes and first-hand experience, from both a management and development perspective, for successful Agile software development.
Resources that were mentioned by Matthew Cooper Posted
Re: Resources that were mentioned by Paul King Posted
  1. Back to top

    Resources that were mentioned

    by Matthew Cooper

    Interesting ideas. I'd be interested in the white paper and the open source projects that were mentioned in the presentation. Any ideas where I can get hold of them?

  2. Back to top

    Re: Resources that were mentioned

    by Paul King

    Hi Matthew,

    Here are some relevant links.

    Some of the IntelliJ plugins we use:
    code.google.com/p/agileplugins/

    BDD-style framework incorporating some of the ideas:
    code.google.com/p/instinct/

    TDD-flavored framework incorporating some of the ideas:
    geekscape.org/daisy/geekscape/g2/128.html

    Groovy now has some of the ideas baked into the language:
    groovy.codehaus.org/

    Agile 2008 conference web site from where you can get the conference proceedings:
    agile2008.org/
    (I couldn't find a link just now but if you contact them I am sure they will give you the details. If you have no luck, get back in touch and I can see what I can do.)

    Cheers, Paul.

Educational Content

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.

Beauty Is in the Eye of the Beholder

Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.

Architecting Visa for Massive Scale and Continuous Innovation

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.