Scrum Master

Scrum Master

Location: Mexico (remote role)

In Agile, the Scrum Master is a challenging position as he cares about the team functionality. Scrum Master is responsible for monitoring the scrum processes and scrum meetings. He increases his team efficiency, motivates his team, spins, argues for changes that will ensure quality and timeliness. He ensures the DoD (Definition of done) is being followed.

Essential Duties:

• Guiding the team and organization on how to use Agile/Scrum practices and values to delight customers.
• Guiding the team on how to get the most out of self-organization.
• Guiding the team on self-organizing to fill in the intentional gaps left in the Agile/Scrum frameworks.
• Assessing the Scrum Maturity of the team and organization and coaching the team to higher levels of maturity, at a pace that is sustainable and comfortable for the team and organization.
• Removing impediments or guiding the team to remove impediments by finding the right personnel to remove the impediment.
• Building a trusting and safe environment where problems can be raised without fear of blame, retribution, or being judged, with an emphasis on healing and problem-solving.
• Facilitating getting the work done without coercion, assigning, or dictating the work.
• Facilitating discussion, decision making, and conflict resolution.
• Assisting with internal and external communication, improving transparency, and radiating information.
• Supporting and educating the Product Owner, especially on grooming and maintaining the product backlog.
• Providing all support to the team using a servant leadership style whenever possible, and leading by example.

Required Skills/Experience:

• Experience in playing the Scrum Master role for at least three years for a software development team that was diligently applying Scrum principles, practices, and theory.
• Experience in PI planning and working on PI planning related activities before and after PI planning.
• Good skills and knowledge of servant leadership, facilitation, situational awareness, conflict resolution, continual improvement, empowerment, and increasing transparency.
• Good knowledge in Jira, managing the team boards and working on several reports from Jira.
• Knowledge of various well-documented patterns and techniques for filling in the intentional gaps left in the Scrum approach (example: numerous Burndown technologies, various Retrospective formats, handling bugs, etc.).
• Good communication skills.