Tech Business Analyst at a Leading UK Charity

As a Tech Business Analyst at Royal Voluntary Service, your responsibilities include translating business requirements into actionable user stories, conducting data analysis, and developing documentation for testing. You'll also engage in user acceptance testing and collaborate with various teams to ensure project deliverables meet stakeholder expectations and quality standards.

To apply for the Tech Business Analyst position at Royal Voluntary Service, candidates should possess 3-5 years of experience in business analysis, proven skills in writing epics, stories, and acceptance criteria, and familiarity with tools like JIRA, Confluence, and Excel. A solid understanding of data architecture and the testing lifecycle is also essential.

Candidates for the Tech Business Analyst role at Royal Voluntary Service should be comfortable using tools such as JIRA and ADO for project management, Confluence or Notion for documentation, and Figma or Miro for prototyping. Experience with data admin tools like Datagrip, along with proficiency in Visio, Excel, and Office applications will also be beneficial.

The team culture at Royal Voluntary Service for the Tech Business Analyst position is collaborative and inclusive. We value everyone's input and ideas, and foster an environment that promotes professional growth, continuous learning, and a healthy work-life balance through hybrid working options.

For the Tech Business Analyst position at Royal Voluntary Service, the salary is competitive, with a monthly payment of up to ZAR55,000, in addition to a private healthcare stipend of ZAR2,300/month. Employees also enjoy opportunities for professional development and the ability to contribute to a meaningful cause.

When gathering requirements, start by identifying stakeholders and conducting interviews or workshops to understand their needs. Use active listening and probing questions to extract detailed information. Document the requirements clearly, translating them into user stories for clarity and reference.

A user story defines a user's need in a simple, relatable format, usually structured as 'As a [type of user], I want [goal] so that [reason].' This helps teams understand user requirements better and ensures that the development aligns with users' needs and expectations.

I prefer Agile methodologies, such as Scrum or Kanban, as they facilitate flexibility and incremental development. Agile allows for regular feedback and adaptation, which I find crucial for managing stakeholder expectations and ensuring project success.

To maintain clarity in documentation, I follow best practices such as using simple language, consistent formatting, and clear headings. I also regularly review my documents for accuracy and completeness, and I seek feedback from team members to ensure understanding.

In my previous roles, I designed logical data models and analyzed data relationships to support business requirements. I collaborated with technical teams to ensure database design alignment and utilized tools like Excel and Datagrip for data manipulation and reporting.

To navigate conflicting stakeholder requirements, I facilitate discussions and hold workshops to uncover the underlying motivations and priorities of each stakeholder. This permits me to find common ground and propose solutions that align with the organization's goals.

For effective user acceptance testing, I develop comprehensive UAT plans and collaborate with stakeholders to define clear test cases that cover all scenarios. I also ensure that users are involved throughout the process to gather their feedback and make necessary adjustments.

I am highly proficient in using JIRA for project tracking, backlog management, and sprint planning, as well as Confluence for documentation and collaboration. I leverage these tools to facilitate project transparency and enhance team communication.

My approach to managing multiple priorities involves effective time management and organization. I prioritize tasks based on urgency and stakeholder impact, utilize digital tools for task tracking, and maintain open communication with my team to align on deliverables.

In a previous role, I analyzed a cumbersome reporting process that involved multiple hand-offs. By streamlining the data collection phase and introducing automated reporting tools, I reduced the reporting time by 50%, significantly improving efficiency for the stakeholders.