When the big bosses breaks the news of the latest project’s target release date to the team, everyone’s adrenaline level rises. Immediately people become attentive because they find out what they need to focus on for the next several days and, consequently, they learn that there is a need to hurry. Often, by this time, programmers can’t wait to start working on the swamp of reported bugs. Software testers, meanwhile, start to feel the huge boulder of testing work that’s up ahead, wanting to make sure that every feature in the application is working as planned. The announcement gets into each person’s nerves, blood pumping much faster than normal. People are up on their toes to beat the deadline.
This is often how software release updates are thrown into production servers: where people are more likely than not rushed to their wits end, where there is less planning but so many expectations, where developers are bombarded with issues to eradicate and where the software tester tends to miss doing several test cases in the list, where the actors are not asked about their capacity to deliver successfully, where everyone’s energy is drained in the end.
The team beats the deadline at the expense of many other small (but rather very important) things.