After a long break, some gyan for my brethren ....
Theorem :1 Last minute issues irrespective of quality of planning.
It is not possible to release a software product without any last minute nasty surprises and slogging irrespective of how meticulously it was planned.
n(Release of software product without last minute issues) = 0
Corollary:
Last minute issues are not related to the quality of the planning done.
n (Last minute issues) = 1
Theorem 2 : Law of Criticality
The number of non-technical issues is a result of the criticality of the situation. The factor that determines the number of issues is directly derived from the criticality of the release to the team.
n(Non-technical issues) (X Criticality of the situation.
Non-technical issues := Lab outages, facility shutdown, long weekends etc...
Corollary:
Everything will work fine when the project starts and will not work when it is about to end.
n(issues at the start) = 0
n(issues at end of cycle) = (X)
Theorem 3: Law of Voting
If any group (QA, QE, Dev, Management, Rel Team, Marketing) has the option of casting a -ve vote, it will!
Corollary:
Number of votes that are cast for release is always less than the total possible votes.
n(Votes for release) < n (total votes possible)
Theorem 4: Arriving at Quorom
The number of iterations it takes to arrive at quorum is directly proportional to the number of votes possible.
n(Iterations it takes for quorum) (X n(Possible votes)
Corollary
To avoid multiple iterations, keep the number of voters small. aka too many cooks spoil the broth.
Theorem 5: Law of Satisfaction and Sense of Achievement
The sense of achievement and satisfaction is greatest when more number of unexpected hurdles are overcome.
Satisfaction when release doesn't have issues = ΓΈ
Corollary
A software product release without hurdles is worthless!
What say?