Creating Customer Value with Quality Requirements

How do you know what to build of your customer wants a “secure solution with a good amount of flexibility and user-friendliness”? You don’t! Force the customer to be more specific!

Maximizing customer value is one of the most important guiding principles in agile development practices. After some years with experience with agile practices, we now see that an exclusive focus on value expressed as functionality can seriously undermine the quality of the software product. This manifests itself as bad usability, poor performance or unchangeable software.

This has led to a slightly stronger focus on code quality and software architecture to solve these issues. But in all project environments resources; time and money, are limited and the owners of the project initiative want value for money. Quality is also perceived as a technical or architectural issue not something the product owner should care (or know something) about.

It is much more difficult to measure quality compared to time, cost or functionality, so it’is hard to know if you’re delivering software with sufficient quality or not. And if you can’€™t measure quality it’is difficult to challenge your development team on it. This is where measurable quality requirements come to the rescue.

This talk suggests how you handle and formulate quality requirements in a way that lets the customer
* prioritize between different quality attributes
* prioritize between quality and cost
* measure if acceptable quality is delivered

I will also explain the clear distinction between two types of non-functional requirements, constraints (technology, design, architecture) and quality requirements.

Video producer:

2 thoughts on “Creating Customer Value with Quality Requirements

  1. Our website\downloads gives plenty of practical advice that Mario refers to from us in this video on quantifying any quality. And any value. See esp gilb essentials. CE book chapter 5 Scales of measure. Or mail me directly for free advice.

Comments are closed.


The 4 Pegs of Software Requirements Engineering

Bad software requirements can jeopardize projects. There is a considerable literature on software requirements, but practice is far behind: what passes for requirements in industry usually consists of a few use cases or user stories, which are useful but not sufficient for a solution. Can we fix requirements engineering (known in other circles as business […]

Read More

Collaborating With Stakeholders

To make UX research and requirements gathering more efficient and effective, you have to get everyone in the software development team and the user representatives involved. When the teams understand user concerns and usability issues, they become better at preventing problems.

Read More

Product Managers Best Practices to Build Highly Effective Teams

This talk shares product management best practices and experiences with you in hopes they will help you in your product development journey to build highly effective teams. It covers key topics including (a) working together, (b) managing and prioritizing the work, (c) customer discovery and readying stories, (d) measuring what and how we work, and […]

Read More

Copyright © 2009-2021 Martinig & Associates