We have one called the "three times" rule. A software or web site enhancement has to be requested a _minimum_ of three times before any actual work is begun.
In practice it goes a little like this: The first time, you can just nod your head and not really listen. It could be a job that takes 5 minutes or 5 months, but it doesn't matter, because it's not likely to ever actually happen. The second time it's permitted to give actual thought to the request. State whether it's doable, give a vague time estimate, but don't even consider doing any real design work and God help you if you start any coding. The third time, it's ok to start the work, but giving it a high priority usually isn't wise. If a fourth or fifth request come in then consider the project to be real. Needless to say, things are fairly informal around here. The boss commonly gets a wild hair and asks for some random software or web site change. In the past I've forgotten the rule and whipped out a solution in a couple of hours, only to have it never put into production in a live web site or software system. Now, nine times out of ten, the original request is forgotten within a few days. If a second request comes in then there's still a better than even chance that it will eventually be forgotten. ----- Original Message ----- From: "Bryan Stevenson" <[EMAIL PROTECTED]> To: "CF-Talk" <[email protected]> Sent: Wednesday, August 03, 2005 7:15 PM Subject: OT: 15 minute rule > Hey All, > > Around Electric Edge we have something called "The 15 Minute Rule". I'm > not sure if this is a common sort of rule, but it sure does help keep > development moving ;-) > > When the rule applies: > > You've been staring at the same error or unexpected output and you've > exhausted your arsenal of coding kung fu and still can't get it sorted. > Around Electric Edge we then call out "I'd like to invoke the 15 Minute > Rule!". At this pooint any available developers will come over so you > can share your heartache over this mysterious situation you just can't > solve. One of them barely glances at your code and says "You spelled > that var name wrong" (you know....the one you double checked 25 times > becuase it was a var undefined error) and wanders back to his/her desk > leaving your jaw on the floor. > > Although techies asking for help is often like guys asking for > directions, it does solve those "stupid" issues but quick ;-) > > Anyways...just figured other teams may have similar "rules"?? > > I often use this list as my "15 minute rule"....hehe ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:213695 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
