Business and System Analyst

Each year, organizations undertake an increasing number of critical projects. These projects may have a business focus, be technical in nature or a combination of both. A number of these projects are challenged from the start due to poor or incomplete requirements. There are many reasons for this, including:

  • Organizations have no formal method for identifying, understanding and documenting business requirements
  • Project stakeholders claim that they are too busy to take part in defining the requirements
  • Project teams feel that the business stakeholders are unable to clearly articulate what they want
  • Business stakeholders feel that project team members are unable to understand their needs and wants
  • Business stakeholders see the technology department as the owners of the requirements

 

Project Challenged Factors % of Responses
1. Lack of User Input 12.8%
2. Incomplete Requirements and Specifications 12.3%
3. Changing Requirements and Specifications 11.8%
The Standish Group, Chaos Report, 1995

 

In order to improve the success rate for complex projects, organizations must not only understand the importance of the requirements definition phase, but must also have an effective approach to manage and execute this important phase.

The Solution: A Smart Approach to Analysis

Smart PlanIT's consultants are experienced analysts who are able to efficiently translate business needs into technology requirements while managing stakeholder expectations. We recognize the importance of solid business requirements as a precursor to project success.

Smart Benefits

Benefits accruing to organizations engaging Smart PlanIT Business and Systems Analysts include:

  • Ownership - business stakeholders feel ownership as they are heavily involved in providing the requirements
  • Confidence in the process - business stakeholders have confidence since they were involved in the requirements gathering
  • Reduced project costs - 'rework' consumes on average 30% of a projects budget; better requirements gathering reduces rework
  • Shorter project duration - using an accelerated approach in the requirements definition phase is an opportunity to reduce overall project duration