Business Analyst

Job Responsibilities

• Have a high-level overview of the business, its vision, and objectives. Understand how the Group Programmes team initiatives that the BA works on, contribute to these objectives and challenge when work does not align.
• Assist in defining and justifying (in business terms) business cases and invitations to tender. This will largely involve eliciting the business, functional and non-functional requirements that underpin the objectives of the initiative.
• Ability to identify the key stakeholders and SMEs who will be pivotal to the initiative’s success. Understand their motivations, preferences and their importance and influence on the success of the initiative. Ensure their views are considered and represented. The BA will develop an effective communication strategy and demonstrate the ability to flex their own preferences where necessary to build a rapport and increase the effectiveness of interaction.
• Ensure all stakeholder perspectives are considered, noting that not all stakeholders will be internal to LR. Improving client Experience and making LR easier to do business with are key goals for the organisation. The BA must develop an effective working relationship with the Customer Experience team to ensure existing pain points & opportunities are captured and impact of any changes are understood.
• Work with SMEs and other colleagues to iteratively understand and document ‘as is’ analysis and ‘to be’ designs, consider the impact from multiple perspectives (e.g. POPIT – people, organisation, process, information & technology). Be curious, proactive, challenge and ask why until the right level of detail and understanding needed is elicited and captured.
• Expertise in the preparation, facilitation and the write up of in person and online workshops and interviews. Ensure the valuable time committed by participants is maximised and key outcomes are achieved and documented.
• Capture & present analysis and designs using common BA Techniques including, functional & non-functional requirements, process models (BPMN), customer journeys and basic data modelling. Ability to create adhoc deliverables to best represent findings where these common models do not fit e.g. rich pictures, context diagrams, bespoke playbooks etc.
• Deliverables should be produced using standard templates (where these exist), with precision and an appropriate level of detail for the intended audience. The BA should establish key terminology to be used early in a given initiative, formalising this in a glossary with a definitions and acronyms (where relevant). The BA will promote correct use of terminology in deliverables, meetings, and workshops.
• Wherever possible seek out and use data to objectively to support your work e.g., number of clients/colleagues impacted by a proposed change, time taken to perform a specific task. In particular, when forming recommendations and priorities for focus.
• Proactively communicate and build a solid working relationship with the PM. Proactively flag, capture and propose mitigation to risks as they arise. Regularly reassess your BA approach, priorities, and workload, highlight challenges and potential solutions so that support can be provided where necessary.
• For initiatives that include a technology component, the BA will provide a link between business users, product teams and third parties throughout the development lifecycle and assist with the resolution of any queries related to BA deliverables.
• Knowledge and ability to support testing with a focus on providing a business (more than a technical) perspective. Examples might include supporting product & development teams gain a better understanding of the end-to-end process, business exceptions and business scenarios to be considered. There may be a need to be more hands on in supporting functional and user acceptance testing due to the business expertise the BA has developed during the initiative. The Business Analyst will not expect to be responsible for any technical, non-functional, unit or integration testing.