07-12-2021 | Mom, Dad... Where do requirements come from?
In this talk we explore the steps needed to discover the right requirements. The work needing to be done, to make a requirement "required". Work that is done before you add something to "the backlog". Steps that are often skipped, resulting in digital products that nobody wants... And you do not want that, do you?
About the speaker - Pieter Hens
Pieter has been working for over 15 years in a software product development and analysis setting. First, as a researcher in the area of Business Process Modelling, for which he received a PhD at the KU Leuven, later as an agile and lean practitioner.
Pieter has taken up roles as a business and functional analyst, project manager, product manager, coach and team lead in projects of various sizes (from small to multi-team efforts). He specialises in the full range of software product management: product strategy, discovery and development.
As an agile and lean adept Pieter speaks and trains on a professional and academic (KU Leuven) level: agile analysis, agile project management and lean product management. In 2019 he founded Gokotta, where his mission is to spread the "product-mindset": build/do the right things for the right reasons for the right people.
I have been in this situation. Have you?
You received a list of requirements. Things to build in your software product. You have a team of extraordinary developers, relentlessly working to create the requested software. You did it! The product was delivered on-time on-budget. Time for a party! Yes?
However, after releasing the product, you realise no-one is using it. Or using it differently than intended. There is resistance. It does not really solve the right problem and does not really help the end-user or company moving forward. The requirements were all wrong...
Where did these "requirements" even come from? Who made them up? Why was the given requirement even "required"? Such a strong word, isn't it, "required"? What even makes a requirement "required"?
These are all valid questions. A lot of work goes into discovering the right requirements for the right problem. Requirements are not just laying around, ready to be "gathered".
Business Analyst, Functional Analyst, Agile coach, Product Owner, Product Manager, Agile Project Manager, Developer, ... everyone involved in "gathering and analysing requirements".