Archive

Posts Tagged ‘process maturity improvement’

What’s Cool in Software Engineering

October 15th, 2009 Jitendra No comments

Might sound like an oxymoron, but it’s not.

As you know, I work for CAST. I work here because our product is really cool.

Let me tell you why it’s cool and perhaps you’ll agree as well.

The CAST Application Intelligence Platform (AIP) is cool because it goes beyond what’s available in 5 groundbreaking ways.

1) The CAST AIP objectively measures software quality, complexity, and size – attributes that have traditionally been very slippery to quantify. (Think about this for a second — it happens to be true.)

2) CAST’s coverage of languages, platforms, and technologies is unmatched (30+ languages, all major platforms and technologies, and all major packaged software including SAP and Oracle).Trying to simulate what the CAST AIP does with open source applications or other existing products is an exercise in frustration. Not only do you end up with a patchwork quilt of systems, they don’t really do what you really want them to do — reliably detect the problems that lurk in the interfaces between technologies and platforms. Only the CAST AIP can do this.

3) Granular, surgical drill downs. The CAST AIP gives you multiple views into the end-to-end (developer, architect, project manager, business manager) and precise guidance on fixing the root cause of the problem. CAST AIP is a great example of how insight is used to guide effective actions.

4) Quantifying productivity and the effectiveness of process improvement. The very metrics that are used to measure software quality, complexity, and size can be used to track the effectiveness of improvement efforts. You can read more about it in a previous post.

5) CAST AIP goes beyond performance testing by:

  • Enabling teams to begin finding performance problems caused by design bottlenecks long before performance testing can begin.
  • Automatically tracing application performance problems to the root cause. Testing teams can find problems more reliably, fix them faster, and fix them once and for all using the precise guidance CAST AIP provides.
  • Finding performance bottlenecks that go beyond those uncovered in traditional performance testing by revealing problems that lie hidden at the interfaces between language and technology tiers.
  • Uncovering future problems, not just present ones. Performance testing doesn’t tell you how something will perform in a few months when production conditions have (invariably) changed. It won’t tell you how easy it will be to modify the system to meet a pressing business need. And it won’t tell you how difficult it will be to transfer support to another team (internal or external). CAST AIP can do all of the above.

When something is this different it takes a while to appreciate the power of it.


A Recipe for Quantifying the ROI on Improving Process Maturity

September 23rd, 2009 Jitendra No comments

Types of Process Frameworks

1.What should I do? — Process Definition Frameworks (Associated Metric Type = Objective or End-Result, or Benefit)

  • ITIL
  • MOF
  • ISO, etc.

2. How well am I doing it? – Control/Audit/Maturity Frameworks (Associated Metric Type = Operational Level or Quality Indicator)

  • BS 15000
  • CMMI, etc.

3.How can I improve it? – Process Improvement Frameworks (Associated Metric Type = mix of above two metric types)

  • Six Sigma
  • TQM
  • Lean, etc.

A Recipe for Quantifying the ROI on Improving Process Maturity — the bang for the buck on improving the repeatability and quality of processes:

1.Define the end-result metric (e.g. support cost per year in $)
2. Define the process performance metric (e.g. defect injection rate)
3. Quantify the end-result metric as a function of the process performance metric — e.g. support cost per year = f(defect injection rate)
4. Define processes and break down process activities (e.g. testing process)
5. Define activity maturity levels — what it means to be at maturity level 1, level 2, etc.
6. Quantify the change in performance metrics due to change from one maturity level to another.
7. Use (3) to calculate the benefit of moving from one maturity level to another.
8. Quantify the cost of moving from one maturity level to another (one-time and ongoing cost categories are: organizational change, business process change, software licences, productivity loss, administrative costs)
9. Divide (7) by (8) to calculate the ROI of process maturity improvement