HBITS-08-14930-Business Analyst-Senior

About the Role

This position is part of the SLA Online Payments project. The consultant will prepare, conduct, and document the results of requirement elicitation activities, apply critical thinking to identify process improvements, and confirm findings with internal and client resources.

Responsibilities

• Participate with the business to understand and define problems, leveraging validated scope to maintain project focus.
• Determine how to capture and document requirements based on the development methodology used for the business system.
• Meet with stakeholders, subject matter experts, process owners, and users to elicit and document needs, expectations, constraints, and external interfaces using methods such as brainstorming, document analysis, facilitated meetings, focus groups, interface analysis, interviews, observation, prototyping, requirements workshops, reverse engineering, and survey questionnaires.
• Ask targeted questions to surface essential requirements information and define constraints for verification and validation.
• Build consensus among stakeholders regarding business issues and requirements.
• Develop business requirements by translating needs, expectations, constraints, and interfaces into a format understandable to both clients and technologists.
• Develop solution and solution component design requirements, deriving requirements from architectural/design decisions.
• Define quality attributes, constraints, and other non-functional requirements.
• Collaborate with developers and business subject matter experts to analyze requirements, design tradeoffs, and priorities.
• Establish and maintain relationships between requirements for change management and requirements allocation.
• Allocate solution component requirements and document relationships among them.
• Identify and develop requirements for interfaces and act as a knowledge source for architects, developers, and testers.
• Obtain commitment to requirements from project participants, including eliciting requirements prioritization.
• Manage requirements scope and changes as they evolve during the project.
• Maintain traceability from requirements through testing and identify project work and requirements inconsistencies.
• Assess change requests as either expanded scope or undocumented requirements and place them in the change control process.
• Evaluate information gathered from multiple sources, reconcile conflicts, and transform high-level information into details or vice versa.
• Analyze requirements to ensure they satisfy higher-level objectives and are complete, feasible, realizable, and verifiable.
• Identify key requirements influencing cost, schedule, functionality, risk, or performance.
• Present requirements in written, verbal, visual, and graphical forms to communicate effectively with the required audience.
• Analyze operational concepts and scenarios to refine business needs, constraints, and interfaces, discovering new requirements.
• Collaborate with the testing lead to develop requirements-based testing strategies that validate the resolution of business problems.
• Manage defects by assessing their disposition and assigning them to the appropriate process for resolution.
• Lead the establishment and implementation of standard operating procedures for effective requirements engineering, including continuous improvement of the requirements process.
• Recommend tools and processes to improve the effectiveness and efficiency of all Business Analysts.
• Implement ways to reuse requirements across projects and lead peer reviews and governance activities to ensure consistency in requirements work products.
• Mentor less experienced business analysts to drive consistency and growth.
• Guide projects involving multiple business analysts, setting direction for requirements elicitation and documentation.
• Determine metrics for monitoring business analysis work.
• Build trustworthy business relationships with stakeholders and business management.
• Partner with clients on business case preparation, project prioritization, and technology roadmaps.
• Facilitate discussions between business and technologists to identify potential technical alternatives and innovative solutions.
• Resolve problems to ensure clients receive prompt and efficient service.
• Identify stakeholders and plan communications with them, defining roles and responsibilities in the business analysis effort.
• Develop estimates for business analysis tasks and plan how requirements will be approached, traced, and prioritized.
• Remain an active participant on assigned projects through to closure.

Qualifications

• Senior-level Business Analyst experience (60–84 months), capable of working independently and providing guidance to others.
• 72 months of experience in requirements gathering and business analysis, producing written documentation of requirements, system design, and implementation.
• 72 months of experience determining how to capture and document requirements based on development methodology, meeting with stakeholders, SMEs, process owners, and users to elicit needs, expectations, constraints, and external interfaces.
• 72 months of experience developing business requirements by translating needs, expectations, constraints, and interfaces into formats understandable to both clients and technologists.
• 72 months of experience developing solution and solution component design requirements, defining quality attributes, constraints, and other non-functional requirements.
• 72 months of experience establishing criteria for requirements evaluation and acceptance, managing requirements scope, and obtaining commitment from project participants.
• 72 months of experience in requirement analysis and validation, ensuring requirements are complete, feasible, realizable, and verifiable, and identifying key requirements influencing cost, schedule, functionality, risk, or performance.
• 72 months of experience preparing and presenting requirements in verbal, written, visual, and graphical forms.
• 12 months of experience in application testing, planning, and defect tracking, collaborating with testing leads to develop requirements-based testing strategies.