Codermetrics

Input Data

Table 5-1 shows the input data elements that will be used in the Response Metrics. These data elements were discussed in Chapter 3. It is assumed that you will measure each of these in some regular time interval, although not as frequently at the data used for Skill Metrics. For example, you might measure and record this data monthly or quarterly.

Some of these data elements may seem challenging for you to gather if you don’t already do so. As discussed in previous chapters, however, there are a variety of ways you can put this in your own hands, mostly by implementing the data gathering directly in your software. If you haven’t already done this, of course, it will take time, but it’s my belief that the extra effort will be worth it. This data will be highly useful in helping you improve your software development teams, and once you’ve established a way to gather the data for these metrics, it will be relatively easy to continue and even enhance the data gathering on an ongoing basis.

Table 5-1. Input data for Response Metrics

Element Name	Description
User Activations	New user activations (not including trial or demo users), tracked either through software installation, user registration, licensing, or other means
User Deactivations	Users (not trial or demo users) who explicitly deactivate or cancel accounts or who stop using software, tracked either through cancellations, software uninstall, detection of non-usage, or other means
Trials Completed	Trial or demo users or accounts ...