Home > Consulting Services > Sys Eng & Development > PSP > Service
Personal Software Process (PSP) Organizational Adoption
Intended For...
Organizations who wish to adopt PSP technologies and organizations who wish to deliver defect free software on schedule
|
Location
The PSP Adoption is conducted at client sites
Related Services
• PSP Executive Seminar
• Disciplined Software Engineering (PSP Training)
Lead Time
Duration
Six months to one year
|
Instructor Information
The STSC's PSP Instructors are certified by the SEI to deliver the SEI's PSP material. They have strong interests and extensive experience in the application of software engineering principles to the development of software systems. They also possess broad technology adoption experiences. For Cost & More Information
801/DSN 775-5555
e-mail: stsc.consulting@hill.af.mil
|
Description
Personal Software Process
The Personal Software Process (PSP) addresses an individual developer's ability to consistently deliver high quality software products in a timely manner. This technology was developed by Watts Humphrey of the SEI as an extension to his earlier CMM work. It has been demonstrated that projects staffed with PSP trained engineers produce extremely low defect density software on schedule.
PSP Adoption
In keeping with the STSC's mission of aiding organizations in adopting useful software engineering technologies, the goal of the STSC's PSP service is the organizational adoption and practice of PSP - not just individual PSP practice. The STSC has identified five necessary activities that lead to the organizational adoption of PSP.
The STSC can provide support in all five areas.
• Obtaining and Maintaining Commitment: This activity is absolutely necessary for all adoption efforts, whether PSP or not. Without commitment the adoption will not succeed.
• PSP Training: PSP training consists of an integrated mix of 14 lectures stressing software engineering topics, 9 tutorials explaining the PSP, 10 programming assignments in which the PSP is used and development data collected, and 5 report assignments in which the PSP data is analyzed and used for personal process improvement.
• Developing Procedures for Managing PSP Engineers: The organization's (and individual manager's) management practices need to evolve to support the PSP engineer's goal of continual personal improvement and to enable the organization to make use of the engineer's improved skills.
• Adopting "Textbook" PSP to the Organization: The organization will need to modify the PSP infrastructure and tailor the PSP processes used and developed during the PSP training to its unique development environment.
• Piloting PSP on a Project: Piloting PSP enables a measurement of the success of the PSP effort, while also supporting rollout of PSP to the remainder of the organization.
Our Goal...
is to be THE organization specializing in solving DoD specific barriers to PSP adoption and in successfully inserting PSP into the DoD software culture.
Prerequisites
None, although a programming background is helpful.
|
|
