Business analysis projects must always remain business focused.
Many so-called "business analysis projects" are not BA projects at all.
Instead, they focus on application system problems and technical issues
rather than trying to understand the business goals,
objectives, problems and opportunities. These misguided projects
"jump ahead", make erroneous assumptions and focus on technical solutions
without a sufficient understanding of the true business needs. This
inevitably results in a "disconnect" between the business and the IT
department.
The business analyst can prevent business analysis projects from being
"hijacked" by technology centric individuals by always focusing on "what" the business does and
"what" information is needed. The business analyst should discourage
project participants from focusing on application system solutions
prematurely. Non-technical business requirements must be clearly
defined, documented and signed-off before technical solutions are
contemplated.
On most business analysis projects, however, there will be a limited need to
examine (physical) forms, application system interfaces, databases
operational procedures, etc. The focus of the business analysis project,
however, must always remain on the business; not on the physical world.
