|
Measure Customer and Business Feedback to Drive Improvement
Slideshow
Companies often go to great lengths to collect metrics. However, even the most rigorously collected data tends to be ignored, despite the findings and potential for improving practices. Today, one metric that cannot be ignored is customer satisfaction. Customers are more than willing to...
|
Paul Fratellone, uTest
|
|
How Experian Revolutionized Product Strategy and Management with Big Data
Slideshow
Agile discussions often focus on stories, backlogs, development, and testing. At Experian they also brought product strategy management and strategy into the agile fold to ensure their teams were in lock-step with customer requirements and priorities. That resulted in the delivery of...
|
Jeff Hassemer, Experian
|
|
On Agile Methods and the Rise of Lean Startup: An Interview with Arlen Bankston Arlen Bankston is a lean six sigma master black belt and certified ScrumMaster trainer. In the following interview with StickyMinds editor Jonathan Vanian, Arlen discusses the rise of the Lean Startup movement, tools to capture customer feedback, and what constitutes good metrics.
|
|
|
Do Your Demos Smell? In the agile world, there is a concept of “smells,” or symptoms that things aren’t going well. Introduced by Kent Beck and expanded on by practitioners, smells now describe problems involving adoption, coaching, design, code, and teams. When we see these symptoms, we can identify opportunities to improve.
|
|
|
Product Backlog Hygiene: Prepare to Be Groomed How do you start with a product backlog when you’re transitioning to agile? In this article, Darin Kalashian shows us how a cross-functional team at the product owner level creates a product backlog.
|
|
|
Not Just a Number: The Real Value of Metrics Metrics can be enormously helpful, but only if they’re used correctly. Abuse them, and they will drive dysfunction. Study the stories behind the data to find the real value.
|
|
|
Non-Pathological Software Metrics
Slideshow
As semi-scientific software professionals, we like the idea of measuring our work. In some cases, our bosses like the idea much more than we do. Yet, meaningful software development metrics are notoriously challenging to define, and many people have given up trying because metrics often...
|
Stephen Frein, Comcast
|
|
The Dangers of the Requirements Coverage Metric When testing a system, one question that always arises is, “How much of the system have we tested?” Coverage is defined as the ratio of “what has been tested” to “what there is to test.” One of the basic coverage metrics is requirements coverage-measuring the percentage of the requirements that have been tested. Unfortunately, the requirements coverage metric comes with some serious difficulties: Requirements are difficult to count; they are ideas, not physical things, and come in different formats, sizes, and quality levels. In addition, making a complete count of “what there is to test” is impossible in today’s hyper-complex systems. The imprecision of this metric makes it unreliable or even undefined and unusable. What is a test manager to do?
|
Lee Copeland, Software Quality Engineering
|
|
The Metrics Minefield In many organizations, management demands measurements to help assess the quality of software products and projects. Are those measurements backed by solid metrics? How do we make sure that our metrics are reliably measuring what they're supposed to? What skills do we need to do this job well? Measurement is the art and science of making reliable and significant observations. Michael Bolton describes some common problems and risks with software measurement, and what we can do to address them. Learn to think critically about numbers, what they appear to measure and how they can be distorted. Improve the quality of the information that we're gathering to understand the relationship between observation, measurement, and metrics. Evaluate your measurements by asking probing questions about their validity.
|
Michael Bolton, DevelopSense, Inc.
|
|
Transition to Agile: Large Technical Debt, Small Project When you transition to agile and you have a reasonably size codebase, chances are quite good that you’ve been working on the product for a while. You certainly have legacy ways of thinking about the code and the tests. Now learn how to work yourself out of the technical debt you have accumulated.
|
|