It did not however help to alleviate the confusion of software development. The order from AlphaTech had a much more galvanizing effect on the software aspects of the project, which still was significantly miscalculated as the company reverted to 80-hour work weeks to get the project done. Overall however the project management tools on the Jaguar project did change behaviour over time in that there were greater levels of accountability for performance. As is the case with any new methodologies or approaches to completing work there was also significant resistance to change. This is entirely expected given the fact that many of the engineers had exceptional levels of freedom in the past. 3. What were the unintended consequences of using the project management tools? What lessons should Teradyne take way from the Jaguar project?

The first unintended consequence was the fact that Teradyne just accelerated what they did well and in so doing, further underscored what they struggled with as an organization. Project management tools accentuated their strengths and weaknesses faster than had...

It also illustrates how fundamentally flawed the Teradyne project definition process is for software development. Third, resistance to change was made even stronger by the multitude of metrics the project managers used as many began to openly question their value. Fourth, having Primavera as the enterprise-based project management system producing critical path analysis ten layers deep just shows how drastically the processes had gone to the minutiae rather than strategic levels. These are the lessons learned for the company and the most strategically important is to define a more effective software development methodology and execute to it. The company also realized that software quality assurance programming efficiency is an area that does not equate to product development. Finally the ability to overcome resistance to change needs to happen more from a thorough plan and less from panic to meet a customer order, as what happened with AlphaTech. The bottom line is that project tools are irrelevant if underlying processes are not well defined first.