What are the responsibilities and job description for the Scrum Master Business Analyst position at Digital Health Links?
Position: Scrum Master Business Analyst
Location: Columbus, OH – Onsite
Duration: Long Term
In-Person Interview
Job Description
The Scrum Master will have 10 years of experience gathering requirements, mapping workflows, writing user stories, and grooming the product backlog.
The candidate will facilitate daily stand-ups, sprint planning, retrospectives, and coach the team on Agile rules. The role will connect business goals with developer actions, document business needs, system specifications, and clear acceptance criteria.
The candidate will design test scripts, use cases, and traceability matrices linking code behavior back to business rules. The role will also lead User Acceptance Testing (UAT), run functional or regression tests, log defects, and connect end-users and developers to clarify ambiguities and confirm alignment.
Required / Desired Skills Matrix
· Experience in a Scrum Master role: 10 years of experience (Required)
· IIBA Certification: Required
· Experience with Salesforce: Highly Desired
· Experience with Azure DevOps: Highly Desired
· Experience with Copado: Highly Desired
· Scrum/Agile Certification: Required
· 4-year college degree or equivalent: Required
· Experience creating template documents for business processes, creating requirements, use cases, and user stories: 10 years (Required)
· Experience developing, documenting, and automating test cases, executing quality assurance, and performance testing: 10 years (Required)
· ITIL Foundations Certification: Preferred (Listed as Required in the original skill matrix)
Responsibilities
· Gather requirements, map workflows, write user stories, and groom the product backlog.
· Facilitate daily stand-ups, sprint planning, retrospectives, and coach the team on Agile rules.
· Connect business goals with developer actions.
· Document business needs, system specifications, and clear acceptance criteria.
· Design test scripts, use cases, and traceability matrices linking code behavior back to business rules.
· Lead User Acceptance Testing (UAT), running functional or regression tests, and log defects.
· Connect end-users and developers to clarify ambiguities and confirm alignment.