Business Analysis using "Method H"
by Neville Turbit
Many Business Analysts start a conversation with users by asking what they do. The conversation tends to drift in no particular direction until a thread is sighted, then the BA follows that thread to the end. The next thread is fleshed out and a similar process followed. Hopefully, by taking enough random walks around the person’s job, sufficient information will be collected to come up with a requirement.
In this article Neville Turbit describes a more methodical approach to eliciting requirements called "Method H".
| Attachment | Size |
|---|---|
| Method_h.pdf | 113.74 KB |
Method H
Hello,
We are using similar sort of approach for our requirement elicitation. We are calling them as our "Shadowing " sessions. However, you can not capture all the business rules and functionality if the business process is very complex.