Recording Benchmark Metrics Data

Prior to Recording your Metrics Data in Benchmark Metrics you will need to set up your Applications, Releases, Projects and Count Sessions in the Application List and the Project List.

Assigning Project Metrics to Benchmark Periods Importing Metrics Data from Excel Spreadsheets

ORGANISATION

Click the details icon to record the contact details for your organisation. These details will be extracted into any XML extracts you export from the Benchmark Data. They are also included in the the text of the email you send to the ISBSG Administrator if you elect to submit your benchmarking data, but the details are not recorded with the XML data file sent in the email attachment. You can remove or change the details in the email before sending. The contact information enables the ISBSG administrator to contact you if they need clarifications about your submitted data, but ensures that your data remains anonymous when forwarded to the Repository Administrator.

Under ORGANISATION you can then set up any number of "Benchmarking Periods" to group your metrics data for comparison and reporting.

BENCHMARK PERIOD

Benchmark Periods can be set up as a 'collection repository' for the set of Projects, Releases, or Applications that you want to benchmark as a set, compare to each other or group together to compare against another Benchmark Period set.

For ISBSG submission the Benchmarking Period is the period in which maintenance and support measures submitted to the ISBSG have been collected for the application. Note that this is not the period over which the application has been maintained by the organisation. The recommendation is that a submission should contain data for a period of 12 months, though a shorter period can be accepted. Data for alternative periods will be scaled appropriately to 12 months before analysis.

Typically a Benchmark Period would be for a particular period of time (e.g. Projects 2010 - 2011). But they may also represent a group of related Projects. e.g. assign all the New Development Projects written in Java developed in the last 3 years into a period called "Java ND : 2009 - 2001".

Example: you may want to set up a Benchmark Period to bes"January to June 2011" and all the Projects that are implementedsin that period are then assigned to that Benchmarking Period Set. Thesnext Benchmarking Period could be "July to December 2011" andsall Projects that are implemented in that period are assigned here. Thatswould allow you to aggregate your projects results by Period to determinesif your productivity was improving over time.

Set the Start and End Date for the Period to document the Reporting Period.

Benchmark Developments and Enhancement (D&E)

SCOPE allows you to record data for size, effort , defect, cost, experience levelssand environment attribute at what ever work group level suits your organizationsand how they collect their time sheets and defects. i.e. you can electsto collect at the following levels:

Benchmark Projects - click the Details Icon to record size, efforts and defect data for a Project at Project Level or record it at Counts Session level and roll-up (derive) into a total for the Project. If you decide to derive Project totals from the Change Requests (Count Sessions) you can then manually override the derived total for the Project to include data allocated at Project level. ie. SCOPE will sum all the defects recorded at Count Session Levels and total them for the Project. However you may also want include defects that were recorded against the project but could not be attributed to a particular Change Request. Theses extra defects can be manually recorded at Project Level.
Benchmark Releases - click the Details Icon to record size, effort and defect data for a Release at Release Level or record metrics at Counts Session level and roll-up (derive) the individual Count Session values into a total for the Release. If you decide to derive totals from the Count Sessions you can then choose to manually override the derived total for the Release. ie. SCOPE will sum all the effort recorded at Count Session Level and total it for the Release. However effort hours may have been expended at Release level. These additional hours for the Release Management and Release Integration and System Testing can be added in manually at Release Level.

A Project or Release can only be assigned to oneBenchmarking Period. If you want to move it to another BenchmarkingsPeriod then either 'Cut and Paste' it or delete it and add it again. Deletingsfrom the Benchmarking Period does not actually 'delete' the Project orsRelease it just removes the Project or Release from being reported withinsthat Benchmarking Period.

For details on how to complete each of the Benchmark Metricsstabs in Count Sessions, Projects and Releases see:

Benchmark Maintenances and Support (M&S)

SCOPE allows you to record datasfor size, effort , defect, cost, usage and documentation quality attributesfor each Application maintained and/or supported.

Benchmark Applications - you can record your maintenance and support metrics data for your Applications for any period you elect. If you want to benchmark quarterly, biannually or annually, then just set the Period duration that the data has been collected for in the Benchmark Period.

For details on how to complete each of the Benchmark Metrics tabs in the Applications Period Metrics Details:

View reports on your Benchmark data.