Leading Change from the QA team
Most efforts to request or implement changes fail. They fail often enough that the “change curve” for organization change is derived from the grieving process when a loved-one dies. Shock, denial, anger, and fear are experienced before the organization starts accepting the change and committing to it. These change efforts fail somewhere between shock and fear.
Yet, the opportunity for change is large, especially when it comes to quality. We all know that preventing bugs is better than finding them. We also know that finding bugs earlier is better than finding them late. Since testing is often done late in the development cycle, when we want to drive a change it usually involves asking other teams to change their behavior.
In this session, I will show you a 4-step process for leading change, and illustrate the process with several examples of successful process changes that lead to better quality and testing. Included with the 4-step process will be a variety of tools which have proven very useful in influencing those teams outside of your direct control.
- Build the case for change.
- Plan the change.
- Test the change.
- Rollout and make adjustments.
Included with each of these steps will be a number of tools, methods, and examples to successfully implement the change.
About our speaker: John Ruberto has been developing software in a variety of roles for 30 years. He has held positions ranging from development and test engineer to project, development, and quality manager. He has experience in Aerospace, Telecommunications, and Consumer software industries. Currently, he is a Director of Quality Engineering at Concur. He received a B.S. in Computer and Electrical Engineering from Purdue University, an M.S. in Computer Science from Washington University, and an MBA from San Jose State University.