From: Dilbert comic strip for 11/01/2009 from the official Dilbert comic strips archive.
This is why there is no such thing as a 5-minute change. Here's the real sequence of events for your "5-minute" change:
- Somebody finds that a 5-minute change needs to be performed. 5 minutes.
- Somebody asks for authorization to make the 5-minute change. 5 minutes assuming the explanation is simple.
- Somebody needs to be selected to make the 5-minute change. 5 minutes if the work schedules are clear and up to date.
- Somebody needs to explain the programmer the 5-minute change. Good luck explaining it in less than 10 minutes.
- The programmer makes a change. 5 minutes.
- Quality assurance checks the work. 5 minutes but it has a mistake.
- The programmer fixes the mistake. 5 minutes.
- Quality Assurance re-tests. 5 minutes.
- Work is deployed to testing environment. 5 minutes.
- Customer tests the change. 5 minutes. Luckily, he likes it as delivered. Staging is approved.
- Deployment to staging environment for regression testing. 5 minutes.
- Quality Assurance does internal regression testing. 5 minutes (in your dreams).
- Customer does regression testing. 5 minutes (yeah, right). It passes, approved to deploy to production.
- Work is deployed to production, assuming no outage is needed. 5 minutes.
- Quality Assurance checks the production environment. 5 minutes.
- Customer does production acceptance testing. 5 minutes.
Your "5-minute" task is going to burn at least 305 minutes of billable work, OVER FIVE HOURS OF WORK.
It gets better, this process includes all players getting copied in all emails, so in reality that 5-minute task probably eats a few more hours, just based on all of the people that will be reading those 15 emails.
Isn't project management awesome?