ForgeApplyTry it free

ForgeApply · Job listing

Release Train Engineer

Dynata

Remote · US$95k – $115k

See all 15 open roles at Dynata →

Tailor your resume for this Dynata job in about a minute.

ForgeApply tailors your resume and cover letter to this exact posting, then hands you a ready-to-submit application for Dynata's site. Free trial, no card required.

Tailor my resume for this jobView original posting →

About this role

Lead, facilitate and coordinate the operation of the Agile Release Train (ART), ensuring quarterly synchronization between business and technology in assigned programs. Facilitate PI Planning events (pre-PI refinement, the 2-day event, Confidence Vote and ROAM exercise), the cross-team ceremonies during the increment (Scrum of Scrums, PO Sync, ART Sync and System Demo) and the Inspect & Adapt workshop at PI close — ensuring plan compliance, cross-team dependency management and predictable delivery of business value in every Program Increment.

DIRECTLY INVOLVED IN THE FOLLOWING PROCESSES • Agile coaching services and SAFe framework adoption.

• Facilitation and governance of PI Planning events.

• Management of the ART operating rhythm (cross-team ceremonies).

• Continuous improvement at program level (Inspect & Adapt).

• Health, safety and work environment compliance.

Key Processes Supported  

• Agile coaching and   SAFe   adoption  

• PI Planning governance and facilitation  

• ART operating rhythm management  

• Program-level continuous improvement  

• Health, safety, and workplace compliance  

ROLE REQUIREMENTS

• Bachelor’s degree in Computer Science , Engineering, Business Administration, or related field  

• Preferred graduate-level education in Agile Project Management, Organizational Transformation, or related disciplines  

• Minimum two (2) active SAFe / Agile certifications (SAFe RTE preferred).

• 5+ years leading software delivery programs  

• 2+ years coordinating multiple teams at the program level  

• Minimum 3 PI Planning events facilitated or co-facilitated in any prior context.

KNOWLEDGE AND SKILLS — TECHNOLOGIES • Backlog and planning: Jira (including Jira Plans), Azure DevOps, Linear. Familiarity with Dynata two-Jira-project model (PM board and Engineering board).

• Visualization and Program Board: Miro, Mural, Lucidchart, Aha! Roadmaps.

• Documentation and knowledge management: Confluence, Notion, SharePoint, Microsoft 365, Google Workspace.

• Communication and collaboration: Microsoft Teams, Slack, Zoom, Google Meet.

• Live polling and surveys: Mentimeter, Slido, Poll Everywhere (for Confidence Vote and PI Planning dynamics).

• Metrics and dashboards: Tableau, Power BI, Jira Dashboards, EazyBI (reading and interpreting Predictability, Flow and Business Value metrics).

• Spreadsheets and modeling: Excel, Google Sheets (Sprint Capacity Planner, capacity debt tracking, ad-hoc analysis).

• Frameworks and methodologies: SAFe 6.0 (ART, Program Increment, PI Planning), Scrum, Kanban, Lean. Working knowledge of Dynata Product & Engineering Process (V1, May 2026).

GENERAL RESPONSIBILITIES These are the strategic, ongoing accountabilities of the role. They apply continuously across every Program Increment. The responsibilities are grouped in two blocks: SAFe-canonical (what any RTE does anywhere) and Chapter-specific (what an RTE at Dynata does within the Chapter structure).

SAFe-canonical responsibilities • Own the ART operating rhythm end-to-end. The RTE is the single accountable owner of every cross-team ceremony that operates above the sprint level: pre-PI refinement, PI Planning, Scrum of Scrums, PO Sync, ART Sync, System Demo and Inspect & Adapt.

• Be the single point of escalation for cross-team dependencies and impediments within the ART. Teams escalate to the RTE; the RTE escalates upward only when a decision is needed above the ART level.

• Maintain the Program Board as the source of truth for what every team is committed to in the current PI. The Program Board is the RTE's primary artifact — updated by them or by named delegates, never left stale.

• Coach the PEMs, Tech Leads and Product Managers of the ART on the SAFe operating model. Coaching is delivered through observation, feedback and structured 1-on-1s — not through training events.

• Hold the trust relationship with the Business Owners of the ART. Business Owners must believe the RTE is operating in service of business outcomes — this is the precondition for BO commitment to 2-day PI Planning attendance and to honest Business Value scoring.

• Track and report Predictability, Flow and Business Value metrics for the ART. Where dashboards are not yet in production, the RTE owns interim manual reporting.

• Facilitate the Inspect & Adapt workshop at PI close and drive the resulting improvement backlog into the next PI. Continuous improvement at ART level is an RTE-owned outcome.

• Manage the ART's interfaces with adjacent teams, vendors and strategic initiatives. When dependencies cross the ART boundary, the RTE is the named liaison.

Chapter-specific responsibilities (Dynata Agile Chapter) • Report weekly to the Chapter Lead on ART health — Predictability trajectory, in-flight impediments, cross-team dependencies at risk, capacity debt balance, upcoming decisions.

• Participate in the monthly Chapter Council (90 minutes). Bring cross-ART issues, template evolution proposals, community-of-practice status.

• Coordinate with peer RTEs as additional ARTs stand up. When features or capabilities span multiple ARTs, peer RTEs collaborate on synchronization — chair-rotated between RTEs.

• Contribute team-level and ART-level data to the Metrics & Reporting Steward for the Chapter's cross-ART dashboards.

• Support the PEM Community Lead and the Agile Team Coach when they need ART-specific input for their communities of practice.

• Own the ART's contribution to the Chapter's rolling 12-month roadmap: onboarding of new teams, tooling improvements, capacity for training or certification.

• Represent the ART at the Chapter Lead's quarterly review with the CPO and Executive Sponsor.

SPECIFIC RESPONSIBILITIES Pre-PI refinement (Weeks 1–6 of the PI cycle) • Facilitate the weekly pre-PI refinement cadence per team: 60-minute session where PM, PEM and Tech Lead jointly groom the top-priority features for the next PI. Required output per team: features sized, acceptance criteria written, depen

Tailor your resume for this Dynata role before you apply.

Tailor my resume for this job

Similar jobs

Free ATS checker · How to Tailor Your Resume to a Job Description (Step by Step)