About Invisia Software
Invisia Software Pvt. Ltd. is a Bengaluru-based software company building and supporting digital products, including Zee Business, a US-focused online travel platform. Our teams work across Product, Engineering, Quality Assurance, Design and business functions to deliver reliable, customer-facing experiences.
The opportunity
We are looking for a hands-on Senior Scrum Master / Agile Delivery Lead who can independently establish and run a disciplined sprint execution rhythm. You will help teams commit realistically, expose delivery risks early, remove impediments through the right owners, recover slipping work and improve delivery predictability from sprint to sprint.
This is not a ticket-administration or meeting-coordination role. You are accountable for the effectiveness and transparency of the sprint delivery process, while Product, Engineering and other functional owners retain accountability for priorities, estimates, technical solutions, quality and business outcomes.
What You Will Own
Sprint readiness, planning and forecasting
- Lead sprint planning, refinement, reviews, daily coordination and retrospectives with clear decisions and follow-through, not ceremony for its own sake.
- Validate backlog readiness, acceptance criteria, dependencies, team availability and capacity with Product, Engineering and QA before commitments are made.
- Challenge vague work, unrealistic timelines and overcommitment; establish an agreed sprint goal, delivery forecast and visible plan with accountable owners.
Active sprint execution and delivery control
- Run the day-to-day sprint operating cadence across Web, mobile, backend, QA, DevOps and Design contributors where applicable.
- Track committed versus completed work, work in progress, ageing tasks, rework, scope changes and emerging schedule risks; keep Jira accurate and decision-useful.
- Spot slippages early, assess impact on the sprint goal and coordinate recovery options with owners instead of merely reporting delayed tickets.
Blocker resolution, dependencies and recovery
- Investigate impediments and recurring bottlenecks, identify root causes, and drive actions with named owners and dates through to closure.
- Coordinate cross-team handoffs, integration dependencies and sequencing; facilitate trade-off decisions on scope, capacity and timing.
- Escalate material risks promptly with evidence, impact, options and a specific decision required. Do not allow unresolved blockers to disappear into status reports.
Cross-functional alignment for shared releases
- Synchronize Product, Engineering, QA, UX, Marketing and Creative contributions connected to the same product initiative, release or launch.
- Maintain an integrated view of sprint-critical milestones, assets, sign-offs, testing and handoffs while adapting workflows where Scrum is not appropriate.
- Coordinate release readiness and handover activities; Engineering, QA, Product and functional leaders retain their respective acceptance and go/no-go authority.
Process improvement, metrics and leadership
- Use retrospectives and delivery data to identify why work slips, why teams are blocked and where estimation, requirements, handoffs or quality controls fail.
- Introduce practical improvements to capacity planning, backlog quality, work-in-progress limits, dependency management and delivery flow; check whether changes work.
- Maintain concise weekly sprint health reporting: outcomes, forecast, blockers, decisions needed, corrective actions and trends, not raw activity counts.
- Constructively challenge Product, Engineering and business stakeholders, resolve delivery friction and encourage ownership without relying on positional authority.
Accountability and decision boundaries
You own the sprint delivery operating system: readiness checks, cadence, transparent forecasting, impediment follow-through, reporting and improvement. You facilitate planning with delivery teams; you do not unilaterally assign engineering estimates, change product priorities, approve releases or manage functional staff.
Product Managers own product priorities and acceptance; Engineering leads and the TPM own technical decisions and engineering delivery commitments; Project Managers own integrated project milestones and stakeholder plans; QA owns testing and quality evidence; Marketing and Creative leads own their departmental outcomes. You make dependencies between these owners visible and drive decisions to closure.
What You Bring
Essential experience and capabilities
- Typically 7–12 years of relevant experience, including at least 4 years of hands-on Scrum Master, Agile delivery or comparable software delivery leadership; equivalent demonstrated impact is welcome.
- Evidence of personally improving sprint predictability or delivery flow in a team with weak planning, recurring spillovers, missed commitments or poor dependency management.
- Strong practical understanding of Scrum, Kanban, Agile estimation, capacity planning, backlog refinement, SDLC, release lifecycles and quality gates.
- Comfort working with engineering teams across APIs/backend, Web and mobile, QA, CI/CD and deployment, without needing to be the technical decision-maker.
- Strong command of Jira and reporting tools, with the ability to diagnose bottlenecks using cycle time, blockers, scope churn, predictability and defect-driven rework.
- Independent judgement, structured root-cause analysis, negotiation, concise communication and the confidence to challenge unclear ownership or unrealistic commitments.
Preferred, But Not Mandatory
- B2C digital products, e-commerce, travel technology, marketplaces, fintech or other transaction-intensive platforms; multi-team, frequent-release environments.
- Experience coordinating Design, Marketing or Creative dependencies alongside software delivery, using lighter-weight workflows where appropriate.
- PSM I/II, CSM, PMI-ACP or similar certification. Practical delivery results matter more than credentials.
What Success Looks Like
First 30 days Establish a baseline for sprint performance, map responsibilities and dependencies, and make delivery risks and blockers visible.
By 60 days Run consistent sprint readiness and follow-through, with actionable recovery plans and reliable reporting used by the teams.
By 90 days Demonstrate measurable improvement against the baseline in predictability, spillovers, blocker ageing and/or cycle time without compromising quality.
Measures of effectiveness
We will evaluate sprint goal achievement, forecast reliability, spillover trends, blocker ageing, cycle time, mid-sprint scope changes, improvement-action closure and stakeholder confidence. Metrics are assessed together and against the initial baseline, not used to reward artificially small sprint commitments or speed at the expense of quality.
What We Value In Applicants
Come prepared with a real example of an underperforming delivery team you helped improve. We will be interested in the starting conditions, your personal decisions and actions, the evidence you used, the delivery impact and what you would do differently. Candidates should be ready for a practical sprint planning and delivery-recovery discussion.
LOCATION & COMMITMENT
Bengaluru, Karnataka |Full-time | Work from office, five days a week
