Business Analyst with Crash Records, SDLC and government experience
Location: St. Paul, MN
Duration: 1-2 years
Positions: 1
Examples of Similar Work Performed
Examples should include deliverables showing both sample work plans and analysis documentation produced by candidate
Minimum Qualifications:
1. Bachelor’s degree from an accredited college or university in business, public administration or management information systems.
2. Four years progressively responsible professional experience in analyzing and interpreting business needs.
3. Two years experience applying recognized data processing concepts to business process planning and analyses.
Preferred Qualifications:
1. Experience working with topics related to Crash Records.
2. Experience with System or Software Development Lifecycle.
Project Tasks and Deliverables
Task 1 – Develop Business Requirements Documentation
The core deliverable of this engagement must be documented internal business requirements as
well as external user requirements that the Crash Records System project can use in meeting its
stated goals. Accomplishing this task involves activities including the following:
- Review of existing project documentation
- Interviews with key stakeholders and Subject Matter Experts as identified by the Crash
Records System project Working Committee
- Identify outdated processes and suggest improvements based on business needs
- Review of the State’s, the Department’s, and the Division’s vision and goals for project
management and architectural alignment
- Review the Office of Enterprise Technologies, Policies and Standards for Enterprise
Architecture and Accessibility; documents for a replacement to the current legacy system
must be addressed in a system solution.
Strategic Alignment: The degree to which the Crash Records project is consistent and compatible
with the State’s, Department’s, and the division’s mission, goals, and priorities, from business and
IT perspectives.
Project Constraints: include the contractual, resource, and operational factors within the project.
For example, staff, budget, schedule, vendor contracts.
Deliverables: Completed questionnaire(s)
Requirements documentation
Representations of Business Process Flows
Identify existing products that may meet the requirements (for instance, tools used by
other States)
Information necessary to inform decision making of buy versus build, including
recommendations
Task 2 – Presentation of Business Requirements
The business analyst will develop and deliver presentations of the business requirements to key
groups including, but not limited to, the Steering Committee, Traffic Records Coordinating
Committee, Crash Data Users Group, MnDOT and law enforcement agencies to ensure buy in and
verify stakeholders’ needs are documented.
Deliverables: Presentation media (PowerPoint slides, handouts, etc.)
Revised Requirements documentation (if necessary)
Task 3 – Act as Liaison to Technical Team
The business analyst will act as a business liaison to the State’s IT Project team to represent
stakeholders as the system requirements are developed by:
- Serve as a member of the Technical team as needed
- Review requirements to ensure that business requirements are represented as project
goes forward
- Act as a resource to Technical team to clarify requirements, reviewing with subject matter
experts as necessary.
No comments:
Post a Comment