Scrum Master (Network or Infrastructure-focused)

Note: The hiring manager wants someone who has been a part of Technology Infrastructure teams vs. Software Engineering teams

• Plan and facilitate: Daily Scrum, Sprint Planning, Backlog Refinement, Sprint Review/Demo, and Retrospectives.
• Partner with Product Owners to maintain a clear, prioritized backlog (well-formed epics/features/stories, acceptance criteria, Definition of Ready/Done).
• Optimize flow: apply WIP limits, manage blockers, visualize work, and improve cycle time/throughput. | | Coaching & Ways of Working |
• Coach teams (new to agile) on Scrum/Lean-Agile mindset, estimation, story slicing, and working agreements.
• Mentor emerging Scrum Masters and squad leads; contribute to a lightweight playbook for Infrastructure teams. | | Jira Governance & Reporting |
• Configure/maintain team boards, workflows, fields, and automation; ensure data quality that drives accurate reporting.
• Build dashboards (e.g., velocity stability, planned vs. done, cycle time, flow efficiency, escaped defects, backlog health).
• Establish simple Jira hygiene standards and perform regular quality checks. | | Risk, Controls, and Dependencies |
• Coordinate with Architecture & Engineering and Governance/Control teams (e.g., lifecycle management/LMNT) to align change windows, CAB requirements, and audit-ready traceability.
• Surface cross-team dependencies and risks early; escalate to the RTE with options/impact. | | Program & Stakeholder Engagement |
• Prepare teams for PI Planning; facilitate team breakouts, capacity planning, and objective drafting.
• Provide clear status and outcomes to Product Managers, the RTE, and stakeholders in Risk/Compliance. |

Success Metrics:

1. Cadence reliability: 90% ceremonies on-time with actionable outcomes; two consecutive sprints meeting sprint goals.
2. Quality Jira data: <5% of issues missing required fields; dashboards adopted by PMs and leadership.
3. Flow improvement: 15 25% reduction in average cycle time and aging WIP; stable velocity ( 15%) over three sprints.
4. Agile maturity: Teams achieve the Proficient level on the agile maturity standards.

• 5+ years as a Scrum Master (2+ years with infrastructure teams).
• Proven success in coaching low-maturity teams into consistent Scrum discipline.
• Advanced Jira/Confluence skills (board/workflow config, automation, dashboarding, report design).
• Outstanding facilitation, conflict resolution, and communication skills for technical and non-technical audiences.
• Solid understanding of dependency management, change control, and built-in quality practices.
• U.S. work authorization: ability to support teams during core U.S. business hours.

• Relevant Certifications: SAFe SSM or SASM, CSM/PSM II (or higher); broad experience with PI Planning.
• Background in technology infrastructure (e.g., corporate networking, data center, cloud platforms).
• Familiarity with ITIL/Change, CAB, and controls in regulated environments.
• Exposure to automation toolchains (e.g., Ansible, Terraform) is a plus