tspsymposium2014

We began implementing TSP across NAVAIR in 1996, first with PSP training and then TSP team coaching in 1998. By 2005 some members of our organizations began to ask, “Can we apply this successful approach to our other projects?” Our response was a resounding YES that ran squarely into non-software teams saying, “We don’t do software.” Our conclusion was that the “S” (in TSP) had to go!

By this time, the SW-CMM had evolved to the CMMI designed to be best practices for all kinds of software/system development and maintenance. Certainly the maxim Plan the Work–Work the Plan–Collect the Data–Report the Status made sense to all sorts of teams doing software, systems, requirements, and testing. In 2006 NAVAIR and the SEI collaborated in the development of processes, training, and tools to launch a set of teams doing software, system requirements, lab support, and CM/DM support. From those experiences, we arrived where we are today, applying something we call Team Process Integration (TPI).

This TPI half-day tutorial will focus on the steps that any technical team must go through to learn and apply personal and team process. This includes learning the fundamentals of what a process is, defining their own widget processes, and learning the fundamentals of estimating and quality, the steps of a detailed planning session (launch), project operations, weekly communications, and finally a tool to automate the combined TPI project management and team product processes.

This presentation will demonstrate NAVAIR’s top-level approach to the relationship between product processes, the data collected and used during development, and how the data is used to analyze the quality of the product. It will also include a discussion of the process for future improvement.