Job Summary
"JOB DESCRIPTION Scrum Master — Digital Engineering Engagement with a Sweden-based global top-tier manufacturing client · Multi-application transition and SAFe Agile delivery 1. Role purpose The Scrum Master is accountable for the delivery health of the engineering pods serving a Sweden-based global top-tier manufacturing client across a large, multi-stack application portfolio. The role runs the Agile operating rhythm, removes impediments before they become escalations, and protects flow and predictability as applications move from the Learn phase into independent, Perform-phase delivery. This is a hands-on delivery role rather than a ceremony facilitator: the Scrum Master owns the transition-readiness view for their pods, maintains the impediment and dependency register, and provides the evidence base for governance and leadership forums. 2. Role at a glance Attribute Detail Role title Scrum Master — Digital Engineering (Design & Development) Engagement Application transition and managed delivery for a Sweden-based global top-tier manufacturing client Reports to Group Project Manager — Digital Engineering, HCLTech Base location India (offshore) with Sweden (CET) time-zone overlap; onsite rotation as required Experience 8–12 years in Agile delivery, with 4+ years as a Scrum Master Band E3 — in line with the approved additional development capacity plan Scope Multiple pods across a 70+ application landscape spanning .NET, Java/JEE, SharePoint Online/M365, Mainframe and Data/BI Engagement phase Transition (Learn → Perform) moving into steady-state Agile delivery 3. Key responsibilities Area Responsibilities Agile facilitation Run the full ceremony set — sprint planning, daily stand-up, review, retrospective and backlog refinement — with clear outcomes, decisions and owners recorded each time. SAFe & PI delivery Drive PI Planning preparation and execution: capacity forecasting, feature breakdown, dependency mapping, PI objective commitment and confidence vote. Participate in Scrum-of-Scrums and ART sync. Impediment management Own the impediment and risk register with RAG status. Resolve blockers at pod level, escalate with evidence and a recommended path when resolution sits outside the pod — including access, environment and onboarding delays. Flow & predictability Track velocity, burndown, throughput, cycle time, carry-over, defect leakage and commitment-versus-delivery. Use the data to improve forecast accuracy, not merely to report it. Transition readiness Track KT completion, playback validation and reverse-walkthrough sign-offs against the Learn-phase scorecard; report independent-delivery readiness ahead of Perform-phase entry. Dependency & release coordination Coordinate cross-pod and cross-tower dependencies with architects, infrastructure and COTS teams; align sprint output with Change and Release Management windows. Stakeholder engagement Work with the client Digital Product Owners, VSM and CSM community and HCLTech delivery leads; present concise, evidence-based delivery status at governance and leadership reviews. Team health & coaching Coach the pod and Business Analysts on Agile practice and definition of done; build cross-skilling and backup cover to remove single-person dependency risk; drive continuous improvement from retrospective actions. 4. Must-have skills and experience Skill area What we expect Scrum mastery Proven delivery as a Scrum Master across multiple concurrent pods; strong facilitation, conflict resolution and servant-leadership practice. SAFe framework Hands-on in a SAFe environment — PI Planning, ART ceremonies, feature and enabler management, PI objectives and dependency boards. Delivery metrics Velocity, burndown, cumulative flow and predictability analysis; able to build and defend a data-backed delivery view for leadership. Agile tooling Azure DevOps, Jira or equivalent for backlog, sprint and reporting;
Key Responsibilities
4. Must-have skills and experience
Skill area What we expect
Scrum mastery Proven delivery as a Scrum Master across multiple concurrent pods; strong facilitation, conflict resolution and servant-leadership practice.
SAFe framework Hands-on in a SAFe environment — PI Planning, ART ceremonies, feature and enabler management, PI objectives and dependency boards.
Delivery metrics Velocity, burndown, cumulative flow and predictability analysis; able to build and defend a data-backed delivery view for leadership.
Agile tooling Azure DevOps, Jira or equivalent for backlog, sprint and reporting; ServiceNow for incident, problem and change interfaces; Confluence or SharePoint for documentation.
Technology literacy Sufficient understanding of enterprise application stacks and integration patterns to challenge estimates and assess technical dependencies credibly.
Service transition Experience running Agile pods through application transition into managed delivery, including KT governance and readiness sign-off.
Communication Ability to hold a clear, evidence-led position with senior client stakeholders and to run effective distributed onsite–offshore teams.
5. Good to have
• Manufacturing, automotive or aftermarket domain background.
• SAFe SSM / SASM, PSM II, CSP-SM or PMI-ACP certification.
• Release Train Engineer exposure or readiness to scale into an RTE role.
• AI and Copilot-assisted delivery reporting, retrospective analysis and status generation.
• Familiarity with SRE practice, error budgets and the incident-to-engineering feedback loop.
6. Behavioural expectations
• Evidence-led — reports delivery status from data, never from optimism.
• Surfaces bad news early with a proposed path, rather than late with an explanation.
• Protects the team’s focus while holding it accountable to committed outcomes.
• Coaches and cross-skills peers to remove single-person dependency risk.
7. Success measures — first 90 days
Window Expected outcome
Days 1–30 Establish the ceremony cadence and working agreements across the assigned pods; publish the baseline impediment, dependency and risk register; align reporting with the governance calendar.
Days 31–60 Deliver two stable sprints with a predictable velocity baseline; close the priority impediments carried from transition; complete the first full PI Planning cycle with committed objectives.
Days 61–90 Demonstrate Perform-phase readiness — commitment-versus-delivery within agreed tolerance, reduced carry-over and defect leakage, completed reverse walkthroughs and a self-sustaining retrospective improvement loop.
8. Interfaces
Client Digital Product Owner (DPO) and DPAO community, Value Stream Managers and Customer Success Managers; HCLTech Digital Engineering delivery leads, Solution Architects, Business Analysts and engineering pods; QA and test teams; infrastructure, database and COTS towers; Change, Release and Problem Management; the incoming SRE pod.