If you have worked in software development for any length of time then you have seen the following scenario, a new software release has just gone live, and shortly after that the clients start complaining that a critical component is no longer working. When the new release fails, operations phone will start ringing most likely late at night. The development team is eventually notified so that they can start firefighting asap. The decision is made to roll back the change almost immediately. After the rollback has been completed by operations, development is tasked with analyzing and fixing the reason for the release failure.
If we are honest and ask ourselves what is being felt at this point from everyone involved, we may not like the answer.
Some are thinking who was the person who developed the piece of code that caused the failure? How Did Quality Assurance miss the bug? Top management is asking for answers. And although processes will look objectively what happened, the finger pointing will begin almost immediately.
Many people inside the organization will start pointing fingers most likely at development and Quality Assurance. What this all means is that the traditional blame game has begun inside the organization.