Cargando…

Software Project Management.

Software Project Management: Measures for Improving Performance focuses on more than the mechanics of project execution. By showing the reader how to identify and solve real world problems that put schedule, cost, and quality at risk, this guide gets to the heart of improving project control and per...

Descripción completa

Detalles Bibliográficos
Clasificación:Libro Electrónico
Autor principal: Kelsey, Robert Bruce, 1954-
Formato: Electrónico eBook
Idioma:Inglés
Publicado: Oakland : Berrett-Koehler Publishers, Incorporated, 2006.
Temas:
Acceso en línea:Texto completo (Requiere registro previo con correo institucional)
Tabla de Contenidos:
  • Cover; Half Title; Title; Copyright; Dedication; Table of Contents; PREFACE; ACKNOWLEDGMENTS; CHAPTER 1. MEASURES, GOALS, AND STRATEGIES; Measuring Performance within a Project; Two Ways to Use Measurement; What Is Software Measurement?; What Do You Want to Accomplish with Measurement?; A Commitment to the Future; Think Globally, Act Locally; Identify Areas of Opportunity; Select an Operational Measure and Strategy; A Strategy for Addressing Product Quality; A Strategy for Addressing Productivity and Workflow; Applying What Youâ#x80;#x99;ve Learned; EXERCISE 1-1: A Clear Rationale.
  • EXERCISE 1-2: A Strategy to Meet Real NeedsCHAPTER 2. IMPLEMENTING A MEASUREMENT ARCHITECTURE; Measures Are Answers to Questions; The ISO/IEC 15939 Architecture; Measurable Concepts; Base Measures; Derived Measures; Models and Indicators; Putting the Architecture to Work; STEP 1: Identify When, Where, and What to Measure; STEP 2: Determine the Details; STEP 3: Establish the Architecture; STEP 4: Identify Tools and Infrastructure Requirements; A Typical Measurement Implementation; Base Measures; Derived Measures; Indicators; Applying What Youâ#x80;#x99;ve Learned.
  • EXERCISE 2-1: Identifying Information NeedsEXERCISE 2-2: Learning from History; EXERCISE 2-3: Approaching Measurement as Risk Mitigation; EXERCISE 2-4: Selecting a Strategy and an Implementation Plan; CHAPTER 3. APPLYING THE BASICS: RUN RATES; Proceed with Caution; The Key Attributes of Defects and Time; Defects, Defects, Everywhere; What Is a Product Defect?; What Is a Process Defect?; How to Use Defect Run Rates; Interpreting Defect Run Rate Data; Project Events Affecting Run Rates; Static and Dynamic Test Approaches; Dynamic Test Events; Time Period for Release Phases.
  • What Do You Mean, You Arenâ#x80;#x99;t Done Yet?Project Time vs. Work Time; Typical Time and Effort Run Rates; The Hidden Danger of Blocked Time; Applying What Youâ#x80;#x99;ve Learned; EXERCISE 3-1: Interpreting Defect Run Rates; CHAPTER 4. BEHIND THE LINES: ATTRIBUTE ANALYSES; Key Defect Attributes; Defect Status and Productivity; EXAMPLE: Defect Rates and States; Injection Phase and the Development Process; EXAMPLE: The Signi? cance of Injection Rates; Detection Phase and Quality Control; EXAMPLE: The Ones That Got Away; Key Time and Effort Attributes.
  • Putting the Pieces Together: Iterative Development Risk AnalysisProblem Report Tracking System Requirements; Injection Phase; Detection Phase; Effect of Change; Documentation Affected; Prioritization; Conifiguration Information; Report Status and History; Defect/Fix Status; Time Fields; Should You Measure Defect â#x80;#x9C;Severityâ#x80;#x9D; Ratings?; Applying What Youâ#x80;#x99;ve Learned; EXERCISE 4-1: Looking into the Future; EXERCISE 4-2: Interpreting Detection Phase Data; EXERCISE 4-3: Interpreting Injection Phase Data; EXERCISE 4-4: Applying Injection and Detection Phases.