Agile, Interviews, Software Development

“Non-functional measurement is not optional: It’s strategic” A Conversation with Fabrizio di Cola

Jun, 16, 2025 | Read 5 min.

Cover of Quanter article with interview with Fabrizio “Non-functional measurement is not optional: it is strategic”.

During the 1st Metrics Event organized by GUFPI-ISMA on May 16 in Rome, an event proudly sponsored by Quanter, we had the opportunity to speak with Fabrizio di Cola, Vice President of GUFPI-ISMA and Chair of the Non-Functional Sizing Standards Committee at IFPUG.

With his usual clarity and strategic vision, Fabrizio addressed the real challenges of introducing metrics into organizations, the evolution of the SNAP model, the collaboration with Quanter, and the role artificial intelligence can play in turning non-functional measurement from a barrier into a competitive advantage.

Interview by Julian Gomez, CDAIO of LedaMC and Quanter. In Italian, subtitles available in English and Spanish.

Fabrizio di Cola: It’s a pleasure.

F.C.: Okay, I’m ready.

F.C.: Well, you’re asking the wrong person because I’m an engineer in Italy. In engineering school, we joke that we make engineer jokes, right? But really, no.
You just need to be interested in certain topics. It’s about developing a kind of sensitivity that only comes through interest and passion for specific areas.

F.C.: Mainly, once a standard is agreed upon with a client, measurement allows you to establish a shared language, regardless of cultural differences between client and provider.
It lets you demonstrate costs without conflict and reduces friction on both sides. And how valuable is that to a company? A lot.

F.C.: The main obstacle for a company that doesn’t currently use metrics is culture.
It takes a significant cultural awareness effort, especially from leadership, because introducing metrics isn’t free, it requires organizational change, process change, and a real plan to achieve the goal of widespread usage.
The first step is to raise awareness among leadership, gain commitment, and implement a realistic rollout plan.

F.C.: Absolutely.

F.C.: From my experience, and also based on a survey we conducted at IFPUG, one of the key things we needed to address with SNAP was the definition of an estimation method.
Because, from my experience, introducing SNAP is a process, and we also need to estimate the non-functional part during the proposal stage, when creating the cost proposal for the client.

F.C.: And the collaboration with Quanter, along with the availability of its data, will help us define a structured way to estimate SNAP, which doesn’t yet exist.
We hope this partnership will lead to a method that enables both structured estimation and, in some contexts, a way to measure SNAP more quickly.
Combining these two aspects, we believe, will lead us to that outcome.

F.C.: As I mentioned before, introducing SNAP should be seen as an organizational change.
In daily work, what changes is not so much the measurement itself, but rather the skills of the measurer.
There’s a difference between a Function Point measurer and a SNAP measurer.

F.C.: Once you overcome that gap, measuring with SNAP is like measuring with Function Points.
The deliverables are different, the process changes slightly, but whether it’s Function Points or SNAP, the core measurement work is essentially the same.

F.C.: Yes, exactly. Once that gap is closed, and the SNAP measurer’s role doesn’t fully overlap with that of the Function Point measurer, the work is still completely analogous.

F.C.: Agile and DevOps are both cultural and organizational changes, just like metrics. Culture, right?
But companies don’t just want a flag to wave, they want real results.

F.C.: If you don’t measure in an Agile project and only measure the traditional ones, you’ll never know what results you’ve actually achieved.
For example, with story points, projects aren’t comparable.
You can’t define KPIs to understand how Agile or DevOps is performing.

F.C.: “It’s fine”, the perfect KPI.

F.C.: But with metrics, you can measure and create something objective and comparable, which lets you make strategic business decisions about how the framework, Agile or otherwise, is progressing.

F.C.: Certification plays a crucial role, especially in markets like Italy, where public tenders often require certification, and IFPUG uses it to recognize measurer quality.
It’s a key factor, not just to guide one company, but to guide the market toward adopting non-functional measurement practices.

F.C.: And with KPIs, absolutely.

F.C.: In my opinion, the main benefit of using AI as a metrics expert is that it’s like having a colleague beside you.
Someone you can interact with, who also does part of your job, and often faster.

F.C.: Maybe one day it will make coffee too. But for a measurer, it’s important because it boosts productivity, even just by speeding up certain tasks.
Also, from what I’ve seen, the measurer won’t be replaced by AI; their work will be enhanced by AI, which will increase productivity and improve quality.

F.C.: Absolutely, with some level of AI. Even the younger generation uses it for everything.

F.C.: No doubt.

F.C.: Yes, and here’s why: automated measurement depends on understanding the requirements. That’s what AI enables.
It can help both in justifying the measurement, linking it to the non-functional requirement, and in the measurement itself, because SNAP measures the solution to a non-functional requirement.
There are multiple deliverables that AI can analyze to automate part of the measurement.

F.C.: For an Italian, football is like choosing between your mother and your daughter…
But being from Rome, I can only support Lazio. I live in the neighborhood where Lazio was born, so absolutely Lazio.

F.C.: Thank you for the interview.

About the author

| | | | | |

Back