What are the responsibilities and job description for the Business Analyst position at Galent?
Job Description/ Responsibilities
Business Analyst
• Business Analyst (BA) is responsible for owning the backlog. They will work closely with the Product Lead and Technology Owner on prioritizing, creating and refining the backlog. They are proficient at story writing to support both business and technical requirements to support feature development, Production stability, security and resiliency requirements. The BA is also responsible for testing and accepting stories and prioritizing the work. The BA would work with the Product Team, SMEs and the Engineering Teams to document and prioritize the backlog and include technical notes that support the implementation. The backlog includes all work the engineering team will implement including Product features as well as security, scalability, resiliency and software version updates.
Responsibilities
• Working with the Product Lead and Technology Owner this resource will create and prioritize the backlog.
• Identify and engage all impacted stakeholders or stakeholder groups; create an open communication channel with all Business and Technology stakeholders
• Own and manage the product roadmap (set of business goals) working closely with the Product Lead and Technology Owner
• Manage intake requests, including making sure all requests are reviewed, prioritized and as appropriate added to the backlog
• Ensure the needs of all stakeholders are identified and acknowledged
• Prioritize appropriate stakeholder requests for development on the Product Backlog
• Collaborate with the engineering team to identify technical, non-functional requirements and resiliency requirements. Prioritize these stories on the Product Backlog, with input from the Product and Engineering teams, alongside stakeholder requests
• Able to work independently to document the business requirements (both front and back end) that are independent of the technical implementation
• Define acceptance criteria for user stories that addresses positive and negative use cases and defines the scope of the story
• Plays a key role in release planning
o Work with Product Leadership on the release plan goal(s)
o Ensure the Product Backlog is populated with sufficient stories with acceptance criteria to meet the release goal
o Work with the Product team and Engineering team on story elaboration
o Collaborate with the team to plan stories in all sprints in the Release Plan up to the teams capacity
o Ensure the release plan fulfills the release goal
o Modify the release plan as new information emerges throughout the sprints, and ensure stakeholders are aware of the updates to the release plan and any impact to their requests
o Continuously add new stakeholder requests to the Product Backlog and re-prioritize as needed
• Attend all Scrum ceremonies including daily standups, story elaboration, sprint planning preparation, sprint planning, sprint reviews and retrospectives. Understand the engineering teams progress and be available to answer the teams questions and provide direction in a timely manner
• Work with the SQM team in reviewing test plans, test scripts and the results of testing. Provide guidance on test cases to make sure the business flow is validated alongside field level testing and interactions with the user interface.
• Understand the user interface features as well as the integration with the backend to be able to test and verify the end-to-end business process.
• Test and accept stories as complete during the sprint, verifying that all acceptance criteria have been met and the story has achieved the objective
• Ensure that the Product Backlog is always
o Complete – Has all ideas captured and represents the needs of all stakeholders
o Organized – Reflects reasonable groupings of ideas by value, constituency, business strategic goal, etc.
o Prioritized – Contains current organizational thinking about sequence of delivery
o Current – Continuously prioritizes Product Backlog Items (PBIs) as new work is identified
o Estimated – Each PBI has a high-level estimate created by the engineering team
o Elaborated – Has full detail required for the next 1-2 sprints including clear acceptance criteria
• Communicate with Product Owners and delivery teams from integrated or adjacent products
o Collaborate with other Product Owners in the same end-user communities and/or business area
o Collaborate with other Product Owners that supply data or have other dependencies with your team
o Share ideas and plans, review plans for connection points, and coordinate integration milestones
• Effectively implement small Minimum Viable Products (MVP) to obtain early and frequent stakeholder feedback
• Contribute to the development of a team culture of continuous learning and improvement
Knowledge/Skills
1. Ability to manage, prioritize and deliver on changing stakeholder expectations
2. Has experience writing user stories
3. Has experience writing back end feature stories
4. Has experience in creating and maintaining a backlog
5. Has experience in agile and scrum
6. Has experience creating visual diagrams that document the user flow including validations and conditional logic as it pertains to the business requirements and existing application functionality
7. Ability to create release goals, and create and maintain release plans that meet stakeholder needs
8. Advanced interpersonal skills – able to establish strong working relationships and promote bi-directional communication within and across teams
9. Strong leadership and organizational skills with excellent written and verbal communication skills
10. Ability to apply advanced principles, theories and experiences, and contribute to the development of innovative ideas and practices
11. Ability to effectively facilitate discussions at various levels and suggest alternative approaches
12. Ability to effectively manage challenging situations through negotiation and conflict resolution
13. Ability to demonstrate and build transparency and provide visibility to stakeholders
14. Ability to develop and grow trust across the team and stakeholders
15. Understanding of all facets of the software development life cycle including planning, development, quality assurance, change management and release management
