My Scrum of Scrums has
Become something other than
What I want it to be

It should be simply
A coming together of
Technical people

Instead it becomes
Like a management review
I lieu of sharing

What did you do since?
What will you do until we?
Is something blocking you?

OK kids. The game is over. There are no more invites left. Here are the last two winners:

Sachi:

Three people submitted Haiku and didn't get an invite from me (because I ran out). Well you guys are in luck! A couple of kind folks have volunteered their invitations for you guys. I'm going to be disconnected until the weekend though, so hang in there and I'll get you guys invited then.

Well that didn't take long. Yesterday I received three and then today got seven more. And all of them are cool in one way or another. Thanks so much to everyone who participated.

Unfortunately, I only have six invites to give away, so I had two choices: the first six recieved, or the best six (as judged by me).

To be fair, I decided to go with first six. Sorry to those of you who were too late. When/if I get more invites, we will play again. Stay tuned.

Here are the six winners in the order they were received. (If you see your name here, you should get your GMail invite shortly.)

1. Jeremiah Johnson:

more test coverage:
dependency injection
for less spring cleaning

2. Scott C. Reynolds:

Error has occurred.
We won't tell you where, or why...
Lazy Programmers.

3. David Yack:

I've got six invites to give away. To get one, please send me a technology-oriented haiku.

Please submit your poem via my contact form I will post the winners and their poems in a day or so.

UPDATE: The game is over. There are no more invites. Sorry.

There's too much to do
And not nearly enough time
To get it all done

I haven't posted a Haiku in a while.

Test, Code, Refactor...
Repeat until you are done.
Is it that easy?

Some say it isn't.
That you can't skip the design.
They can't stop asking...

"How can it be that
Emergent design will work?
Where's the architect?"

Architects are there.
Writing tests and writing code.
Over and over.

But they let the code
Tell them what the design is.
They just listen well.

The meeting goes on
The customer talks and talks
He says not a thing

Some of it I write
Some comes from other places
I blog it the same

About trying to balance writing my own stuff (on my wiki for now) and keeping up with my news aggregator.

The code talks to me
Teaching me how it should look
Explains what to do

A little poem about what it feels like to do test-driven-development and coding-by-intention.