Parveen Khan
3y ago
Welcome to my blog! I write about Software Quality
🗣️ Quiet a lot of times teams don't think or care about CFR's.
They are famously known as Non-Functional Requirements and it kind of reads as "Not Important" 😬
A lot of times there are assumptions around what CFR's are and how they can be implemented.
What is cross functional requirement?
A CFR specifies the criteria that can be used to understand the operation of a system rather than its functionality.
If you are interested to get the team to think and consider CFR's then you can try doing these things :
Talk about the difference between Functional and CFR's
Many times I have seen teams not being fully aware of what exactly is the difference between functional requirements and CFR's.
The best way to help team is by sharing the knowledge and sharing the awareness of how functional and CFR's are different.
As an example :
Functional requirements specifies about what a system should be doing by looking at the acceptance criteria.
CFR specifies about the operational requirements of the feature.
Collaborate with team and stakeholders
Collaborate with the entire team and stakeholders to think and decide about the CFR's that are required and applicatble to be considered as part the current work.
It helps in coming up with what CFR's are important and remember these would always be emerging as the product evolves.
Talk about how to measure
It's not about just coming up with CFR's but also thinking about how to measure to check they have been fullfilled or implemented. Brainstorm as a team to think about this for each CFR and document it.
For example : If you thinking about security CFR then think about what should be considered and implemented. Having vulnerability scans as part of pipeline, no PII in the logs, use burpesuit to do some security checks and so on.
Remember there are many different types of CFR's and they are equally important as functional requirements. So keep bringing this up and keep advocating about it!