IIBA Waterloo Wellington Chapter: May 29, 2013
So You Think You Can Elicit Requirements
Consider these sobering statistics:
- 60% – 80% of project failures can be attributed directly to poor requirements gathering, analysis, and management (Meta Group)
- Up to 80% of budgets are consumed fixing self-inflicted problems (Dynamic Markets Limited 2007 Study)
We spend so much time fixing the solution; we don’t have time to fix the problem. The Business Analyst and the Project Manager are often at the end of the blame stick. But most of the time, they are not the cause.
There are two fundamental factors that lie at the root cause of these sad statistics. This presentation/workshop explores those two root causes. But more than that, it provides you with a framework that addresses both and more.
Together we’ll explore the Relational Process Model (RPM), a methodology-independent framework for expressing, sharing, and retaining business process knowledge.
RPM is both simple and complex. It can be understood and deployed incrementally and locally to minimize risk. It doesn’t invalidate your current skills. Instead it amplifies them, making you more competent and successful regardless of your level of experience.
So if you need to find out the true and root cause for so many requirements issues, challenges, and failures, join us and let’s learn together. Remember, sometimes it’s the paradigm, not the people that needs to be changed.
IIBA Waterloo Wellington