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! 💡

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

Scrum conceals bad teams.

Scrum conceals bad teams. Far too often, we confuse Scrum with a magic wand that transforms any team into a high-performing 'dream team'. It's tempting to believe that the sprint system, with its regular completion and initiation of tasks, gives us an agile and...

read more

🚀 Process Automations in Microsoft Loop!

🚀 Process Automations in Microsoft Loop! Now you can create Power Automate-backed rules to streamline repetitive tasks in your Loop table. See Loop is slowly...

read more

You don’t control the truth in Production!

You don't control the truth in Production! Now a days multiple teams/projects are working on the same Dataverse production environment. So thinking you can manage the complete production truth in your ALM pipeline is strange. Not every environment is 💯 equal to...

read more
Share This