Chandra Munagavalasa writes that because the requirements change over time, the product backlog is never complete. As the project progresses and more detailed information becomes available, the product backlog items and their rankings change continually. One of the many techniques available for ranking the product backlog is the Kano model.
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.
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.
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.
In this interview, Ellen Gottesdiener talks about her presentation at Agile Development Conference and Better Software Conference West 2014, the importance of having context for requirements, good ways to set value considerations for requirements, and the common mistakes of product owners.
In this interview, Mike Trites, a senior test consultant, talks about his upcoming presentation at STAREAST 2014, the future of metrics, the importance of improving the efficiency of your metrics, and even an interesting take on the old phrase that numbers never lie.
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.
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...
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...
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...
One of the most challenging problems that test managers face involves implementing effective, meaningful, and insightful test metrics. Data and measures are the foundation of true understanding, but the misuse of metrics causes confusion, bad decisions, and demotivation.