Senior Consultant - Principal Business Analyst

Oxford Government Consu•Frederick, MD

17h

About The Position

The Principal Business Analyst analyzes, develops, defines, and documents business requirements for enhancements, new functionality, and sustainment or maintenance of a large, complex Federal loan system. The role interviews key stakeholders and support staff and creates process flows, workflows, and narrative documentation of business requirements. In collaboration with other components of the software development life cycle (SDLC), the analyst identifies, documents, reviews, and finalizes requirements for use by designers, developers, and testers implementing functionality through scheduled software releases. The work is performed both independently and as part of a team. The analyst elicits requirements through documentation analysis, communication, interviews, JAD sessions, and other appropriate techniques, working with colleagues, Federal customers, and subject matter experts. The role decomposes high-level business and user requirements into functional requirements; identifies derived and implicit requirements; and defines business rules, quality attributes, external interfaces, constraints, and other nonfunctional requirements. Requirements are written clearly and concisely using standard templates. The analyst also participates in peer reviews and inspections to identify ambiguous, conflicting, incorrect, or incomplete requirements.

Requirements

U.S. citizenship.
At least five years of IT requirements analysis and development experience.
Bachelor’s degree.
Experience with student loan servicing software or financial systems.
Experience with Federal government contracts and comprehensive support to the SDLC.
Understanding of requirements elicitation, analysis, specification, verification, and management practices, and ability to apply them.
Strong analytical, planning, problem-solving, organizational, and communication skills.
Strong interpersonal skills to negotiate priorities and resolve conflicts among project stakeholders.
Ability to critically evaluate information from multiple sources, reconcile conflicts, decompose high-level information, abstract from detailed information, distinguish user requests from underlying needs, and distinguish solution ideas from requirements.
Ability to interact professionally with a diverse group, including executives, managers, Federal technical subject matter experts, and clients.
Ability to manage multiple tasks in a fast-paced, high-volume environment.
Understanding of financial systems and processing.
Independent thinking and decision-making skills.
In-depth knowledge of and experience with similar large-scale IT systems and the support required to operate, maintain, and enhance them.
Ability to conduct requirements-gathering meetings and interactive sessions with end users and other system stakeholders, facilitate discussions, and reach consensus or decisions.

Nice To Haves

Knowledge of and experience with debt management systems and software.
Knowledge of and experience with Federal student loans.

Responsibilities

Analyze, develop, define, and document business requirements for enhancements, new functionality, and sustainment or maintenance of a large Federal loan system.
Interview key stakeholders and support staff to determine business requirements.
Create process flows, workflows, and narrative documentation of business requirements.
Identify, document, review, and finalize requirements in collaboration with other SDLC components.
Elicit requirements through documentation analysis, communication, interviews, JAD sessions, and other techniques.
Decompose high-level business and user requirements into functional requirements and identify derived or implicit requirements.
Define business rules, quality attributes, external interfaces, constraints, and other nonfunctional requirements.
Write clear, concise, unambiguous requirements specifications using standard templates.
Participate in peer reviews and inspections of requirements documents, identifying ambiguous, conflicting, incorrect, or incomplete requirements.
Conduct requirements-gathering meetings and interactive sessions with end users and system stakeholders, facilitate discussions, and help reach consensus or decisions.