Margarita Neumueller
ALDI Sued - IT Consultant
Mülheim, Germany
Margarita Neumueller started her apprenticeship in 2014, where her first experiences with the MS SQL Server started. After her graduation in 2017 she started as a Consultant for MS Business Intelligence and gained experiences in different projects with different focuses - frontend, backend, Cloud, On Premises...
Requirements Engineering became one of her main interests, because she identified a big gap in a lot of projects that failed. The requirements weren't clear documented or never questioned/analyzed, so in the end the customer was unhappy.
Links
Area of Expertise
Topics
Let's talk more about Requirements Engineering
Requirements are amongst the most important factors in successfully concluding a project. Not knowing what to do or in the worst case accidentally doing the wrong things, could lead to project failure.
When asked, customers will likely be sure what to do. But to be honest - they often don’t know what they want. Almost always specific solutions are requested, even the problem has not been determined correctly. You can’t rely on the words of the customer alone.
Data projects are especially tricky, because unlike process driven projects data is abstract to most customers.
So which tools can provide help with digging into the needs and problems of the customer? Who do you talk to? What are the required steps for a solution-minded requirement analysis?
This session will provide a quick insight into holistic requirements engineering on data-focused projects.
Problematic projects and what we can learn from them
At conferences we talk a lot about doing the right things and what this right things could be. But even though everyone made experiences with problems in projects - nobody I know was blessed with projects where everything was going perfect -, we talk rarely about failures and what to do, when everything is falling apart.
Thinking about my previous career and what experiences I made, I learned the most with a big gap in projects or situations, that were problematic. I didn't want to go through those failures again, so I learned what to do to prevent them.
But it is not neccessary that everyone has to go through the same failures, we can and should learn from each other.
This is the reason, why I want to talk about my worst projects in an interactive session and what concrete learnings I could make, hoping it encourages you to do the same.
You didn't found a good solution of your problems in projects in the past? This is also fine, let's discuss what could have been done. Maybe someone with a similar situation is there and did find a way to handle it.
So let's talk about our "Worst Of" projects and how to prevent them for us and for other.