Worth Repeating: 12 Days After GA

0saves

snowflakes

It’s that time of year. This was originally posted almost exactly 2 years ago. I tried to come up with a new seasonal spoof — I may still yet — but in the mean time, here’s one to tide you over.

—–

On the first day after GA, my team reported to me:

A bug in the installer.

On the second day after GA, my team reported to me:

Two corrupt downloads
And a bug in the installer.

On the third day after GA, my team reported to me:

Three evals pending,
Two corrupt downloads
And a bug in the installer.

On the fourth day after GA, my team reported to me:

Four angry prospects,
Three evals pending,
Two corrupt downloads
And a bug in the installer.

On the fifth day after GA, my team reported to me:

Five suspect leads,
Four angry prospects,
Three evals pending,
Two corrupt downloads
And a bug in the installer.

On the sixth day after GA, my team reported to me:

Six critical patches
Five suspect leads
Four angry prospects
Three evals pending
Two corrupt downloads
And a bug in the installer.

On the seventh day after GA, my team reported to me:

Seven production crashes
Six critical patches
Five suspect leads
Four angry prospects
Three evals pending
Two corrupt downloads
And a bug in the installer.

On the eighth day after GA, my team reported to me:

Eight proofs of concept
Seven production crashes
Six critical patches
Five suspect leads
Four angry prospects
Three evals pending
Two corrupt downloads
And a bug in the installer.

On the ninth day after GA, my team reported to me:

Nine sales reps selling
Eight proofs of concept
Seven production crashes
Six critical patches
Five suspect leads
Four angry prospects
Three evals pending
Two corrupt downloads
And a bug in the installer.

On the tenth day after GA, my team reported to me:

Ten new requirements
Nine sales reps selling
Eight proofs of concept
Seven production crashes
Six critical patches
Five suspect leads
Four angry prospects
Three evals pending
Two corrupt downloads
And a bug in the installer.

On the eleventh day after GA, my team reported to me:

Eleven requests for info
Ten new requirements
Nine sales reps selling
Eight proofs of concept
Seven production crashes
Six critical patches
Five suspect leads
Four angry prospects
Three evals pending
Two corrupt downloads
And a bug in the installer.

On the twelfth day after GA, my team reported to me:

Twelve deals a pending
Eleven requests for info
Ten new requirements
Nine sales reps selling
Eight proofs of concept
Seven production crashes
Six critical patches
Five suspect leads
Four angry prospects
Three evals pending
Two corrupt downloads
And a bug in the installer.

Saeed

P.S. Check out another version of this song – The Twelve Days before my PM Christmas — on Outside-In View blog. Saw it after I originally (re)posted my own.

Related Posts Plugin for WordPress, Blogger...
If you enjoyed this post, please consider leaving a comment or subscribing to the RSS feed to have future articles delivered to your feed reader.

Related posts:

  1. The 12 days after GA
  2. Worth Repeating: The High-Tech Product Manager
  3. Worth Repeating: Devil’s Dictionary for High Tech
  4. Worth Repeating: Rules of the Product Management Jedi
  5. Worth Repeating: Do Product Managers need Domain Knowledge?
2 Responses to Worth Repeating: 12 Days After GA
  1. Worth Repeating: The 12 Days after GA – http://wp.me/pXBON-1UT #prodmgmt #prodmktg #humour

  2. Worth Repeating: 12 Days After GA: http://saf.li/c8zRI

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>