Scrum Master

Core Requirements:

• 5+ years Scrum Master / Agile facilitation (2+ years with multiple concurrent development teams).

• Ability to quickly grasp business and technical requirements, understand or learn technical jargon and government acronyms, produce communication for all levels of the organization.

• Proficient with VersionOne / Agility (or comparable tool) for boards, dependencies, impediments, and lightweight rollup reporting.

• Proven ability to keep ceremonies purposeful, timeboxed, and engaging (planning, daily, refinement, review, retro).

• Demonstrated success by reducing carryover, aging blockers, and decision latency without adding heavy process.

• Ability to coach backlog readiness (thin vertical slices, clear acceptance criteria, limited WIP).

• Hold teams accountable to sizing activities to ensure project ends dates can be projected.

• Manage over and under talkers in ceremonies.

• Ability to schedule, track, and manage meetings.

Key Responsibilities:

• Facilitate core Agile events and lightweight cross team syncs; maintain sprint goal clarity.

• Make Agile “feel useful” via energetic, varied, participatory ceremonies (not rote compliance).

• Track and drive resolution of impediments (environment, integration, data, approvals) across platforms.

• Coordinate cross team and cross platform dependencies (batch windows vs deployment timing, integration points).

• Maintain visible radiators: sprint goals, impediment log, experiment tracker, simple metrics (goal attainment %, carryover, blocker aging).

• Coach Product Owners / BAs and tech leads on prioritization, slicing, and readiness.

• Drive 1–2 small improvement experiments per team per sprint; follow through to closure.

• Foster psychological safety, inclusive participation, and sustainable pace.

Minimum Tool/Process Capability:

• VersionOne (boards, simple dashboards, dependency & impediment tracking).

• Basic understanding of CI/CD flow.

Preferred (Not Mandatory):

• CSM / PSM / A CSM (higher certifications welcome but not required).

• Experience with informal scaling practices (Scrum of Scrums, quarterly alignment).

• Comfort with basic flow visuals (cycle time scatter, aging WIP snapshot).