Lead: @apaskulin
Advising: @TBurmeister

Goals

A set of practices for prioritizing and managing work within the Tech Docs Team is documented and understood by team members. The main goal of this project is to establish a baseline that we can continue to iterate on.

• Team members maintain a sustainable amount of in-progress work.
  • Target capacity
  • Documented process for projects and advising
• Anyone can find out what the team is working on.
  • Active projects
  • Twice-monthly updates
  • Details in the Active projects and Advising columns on our Phabricator workboard

Scope

• In scope
  • Common types of work done by the team
    • Projects (team-aligned and KR-aligned)
      • Defining
      • Managing
      • Prioritizing
    • Advising a team project
    • Advising a project outside the team
    • Maintenance
  • Team values
  • Team lead role
• Out of scope
  • Common types of work done by the team
    • Community support
    • Requests and rabbit holes
    • Professional development
    • WMF org work
  • Offsite planning
  • Professional development
  • Evaluating the needs of documentation collections

Priority

In order to achieve our team goals, tech docs planning and management must be centralized, and driven by technical writers. After forming a team of technical writers within the Technology department, we can then standardize how we pursue documentation goals, define processes for how we receive and prioritize documentation requests, and create a framework for working with engineering teams.

The Tech Docs Team was formed in June 2023 by moving technical writers from the Architecture and Developer Advocacy Teams to a centralized team within the Technology department's Developer Experience group. The team defined our mission and high-level goals as part of a strategy process in early 2023, but we still need to define our team values and practices.

Stakeholders

• Tech Docs Team members

Project plan

• Draft proposals for each subtask
• Discuss and incorporate feedback
• Publish