<?xml version="1.0" encoding="UTF-8"?>
<mods xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" version="3.1" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-1.xsd">
  <titleInfo>
    <title>PSP</title>
    <subTitle>A self-improvement process for software engineers</subTitle>
  </titleInfo>
  <name type="personal">
    <namePart>Humphrey, Watts S.</namePart>
    <role>
      <roleTerm authority="marcrelator" type="text">creator</roleTerm>
    </role>
    <role>
      <roleTerm type="text">autor.</roleTerm>
    </role>
    <role>
      <roleTerm authority="marcrelator" type="code">aut</roleTerm>
    </role>
  </name>
  <typeOfResource>text</typeOfResource>
  <originInfo>
    <dateIssued encoding="marc">2005</dateIssued>
    <issuance>monographic</issuance>
  </originInfo>
  <language>
    <languageTerm authority="iso639-2b" type="code">spa</languageTerm>
  </language>
  <language>
    <languageTerm authority="iso639-2b" type="code">eng</languageTerm>
  </language>
  <physicalDescription>
    <form authority="marcform">print</form>
    <extent>346 páginas : :ilutraciones.;tablas.;gráficas.</extent>
  </physicalDescription>
  <abstract>Most software-development groups have embarrassing records: by some accounts, more than half of all software projects are significantly late and over budget, and nearly a quarter of them are cancelled without ever being completed. Although developers recognize that unrealistic schedules, inadequate resources, and unstable requirements are often to blame for such failures, few know how to solve these problems. Fortunately, the Personal Software Process (PSP) provides a clear and proven solution. Comprising precise methods developed over many years by Watts S. Humphrey and the Software Engineering Institute (SEI), the PSP has successfully transformed work practices in a wide range of organizations and has already produced some striking results. This book describes the PSP and is the definitive guide and reference for its latest iteration. PSP training focuses on the skills required by individual software engineers to improve their personal performance. Once learned and effectively applied, PSP-trained engineers are qualified to participate on a team using the Team Software Process (TSP), the methods for which are described in the final chapter of the book. The goal for both PSP and TSP is to give developers exactly what they need to deliver quality products on predictable schedules.</abstract>
  <tableOfContents>The personal process strategy. -- The baseline personal process. -- Measuring software size. -- Planning. -- Software estimating. -- The probe estimating method. -- Software planning. -- Software quality. -- Desing and code reviews. -- Software design. -- The PSP design templates. -- Desing verification. -- Process extensions. -- Using the personal software process. </tableOfContents>
  <note>Incluye tabla de contenido.</note>
  <note>Incluye referencias bibliográficas.</note>
  <subject authority="">
    <topic>Ingeniería de software</topic>
  </subject>
  <subject authority="">
    <topic>Productividad de software</topic>
  </subject>
  <subject authority="">
    <topic>Software de programación</topic>
  </subject>
  <subject authority="">
    <topic>Industria de software para computadores</topic>
  </subject>
  <classification authority="ddc">005.1 H926p</classification>
  <identifier type="isbn">0321305493</identifier>
  <recordInfo>
    <recordContentSource authority="marcorg">CO-ViULL</recordContentSource>
    <recordCreationDate encoding="marc">191024</recordCreationDate>
    <recordChangeDate encoding="iso8601">20251030135723.0</recordChangeDate>
    <languageOfCataloging>
      <languageTerm authority="iso639-2b" type="code">spa</languageTerm>
    </languageOfCataloging>
  </recordInfo>
</mods>
