I Was a Strange Loop

Best part of fall 2009 in St. Louis? The two day geek rapture that occurred during Strange Loop 2009. I went to that very first one last year on my own dime, and it was a tremendously worthwhile experience. Good networking, lots of new approaches to software development, and lots of cutting-edge research and methodologies.

For two glorious days I rode my bike from my University City home, down 5 blocks to my favorite theatre, the classy Tivoli, and nerded out.

New languages that were self-proclaimed of questionable utility (humility is refreshing).
Ad Reinhardt by al3x

Simplicity (al3x, formerly of Twitter, gave one of the most thoughtful and grounded conceptual discussion I’ve ever attended, including my years attending academic philosophy conferences).
simplicity by al3x

Awesome slides.
jquery slide by rhyolight

The open bar at Blueberry Hill and Strange Passions night were thoroughly enjoyable from both an academic and bacchanalian perspective.

Of course, you should have seen the shill approaching. Strange Loop 2010 promises to be bigger and better. Register today for $150, rock out in STL (I’ll even show you around if you’re out of town), and enjoy FREAKING GUY STEELE AND DOUGLAS CROCKFORD!!!1!!!!1

Seriously, this was by far the best conference I’ve ever been to, blocks from my house, and tickled multiple parts of my lobes.

August 6th, 2010 | .NET, Discipline, Intelligence, IT, Software, St. Louis, Technology | 12 comments

Lessons in Scrum: Sneak Previews and Test Screenings

We’ve been trying to use Scrum to manage our software development for the last six months. It’s work as far as we have let it (or as far as others let it), and I’m slowly clueing in to what should raise red flags in my Scrummified brain.

Recently the customer (chicken!) requested to schedule a couple of demos over the course of a sprint. I became very concerned.

Giving the customer demos at the sprint mid-point will encourages the customer to give feedback with the expectation of immediate implementation and delivery by the end of the sprint. We cannot sustainably support that. If the customer really wants a peek into what is coming in the next sprint delivery, then perhaps a demo at the end of the sprint development and before the testing and production deployment would work.

To borrow a movie analogy, we must maintain the difference between a test screening, and a sneak preview. The test screening, when a movie is shown for a small audience who gives feedback, is used when the movie is still being made. The sneak preview, when a film that is finished is shown before it is distributed, is used to generate excitement and approval for the finished movie.

In Scrum, a test screening should occur after a delivery & during planning for the next sprint. That is the time for customer feedback that results in products implemented in a sprint. A sneak preview should occur during a sprint in order to consolidate customer buy-in and get them excited about what is coming.

I want to make sure that the demo schedule during a sprint is a sneak preview and not a test screening.

March 30th, 2008 | Discipline, Scrum, Transparency | No comments