Wikimedia Language engineering/Language Engineering Team Roles and Responsibilities

Jump to navigation Jump to search

Language Engineering Team Roles and Responsibilities[edit]

Role: Director of Engineering[edit]

Who: Alolita Sharma


  • Defining individual annual goals for team members (e.g. training, skills development), distinct from product roadmap
  • Resourcing engineering team
    • Hiring, firing, performance reviews, personnel management following WMF processes
    • Support alignment of team members to broad areas of work to support Product and Wikimedia Foundation goals, within scrum process
  • Mentorship, on-boarding and career growth: Providing staff mentorship for personnel and help advance professional growth
  • Budget responsibilities
  • Inter-departmental collaboration
    • Empower cross collaboration between WMF engineering teams
    • Facilitate internal WMF cross-team collaboration on language support, in close partnership with Product
  • Awareness: Communicate and raise awareness of language projects and accomplishments outside WMF
  • Partnerships and Collaboration: Connecting external partners with internal team as necessary
    • Collaborate with other open source projects and organizations on i18n/L10n projects
    • Nurture technical innovation for our language tools being developed or integrated from other projects and organizations
    • Support capturing partnership opportunities in the team’s product backlog and prioritization by product owner
    • Organize language engineering outreach activities in sync with team and WMF Engineering goals
  • Standards: Increase visibility in standards bodies and create opportunities to contribute or comment on standards and specifications relevant to team

Role: Product Owner[edit]

Who: Amir E. Aharoni (acting)


  • Act as the single individual managing the list of work to be done, the backlog. Management of the backlog includes:
    • Ensuring backlog items are clearly expressed
    • Sorting, organizing and prioritizing the items in the Product Backlog to best achieve goals;
    • Optimizing the value of the work the team performs, in the scope of product ownership responsibilities;
    • Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the team will work on next; and,
    • Ensuring the team understands items in the Product Backlog to the level needed.

Additional Responsibilities (specific to Siebrand Mazeland):

  • Code maintenance on MediaWiki core and hundreds of extensions
  • i18n/l10n code reviews on MediaWiki core and extensions
  • Consulting for WMF and non-WMF developers on i18n/l10n-related questions
  • Some miscellaneous development work.
  • technical support, outreach, communications

Role: Scrum Master[edit]

Who: Amir Aharoni


  • General responsibilities:
    • Facilitating Scrum events as requested or needed.
  • Serving the product owner:
    • Finding techniques for effective Product Backlog management;
    • Helping the Scrum Team understand the need for clear and concise Product Backlog items;
    • Understanding product planning in an empirical environment;
    • Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value;
    • Understanding and practicing agility;
  • Serving the Development Team:
    • Coaching the Development Team in self-organization and cross-functionality;
    • Helping the Development Team to create high-value products;
    • Removing impediments to the Development Team’s progress;
  • Serving the Organization (WMF):
    • Leading and coaching the organization in its Scrum adoption;
    • Planning Scrum implementations within the organization;
    • Helping employees and stakeholders understand and enact Scrum and empirical product development (e.g. iterative, time-boxed development; data-informed development);
    • Causing change that increases the productivity of the Scrum Team; and,
    • Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization