Sign upLog in
IT Project Manager Jobs in Boston, MA

US - Staffing - IT Scrum Master/Project Manager

HireTalent

Boston, MA(remote)

Apply
JOB DETAILS
SKILLS
Agile Programming Methodologies, Artificial Intelligence (AI), Atlassian JIRA, Calendar Management, Coaching, Communication Skills, Continuous Improvement, Data Analysis, Data Quality, Machine Tool, Microsoft Windows Operating System, Organizational Skills, Project Tracking, Project/Program Management, Refactoring, Release Management/Engineering, Reporting Skills, Risk, Risk Management, ScrumMaster, Software Administration, Software Engineering, Software Upgrades, Team Lead/Manager, Technical Delivery, Technical Leadership, Time Tracking, Validation Testing
LOCATION
Boston, MA
POSTED
1 day ago
Title: US - Staffing - IT Scrum Master/Project Manager
Location: Remote or Indianapolis, Boston or Portsmouth preferred.
Duration: Till 12/31/2026

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 be
Any 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 portfolio
What 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 scalability
Security and resiliency
Maintainability and cost efficiency
Alignment with cloud and modern engineering practices
In 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 planning
Refactoring and build
Testing and validation
Production release and stabilization
Because this work spans many teams, applications, and dependencies at once, it requires strong coordination to ensure:
Releases happen predictably
Risks are managed proactively
Teams stay aligned across shared timelines
Where 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 accountability
Inconsistent execution of Agile practices and tooling (JIRA)
Release management is the primary delivery bottleneck
Additionally, teams experience friction due to:
Lack of clear release ownership and tracking discipline
Over-reliance on Solution Engineers and tech leads to manage:
JIRA updates
Release coordination
Administrative tracking
Fragmented, ad hoc execution across applications
Role Purpose
To 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 leads
Executes coordination work directly, rather than relying on others
Reduces administrative burden ( administrivia ) and friction
Ensures releases are planned, tracked, and executed consistently across the factory
This is a highly execution-oriented role, focused on doing the work, not just facilitating it.
Operating Model: Ride-Along Support
This role follows a high-touch, embedded model, meaning:
Works side-by-side with application teams throughout the release lifecycle
Proactively handles coordination and tracking tasks
Reduces the need for engineers to manage:
Release tracking
JIRA maintenance
Cross-team coordination
Key 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 & Execution
Own and maintain the integrated release calendar
Actively coordinate across teams to drive releases forward
Step in to do the work where gaps exist
2. Release Plan Ownership (Execution-Focused)
Ensure every release has:
A defined plan
Clear tasks, owners, and timelines
Directly maintain and update release tracking artifacts (JIRA, Confluence)
Continuously track progress and follow up
3. Release Readiness Management
Establish and enforce:
Standard readiness checkpoints
Go-live entry criteria
Validate readiness across:
Engineering
Testing
Operations
Identify and act on risks early
4. Change & Production Coordination
Coordinate and support:
Change ticket creation and submission
Approval processes
Production readiness steps
Manage cross-team coordination required for production entry
5. Cutover & Go-Live Execution
Lead:
Cutover planning
Go-live coordination
Real-time status tracking and communication
Act as the central coordination point during release events
6. Post-Release Stabilization (Hypercare)
Coordinate:
Post-release monitoring
Issue tracking
Incident response
Ensure smooth transition into stable operations
7. JIRA Ownership & Data Integrity
Enforce JIRA as the single source of truth
Actively maintain and update:
Epics, stories, release artifacts
Ensure:
Data accuracy
Standardization
Alignment to reporting needs
8. Dependency & Risk Coordination
Track:
Dependencies
Risks
Blockers across applications
Drive resolution through direct coordination
9. Standardization & Continuous Improvement
Establish repeatable:
Release templates
Checkpoints
Best practices
Build release management as a formal discipline
10. AI-Enabled Insights
Use AI tools to:
Monitor readiness signals
Identify risks and delays
Improve release predictability over time
Aligned Transformation Pillars
1. Establish Clear Ownership & Accountability
Identify key ownership and responsibility per app or initiative
Enforce RACI across Tech Mod, SMO, and App Teams
Require named owners for:
Release plans
Deliverables
Backlog
2. Standardize Release Management as a Core Capability
Treat release management as a first-class discipline
Implement:
Standard templates
Required readiness checkpoints
Centralized coordination support
3. Fix JIRA as the System of Record
Enforce JIRA as the single source of truth
Standardize structures, fields, and usage
Ensure continuous updates and accountability
Use huddles to review upcoming and in-flight work
Key Differentiator of This Role
Traditional Model
PM coordinates
Teams update tools
Engineers manage admin work
This Role
Executes coordination work
Maintains tracking tools
Drives progress directly
=I Removes the need for Solution Engineers and tech leads to spend time on administration instead of delivery
Success Outcomes
Reduced friction for engineering teams
Improved 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 factory
Better visibility into risks and dependencies
Scalable, repeatable release execution model

About the Company

H

HireTalent

Resume Resources

Free Resume TemplatesFree Resume Builder

Similar Job Searches

Product Owner JobsTechnical Program Manager JobsTechnical Project Manager Jobs