US - Staffing - IT Scrum Master/Project Manager

Mananger Intake Call Notes:Max Bill Rate: Location: remote is ok, but prefer ET for time zone, and if they are close to Indianapolis, Boston or Portsmouth that is a bonus.Contract to hire: Not currently looking to convert to FTE, but the role aligns to the roles on my team and should I lose a team member and have a good worker I would then become interested in hiring.Timeline: right now I know I want someone for this year, but if it works well I am likely to extend next year and on beyond that.Interview Details: Round one - with the HM and then round two have the team meet with selected candidates.Is this supporting any specific project: yes- there are two projects that need support.Lifecycle support - initially will help GRS complete Windows 2016, REHL6 updates, and a GCS access to application standards project.GRS Tech Modernization - will support release coordination efforts bridging between and coaching teams from a coordinated factory and vendor modernization model that will need to also coordinate with and align to delivery timelines, ensure accuracy in JIRA for applications being modernized, coaching teams and arranging visibility.What is the most important skillset: Both roles benefit from a combination of Project Management and agile Scrum Master, both positions will benefit from and really need some technical skills - these are in the Technology organization and will provide coordination of technical deliveries. Being a strong communicator, able to track and identify progress and help people along the way would beAny immediate disqualifiers: No technology background,Is there a preference for industries the candidates have worked in: Technical/ technology work is preferred. Generally, any space with legacy applications that require modernization and upkeep, the ability to understand legacy technology and speak tech with software engineers etc would be key.Can you tell me what the person's day to day will be like: significant amounts of coordination, independently leading data review and analysis, and coaching, gathering, and connecting with people across GRS to ensure progress, keeping clear and visible records - for Tech Mod in JIRA and for the lifecycle work also likely JIRA but may also involve using excel. Creating regular reports and raising risks to leaders, developing a plan and building connections and relationships to ensure progress is made on the plan. Must have the ability to navigate across an organization, get to know the key players and to track and ensure progress.Tech Mod Factory Release Coordinator (Scrum Master and Project Manager skill mix are desired)Scope: Factory-wide release coordination across Tech Mod modernization portfolioWhat is Tech Modernization? (Context for This Role)Tech Modernization (Tech Mod) is the process of upgrading existing applications, platforms, and infrastructure to modern standards to improve:Performance and scalabilitySecurity and resiliencyMaintainability and cost efficiencyAlignment with cloud and modern engineering practicesIn the Tech Mod Factory model, multiple applications are modernized in parallel using shared patterns, tools, and delivery teams. This creates a high-volume, pipeline-based approach where applications move through stages such as:Discovery and planningRefactoring and buildTesting and validationProduction release and stabilizationBecause this work spans many teams, applications, and dependencies at once, it requires strong coordination to ensure:Releases happen predictablyRisks are managed proactivelyTeams stay aligned across shared timelinesWhere this breaks down today: [br "SCXW142898993 BCX8" style="margin: 0px; padding: 0px; user-select: text; white-space: pre;"]Release coordination often becomes fragmented, inconsistent, or pushed onto engineers leading to delays, risk, and unnecessary operational overhead. There is a need to coordinate and align delivery teams for modernization (often vendor teams working on multiple applications) with the teams that own the applications (initiation, dependency management and testing will all be needed from these teams that own the application and timeline commitment, right now without this role, those timelines and deployments are slipping)Executive Summary (Core Diagnosis & Need)Current Tech Mod Factory feedback and pilot work indicate:Gaps in ownership, structure, and accountabilityInconsistent execution of Agile practices and tooling (JIRA)Release management is the primary delivery bottleneckAdditionally, teams experience friction due to:Lack of clear release ownership and tracking disciplineOver-reliance on Solution Engineers and tech leads to manage:JIRA updatesRelease coordinationAdministrative trackingFragmented, ad hoc execution across applicationsRole PurposeTo enable predictable, low-risk, and scalable releases, this role establishes a hands-on Release Coordination function that:Acts as a ride-along partner to Solution Engineers and tech leadsExecutes coordination work directly, rather than relying on othersReduces administrative burden ( administrivia ) and frictionEnsures releases are planned, tracked, and executed consistently across the factoryThis is a highly execution-oriented role, focused on doing the work, not just facilitating it.Operating Model: Ride-Along SupportThis role follows a high-touch, embedded model, meaning:Works side-by-side with application teams throughout the release lifecycleProactively handles coordination and tracking tasksReduces the need for engineers to manage:Release trackingJIRA maintenanceCross-team coordinationKey Principle: [br "SCXW142898993 BCX8" style="margin: 0px; padding: 0px; user-select: text; white-space: pre;"]=I Engineers build. This role enables them to do that by removing friction.Core Responsibilities

1. Hands-On Release Coordination & ExecutionOwn and maintain the integrated release calendarActively coordinate across teams to drive releases forwardStep in to do the work where gaps exist
2. Release Plan Ownership (Execution-Focused)Ensure every release has:A defined planClear tasks, owners, and timelinesDirectly maintain and update release tracking artifacts (JIRA, Confluence)Continuously track progress and follow up
3. Release Readiness ManagementEstablish and enforce:Standard readiness checkpointsGo-live entry criteriaValidate readiness across:EngineeringTestingOperationsIdentify and act on risks early
4. Change & Production CoordinationCoordinate and support:Change ticket creation and submissionApproval processesProduction readiness stepsManage cross-team coordination required for production entry
5. Cutover & Go-Live ExecutionLead:Cutover planningGo-live coordinationReal-time status tracking and communicationAct as the central coordination point during release events
6. Post-Release Stabilization (Hypercare)Coordinate:Post-release monitoringIssue trackingIncident responseEnsure smooth transition into stable operations
7. JIRA Ownership & Data IntegrityEnforce JIRA as the single source of truthActively maintain and update:Epics, stories, release artifactsEnsure:Data accuracyStandardizationAlignment to reporting needs
8. Dependency & Risk CoordinationTrack:DependenciesRisksBlockers across applicationsDrive resolution through direct coordination
9. Standardization & Continuous ImprovementEstablish repeatable:Release templatesCheckpointsBest practicesBuild release management as a formal discipline
10. AI-Enabled InsightsUse AI tools to:Monitor readiness signalsIdentify risks and delaysImprove release predictability over timeAligned Transformation Pillars
11. Establish Clear Ownership & AccountabilityIdentify key ownership and responsibility per app or initiativeEnforce RACI across Tech Mod, SMO, and App TeamsRequire named owners for:Release plansDeliverablesBacklog
12. Standardize Release Management as a Core CapabilityTreat release management as a first-class disciplineImplement:Standard templatesRequired readiness checkpointsCentralized coordination support
13. Fix JIRA as the System of RecordEnforce JIRA as the single source of truthStandardize structures, fields, and usageEnsure continuous updates and accountabilityUse huddles to review upcoming and in-flight workKey Differentiator of This RoleTraditional ModelPM coordinatesTeams update toolsEngineers manage admin workThis RoleExecutes coordination workMaintains tracking toolsDrives progress directly=I Removes the need for Solution Engineers and tech leads to spend time on administration instead of deliverySuccess OutcomesReduced friction for engineering teamsImproved release predictability and consistency (dates are set and adhered to, changes follow risk and escalation approach as defined by the program)Clear ownership and accountability across the factoryBetter visibility into risks and dependenciesScalable, repeatable release execution model