The cloud and the rapid migration to mobile devices and the Internet of Things have made traditional software licensing schemes obsolete. Omkar describes new software monetization based on business, pricing models, and usage.
This article explains methods to build a team that will embrace "required work" and deliver robust software in a predictable fashion. It proposes a measure that helps calculate the throughput of an agile team by comparing work committed to work actually done.
Observing customers in a usability lab can be invaluable for improving product design. But, once your software leaves the lab, do you know what your customers are actually doing and whether or not your software meets their expectations? Learn how engineers on the Microsoft Office team apply a variety of software telemetry techniques to understand real-world usage, how the results drive product improvements, and how you can apply similar techniques.
Managers often use metrics to help make decisions about the state of the product or the quality of the work done by the test group. Yet, measurements derived from bug counts can be highly misleading because a "bug" isn't a tangible, countable thing; it's a label for some aspect of some relationship between some person and some product, and it's influenced by when and how we count ... and who is doing the counting.
Ever wondered what productivity experiments on factory workers in the early twentieth century have in common with today's adoption of agile practices? Lee sheds some light on the "process of process" and the importance of retrospectives as catalysts for change.
Just because a metric is easy to capture doesn't mean it is useful. The metrics that are really needed are the ones that can help you make good decisions. Find out how to establish a project dashboard with meaningful metrics that will guide your project safely to its destination without getting bogged down in an endless pursuit of unnecessary information.
An old adage says that you cannot manage what you cannot measure, but Mike Cohn thinks differently. Here, he offers suggestions on when to use metrics and when you can manage without, as well as some guidelines to help you choose your metrics carefully.
Typical metrics are used to predict an outcome by comparing plans to actual results. They are objective and don't influence what you are trying to measure. Biased metrics, on the other hand, are a valuable tool for deliberately altering behavior to improve the performance of a group. Find out how biased metrics can be used on your projects to pinpoint problems in specific areas and to influence people to fix them.
No one starts a project with the goal of failing, but some metrics experts claim that 80 percent of software metrics initiatives fail. Just as your software project has goals for success, you should have goals for success in your metrics initiatives. Find out what you can do to better your chance for success.