23 August 1994, Version 0.1 Action Team Description 1.0 Purpose To define the organization, function, and plan of operation of the Software Process Improvement (SPI) Action Teams within our organization. To define the role and relationships of the Quality Steering Team (QST), SPI Quality Improvement Team (QIT), and the SPI Action Teams. 2.0 Policy The SPI process is an approach that recognizes the individual team member as a person anxious to participate in and contribute to decisions affecting his or her own work. The SPI concept provides a process for all levels of the organization to work together as a team to provide a high standard of work life and higher quality software products. The QST endorses this basic philosophy and is dedicated to the support and success of the SPI teams. 3.0 Goals 3.1 To reduce errors, cost, and improve quality and productivity. 3.2 To promote teamwork and communication between all levels of the organization. 3.3 To develop and promote the involvement of team members in the planning and control of their jobs. 3.4 To create a broader problem solving capability within the organization. 3.5 To encourage personal and leadership growth and the development of each team member. 4.0 Responsibilities 4.1 SPI Team Member A. Participation in the SPI Action Team is totally voluntary. B. Training in team building, project management, and SPI activity area is completed as required to successfully complete the QIT assigned action. C. Members are asked to actively support their team by attending and participating in all team activities. D. Members are asked to analyze, plan, estimate, schedule, and implement or monitor the piloting and/or full implementation of improvements identified by the QIT. F. Members develop detailed SPI Implementation Activity Plans. E. SPI Action Team Activity Improvement Reports are generated at the conclusion of the implementation's pilot and full implementation. G. Track cost of team activities. H. Establish and maintain an SPI Project Notebook. 4.2 QIT Members A. Participation in the SPI activity is totally voluntary. B. Training in team building, project management, and SPI activities are completed as required to accomplish our SPI Action Plan. C. Serve on the SPI Action Teams. D. Know and understand the tools used in SPI. F. Coordinate QST, QIT, and SPI Action Team activities. G. Generate this description of and guidelines for the SPI Action Teams. H. Analyze and rank opportunities for improvement. I. Describe the improvement, Define the statement of work, objectives of the improvement, target measures for the improvement to achieve, target schedules for accomplishing a pilot and/or final implementation, any resource constraints, and any recommendations. J. Form a link and serve as a liaison between the teams and the rest of the organization. K. Maintain records of the SPI activities. L. Work closely and keep the QST informed. M. Keep the SPI Action Teams, software staff, and management informed. N. Locate specialist who will assist a team on a particular problem. O. Identify candidates for the SPI Action Teams. P. Coordinate the SPI Action Plan implementation. Q. Evaluate the current SPI Action Plan implementation results near the end of the improvement cycle. R. Formulate the improvement plans for the next improvement cycle. S. Track cost of improvement activities. 4.3 QST Members A. Establish the SPI mechanism, policies, objectives, and resources. B. Provide guidance and direction to the teams. C. Demonstrate commitment by setting high priority on the team's recommendations to be implemented. D. Meet and work closely with the QIT and SPI Action Teams, as required. E. Be openly supportive of the program by actions. F. Recognize team progress. 5.0 Procedures 5.1 Code of Conduct Activities conducted according to our Code of Conduct. 5.2 Size of Teams The size of the teams varies with the SPI activity. The QIT will recommend a size and the SPI Action Team will provide feedback. The QIT informs the QST and software management of the need to increase the number of team members and obtains concurrence prior to making the team size changes. 5.3 SPI Action Team Effort Budgets The frequency of meetings and the level of effort is determined by the resource allocation approved by the QST and software management. Schedules for SPI activity planning and implementation are constrained by the resource authorization. Resources for the SPI activity come from the overall resource allocation. Headcount will not be added to implement the SPI program. 5.4 SPI Action Team Activities A. Review the SPI Action Plan generated by the QIT. B. Analyze the specific process improvement activity assigned by the QIT. C. Describe in detail how the improvement is to be accomplished in the SPI Activity Implementation Plan. D. Estimate the effort required to fully implement the improvement. E. Generate a schedule based on the effort required and the resource constraints. F. Identify in detail the responsibilities of the SPI Action Team for accomplishing the improvement. G. Recommend whether a pilot or full implementation approach should be used. H. Review the details of the SPI Activity Implementation Plan with the QIT and software staff. I. Implement the SPI Activity Implementation Plan. J. Monitor and report progress. K. Recommend to the QIT practical metrics that can be tied to our current business demands. L. Collaborate with the QIT to prepare a report at the end of the pilot and/or full implementation. M. Maintain records of team plans, schedules, costs, accomplishments, process definitions, and lessons learned. N. Write process descriptions suitable for use by the software staff. O. Share SPI activity expertise with software staff during and after implementation.