Stop calling requirements ‘non-functional’!

by May 24, 2023

Stop calling requirements ‘non-functional’!

You want deliveries that don’t function?

Why name it wrong? Call it what it is!

If you look closer at non-functional requirements, they fall into two groups:

1️⃣ Operational requirements 🚀

Just like Function requirements, it describes what users can observe at runtime: the behavior. But we focus more on how it does this, like Performance and Availability.

2️⃣ Developmental requirements 🛠️

Users can’t observe these, but they are also important. These are developmental qualities, requirements from the development team. Like Maintainability, Portability, and guidelines.

Change the conversation by doing this! 💡

Remy van Duijkeren

Remy van Duijkeren

Power Platform Advisor

Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.

Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).

Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.

Services:
– Strategy and tactics advise
– Automating and integrating

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

Backlog: The Black Hole of ideas

Backlog: The Black Hole of ideas Is your backlog turning into an ever-expanding universe of forgotten dreams? We all know that mix—a jumble of big ideas and tiny tasks waiting for their day in the sun. Some items linger for years. Why do backlogs grow? Because we...

read more

The Trade-off Between Budgets and Quality ⚖️

The Trade-off Between Budgets and Quality ⚖️ In my previous post, I talked about shifting from Estimates to Budgets for feature development 💡. Let's dive deeper. Using a Budget instead of an Estimate introduces a trade-off: Scope and Quality adjust to fit the time...

read more

Budgets instead of Estimates

Budgets instead of Estimates Estimating a feature is difficult and is often a guess (or even a lie). An Estimate is for a fixed scope. So, you need to think deeply how to implement the feature, before giving an Estimate. The business can then use the Estimate to...

read more