Session

From Requirements to Report - a practical guide on how NOT to spend months on requirement gathering

Every data project is 80% requirement gathering and 20% implementation.

Thinking back to your last 5 end-to-end data projects – how many meetings did you have to take to clarify requirements? How many times did you hear the phrases “that’s not what I asked for” or “that’s not what I expected” - “please redo”.

Requirement gathering feels like an art form, that takes forever. It is frustrating for everyone around because it goes back and forth, and it feels like you are getting nowhere with the request.

It does have a lot to do with the experience level of the requester, but sometimes it feels like it depends on the moon’s placement in the sky.

So what do you do? How does one get from frustration to results?

Let me walk you through my templates of requirement gathering process that cut “alignments” and “requirement clarification” by 50-60% per each project.

Kristina Nuppenau

STARK Group IT, Product Owner BI

Skanderborg, Denmark

Actions

Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.

Jump to top