Business Analyst

 

Location: Baltimore

 

Education Level: BS

 

Hours: Personnel shall work an eight-hour day (normal business hours, but actual work hours to be changed), Monday through Friday

 

Personnel may be required to work past this time, on evenings, overnight, weekends, or Holidays as the work dictates.

 

Salary: 42 to 52$/hour

 

Minimum Requirements

Candidates for the Business Analyst positions shall:

·         Understand current and emerging IT products, services, processes, and methodologies, along with a continuing understanding of the business function and process.

·         Have an understanding of the BABOK.

·         Demonstrate at least five (5) years of experience with requirements elicitation and definition, requirements planning and management, gap analysis, requirement documentation, requirement verification and validation, conducting feasibility studies, preparing business cases, solution assessment and validation.

Duties and Responsibilities of the Business Analyst Candidates

The Business Analyst shall:

 

A)                Participate in the Project Preliminary Planning phase, which covers the receipt/review of initial project requests, refinement of the project request, and development of the business case and concept proposal.

 

B)                 Produce project feasibility and cost benefit analysis reports to assist MDTA executive management In determining whether a project should proceed.

 

C)                 Transition a project from idea or concept through preliminary planning phase to become a chartered project.

 

D)                Assist with project scope definition and management plan.

 

E)                 Have the ability to correctly identify project stakeholders and respective Subject Matter Experts (SME’s)

 

F)                  Facilitate an elicitation session with a large group of stakeholders.

 

G)                Understand and communicate information on the requirements development and management process to the project team.

 

H)                Have the ability to differentiate between modeling techniques to determine which is appropriate for a project (ie use cases, workflow, swim lanes, context diagrams ….).

 

I)                   Develop and utilize modeling tools and techniques to communicate with the stakeholders.

 

J)                   Develop, maintain and present a different requirement documents (Business, Functional, Non-Functional)

 

a.       Business Requirements are higher-level statements of the goals, objectives, or needs of the enterprise. They describe the reasons why a project has been initiated, the objectives that the project will achieve, and the metrics that will be used to measure its success. Business requirements describe needs of the organization as a whole, and not groups or stakeholders within it. They are developed and defined through enterprise analysis.

 

b.      Functional Requirements - describe the behavior and information that the solution will manage. They describe capabilities the system will be able to perform in terms of behaviors or operations - specific information technology application actions or responses.

 

c.       Non-functional Requirements capture conditions that do not directly relate to the behavior or functionality of the solution, but rather describe environmental conditions under which the solution must remain effective or qualities that the systems must have. They are also known as quality or supplementary requirements. These can include requirements related to capacity, speed, security, availability and the information architecture and presentation of the user interface.

 

K)                Develop, maintain and present test plan.

L)                 Develop, maintain and present test cases.

M)               Develop, maintain and present test scripts.

N)                Develop and maintain defect management.

O)                Conduct a quality review walkthrough of business requirements documentation.

P)                  Facilitate and obtain signoff on requirements documentation.

Q)                Implement and enforce a change management procedure for requirements documentation.

R)                 Comprehend basic to complex business issues; contribute to Information Technology projects by translating business needs into understandable requirements.

S)                  Operate as a spokesperson for the business departments..

T)                 Examine a business activity to help decide whether new IT solutions will improve productivity.

U)                Elicit and document existing business models and work flows with the applicable SME’s.

V)                Provide recommendations related to proposed solution.

W)               Deliver informative, well-organized presentations.

X)                Understand the role of the system in the big picture and provide ideas and recommendations regarding the evolution of the system and any project interdependencies to consider.

Y)                Using a variety of technical and analytical tools create and present cost specifications for possible improvements

Z)                 Produce high level outline designs or use cases to aid in the development and construction of requirements.

AA)           Provide client support and consultation for IT issues and make recommendations on applicable technology.

BB)            Identify the benefits of a project, potential project team members, project deliverables, and appropriate project performance metrics.

CC)            Identify initial performance measures that will be used to determine whether the project was successful.

DD)           Attend internal staff meetings as requested.

EE)         Facilitate communication and project meetings in the absence of the project manager.