Time-boxed requirements discovery sessions have been around since 1979 under a variety of acronyms. They are as germane to the challenge of enhancing communicaiton between IT and the business community today as when they were first conceived.
Decomposing business and stakeholder requirements identifies functions and data the people need to do their job and that information technology can support.
Business analysis is about much more than just writing requirement. Unless the requirement is understood by the developers and the subject matter experts the same way, it will lead to problems.
Examples of good versus bad business requirements anno 2006
In a single sentence, this is what business analysis is all about – regardless who does it.
Making your requirements traceable is non-trivial, but so are the benefits associated with having them traceable.
The Requirements Solutions Group offers on-line and on-site training for all skills related to business analysis.
The general idea of JAD was to assemble a cross-functional team consisting of subject matter experts and systems analysts/developers. Put this group off-site under the direction of a skilled and motivated facilitation team, this group could define high-quality business and stakeholder requirements in a week.
