Objective Oriented Requirement Analysis

In today's economic crunch, there is absolute need of executing projects for value. There are different successful methodologies (Lean six sigma, CMM, Kaizen, TQM etc) practiced by industry. Definitely, all these techniques/methodologies are helping project managers and other stakeholders to execute projects for value.

As a business analyst, I would like to propose a tool/technique for one of the most critical knowledge area of business analysis, Requirement Elicitation.

I had invented/discovered this technique during my one of previous assignments in South Africa and which was much appreciated by business and technical community over there. I named it as “Objective Oriented Requirement Analysis”. I will share few thoughts about this tool in this blog.

Before sharing these thoughts, I would like to mention one thing, the methodology is still in conceptual stage, I might come up some tool in near future.

Objective Oriented Requirement Analysis
Every project has one or more qualitative and/or quantitative goals or objectives to improve or automate business functions/processes. This is also true for product.

Currently, OORA is in matrix form.

How to use OORA matrix
1. On horizontal scale, jot down project objectives/ expected outcomes from this project
2. On Vertical scale, jot down business functions/process relevant to the project
3. All other cells represent impact of business functions on project output in the form of Question & Answer
The advantage of this matrix is
1. Snapshot view of all business requirement
2. Answers all alternate and exceptional flows
3. Covers most of business scenarios
4. Helps Business Analyst to approach business users with framed question
5. Works as checklist while transforming business requirement into use case form

Appreciate your inputs/thoughts on this blog