Community Business Analyst
- Grace Potma
Description
Community Business Analysts (BAs) identify and escalate pain points of real-world users and implementer organizations. They are great communicators who repeatedly explain top priorities and help partners to triage high-impact, high-value work to benefit both the OpenMRS community and Global Goods partners.
Responsibilities
This role includes activities such as:
Communication:
Bring together stakeholders, being the bridge across partners, orgs, people, projects
“Unsticking” organizations or partners confused about priorities or the value a product can bring to their organization
Help to get high-priority, high-value ideas into a “ready to go”, clearly communicated state that the design and/or development team can act on
On-call for issues that come up during design, development, or delivery, where we need to clarify user stories, market context, etc
Solve problems collaboratively with other organizations
Discovery:
Organize feedback
Collect, distill, and disseminate user research and industry research
Partner with designers on user research, design feedback, and prioritize high-value user workflows
Development:
Roadmap creation, maintenance and escalation
Creating actionable issues/tickets and following up regularly on high-priority issues
Supporting developers to understand business requirements
Solid baseline project management skills
Facilitates sprint preparation (where applicable) and facilitates sprint activity by gathering requirements, and converting epics/stories into actionable tickets
Backlog review, cleaning/curation, & prioritization
Diving into code or config files (if able) if they need small tweaks, or to understand work complexity
May apply tools such as those in the Business Analyst Framework kit
Delivery:
Create or Support documentation and training materials
Release communication planning and clear release notes
Success Metrics planning
Requirements
Has obtained PM stage 3; AND,
Commitment to understanding users, demonstrated through routine virtual and in-person user interviews; AND,
An established precedent of community product contributions: Clear, demonstrated evidence of the above types of activities successfully used for community product momentum; AND,
Actively growing in the foundational Product Management categories of Communication, Discovery, Development, and Delivery, as evidenced by recent product or feature success, and/or growth, e.g. as demonstrated in an ongoing PM Self-Assessment; AND,
Demonstrates ongoing learning about the modern Product Team process and how to improve, e.g. through attending webinars, workshops, conferences, or online courses (e.g. Industry Virtual conference; Product-Led Certification course; etc.).