Everything About ___
Live briefing

Everything about Personal software process

Process to improve programming quality

The Personal Software Process (PSP) is a structured software development process that is designed to help software engineers better understand and improve their performance by bringing discipline to the way they develop software and tracking their predicted and actual development of the code. It clearly shows developers how to manage the quality of their products, how to make a sound plan, and how to make commitments. It also offers them the data to justify their plans. They can evaluate their work and suggest improvement direction by analyzing and reviewing development time, defects, and size data. The PSP was created by Watts Humphrey to apply the underlying principles of the Software Engineering Institute's (SEI) Capability Maturity Model (CMM) to the software development practices of a single developer. It claims to give software engineers the process skills necessary to work on a team software process (TSP) team. Wikipedia →

🧭 Start here: a 6-step reading path

  1. Read the overview: Personal software processA 5-minute orientation
  2. Skim a recent paper: Privacy-aware sharing and collaborative analysis of personal wellness data: Process model, domain ontology, software system and user trialInfluential work since 2022
  3. Pick up a classic book: Interactive Computing SeriesThe most-reprinted book on the subject
  4. Read the landmark paper: Using a defined and measured Personal Software ProcessCited 71 times
  5. Go sideways: Watts HumphreyA closely related topic
  6. Go sideways: Team software processA closely related topic

📖 Definitions

No dictionary entry for this exact phrase.

🏆 Landmark papers (most cited)

🆕 Influential since 2022

📚 Books worth reading

Ranked by number of editions on Open Library, a rough measure of how lasting a book is.

🔗 Related topics