Methods and Techniques
From the outset, we emphasize the difference between a Business Requirement and a Software Requirement.
We approach the analysis of business processes with the presumption that the organization has adopted its processes for a reason. Even where there are industry-standard processes an organization can reasonably have its own variations for a number of reasons, especially if these variations support company success.
We actively encourage the active participation of client staff in all analytical activities. The primary reason is that client staff possess the knowledge that is required to build an information repository that will support the project being considered. So, this is, quite simply, the most effective way to proceed.
However, we also recognize that client staff have demanding responsibilities without the added burden of contributing to additional projects, even when they are authorized to do so. For this reason we conduct structured interviews and ensure that requests for information are appropriately coordinated to minimize duplication of effort.
The interviews and requests for information are designed to allow efficient creation of these relevant sets of business knowledge:
* forms: life cycles; related information content; usage and flow
* processes: relationships, dependencies, enablers and constraints
* events: triggers and outcomes
Where appropriate we verify conclusions reached via walkthroughs and test scenarios.
Last, but not least, we apply standard project management principles. Clear communication of progress and issues, and timely resolution, is a fundamental prerequisite for success.
|
|
