Has it been two weeks already?

Mark Levison produces our latest edition

Great job, Mark!

Welcome to the June 7th Carnival of the Agilists. Today’s theme is: There is no theme.

• Software Insurance? Are you mad? Laurent Bossavit provides the precedent.
• Glen Alleman lays out some examples of non-software applications of Agile Development techniques.

• Is delivering on time a synonym for success? Jason Gorman feels otherwise.
• Wil Shipley prefers to be agile by being inflexible. A contradiction in terms?
• Do you have a sticky buddy? David Anderson things you should.

• All of us are smarter than any of us. Mike Griffith provides the do’s and dont’s of team problem solving.
• Dave Churchville suggests ways to be agile in a distributed development environment. Maybe he needs a sticky buddy.
• Ten New Rules for Project Managers - but I bet they won’t all seem new to you!

• Jason Gorman asks Is the Agile Community a Clique? Just for that, I’m not inviting him to the secret Agilist Beach Party.
• Alan Shalloway is contemplating Why Scrum Works.

New Submitters:

• Alexey says “Thing Bigger, Think Agile Product Management“
• “To Be, Or Not To Be… Agile” - That is Basil Vandegriend’s question.

New Group Blogs

• The Agile Practitioner’s Blog

Resources

• A colorful and well-rounded Scrum Reference Card - from Contrado Solutions.

Books

• James Shore’s agile book is done, it’s just not done done.
• Johanna Rothman’s book, Manage It! is, however, done done.

Next Edition

• The next edition of the carnival will be on June 21st. I’ll fill in the URL here _________ when I find it.

Submissions

• Want to be included in the carnival? You’re more likely to get noticed if you send a link to your posts to agilists.carnival@gmail.com.

Add your Voice

• Think we’re a bunch of yahoos, and you could do this whole Carnival thing a thousand times better? Let us know, and you’ll get the chance to produce your own edition of the Carnival.

Harry Pierson says:

Yet, I get the feeling that the REST community would consider a solution that uses the REST architectural style but not HTTP and/or URI as “not RESTful”.

In general, I suspect that the community might balk.   But I happen to believe that a resource-oriented communications protocol should be implementation independent.   One should be able to implement a RESTful protocol in just about any messaging system.

You can do this in Ruby, and there is some argument whether it is a good thing to be able to do (in terms of readability, comprehensibility).  You can override an existing method w/your own   (I forget what the term is, right now, mainly because I never use it).  Ruby on Rails takes full advantage of this.

Apparently, you can do the same thing in Flex, for the internal functions/capabilities of the MX Controls.

Void where prohibited, your mileage may vary, etc.