Helping Business to Articulate Problems and to Identity Solution Options

Helping Businesses Articulate Problems and Identify Solutions - from analysis to desired outcomes

From acquiring simple applications to the development of a full software solution or process improvements, business unit transformations or other organisational changes, the business analysis discipline ensures that the right solution is implemented in each of these.

Business Analysis is part of the Initiation Phase of a product development project management lifecycle.

Some of the reasons for project failure are

1. Gaps in requirements
2. Inability to convert 'vision' and 'concepts' into useful business requirements
3. Not getting project owners to acknowledge actual requirements and signing these off
4. Prototyping without fully understanding requirements and desired project outcomes
5. Not baselining requirements and scope to allow for change control
6. Poor testing and quality assurance

These 6 reasons for failure are by no means comprehensive and there are many more reasons for failure. However, these are the tasks typically carried out by a business analyst.

Both the Scope and the Requirements of a Project belong to the Scope Management process in a project methodology. Project requirements reflect the needs and expectations of it's key stakeholders - the project sponsor, project owners, business unit managers etc. The Scope Statement on the other hand, is a definition of the boundaries of the work that is to be carried out, the project deliverables, exclusions and the acceptance criteria.

When stakeholders can clearly see, appreciate and sign-off the Project's Requirements and it's Scope, they will continue to champion and support the Project till completion.