Development Manager / SCRUM Master


(R 70 000 – R 90 000 per month, dependent on skills and experience)

 

Main purpose of the Job

To manage and co-ordinate resources and processes to deliver software releases of Interfacing Technologies products in a Java shop, while participating in defining the strategy or the product development team by driving initiatives that deliver on the Interfacing vision.

 

Key elements of the job

  • Work together with the Product Owner and Operations to ensure that teams have appropriate product and technical specifications, direction and resources to deliver products effectively by establishing realistic estimates for timelines while ensuring that projects remain on target to meet deadlines.
  • Work closely with the Product Owner (PO), Sales and Business Analysts for understanding the system’s functional and non-functional requirements.
  • Collaborate with Business in defining the Product Vision
  • Demonstrate leadership abilities to our clients with the deployment of software upgrades, enhancements and fixes that are co-ordinated based on release schedules.
  • Help developers resolve both technical problems as well as human resources issues.
  • Monitor individual employees’ performance.
  • Provide leadership and guidance to coach, motivate and lead team members to their optimum performance levels and career development.
  • Ensures a proper power balance between PO, Team, Management
  • Educates PO, Team, Management and Organisation

 

Meetings

  • Facilitating meetings for the team. This includes: preparing, moderation, post processing, holding retrospectives

 

Team Dynamics

  • Helps to keep the Team focused on the current Sprint and achieve sprint goals
  • Supports Team building and Team development by utilising the abilities and skills of individuals, and fostering a Feedback culture
  • Strives to develop a Team into a High Performance Team
  • Encourages and fostering the developer team’s self-organisation
  • Educates and focuses a Team toward business-driven development
  • Protects the team
  • Moderates in the team
  • Coaching team members (e.g. with one-on-one coachings)
  • Mediating through conflicts
  • Helping the team to make decisions
  • Helps Team to learn from its experiences
  • Mediating the general conflict of goals between development team and PO
  • Detects hidden problems and strives to solve them
  • Ensures and supports Empowerment of the Team
  • Encourages and helps to achieve transparency
  • Addresses needs efficiently and effectively

 

Learning

  • Continuing learning regarding everything Agile (e.g. visit user groups, attend conferences, read books, write blogs, etc.).
  • Consulting team members regarding everything Agile
  • Giving feedback to the team
  • Encouraging the use of Agile Engineering Practices within the development team
  • Challenge team with Agile management innovations (e.g. FedEx-Days)

 

Product

  • Helping to write or split user stories.
  • Helping to write or adapt product visions
  • Helping to order product backlog items
  • Helping with the release planning.
  • Being familiar with the team’s work (i.e. the product).

 

Big Picture

  • Bringing people together who should talk to each other
  • Keeping in touch with every stakeholder regularly
  • Report to management
  • Giving learning opportunities to people in the organization (e.g. talks or workshops) and letting them learn important Agile concepts like e.g. technical debt

 

Change

  • Helping the team to get rid of impediments
  • Suggesting new metrics for the team as catalysts for change

 

Mirror

  • Reflecting Agile and Scrum values to the team
  • Helping the team to continuously improve their process
  • Reflecting issues to the team through observation from outside of the team
  • Asking open questions

 

Miscellaneous

  • Helping the team to keep focus (e.g. by acting as a buffer between external distractions and the team)
  • Helping the team to maintain their Scrum tools (Story board, Action board, charts, backlogs, etc.)

Reporting

  • customer feedback – number of bugs and level of customer satisfaction
  • burndown chart – report on the amount of work completed and not completed