Software Improvement Metrics

Paolo Cornali Project Manager| HTA srl Brescia, Lombardia, Italy

Hello everyone,

I must to manage a project that have the scope to improve the software development and debug process. In particular to reduce the number of development and debug hours. I need to find some metrics that let me know if the project is profitable. Do you have any suggestions?

I thought to consider those metrics at the moment:
bug numbers/number of new cycles developed (efficacy)
bug numbers/number of new forms created (efficacy)
(development hours+debug hours+fix bugs hours)/number of cycle steps developed (efficiency)
(development hours+debug hours+fix bugs hours)/number of new forms created (efficiency)

Thanks in advance for your suggestions.

Posted: Jan 12, 2016 12:30 AM

Sort By:

Suhail Iqbal Suhail Iqbal PMIATP CIPM FAAPM MPM MQM CLC CPRM SCT AEC SDC SMC SPOC PRINCE2 MCT| PM Training School Rawalpindi, Punjab, Pakistan

I suppose number of cycles steps is OK with me and you can leave out number of new forms. I also agree that in numerator you should have a combination but I am unable to establish a good link between the three things you are adding. Simply call it hours spent (development, debug and fix). What of you can create an equation in which number of bugs, hours spent and number of cycles , all can be considered?

Posted: Jan 12, 2016 2:01 AM

Paolo Cornali Project Manager| HTA srl Brescia, Lombardia, Italy

Thanks for your suggestion Suhail.
Which are the reasons why you suggest to create a single equation with all the variable considered? Do you think that is more manageable and effective?
I was thinking to maintain separate efficiency from efficacy metrics.

...

1 reply by Suhail Iqbal

Jan 13, 2016 12:45 AM

Suhail Iqbal

...

I probably misunderstood earlier, I agree with your contention.

Posted: Jan 12, 2016 7:32 AM

Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina

Paolo: you have to go to software engineering sites where you find a lot of them. Mainly inside CMU SEI site. But let me say this about metrics: it may be defined from strategy. For example to reduce what you are stating above, preventive maintenance is critical. But, it is your company strategy ready to pay for that?. On the other side, to decide if a project is profitable you metrics are not about that.

...

1 reply by Paolo Cornali

Jan 13, 2016 12:22 AM

Paolo Cornali

...

Thanks for your feedback Sergio. I think that our company shall change in that direction. The difficult part will be the cultural change that this improvement require.

Posted: Jan 12, 2016 6:33 PM

Paolo Cornali Project Manager| HTA srl Brescia, Lombardia, Italy

Jan 12, 2016 6:33 PM

Replying to Sergio Luis Conte

...

Thanks for your feedback Sergio. I think that our company shall change in that direction. The difficult part will be the cultural change that this improvement require.

Posted: Jan 13, 2016 12:22 AM

Suhail Iqbal Suhail Iqbal PMIATP CIPM FAAPM MPM MQM CLC CPRM SCT AEC SDC SMC SPOC PRINCE2 MCT| PM Training School Rawalpindi, Punjab, Pakistan

Jan 12, 2016 7:32 AM

Replying to Paolo Cornali

...

I probably misunderstood earlier, I agree with your contention.

Posted: Jan 13, 2016 12:45 AM

Please login or join to reply

Software Improvement Metrics

Sponsors

Vendor Events

Guessing is not a strategy: How to build decision velocity with AI and real-time data

Newsletters