|
Meaningful Metrics Your numbers are solid and your graphs are works of art. Now boost your metrics' value through the roof with some simple annotations that will put all that data in context.
|
|
|
How Good Is This Software?—A Model to Measure Subjective Data How do you really know how good your software is? Many traditional measures only look at the quantitative aspects of quality. Here's a model to measure and analyze subjective—or qualitative—data about software quality.
|
|
|
Customer Satisfaction: What to Ask, How to Ask, and Who to Ask Improving customer satisfaction should be a primary goal of process improvement programs. So how satisfied are our customers? One of the best ways to find out is to ask them. Here are techniques for creating a useful survey and interpreting the results.
|
|
|
Getting the Most from Outsourcing Outsourcing can be a great way to augment your software efforts. Here are guidelines to help you choose the right provider and ensure that you get what you paid for.
|
|
|
The Quality Barometer A QA manager is often faced with measuring the impossible. Here is a simple, post-ship metric to help judge the test effort's effectiveness. The Quality Barometer method uses the bug counts found during testing, calculates a percentage, and then uses that percentage as the defect target number that can be tolerated after shipment.
|
|
|
Designing Useful Metrics: Using Observation, Modeling, and Measurement to Make Decisions First-order measurement can help you understand what's going on, make decisions, and improve results. Observation, modeling, and simple data gathering are things that you can implement in your work group without a big measurement program or big funding. Start by modeling your system and working out on paper how different measures will affect your system. Then involve your team, expand your model, and try some simple data gathering. This approach to measurement is one more tool in your toolkit, and it will move your organization toward better quality.
|
|
|
Cem Kaner on Rethinking Software Metrics The theory underlying a measurement must take into account at least nine factors. This article defines these nine factors (e.g., the scope of the measurement, the scale of the instrument, and the variation of measurements made with the instrument) and applies them to a few examples.
|
|
|
Why Nobody in Our Business Can Estimate To put it politely, software estimation has proven to be challenging. But to be frank, software estimation has proven to be a nightmare. Most organizations that develop software have lost all credibility with their clients when it comes to simple questions like "When will you be done?" and "How much is it going to cost?" In this fast-evolving industry, one thing is clear: Time hasn't given us a chance to improve our estimating skills. In this presentation, Tim Lister investigates the estimation issue, offers some suggestions, and promises to come up with some surprising answers to the question of whether anyone in our business can estimate.
|
Tim Lister, Atlantic Systems Guild, Inc.
|
|
Software Sizing: There is an Easier Way Project managers and software engineers need to accurately calculate delivery dates and resource needs for their software. This means they have to measure the size of the requirement, and estimate how much it will require in time and expense. But is there a sizing technique that's both effective and efficient? Popular sizing techniques such as the function point method can be difficult and labor intensive. However, there are alternative methods that produce quicker results, often without compromising accuracy. This presentation shares new ways to determine the size of your software deliverable while maintaining accuracy.
|
David Herron, The David Consulting Group
|
|
IS and IT Benchmarking: Current Status Are you having trouble making a business case for benchmarking at your organization? Mark Czarnecki delivers his benchmarking expertise in a presentation designed to help participants impact their corporate culture as well as their benchmarking abilities. He reviews the current status of information systems and technology benchmarking, and he explains current benchmarking theory. The presentation also covers generalized database sources for benchmarking.
|
Mark Czarnecki, The Benchmarking Network, Inc.
|