Scrum Master

Scrum Master

Responsible for all aspects of the development and implementation of assigned projects and provides a single point of contact for those projects. Takes projects from original concept through final implementation. Interfaces with all areas affected by the project including end users, computer services, and client services. Defines project scope and objectives. Develops detailed work plans, schedules, project estimates, resource plans, and status reports.

Conducts project meetings and is responsible for project tracking and analysis. Ensures adherence to quality standards and reviews project deliverables. Manages the integration of vendor tasks and tracks and reviews vendor deliverables. Provides technical and analytical guidance to project team. Recommends and takes action to direct the analysis and solutions of problems. Performs all functional duties independently. Works on high‑visibility programs, or mission critical aspects of assigned program(s).

Oversees the efforts of direct reporting resources and/or is responsible for the efforts of all staff assigned to a specific job.

• Minimum of eight (8) years' relevant experience.
• 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 Version One / 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.

• 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 / Client 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.

• Uses creative retros (rotating formats) and lightweight recognition of small wins.
• Introduces tasteful micro‑gamification (e.g., blocker bust streaks) to energize without distracting.
• Encourages rotating spokespeople and silent ideation rounds to amplify quieter voices.

• Sprint goals achieved &Client;80–85% without overtime spikes.
• Declining trend in blocker aging and repeat impediments within first 2–3 months.
• Story/task carryover trending toward