Measurements and reports

Today I was confronted with a question what SCM measurements we would need and what SCM reporting. Although measurements are often put in reports, our objective was quite different for the two.

The SCM measurements were intended to give us information about the SCM processes. By measuring some primary indicators we want to get an idea about how accurate SCM processes are followed and how efficient the SCM processes are. For example, suppose a subsystem baseline is created more than 10 times a day, there probably is something strange going on.

On the other hand, SCM reporting was intended to support the operational project execution. For example, to support the integration process the integration managers need to know what changes are made in the new baselines compared to the previous baseline that was integrated. Managers may argue that this is listed in the baseline report, but the author of the baseline report has to get the info from somewhere. As the SCM system keeps track of all changes made to the product, SCM reporting may provide the info the integration manager needs.

Other examples of SCM measurements are:

  • Number of parallel streams that are used
  • Number of deliveries from a developer to the integrator, per day
  • Number of changes per delivery
  • Amount of time to get a change of one developer to another, going through all the formalities, quality checks (build, tests, reviews) and data transfers (deliver, export, import, install)
  • Number of problem reports solved per week, and the trend over the past year.

Other examples of SCM reporting are:

  • Changes made in a baseline compared to a previous baseline
  • Problem solutions present in a particular stream
  • Problem Report and Change Requests found a particular release
  • Persons accountable for creating, testing, integrating a particular change
  • Evidence of a particular SCM promotion step

I do not claim that the distinction between SCM measurements and SCM reporting is universal. But that is what I ran into today.

About Frank Schophuizen (fschop)

Hi, my name is Frank Schophuizen and I am working as a consultant in CM, Agile and ALM for TOPIC Embedded Systems. I have over 30 years experience in software development in the technology industry, with the last 15 years mainly in process improvement, deployment and integration of methods and tools in the area of Agile (SAFe, Scrum), CM and ALM. I am strongly interested in the complexities of collaboration and integration in multi-project and multi-site organizations. I have worked with various technology companies such as Philips, ASML, NXP and Vanderlande, and with various tool vendors such as Atlassian (e.g. Jira, Confluence),IBM Rational (e.g. ClearCase, Synergy, Jazz products) as well as open source tools (e.g. SVN, Git, Jenkins, Trac, Eclipse). I am living in Eindhoven, the Netherlands, with my wife. We have 3 adult children. My main hobbies are classical music and photography.
This entry was posted in configuration management, reporting. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.