Many of software's current problems stem from the pervasive culture of software organizations. This "hacker" culture glorifies rapid coding, is schedule-driven, and objects to measurement and planning. Commitments are generally missed while quality is unmeasured and unmanaged. In this presentation, Watts Humphrey describes steps to change the current software culture and its consequences. Learn how the Personal Software Process (PSP) and Team Software Process (TSP) guide engineers in planning and measuring their work. Explore the benefits of following a defined, planned, and measured process and the guidelines for making these practices more general in software organizations.
Watts Humphrey, The Software Engineering Institute
This presentation explores ways to plan and execute technical training to ensure the best possible use of resources to meet your organization's objectives. Learn how to avoid the most common problems and shortfalls, including budget woes, business relevance, and lack of commitment. Discover the most effective ways to breathe life into your organization's training program.
Anntoinette Gurvin, General Dynamics Information Systems
Learn how one company successfully implemented SEI-PSP to a significant part of its software engineering organization. Key discussion points include organization readiness, a training approach, lessons learned, and ways to successfully introduce PSP into an organization. Discover the three process areas (inspections, planning, and quality) where PSP can have a significant impact.
Several years ago, the Naval Oceanographic Office initiated its process improvement effort with Team Software Process (TSP) and Personal Software Process (PSP) as its foundation. Learn about the areas in which TSP/PSP made a significant impact on implementing change relating to the organization's CMM maturity level. Discover how the structure provided by TSP/PSP facilitated the implementation of a Quality Assurance program, and explore the major impact TSP/PSP had on the organization's ability to establish a baseline of historical project data.