DOT is looking for a BA3 for a 2080-hours assignment.
Local candidates are highly preferred. ONLY ONSITE INTERVIEWS will be conducted. Do not submit candidates unavailable to interview onsite.
Posting will close to submissions on Monday, 6/18 at 10amEST
PLEASE DO NOT reach out to ANY individuals at ODOT regarding this posting nor candidates for this posting. Thank you in advance for your cooperation and support on this.
Job Classification: Business Analyst (BA3)
Role: The BA3 is requested from August 1, 2016 to June 30, 2017 (2080 hours)
ALPS Project: The candidate will be supporting The Ohio Department of Transportation’s Road Weather Information System (RWIS) and the Global Position Systems/Automated Vehicle Locator (GPS/AVL) projects.
MBE/Open Market
MBE
Requirement Description:
Work with business units and other 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)
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.
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
Description of Duties:
50% of Total Work Effort: 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)
40% of Total Work Effort: Work with business units and other stakeholders to gather requirements, using techniques like interviews and requirement gathering sessions
10% of Total Work Effort: Work closely with the program manager, project manager and senior business analyst
