> Markdown version of [/jobs/ext/1924904-scrum-master](https://www.wearedevelopers.com/jobs/ext/1924904-scrum-master). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Scrum Master - **Company:** uMed - **Location:** UK (Remote available) - **Salary:** £70,069.0 - **Contract:** Permanent contract - **Skills:** Agile Methodology, JIRA, Scrum Methodology, Software Engineering - **Published:** August 5, 2026 - **Apply:** https://www.adzuna.co.uk/jobs/details/5827733597 ## About the Role * Proven experience as a Scrum Master supporting cross-functional software development teams. * Demonstrated ability to improve team delivery effectiveness through the pragmatic application of Scrum, Kanban, or hybrid agile practices. * Experience coaching cross-functional teams and improving agile maturity through practical, hands-on guidance. * Strong facilitation, coaching, conflict resolution, and stakeholder management skills. * Recognized Scrum or Agile certification is desirable but not essential, with strong practical experience. * Strong experience using Jira or equivalent agile delivery tooling to manage workflow, reporting, and delivery transparency. * A proactive problem solver who takes ownership of removing delivery impediments rather than simply reporting them. * Pragmatic in applying agile practices, understanding when structure adds value and when simplicity is more effective. Focused on improving delivery outcomes rather than enforcing process for its own sake. * Excellent communication skills, with the confidence to challenge unhelpful behaviors constructively while building trust across teams. * Calm, organized, highly collaborative, and able to influence without direct authority. * Understanding of, or willingness to learn, the delivery considerations of working within a regulated healthcare or medtech environment. * Experience working in a startup or scale-up environment is desirable. ## Description The Scrum Master is responsible for enabling one or more product and engineering teams at uMed to deliver work effectively through strong agile practices, effective facilitation, continuous improvement, and proactive removal of delivery impediments. The Scrum Master owns the team's agile delivery process and ways of working. They facilitate effective collaboration, improve team predictability, and create an environment where the team can consistently deliver high-quality outcomes. Beyond supporting day-to-day delivery, the Scrum Master plays a key role in improving uMed's delivery culture by embedding effective agile practices, increasing collaboration across disciplines, and helping teams continuously mature in how they plan, communicate, and deliver software. This is a servant-leadership role. The Scrum Master does not own product priorities, roadmap execution, technical decisions, or people management, but is accountable for the effectiveness of the delivery process and the continuous improvement of how the team works. Requirements Agile Facilitation * Facilitate agile ceremonies, including sprint planning, daily stand-ups, backlog refinement, sprint reviews, and retrospectives. * Ensure ceremonies are effective, outcome-focused, and continually improved to maximize value for the team. * Coach the team in agile principles and practices, helping individuals and teams continuously improve their ways of working. * Encourage accountability, collaboration, transparency, and continuous learning across the team. * Ensure agreed agile standards, ceremonies, and delivery practices are followed consistently. Agile Coaching & Adoption * Champion the adoption of pragmatic agile practices across the product and engineering teams, helping move beyond process compliance to a culture of collaboration, ownership, and continuous improvement. * Coach the product and engineering teams on effective agile ways of working, ensuring ceremonies become meaningful planning and collaboration sessions rather than routine meetings. * Work with teams to establish effective delivery practices such as collaborative backlog refinement, estimation, technical design discussions, dependency management, and transparent delivery planning. * Identify gaps in agile maturity and develop practical improvement plans to help teams continuously evolve their ways of working. * Partner with the Director of Product & Delivery to continuously improve delivery processes, collaboration, and engineering effectiveness across the organization. Delivery Enablement * Identify and remove blockers to the team's progress, escalating promptly where resolution sits outside the team. * Support realistic sprint planning and capacity management, helping the team make achievable commitments based on capacity and historical performance. * Work with the Product Manager to ensure backlog items are sufficiently refined, understood, estimated where appropriate, and ready for sprint planning. * Monitor workflow throughout the sprint, helping the team maintain a sustainable pace and minimize bottlenecks. * Manage cross-team delivery dependencies to ensure risks and impediments are identified and addressed early. * Help improve sprint predictability by enabling teams to make realistic commitments and deliver consistently. Continuous Improvement * Drive a culture of continuous improvement, ensuring actions from retrospectives are tracked, owned, and completed. * Track team delivery metrics such as velocity, cycle time, sprint predictability, and flow, using data to identify opportunities for improvement rather than individual performance management. * Identify recurring process challenges and work with Product and Engineering leadership to address root causes. * Promote pragmatic improvements to team practices while maintaining consistency with uMed's delivery standards. Team Health & Collaboration * Protect the team's focus by minimizing unnecessary interruptions, context switching, and unplanned work where possible. * Foster an environment where risks, impediments, and differing viewpoints can be raised openly and addressed constructively. * Encourage collaboration across Product, Engineering, and QA, helping break down silos and improve shared ownership of delivery outcomes. * Support the onboarding of new team members into the team's agile ways of working. * Build strong working relationships that improve communication, coordination, and dependency management across teams. Reporting & Stakeholder Communication * Provide clear, transparent updates on sprint and release progress to Product and Engineering leadership. * Surface delivery risks and impediments early, providing sufficient context for informed prioritization and resourcing decisions. * Ensure Jira and related delivery tooling accurately reflect the team's progress and support portfolio-level reporting. * Provide timely visibility of upcoming changes to support operational readiness and product configuration activities. ## Related Videos - [ShapeShift: Reinventing Agile for a B2B SaaS Scale-Up](https://www.wearedevelopers.com/videos/1655-shapeshift-reinventing-agile-for-a-b2b-saas-scale-up) - [Diversity as a Growth and Happiness Factor in Agile Development](https://www.wearedevelopers.com/videos/862-diversity-as-a-growth-and-happiness-factor-in-agile-development) - [Improving quality with Agentic AI with Rovo Dev and Xray](https://www.wearedevelopers.com/videos/2005-improving-quality-with-agentic-ai-with-rovo-dev-and-xray) - [Coffee with Developers - Cassidy Williams - ](https://www.wearedevelopers.com/videos/912-coffee-with-developers-cassidy-williams) - [Shaping Up: Rethinking Product Development with Basecamp's Shape Up Methodology](https://www.wearedevelopers.com/videos/1588-shaping-up-rethinking-product-development-with-basecamp-s-shape-up-methodology) - [Systems Thinking for Performance: How to Diagnose and Fix Slow Systems without Guessing](https://www.wearedevelopers.com/videos/2103-systems-thinking-for-performance-how-to-diagnose-and-fix-slow-systems-without-guessing) ## Related Articles - [Fully Remote Software Engineer Jobs](https://www.wearedevelopers.com/magazine/447-fully-remote-software-engineer-jobs) - [Mastering Remote Work: Tips for Developers](https://www.wearedevelopers.com/magazine/558-mastering-remote-work-tips-for-developers) - [UK Business Culture and Etiquette](https://www.wearedevelopers.com/magazine/326-uk-business-culture-and-etiquette) - [Remote Work: Best Practices for Developers](https://www.wearedevelopers.com/magazine/315-remote-work-best-practices-for-developers) - [Best Job Boards for Remote Work for Developers](https://www.wearedevelopers.com/magazine/290-best-job-boards-for-remote-work-for-developers) - [Why Upskilling And Reskilling is Important For Developers](https://www.wearedevelopers.com/magazine/428-why-upskilling-and-reskilling-is-important-for-developers)