Scrum Master

Must Have Technical/Functional Skills
• Core Scrum Master Skills
• 410 years of overall experience, with 3+ years as Scrum Master for software engineering teams.
• Strong understanding of Scrum, Agile delivery practices, and servant leadership.
• Proven ability to handle multiple stakeholders and manage cross-team dependencies.
• Hands-on expertise with Agile tools: Jira / Confluence / Azure DevOps.


Roles & Responsibilities


Agile Facilitation & Delivery Excellence
• Facilitate Scrum ceremonies: Sprint Planning, Daily Stand-ups, Sprint Reviews/Demos, and Retrospectives.
• Partner with Product Owner/Product Manager to maintain a healthy, prioritized product backlog and ensure stories meet Definition of Ready (DoR).
• Ensure the team adheres to Definition of Done (DoD) including quality gates (testing, security checks, documentation, release criteria).
• Track and improve flow metrics: velocity, cycle time, lead time, throughput, and sprint predictability.
• Promote Agile principles and coach team members on Scrum/Lean/Kanban practices where needed.


Impediment Removal & Cross-Team Coordination
• Proactively identify and remove blockers across engineering, QA, and infrastructure teams.
• Coordinate dependencies across multiple squads and external stakeholders (security, compliance, operations, vendors).
• Drive risk managementidentify delivery risks early (e.g., smart contract audit timelines, node upgrades, RPC provider constraints).


Product & Engineering Collaboration (Blockchain/Web3 Context)
• Work closely with engineering and product teams to plan and manage delivery across:
• Smart contract development/testing, audits, and deployment windows
• Backend microservices integrating with blockchain nodes/RPC endpoints
• Node operations / infrastructure, monitoring, and incident readiness
• Wallet operations workflows, policy/approval screens, and compliance features
• Support release planning for environments (Dev/Test/UAT/Prod) including hard-fork/upgrade readiness, key management constraints, and rollback plans.


Continuous Improvement & Team Health
• Run retrospectives with measurable action items and follow-through.
• Improve team practices around estimation, story slicing, acceptance criteria, and technical debt management.
• Encourage strong collaboration, psychological safety, and ownership mindset.
• Support onboarding of new team members and ensure consistent Agile ways of working.


Reporting & Governance
• P rovide concise status reporting and dashboards for stakeholders.
• Maintain Agile artifacts in tools like Jira/Azure DevOps (boards, workflows, sprint reports, release tracking).
• Facilitate stakeholder alignment on scope, timeline, and delivery trade-offs.