home

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".

AttachmentSize
Method_h.pdf113.74 KB

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Method_H improvement by hirondel
Method H by modern_ba
Shadowing... by fifedog
Shadowing... by modern_ba
Efectiveness by neville.turbit
Model H by charbor
Method H by dtegart

    Sponsored Announcements & Special Offers

Are Your Processes Making You See RED?
Learn how to save Time, Cost and Heartburn!
Register for our OnDemand Webinars ($150 per webinar):
* Essentials of Process Mapping
* Eliminating Non-Value Added Activities

These pre-recorded e-Learning modules are based on time-tested seminars that are sponsored by prestigious universities from coast to coast. For more information, call us at 800-510-2117. Orion Development Group is the premier strategic process management training and consulting firm in America. For more information

view counter

Iterative Requirement Management – Just Got Easier
Write effective functional specs, use cases or user stories. Elicit, manage and elaborate software requirements. Communicate iterative change. Discover how AppLife DNA can enable iterative requirements elicitation and allow your team to reap the benefits of a living requirements document. You will see the difference. Take a 30-day FREE TRIAL

view counter
© 2007 Requirements Networking Group All rights reserved. contact | advertise | privacy
Requirements Networking Group