Address
Form of workA Technical Scrum Master works as an integrated part of the NICE CEA Cloud Analytics software engineering team with specific focus on supporting agile processes towards delivering software products into a cloud-native production environment.
Responsibilities of a Technical Scrum Master Include the Following:
Facilitate all scrum ceremonies
Drive for open line of communication and useful collaboration between all parties (team members , PM/PO, GL, Architect)
Ensure the Team members have clarity of the Epics' value / intent and the motivation for doing it.
Ensure the team understands the "WHY" behind what we do, and raise their own ideas for improvement, new features, or new concepts
Ensure the team members are engaged in User stories slicing according to INVEST guidelines
Mentor team members on how to identify and handle Impediments, and ensure that all possible obstacles that could affect the team are removed
Encourage and Coach the team on continuous improvement of the development process in order to improve efficiency - Adhere and implement CEA SDLC process
Encourage the team to be creative with how to improve team efficiency (e.g. creating tools that save team time)
Ensure smooth implementation of Scrum and Agile principles within the scrum team
Make sure dependencies with external teams and other scrum masters are managed properly
Promote an empowered, self-management, collaborative, multidisciplinary team environment that fosters ownership, creativity and innovation
Ensure the team understands their collective ownership for the overall sprint delivery as well as to ongoing routine sprint tasks
Encourage few team members swarming (working together) on the same story to complete it fast before moving to the next one.
Encourage team members to take more responsibility (e.g. as epic owners, or by delegating responsibility that overloads you as TSM)
Mentor the team to interact with others within and beyond the team
Take an active part in the sprint delivery activities
Be a technical "go to" authority for the team.
Provide the team with new/different technical point of views to improve their level of knowledge and execution
Encourage Shift left of quality (TDD/BDD, early integrations, automation, etc.)
Enforce Jira status updates
Communicate team's KPIs (maintenance vs. development, capacity, committed vs. delivered etc...) on a sprint/weekly basis.
