The 12 days after GA
It’s that time of year, so here’s a software industry adaptation of a familiar holiday song.
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
Related posts:
- Worth Repeating: 12 Days After GA
- Gilbert and Sullivan present: The High-Tech Product Manager
- Case Study – First 30 days into a New Role
nice! I could also sing a song about this
[...] The 12 Days after GA Possibly related posts: (automatically generated)How much customer “capital” have you earned?Presentation skills – do you care about your customer needs?Quick impressions from MMS ‘07Daily gear deal – 40% off select SeV products [...]
[...] The 12 days after GA [...]
[...] 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 [...]
Thomas,
Thanks. Any suggested changes or new lines for this song?