Business Analyst - I&T, Head Office Reitz at VKB Group

Overview:

The Business Analyst (BA) will be responsible for analysing the business needs of clients and stakeholders to help identify business problems and propose solutions. Within the systems development life cycle domain, the BA will work as a liaison among stakeholders to elicit, analyse, communicate and validate requirements for changes to business processes, policies and information systems. The BA will understand business problems and opportunities in the context of the requirements and recommends solutions that enable the organisation to achieve its goals.

Responsibilities:

• Guide stakeholders on devising effective and efficient approaches to achieving project objectives
• Identify and resolve issues
• Manage risks and provide input to the risk management process
• Liaise with other project areas to coordinate interdependencies and resolve issues
• Liaise with various business units to determine requirements and resolve issues
• Identify business process improvement opportunities
• Identify and define business requirements
• Analyse and map business processes (current state/future state)
• Analyse processes and data to identify gaps or perform process or data mapping
• Prepare or provide input to business cases, feasibility assessments, etc
• Produce high quality documentation
• Report status and issues to the Project Manager(s)
• Contribute to enterprise architecture development from a business needs perspective

Deliverables:

The BA will prepare or assist in the preparation of the following key deliverables:

• Business Requirements constitute a specification of what the business wants. This is usually expressed in terms of broad outcomes the business requires, rather than specific functions the system may perform. Specific design elements are usually outside the scope of this document, although design standards may be referenced.
• Functional Requirements describe what the system, process, or product/service must do to fulfil the business requirements. Note that business requirements can often be split into sub-business requirements and many functional requirements. These are also called System Requirements.
• Non Functional Requirements are requirements that cannot be met by a specific function, e.g. performance, scalability, security and usability requirements. These are often included within the System Requirements, where applicable.
• Report Specifications are reporting requirements such as the purpose of the report, justification of the report, report attributes and columns, or runtime parameters.
• Traceability Matrix is a cross matrix that traces the requirements through each stage of the requirements gathering process. High level concepts will be matched to scope items which will map to individual requirements which will map to corresponding functions. This matrix should also take into account any changes in scope during the life of the project. At the end of a project, this matrix should show each function built into a system, its source and the reason that any stated requirements may not have been delivered.

Skills:

• Leadership, to structure work and information for use by management and developers, set priorities and manage the work to those priorities, and meet deadlines.
• Relational, to develop good professional relationships with clients and internal staff, and represent the organisation in a professional and positive manner.
• Interviewing, to talk with individuals and groups about their needs and ask the right questions to surface essential requirements information.
• Listening, to understand what people say and to detect what they might be hesitant to say.
• Analytical, to critically evaluate the information gathered from multiple sources, reconcile conflicts, decompose high-level information into details, abstract up from low-level information to a more general understanding, distinguish presented user requests from the underlying true needs, and distinguish solution ideas from requirements.
• Facilitation, to lead workshops, meetings and other forums to achieve a desired outcome.
• Observational, to validate data obtained via other techniques and expose new areas for elicitation.
• Communicating, to articulate, both verbally (Afrikaans and English) and in written (English) form, information effectively to customers, marketing, managers, and technical/developer staff.
• Organisational, to work with the vast array of information gathered during elicitation and analysis and to cope with rapidly changing information.
• Interpersonal, to help negotiate priorities and resolve conflicts among project stakeholders (such as customers, product management, and engineering).
• Modelling, to represent requirements information in graphical forms that augment textual representations in natural language, including using modelling languages already established in the development organization.

Qualifications:

• A Bachelor’s degree in computer science, engineering, math or technical discipline preferred or equivalent experience required.
• 3-5 years of business analysis, business process, systems and development experience (preferred).
• Expert knowledge of requirements elicitation, analysis, specification, verification, and management practices and the ability to apply them in practice.
• Familiarity with requirements engineering books and resources requirements engineering and its place within the software development life cycle in a team environment.
• Ability to work constructively as an individual or in groups with minimal supervision. Understands and can apply business analysis methodologies in a complex multi-project environment.

Closing Date: 26th, May 2022