An In Process Analysis of The

Information Technology

Business Analyst Profession

The Business Analyst is the primary interface between the business and the Information Technology Department. this could be anyone internal to the business or it could be external such as customers. As the primary interface there are a wide range of responsibilities for the Analyst to perform.

The Business Analyst will report to a wide variety of people in the business. It ranges from a supervisor to senior level management. Along the way the Business Analyst will report to Information Technology Management who's money is being spent, to business stakeholders. These stakeholders include Project sponsors, project stakeholders.

The Business Analyst will provide a wide variety of services. These services include,

• Analyzing and initiation of project requests.

• Developing and managing project plans.

  • Ability to communicate Status of project.

  • Provide recommendations for team/activity efficiencies

  • anticipate tasks outside of the normally identified steps

  • provide recommendations and/or risks

• Requirements gathering and documentation.

  • Business Requirements

    • Process flows

    • Business Models

    • Activity Diagrams

  • Technical Requirements

    • Working knowledge of Technology

    • Work with Developers

    • Wire Frames

    • Site Maps

• Identify, Conceptualize, and Develop Business Solutions

  • conceptual modeling; ability to see the big picture and envision possible solutions

• Produces Release Notes or Schedules Demonstrations for New Functionality

• Acting as a Subject Matter Expert

• Solve problems of diverse scope where analysis of data requires evaluation of complex factors

• Test Plan Development

• Software Implementations

• User Training and Support.

• Public speaking

• Business writing

Analyzing and initiation of project requests.

Projects have their start when someone sees value in using information technology to create business value. All projects start with a business problem or opportunity. This is the point that a Business Analyst should be assigned to the business unit to help them create a Business Definition or a Business Case. At this point the business stakeholders will have a sometimes vague idea of what they want to achieve with a technology solution. In most cases this Idea will go through many iterations as more and more people become involved and more views are represented. If one exists a template of the Business Case document should be given to the stakeholders so they may begin in a structured manner to gather and record a definition of the problem and envisioned solution. Working with the project requesters the Analyst will drive the Business Case to include the problem or opportunity, the goals of the proposed project, a summary of the approach, cost estimates, and assumptions. It should also include a draft scope statement, both inclusive and exclusive. It should also include measures of success which should be clear and qualitative. Remember that if this project is implemented as you work toward the finish you will want a guide that explains your objectives. Your work will be measured against these success factors and you will want them to be easily understood in terms of whether you hit the goal or not. This process is used to turn the vague description into a project description. In this document it is incumbent to write the descriptions so subsequent readers will be able to understand the problem from the perspective of the business user. Many Analysts will overwrite this document but it should be a summary of information. Don't forget that further down the road there will be meetings that require your attendance to help the decision makers understand the nuances of the proposed project. This is also a time for the Analyst to begin to help stakeholders reconcile their views of the proposed system. So at this point it is a good idea to make the document represent a consensus of the participants. By having stakeholders participate in this process it will help with both reconciliation but also expectations. The final piece of the business definition document will be your recommendation. The two major pieces will be whether to proceed, and if so how to proceed. As a final note the Project Management Office will be reviewing your document. They will be reading for and basing recommendations on things such does this project appear consistent with organizational strategies? Does if follow technical organizational standards? And has it been appropriately reviewed to ensure that all issues have been considered?

Next Developing and Managing Project Plans.