Codermetrics : Analytics for Improving Software Teams

Experienced team builder Jonathan Alexander explains how codermetrics helps teams understand exactly what occurred during a project, and enables each coder to focus on specific improvements. Alexander presents a variety of simple and complex codermetrics, and teaches you how to create your own. Concepts Chapter 1 Introduction Chapter 2 Measuring What Coders Do The Purpose of Metrics Timeout for an Example: The Magic Triangle (Partially) Debunked Patterns, Anomalies, and Outliers Understanding the Limits Timeout for an Example: An Unexpected Factor in Success Useful Data Timeout for an Example: Metrics and the Skeptic Chapter 3 The Right Data Questions That Metrics Can Help Answer Timeout for an Example: An MVP Season The Data for Metrics Timeout for An Example: A Tale of Two Teams Metrics Chapter 4 Skill Metrics Input Data Offensive Metrics Defensive Metrics Precision Metrics Skill Metric Scorecards Observations on Coder Types Chapter 5 Response Metrics Input Data Win Metrics Loss Metrics Momentum Metrics Response Metric Scorecards Observations on Project Types Chapter 6 Value Metrics Input Data Contribution Metrics Rating Metrics Value Metric Scorecards Observations on Team Stages Processes Chapter 7 Metrics in Use Getting Started Timeout for an Example: The Seven Percent Rule Utilizing Metrics in the Development Process Timeout for an Example: The Turn-Around Using Metrics in Performance Reviews Taking Metrics Further Timeout for an Example: The Same But Different Chapter 8 Building Software Teams Goals and Profiles Roles Timeout for an Example: Two All-Nighters Personnel Timeout for an Example: No Such Thing As a Perfect Team Chapter 9 Conclusion Appendix Codermetrics Quick Reference Appendix Bibliography 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.Experienced team builder Jonathan Alexander explains how codermetrics helps teams understand exactly what occurred during a project, and enables each coder to focus on specific improvements. Alexander presents a variety of simple and complex codermetrics, and teaches you how to create your own.Learn how codermetrics changes long-held assumptions and improves team dynamicsGet recommendations for integrating codermetrics into existing processesAsk the right questions to determine the type of data you need to collectUse metrics to measure individual coder skills and a team’s effectiveness over timeIdentify the contributions each coder makes to the teamAnalyze the response to your software and its features—and verify that you're meeting team and organizational goalsBuild better teams, using codermetrics to make personnel adjustments and additions 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 engineersnot as part of a performance review, but as a way to make the team a more cohesive and productive unit. Experienced team builder Jonathan Alexander explains how codermetrics helps teams understand exactly what occurred during a project, and enables each coder to focus on specific improvements. Alexander presents a variety of simple and complex codermetrics, and teaches you how to create your own. This book attempts to flesh out and share some of the ideas that are not well documented, written or otherwise available regarding metrics that can be used to analyze coders and software teams.