Job Title: Business Analyst 3/BA3
Interview: Onsite only- local candidates. Please submit resumes in a word document and remove all candidate personal information (phone,address,email) and vendor information (logos). Please do not submit candidate recently submitted/ for recent DOT BA3 openings. Check with candidates prior to submitting.
Will close to submissions on: Wednesday 9/20 @ 10AM
PLEASE DO NOT reach out to ANY individuals at ODOT regarding this posting nor candidates for this posting. All questions/comments/etc. must be directed to the MSP Team, specifically, Andy Hovest. Thank you in advance for your cooperation and support on this.
Job Classification:
Business Analyst 3 (BA3) - 2 Positions
Role:
The BA3 is requested from October 2, 2017 to June 30, 2018 (1500 hours)
ALPS Project:
DOT Staff Augmentation
The candidates will be supporting The Ohio Department of Transportation’s PMO.
MBE/Open Market:
Open Market
Requirement Description:
. Work with business units as well as internal and external stakeholders to gather requirements, using techniques like interviews and requirement gathering sessions.
. Elicit, analyze, document, and communicate business requirements as well translate them into more detailed user stories and/or use cases, and other functional requirements documents such as process flows, screen mock-ups, gap analysis (also known as Business Requirements Documents)
. Engage various internal and external business units to validate the business processes and define solutions requirement.
. Create documents and other artifacts to promote sustainable knowledge management within the organization.
. Work closely with the program manager, project manager and senior business analyst.
. Engage members of the Software Production team to:
- Identify potential technical constraints, dependencies, assumptions, non-functional requirements, and transition requirements associated with a new solution.
-Define ownership, ongoing support and maintenance expectations associated with a new solution.
-Understand decommission or deprecation tasks related to the existing permit management systems.
. Engage members of the Database team to:
-Identify potential technical constraints, dependencies, assumptions, non-functional requirements, and transition requirements associated with a new solution.
-Determine data migration and/or data conversion strategies.
-Understand regulatory compliance and data security.
-Understand data storage requirements.
-Understand data warehousing or reporting needs.
. Engage members of the Infrastructure team to:
-Identify potential technical constraints, dependencies, assumptions, non-functional requirements, and transition requirements associated with a new solution.
-Define environments needed (e.g. production, test, dev, others).
-Define hardware needed based on projected business volumes.
-Understand level of integration required with other ODOT systems.
-Decommission of existing environments or hardware.
Experience:
. Experience conducting Facilitated Workshops for requirements analysis.
. Experience creating workflows using formal notation such as the Business Process Modeling Notation (BPMN).
. Knowledge of formal requirements gathering methodologies.
. Experience developing Business Requirements - project initiation document, what the needed achievements will be, and the quality measures.
. Experience developing Functional requirements - describe what the system, process, or product/service must do in order to fulfill the business requirements.
. Experience developing User (stakeholder) requirements - are a very important part of the deliverables, the needs of the stakeholders will have to be correctly interpreted. This deliverable can also reflect how the product will be designed, developed, and define how test cases must be formulated.
. Experience developing Quality-of-service (non-functional) requirements - requirements that do not perform a specific function for the business requirement but are needed to support the functionality. For example: performance, scalability, quality of service (QoS), security and usability.
. Experience developing Report Specifications - define the purpose of a report, its justification, attributes and columns, owners and runtime parameters.
. Experience developing Requirements Traceability Matrix - a cross matrix for recording the requirements through each stage of the requirements gathering process.
Strong organization and writing skills.
. Experience developing graphic representations of complex business processes.
. Technical skills focusing on Systems Analysis roles.
. Experience in a leadership role as a Business Analyst.
Mandatory Requirements/Time:
. 7 years’ experience in the analysis, documentation of business requirements functional and non-functional
. 7 years’ experience creating application prototypes and screen mockups
. 7 years’ experience creating graphical representations of complex business processes
. 7 years’ experience in using Microsoft products; Visio, PowerPoint, Excel and Word
. 7 years’ experience facilitating workshops for requirements gathering
. 5 years’ experience managing requirements on several projects at the same time
. 7 years’ experience in analyzing data elements of enterprise applications; determining how the data elements relate to each other
. 6 years’ experience with business process modeling methods and techniques
. 7 years’ experience performing Gap analysis As-Is/To-Be for large applications
Desired Skills/Time:
None
