From problem to solution: helping people who know the problem and people who build the solution speak the same language.
Business analyst in data & AI, author, speaker and lecturer.
Requirement engineering
Two independent and complementary paths: learning to express a need, and learning to make it emerge.
Need, requirement, goal, system, context
The basic concepts, the different types of requirements, and the red flags to watch for.
Quality, continuity and decisions
Quality in requirement engineering, impact assessment and the decision process.
From goal trees to design thinking
Goal trees and KPIs, 5W2H, classification of requirements, prototyping and wireframes, MoSCoW.
About me
I’ve spent 20 years in requirement engineering, starting in business intelligence and working as BA, PM and developer on legal projects.
I’ve lived abroad for 15 years, I ride motorcycles, and I’m the author of two books.
Articles
Why requirements exist: avoiding the solution nobody needs
Need, requirement, goal: three words, three meanings
Red flags to spot before a project starts
Self-evaluation
Answer yes or no for your current project. Each “no” is a place to look closer.
Can you state the need behind each request?
Is every requirement traceable to an explicit goal?
Does each requirement describe what is expected, not how to build it?
Is the context of use written down?
Do the people who know the problem and the people who build the solution use the same words?
Books
Title of your first book
Short description and where to buy it.
Title of your second book
Short description and where to buy it.
Contact
For trainings, talks and collaborations:
polini.eva@gmail.com