Quality Metrics for OSS Projects

Last week a colleague asked about software quality metrics for Operational Support System (OSS) projects. A large telecommunications provider was complaining that the system that they had delivered contained too many bugs. The question that she needed answered was "How many bugs is too many?". In answer to this question she wanted some benchmarks for industry best practice in terms of bugs per lines of code (LOC).

Before examining this question, we thought we should look at some of the characteristics of OSS projects, including:

  1. Typically they are large in terms of code base and time to deliver;
  2. They are complex;
  3. They are highly customised;
  4. They are expensive and;
  5. They deliver strategic benefits to the service provider.

In situations such as these we start by looking at the customer's real concerns - there is usually an underlying problem that elicits the response "Your system contains too many bugs". Here is a quick checklist:

  1. Is the system intent correct - that is, were the initial requirements accurate?;
  2. When bugs are identified, can the customer report and track them online?;
  3. Are any of the bugs fundamentally hampering the service provider's ability to achieve their strategic objectives? and;
  4. Is the process to manage bugs satisfactory from the customer's perspective?

In this instance, the problem was with the last point above. When the customer raised a bug (which they could do online), the systems integrator (SI) would identify and triage the bug, request a fix from the OSS vendor and then implement the patch. This took time and although OSS vendor was not charging for bug fixes the SI was charging for their time to report the bug and implement the fix. This was the source of the customer's dissatisfaction.

So benchmarking themselves based on metrics such as bugs per LOC would have been useless. Instead, we recommended an approach that we had used on a previous project experiencing similar difficulties. The SI and OSS vendor would agree to share the cost of each bug fix and not pass these costs on to the customer. The result:

  1. The customer saw an immediate improvement in responsiveness from the SI;
  2. Fixes for their two critical bugs were implemented within in two weeks;
  3. The customer was happy for their remaining 16 bugs to be resolved within a timeframe spanning 3 months.

The lesson here is that the solution to achieving a quality result may not depend so much on technical issues as organisational and management ones.

Comments

  1. This is a wonderful article, Given so much info in it, These type of articles keeps the users interest in the website, and keep on sharing more ... good luck.
    SHERIDAN OUTLET

    ReplyDelete
  2. My story started about 40 years ago as due to my grand parents being in textile business since 1970s i always had the passion about textiles.
    About 2 years ago during shopping in a Melbourne local store someone sold me Polyester sheets saying they were pure cotton. I realised it once i got home and opened the package. I took those sheets to some of my friends to ask if they were cotton or polyester. No one could tell me with the confidence.
    I took the sheets back to store and store keeper told me that even she did not know how to differentiate between cotton and polyester blends.

    It gave me the motivation to educate people and bring awareness between them who don't know much about bedding and how to choose correct bedding. After all we spend 30% of our life on beds. I decided to start COTTON CLOUD AUSTRALIA a place where people can shop with confidence that whatever they are buying is 100% natural and pure cotton. They don't have to get surprised or worried that someone might sell them a polyester or other synthetic blend. So that people don't have to look for what they love and they don't have to compromise on the quality with or without their choice.

    We went out in the markets, Online marketplaces, Forums, Blogs. Almost everywhere we found and met people who were in love with pure cotton bedding and other essentials. We got enormous response and support. So we started COTTON CLOUD just like any other cloud services its cloud service for cotton bedding, bath and living essentials. The same big brands you love and trust but no blends and plastics.

    We have a mission to serve you in the best way we can and to educate the population about what they spend almost 30% of their whole life on. We are local just like you and full of passion and ambition. Please become part of our story and share it.

    Thank you for your time to read about us.

    ReplyDelete

Post a Comment

Popular posts from this blog

The Service Catalog

We're back