Agile, Relevance Style

The Agile Manifesto, like any good scripture, admits of many interpretations. There is no one “right path.” What works for us may not work for you. At Relevance we have tried many paths, and learned many lessons. Join us to see dozens of ideas that have worked for us, plus some that haven't.

The Agile Manifesto states four key values:

• Individuals and interactions over processes and tools.
• Working software over comprehensive documentation.
• Customer collaboration over contract negotiation.
• Responding to change over following a plan.

That manifesto sounds great, but perhaps a little vague. It gets more concrete quickly when you start doing it! In this talk, we will share our experiences, both good and bad, with various practices and problems associated with agile:

• Pairing all the time (except when we don’t)
• Running cross-project retrospectives
• Code coverage standards
• Choosing the sharpest tools
• Fixed-bid projects
• Handling budget problems
• Teaching customers
• Setting the wrong kinds of targets
• Holding all participants accountable
• Forking everything
• Introducing new technologies

Hold on tight to your sacred cows, because no assumption you have about agile will be safe.

About Stuart Halloway

Stuart Halloway is a founder and President of Cognitect, Inc. (www.cognitect.com). He is a Clojure committer, and a developer of the Datomic database.

Stuart has spoken at a variety of industry events, including StrangeLoop, Clojure/conj, EuroClojure, ClojureWest, SpeakerConf, QCon, GOTO, OSCON, RailsConf, RubyConf, JavaOne, and NFJS.

Stuart has written a number of books and technical articles. Of these, he is most proud of Programming Clojure.

Learn more about Stu's presentations on his wiki.

More About Stuart »