Business Analyst - The Panther Group
Augusta, ME 04330
About the Job
Skill 1: Experience with user stories and test cases
Skill 2: Experience working within State and Federal projects
Skill 3: Writing Test Plans and executing Test Cases
We are hiring a Business Analyst to join our project team to assist in supporting the life cycle. You will report directly to the Project Manager. Your main tasks will include user stories and test Cases, performing detailed requirements analysis,
documenting processes. To succeed in the role, you should have a natural analytical way of thinking and be able to explain difficult concepts to non-technical users.
The Business Analyst will partner closely with the various IT support teams to define requirements that will inform the project's goals.
The three major areas of the Business Analyst's responsibilities will be:
Collaborate with the Project Manager to build a path to success and to define risk mitigation strategy when risks arise
Development of future-state business process models to address roadblocks, challenges, and opportunities
Develop clear and concise functional and technical requirements (user stories and acceptance criteria) to be used for solution planning
Key Responsibilities: Role Description
Conducting Facilitated Workshops for requirements analysis.
Creating workflows using formal notation such as the Business Process Modeling Notation (BPMN).
Knowledge of formal requirements gathering methodologies.
Developing Business Requirements - project initiation document, what the needed achievements will be, and the quality measures.
Developing Functional requirements - describe what the system, process, or product/service must do in order to fulfill the business requirements.
Developing User (stakeholder) requirements - are a very important part of the deliverables, the needs of the stakeholders will have to be correctly interpreted.
Developing Quality-of-service (non-functional) requirements - are 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.
Developing Report Specifications - define the purpose of a report, its justification, attributes and columns, owners and runtime parameters.
Developing Requirements Traceability Matrix - a cross matrix for recording the requirements through each stage of the requirements gathering process.
Skill 2: Experience working within State and Federal projects
Skill 3: Writing Test Plans and executing Test Cases
We are hiring a Business Analyst to join our project team to assist in supporting the life cycle. You will report directly to the Project Manager. Your main tasks will include user stories and test Cases, performing detailed requirements analysis,
documenting processes. To succeed in the role, you should have a natural analytical way of thinking and be able to explain difficult concepts to non-technical users.
The Business Analyst will partner closely with the various IT support teams to define requirements that will inform the project's goals.
The three major areas of the Business Analyst's responsibilities will be:
Collaborate with the Project Manager to build a path to success and to define risk mitigation strategy when risks arise
Development of future-state business process models to address roadblocks, challenges, and opportunities
Develop clear and concise functional and technical requirements (user stories and acceptance criteria) to be used for solution planning
Key Responsibilities: Role Description
Conducting Facilitated Workshops for requirements analysis.
Creating workflows using formal notation such as the Business Process Modeling Notation (BPMN).
Knowledge of formal requirements gathering methodologies.
Developing Business Requirements - project initiation document, what the needed achievements will be, and the quality measures.
Developing Functional requirements - describe what the system, process, or product/service must do in order to fulfill the business requirements.
Developing User (stakeholder) requirements - are a very important part of the deliverables, the needs of the stakeholders will have to be correctly interpreted.
Developing Quality-of-service (non-functional) requirements - are 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.
Developing Report Specifications - define the purpose of a report, its justification, attributes and columns, owners and runtime parameters.
Developing Requirements Traceability Matrix - a cross matrix for recording the requirements through each stage of the requirements gathering process.
Source : The Panther Group