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

AI isn’t asking questions. It’s just making assumptions.

AI isn’t asking questions. It’s just making assumptions. In consulting or sales, you learn fast: What customers want isn’t always what solves their problem. They ask for solutions they know based on limited knowledge. Experienced consultants do something else: They...

read more

Cancel Culture in IT: How Codes of Conduct Became Weapons

Cancel Culture in IT: How Codes of Conduct Became Weapons Cancel Culture is happening in major communities to developers and contributors, like the: Linux Kernel C++ Standard Committee Python NixOS openSUSE Godot And the reasons? Completely absurd: Being Republican...

read more