CoderMetrics: Analytics for Improving Software Teams

Overview

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 ...

See more details below
Paperback
$33.81
BN.com price
(Save 15%)$39.99 List Price

Pick Up In Store

Reserve and pick up in 60 minutes at your local store

Other sellers (Paperback)
  • All (16) from $4.56   
  • New (9) from $24.59   
  • Used (7) from $4.56   
Codermetrics: Analytics for Improving Software Teams

Available on NOOK devices and apps  
  • NOOK Devices
  • NOOK HD/HD+ Tablet
  • NOOK
  • NOOK Color
  • NOOK Tablet
  • Tablet/Phone
  • NOOK for Windows 8 Tablet
  • NOOK for iOS
  • NOOK for Android
  • NOOK Kids for iPad
  • PC/Mac
  • NOOK for Windows 8
  • NOOK for PC
  • NOOK for Mac
  • NOOK Study
  • NOOK for Web

Want a NOOK? Explore Now

NOOK Book (eBook)
$18.99
BN.com price
(Save 44%)$33.99 List Price

Overview

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 dynamics
  • Get recommendations for integrating codermetrics into existing processes
  • Ask the right questions to determine the type of data you need to collect
  • Use metrics to measure individual coder skills and a team’s effectiveness over time
  • Identify the contributions each coder makes to the team
  • Analyze the response to your software and its features—and verify that you're meeting team and organizational goals
  • Build better teams, using codermetrics to make personnel adjustments and additions
Read More Show Less

Product Details

  • ISBN-13: 9781449305154
  • Publisher: O'Reilly Media, Incorporated
  • Publication date: 8/31/2011
  • Edition number: 1
  • Pages: 262
  • Sales rank: 1,379,752
  • Product dimensions: 6.90 (w) x 9.10 (h) x 0.50 (d)

Meet the Author

Jonathan Alexander has over 25 years of experience in software development. He is currently VP of Engineering at Vocalocity, a leader in cloud-based business telecommunications. Previously he built and managed software teams at vmSight, Epiphany, and Radnet. He studied computer science at UCLA, and began his career writing software for author Michael Crichton.

Read More Show Less

Table of Contents

Preface;
Organization of This Book;
Safari® Books Online;
How to Contact Us;
Acknowledgments;
Concepts;
Chapter 1: Introduction;
Chapter 2: Measuring What Coders Do;
2.1 The Purpose of Metrics;
2.2 Timeout for an Example: The Magic Triangle (Partially) Debunked;
2.3 Patterns, Anomalies, and Outliers;
2.4 Understanding the Limits;
2.5 Timeout for an Example: An Unexpected Factor in Success;
2.6 Useful Data;
2.7 Timeout for an Example: Metrics and the Skeptic;
Chapter 3: The Right Data;
3.1 Questions That Metrics Can Help Answer;
3.2 Timeout for an Example: An MVP Season;
3.3 The Data for Metrics;
3.4 Timeout for An Example: A Tale of Two Teams;
Metrics;
Chapter 4: Skill Metrics;
4.1 Input Data;
4.2 Offensive Metrics;
4.3 Defensive Metrics;
4.4 Precision Metrics;
4.5 Skill Metric Scorecards;
4.6 Observations on Coder Types;
Chapter 5: Response Metrics;
5.1 Input Data;
5.2 Win Metrics;
5.3 Loss Metrics;
5.4 Momentum Metrics;
5.5 Response Metric Scorecards;
5.6 Observations on Project Types;
Chapter 6: Value Metrics;
6.1 Input Data;
6.2 Contribution Metrics;
6.3 Rating Metrics;
6.4 Value Metric Scorecards;
6.5 Observations on Team Stages;
Processes;
Chapter 7: Metrics in Use;
7.1 Getting Started;
7.2 Timeout for an Example: The Seven Percent Rule;
7.3 Utilizing Metrics in the Development Process;
7.4 Timeout for an Example: The Turn-Around;
7.5 Using Metrics in Performance Reviews;
7.6 Taking Metrics Further;
7.7 Timeout for an Example: The Same But Different;
Chapter 8: Building Software Teams;
8.1 Goals and Profiles;
8.2 Roles;
8.3 Timeout for an Example: Two All-Nighters;
8.4 Personnel;
8.5 Timeout for an Example: No Such Thing As a Perfect Team;
Chapter 9: Conclusion;
Codermetrics Quick Reference;
Bibliography;
Colophon;

Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star

(0)

4 Star

(0)

3 Star

(0)

2 Star

(0)

1 Star

(0)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & Noble.com that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & Noble.com does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at BN.com or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on BN.com. It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

 
Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously
Sort by: Showing 1 Customer Reviews
  • Posted April 26, 2012

    more from this reviewer

    This is a book about metrics for software developers and softwar

    This is a book about metrics for software developers and software development teams. It is not about software quality but about the contribution of each individual to the software and the product.

    The book is organized into three parts.

    Part I talks about the concepts. It outlines the purpose of the metrics and then talks about how important it is to get the right data. It drills into the kind of data that is relevant to each individual - based on the project that he works in and his responsibilities. The book then moves on to describe the various data that can be used for the metrics like productivity, speed, accuracy, breadth, helpfulness, innovation and initiative.

    Part II is about the metrics themselves. These are categorized as Skill Metrics, Response Metrics and Value Metrics. Skill Metrics is in turn sub-categorized as Offensive, Defensive and Precision Metrics.

    The last part is about the processes - essentially how to use the metrics.

    The author uses the analogy of American football in the entire book to illustrate his thoughts. His real-life experiences has helped him with a wealth of information for the book.

    While the book is quite useful in theory, it is arguable how much of it can be put to practice and the effort it takes to do that. Perhaps a subset of the metrics can used as applicable.

    The book does get dry when it gets into the nitty-gritty and thus may not make a great reading end to end.

    Was this review helpful? Yes  No   Report this review
Sort by: Showing 1 Customer Reviews

If you find inappropriate content, please report it to Barnes & Noble
Why is this product inappropriate?
Comments (optional)