Scrum Master – Software Product Team

Location: Sydney CBD – hybrid, 2–3 days per week in the office
Employment type: Permanent, full-time

The Opportunity

We are partnering with an established Australian software company to appoint an experienced Scrum Master to a distributed product engineering team.

The team develops and continually improves a business-critical cloud platform used by a live customer base. Working across Australia, Eastern Europe and Southeast Asia, the 13-person team delivers in two-week sprints alongside a continuous release pipeline.

This is a hands-on delivery position rather than a ceremonies-only Scrum Master role. You will own the team’s delivery cadence, improve agile maturity and coordinate release readiness across multiple concurrent releases. You will also administer the team’s Jira projects and ensure delivery reporting is accurate enough for Product and executive stakeholders to rely on.

The business is partway through a deliberate uplift of its delivery practices. You will inherit documented processes, release gates and reporting conventions, while having genuine scope to improve how the team operates.

What You’ll Be Responsible For

Agile delivery and team effectiveness

- Facilitate sprint planning, daily stand-ups, reviews, retrospectives and backlog refinement.

- Make ceremonies effective and inclusive for a team operating across three locations and time zones.

- Coach the team on practical agile delivery and drive measurable improvements in delivery maturity.

- Build strong relationships across the distributed team and ensure consistent communication and visibility.

- Support new team members in adopting the team’s ways of working.

- Identify and actively remove delivery impediments, escalating only where necessary.

- Protect agreed sprint scope and ensure unplanned work is introduced through a conscious prioritisation decision.

Sprint and backlog execution

- Own day-to-day sprint execution, board hygiene, capacity planning and progress reporting in Jira.

- Partner with Product Managers and Product Owners to translate priorities into a refined, delivery-ready backlog.

- Communicate delivery progress, risks and dependencies clearly to Product and senior leadership.

- Improve delivery predictability without applying agile frameworks rigidly or focusing solely on velocity.

Release coordination

- Coordinate release readiness across multiple concurrent release trains and deployment environments.

- Work closely with development and QA leads to confirm release scope, environment promotion,



deployment planning and post-release verification.

- Ensure all code, database, reporting and legacy-system components are identified before a release progresses.

- Maintain visibility of the release sequence and surface conflicts between releases competing for the same environments or resources.

- Reduce production issues caused by incomplete, incorrect or partially verified release scope.

Jira administration and reporting

- Act as the hands-on Jira administrator for the team’s projects.

- Configure workflows, transitions, screens, custom fields, issue types, automation rules and post-functions.

- Manage shared filters, dashboards, boards and versions.

- Use strong JQL skills to diagnose reporting and board-configuration problems.

- Establish and enforce Jira conventions that make delivery data consistent and trustworthy.

- Produce explicit reporting covering throughput, cycle time, sprint health, delivery risk and release status.

- Explain what the delivery data means, including where limitations or data-quality gaps remain.

- Manage and surface cross-team and program dependencies.

What We’re Looking For

- At least five years’ experience as a Scrum Master, Delivery Lead or Agile Delivery Manager.

- Demonstrated experience supporting a software product team that regularly develops and releases its own software into production.

- Evidence of sustained ownership within product environments, ideally spending two or more years supporting the same product, platform or engineering function.

- Experience working with distributed engineering teams across multiple time zones.

- Strong hands-on Jira administration experience is essential.

- Advanced JQL skills and the ability to identify and correct underlying workflow, board and reporting configuration issues.

- Experience coordinating releases through development, QA, release-candidate and production environments.

- A practical understanding of release scope, dependencies, environment promotion and the risks of partial deployments.

- Experience working across both modern platforms and business-critical legacy systems.

- Strong facilitation, coaching and stakeholder-management skills.





- The confidence to communicate delivery performance and risk to executive stakeholders.

- A proactive approach to removing blockers and resolving problems.

- Availability to work from the Sydney office two to three days per week.

Scrum Master certification such as CSM, PSM or an equivalent qualification will be well regarded.

What We Mean by Product Experience

This role requires experience supporting a stable engineering team that continually owns, releases and improves a live software product.

Your background should include regular production releases and ongoing responsibility for features, customer feedback, defects, technical debt and platform reliability.

Experience limited primarily to one-off technology implementations, package deployments or transformation programs may not provide the product-delivery exposure required for this position.

How the Team Works

- Two-week sprints with a separate Kanban view across deployment environments.

- A continuous release pipeline with multiple releases progressing concurrently.

- Product priorities managed through a regular intake and prioritisation process.

- Jira as the operational system of record, supported by Confluence and dedicated test-management tooling.

- Documented delivery processes, release gates and Jira conventions.

- A prioritised backlog of Jira and delivery-configuration improvements ready for the successful candidate to own.

What Success Will Look Like

Within 30 days

- You have taken ownership of the core ceremonies and completed the delivery handover.

- You understand the current release sequence, dependencies and key risks.

- You have established credibility with team members across all three locations.

Within 90 days

- Sprint delivery is more predictable and risks are clearly visible.

- Releases are progressing through environments with scope confirmed before each promotion.

- Product and leadership have delivery reporting they can trust.

- Priority Jira configuration improvements have been implemented.

Within six months

- The distributed team is engaged and operating cohesively.

- Recurring blockers have reduced and issues are resolved more quickly.

- Release defects caused by incomplete or unverified scope have measurably decreased.

- Agile and delivery practices are embedded in the team rather than dependent on manual reminders.

This is an opportunity to take genuine ownership of delivery within a complex software product environment and make a visible impact across team performance, release reliability and leadership decision-making.

📌 Scrum Master (Sydney)
🏢 Change Recruitment
📍 Sydney