Scrum Master

Role title: Scrum Master 

Function: 

Band: H1/H2

Department: IT P&A

Reports to: Prashant Wagherkar

Location: Pune

SKILL SET REQUIRED: 

• Minimum 3-4 years of experience as scrum master 

• Knowledge of agile methodology and frameworks like Scrum, Kanban, safe agile, etc.

• Basic knowledge of software development processes and procedures to understand the team needs

• Working knowledge of tools such as Jira

• Knowledge about tasks, backlog tracking, burn down metrics, velocity, and user stories etc.

ABOUT ROLE:

The candidate is responsible for delivering the project in an agile based manner. His duties include managing timelines, resolving problems and coaching team members on agile methodologies. The individual should be self-motivated, creative and proactive, to work successfully in a fast-paced environment. The individual will work closely with developers, testers, product owners and other scrum masters. The individual should have a strong understanding of agile processes along with behavioural qualities like team management, stakeholder management, impediment resolution etc.

DUTIES & RESPOSIBILITIES:

• Coach the team in agile practices while ensuring the application of scrum practices

• Facilitate various meetings like daily scrum, sprint planning, sprint demo, and retrospective etc.

• Estimate and plan for the whole software development project along with team

• Forecast the number of deliverable possible in an iteration based on evidence

• Build and maintain a healthy product backlog for team  

• Ensuring a good relationship between the team and product owner as well as others outside the team

• Clearing obstacles, addressing team dynamics and establishing an environment where the team can be effective

• Working in coordination with other scrum masters to resolve dependencies, address risks in program level safe agile framework

• Work as the administrator of the scrum board. Ensure that user stories/tasks are up to date and the scrum tool, Jira software or otherwise, is working well. 

• Tracking and recording various metrics and reports like burn down chart, defect frequency etc.

Guidelines for the scope of the role

Topic 

Please describe

Scale of influence across organisation

(H, M or L and description e.g. direct and indirect interfaces across markets / levels etc.)

M– Frequently consulted by stakeholders outside the Domain for advice on Pega System design practices and other software engineering issues.  Accountable to Domain Lead for good quality designs which meet the needs of customers and comply with architecture directives and industry best practice.  

Strategic elements of role

(H, M or L and description e.g. long term roadmaps / priorities / decision making etc. versus day-to-day operational activities)

L – Ensure effective design of applications on Pega platforms/applications. Advise colleagues on platform specific technical issues when consulted.  

Operational accountability and impact on service to customers

(H, M or L and description e.g. level of influence on customer experience, management of large operational teams etc)

H – Accountable for every technical aspect of the delivery of high quality and effective integration designs and implementation for Pega solutions.  No direct operational responsibilities, but may be consulted on platform technical behaviour and best practice.

Impact of risks managed by role on Vodafone 

(H, M or L and description e.g. management of stability of networks, large budgets, strategic direction etc)

M – Effective performance in this role will have positive impact on internal implementation effort savings and on rework and defect resolution for Pega applications.

Level of expert knowledge required for role

(H, M or L and description e.g. knowledge of technologies, centres of excellence etc)

H – Requires strong, well established Pega design and implementation know how as well as general IT expertise (DB, general web/integration technologies etc.). Requires wide software engineering expertise. 

Extent that individual thinking and judgement are required for role

(H, M or L and description e.g. repetitive and formulaic activities versus creation of new approaches )

H – Must have creative and positive approach to resolving technical issues and challenges.  Must be able to take ownership of problems that arise and to guide and influence team colleagues to find effective and timely solutions

Critical success factors and competencies for role

 (e.g. knowledge of telecoms technologies, influencing skills, critical thinking etc)

Expert knowledge in Pega design and development practices.

Excellent analytical, technical communication and coaching skills.

Pragmatic, but forward looking approach to design and development

Ability to communicate technical issues to technical and non-technical audience

Collaborative approach to team work.