Codermetrics Analytics for Improving Software Teams
How can you help your software team improve? This concise book introduces codermetrics, a clear and objective way to identify, analyze, and discuss the successes and failures of software engineers-not as part of a performance review, but as a way to make the team a more cohesive and productive unit....
| Autor principal: | |
|---|---|
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
Sebastopol :
O'Reilly Media
2011.
|
| Edición: | 1st ed |
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009628357406719 |
Tabla de Contenidos:
- Table of Contents; Preface; Organization of This Book; Safari® Books Online; How to Contact Us; Acknowledgments; Part I. Concepts; Chapter 1. Introduction; Chapter 2. Measuring What Coders Do; The Purpose of Metrics; Metrics Are Not Grades; Team Dynamics; Connecting Activities to Goals; Good Metrics Shed a Light; Examining Assumptions; Timeout for an Example: The Magic Triangle (Partially) Debunked; Patterns, Anomalies, and Outliers; Peaks and Valleys; Ripple Effects; Repeatable Success; Understanding the Limits; Timeout for an Example: An Unexpected Factor in Success; Useful Data
- Choosing DataObtaining Data; Spotters and Stat Sheets; Fairness and Consistency; Timeout for an Example: Metrics and the Skeptic; Chapter 3. The Right Data; Questions That Metrics Can Help Answer; How Well Do Coders Handle Their Core Responsibilities?; How well do coders write code?; How well do coders design their code?; How well do coders test their code?; How Much Do Coders Contribute Beyond Their Core Responsibilities?; How many areas do coders cover?; How effectively do coders take initiative?; Do coders innovate?; How well do coders handle pressure?
- How well do coders deal with adversity?How Well Do Coders Interact With Others?; Do coders demonstrate leadership?; Do coders inspire or motivate their teammates?; How well do coders mentor others?; How well do coders understand and follow directions?; How much do coders assist others?; Is the Software Team Succeeding or Failing?; What is the user response to each software release?; How is the software doing versus competitors?; What is the quality of each software release?; How efficiently does the team deliver new software releases?; Timeout for an Example: An MVP Season
- The Data for MetricsData on Coder Skills and Contributions; Productivity; Speed; Accuracy; Breadth; Helpfulness; Innovation and Initiative; Data on Software Adoption, Issues, and Competition; Interest and Adoption; Notable Benefits; User Issues; Competitive Position; Timeout for An Example: A Tale of Two Teams; Part II. Metrics; Chapter 4. Skill Metrics; Input Data; Offensive Metrics; Points; Utility; Power; Assists; Temperature; O-Impact; Defensive Metrics; Saves; Tackles; Range; D-Impact; Precision Metrics; Turnovers; Errors; Plus-Minus; Skill Metric Scorecards; Observations on Coder Types
- ArchitectsSenior Coders; Junior Coders; Chapter 5. Response Metrics; Input Data; Win Metrics; Wins; Win Rate; Win Percentage; Boost; Loss Metrics; Losses; Loss Rate; Penalties; Penalties Per Win (PPW); Momentum Metrics; Gain; Gain Rate; Acceleration; Win Ranking; Capability Ranking; Response Metric Scorecards; Observations on Project Types; Consumer Software; Enterprise Software; Developer and IT Tools; Cloud Services; Chapter 6. Value Metrics; Input Data; Contribution Metrics; Influence; Efficiency; Advance Shares; Win Shares; Loss Shares; Rating Metrics; Teamwork; Fielding; Pop; Intensity
- Value Metric Scorecards
