ROLE OVERVIEW
We are hiring a Scrum Master to drive disciplined, predictable, and high-velocity delivery across 2–3
engineering teams operating within our portfolio companies.
This role combines rigorous sprint execution, project planning, release management, delivery tooling
ownership, and hands-on quality assurance. You will own the delivery operating rhythm end-to-end:
from project plan creation and Gantt chart tracking through sprint ceremonies, release coordination
in Redmine, and exploratory testing that ensures we ship quality software.
You are not running ceremonies in isolation. You are the single point of accountability for delivery
health, project timelines, release readiness, and product quality across your assigned teams.
WHAT YOU’LL DO
1. Project Planning & Delivery Tracking
1. Prepare and maintain project plans with clear milestones, delivery deadlines, task
dependencies, and resource assignments for each active engineering workstream
2. Create and manage Gantt charts to visualize project timelines, critical path, and milestone
progress across teams
3. Track delivery against committed deadlines, flag slippage early, and drive corrective action
with engineering leads before deadlines are missed
4. Own the mapping between sprint-level work and project-level milestones, ensuring
individual sprints roll up to cohesive delivery timelines
5. Maintain a consolidated project status view across all assigned teams, giving leadership clear
visibility into what is on track, at risk, or blocked
2. Sprint Execution & Agile Delivery
1. Own and facilitate core agile ceremonies: sprint planning, daily stand-ups, backlog
refinement, sprint reviews, and retrospectives across 2–3 teams
2. Ensure each team maintains clear sprint goals, realistic commitments, and a predictable
delivery cadence
3. Track sprint progress, identify risks early, and resolve blockers before they impact delivery
timelines
4. Drive continuous improvement in team velocity, estimation accuracy, and sprint completion
rates
5. Own sprint capacity planning across teams, accounting for shared resources, availability
gaps, leaves, and cross-team dependencies
6. Run Scrum-of-Scrums or equivalent cross-team syncs to manage inter-team dependencies,
shared resource conflicts, and staggered sprint cadences
3. Release Management & Redmine Operations
1. Create and manage releases in Redmine, ensuring every release has a clear scope, version
tag, target date, and linked tickets
2. Track ticket progress against releases: monitor open vs. closed vs. in-progress issues, flag
scope creep, and ensure release readiness before deployment
3. Configure and maintain Redmine projects, trackers, custom fields, workflows, and
permissions to support clean delivery operations
4. Maintain Redmine dashboards and saved queries that give instant visibility into release
health, aging tickets, blockers, and team workload
5. Ensure sprint outputs flow cleanly into releases: tested, documented, reviewed, and ready
for deployment
6. Coordinate release timing with QA, DevOps, and engineering leads to ensure smooth,
predictable releases
4. Backlog Management & Cross-Functional Alignment
1. Partner with Product Managers, Engineering Managers, QA, and Customer Success to ensure
backlog items are well-defined, prioritized, and delivery-ready
2. Ensure user stories have clear acceptance criteria, dependencies, estimates, and ownership
before entering sprint planning
3. Maintain visibility into scope changes, spillovers, and risks across active workstreams
4. Help align product priorities with engineering capacity and customer-impacting
commitments
5. Triage production incidents and customer escalations against sprint commitments — ensure
urgent customer-impacting work is properly sized and slotted without derailing sprint goals
5. Quality Assurance & Exploratory Testing
1. Develop deep product knowledge across assigned teams to serve as an effective QA
checkpoint, not just a process coordinator
2. Conduct hands-on exploratory testing: break the product, find edge cases, test user
workflows end-to-end, and validate that delivered features actually work as intended
3. Verify delivered stories against acceptance criteria before sprint review, catching gaps before
they reach stakeholders or customers
4. Identify patterns in escaped defects and work with engineering leads to address root causes
in testing practices, code review, or definition of done
5. Collaborate with dedicated QA engineers where available, but own the quality gate when
formal QA capacity is limited
6. Test across browsers, devices, and environments as needed — ensure releases are
production-ready, not just code-complete
6. Delivery Playbooks & Process Standardization
1. Create and maintain delivery playbooks that standardize sprint operations across all assigned
teams: sprint ops, backlog hygiene, definition of ready/done, escalation paths, and
onboarding guides
2. Document release management processes, Redmine conventions, and project planning
standards so that delivery operations are repeatable and not dependent on tribal knowledge
3. Build QA checklists and exploratory testing guides for each product area
4. Ensure playbooks are living documents — updated based on retrospective learnings and
evolving team needs
5. Enable new team members to ramp up on delivery processes quickly through clear,
accessible documentation
7. Delivery Governance & Reporting
1. Build and maintain delivery dashboards covering sprint health, velocity, burndown, blockers,
aging tickets, release readiness, and project milestone tracking
2. Provide consolidated sprint health visibility across all assigned teams, identifying cross-team
patterns and systemic improvement areas
3. Escalate delivery risks, unresolved blockers, and dependency gaps with clear action owners
and timelines
4. Report on engineering delivery metrics: sprint predictability, cycle time, defect escape rate,
release frequency, and estimation accuracy
5. Surface patterns across teams — e.g., all teams struggling with estimation, one team
consistently spilling stories — and drive targeted improvements
8. Team Enablement & Continuous Improvement
1. Coach engineering teams on agile principles, delivery discipline, estimation techniques, and
continuous improvement practices
2. Identify recurring delivery bottlenecks and work with leadership to improve process, tooling,
and operating rhythm
3. Encourage accountability without creating bureaucracy — help teams move faster with
better clarity
4. Support distributed teams with structured communication, clear follow-ups, and strong
async execution habits
WHAT WE’RE LOOKING FOR
Required:
1. 5+ years of experience as a Scrum Master or Delivery Lead, with demonstrated experience
managing 2+ engineering teams simultaneously
2. Strong hands-on experience with Redmine (or Jira): project configuration, release creation,
custom workflows, Gantt charts, dashboards, and sprint reporting
3. Proven ability to create and manage project plans, delivery timelines, Gantt charts, and
milestone tracking across multiple concurrent workstreams
4. Hands-on QA capability: ability to learn products deeply, conduct exploratory testing, find
edge cases, and validate delivered features against acceptance criteria
5. Strong understanding of Scrum, Kanban, backlog management, sprint planning, estimation
techniques, and release coordination
6. Experience creating delivery playbooks, process documentation, and standardized operating
procedures for engineering teams
7. Strong stakeholder management skills across Product, Engineering, QA, Customer Success,
and leadership teams
8. Experience working with remote-first or globally distributed teams
9. Excellent communication, follow-through, meeting facilitation, and written documentation
skills
10. Bias toward clarity, ownership, execution discipline, and measurable delivery outcomes
Nice to Have:
1. Experience in SaaS, enterprise software, or platform engineering environments
2. Experience in post-acquisition or turnaround environments where processes needed to be
built from scratch
3. Familiarity with engineering metrics: cycle time, lead time, defect leakage, sprint
predictability, deployment frequency, and MTTR
4. Exposure to AI-assisted software delivery, engineering automation, or modern SDLC tooling
5. Scrum Master certification (CSM, PSM, or equivalent)
WHY THIS ROLE MATTERS
You are not just running ceremonies. You are the delivery backbone for 2–3 engineering teams — the
person who ensures project plans are realistic, sprints are productive, releases ship on time, and the
product actually works.
This is a high-impact role for someone who can bring structure to ambiguity, build repeatable
delivery systems, personally validate product quality, and help portfolio companies scale engineering
delivery with speed, discipline, and accountability.
Your playbooks, dashboards, Redmine configurations, and testing rigor become the operating
infrastructure that makes predictable delivery possible across the portfolio.