Implementing DevOps practices can significantly accelerate software releases while still assuring applications meet quality objectives. But DevOps can’t be bought, bolted on, or just declared. If you’re considering a move to a DevOps delivery model, here are six approaches for ensuring a successful DevOps adoption within an organization.
With the transparency of agile and the granularity of team-based metrics, it's important to be responsible in how you use your measurements. There are five principles Joel Bancroft-Connors adheres to when dealing with metrics: start collecting early and often, be consistent, stay focused, measure the project and the teams separately, and—most importantly—measure responsibly.
Whatever your feelings on metrics, organizations will expect them for your team. You don't want to measure only one aspect to the detriment of other information, but you also don't want to measure too many things and scatter your team's focus. Here are four metrics that balance each other out and help gauge an agile team's productivity, work quality, predictability, and health.
If you aren’t measuring the coverage your regression tests provide, you may be spending too much time for little benefit. Consider the value of your regression tests as you create and manage them. You need to be smart about the regression tests you maintain in order to gain the maximum value from the work put into creating, running, and analyzing their results.
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.
People often point to requirements documents and process manuals as ways to guide a new tester. Research into knowledge transfer, as described in The Social Life of Information, suggests that there is much more to the process of learning. Michael Bolton describes his own experiences on a new project, noting how the documentation helped ... and didn't.
In this interview, Larry Maccherone, the director of analytics and research at AgileCraft, explains how you can better use data within your software team. He digs into metrics and measurements within an agile environment and how to determine what data is valuable.
In this interview, TechWell CIO and consultant Mike Sowers details key metrics that test managers employ to determine software quality, how to know a piece of software's readiness, and guidelines for developing a successful test measurement program.
When software development teams work in waterfall environments, traditional performance management programs can help encourage personal development and innovation. However, Tina Rusnak says that when organizations move to agile, measuring performance takes on a new form that often causes...
The Mismeasure of Software: The Last Metrics Talk You'll Ever Need to Hear Lee Copeland claims that most organizations have some kind of metrics program—and almost all are ineffective. After explaining the concept of measurement, Lee describes two key reasons for these almost universal...
Committed to covering the latest trends and approaches for anyone investigating or implementing agile development practices, processes, technologies, and leadership principles, Agile Development & Better Software Conference West offers their 2013 interview series.