Skip to content

Latest commit

 

History

History
26 lines (19 loc) · 1.5 KB

technical_liaisons.md

File metadata and controls

26 lines (19 loc) · 1.5 KB

Technical Liaisons

DLS will designate a technical liaison to each project in the team's portfolio.

Why Technical Liaisons

  • Ensure that each of our projects are stewarded, looked over, and thought about reliably.
  • Empower developers to learn deeply about the context and stakeholder use cases for a particular application.
  • Act as a point of contact for the product owner to support their interactions with stakeholders.
  • Bring knowledge of issues and talking points back to the team for implementation discussion and prioritization.
  • Promote the needs of the application to the team to ensure it isn't lost in the shuffle.
  • Product owners have told us this role is useful.

A technical liaison is not necessarily the technical authority or expert on the codebase they steward. Technical and architectural decisions are a team effort.

Responsibilities of a Technical Liaisons

  1. Collaborate closely with the product owner to prioritize issues and ensure the backlog is groomed appropriately. This work may also be delegated or shared.
  2. Triage the inbox for the project's zenhub board
    1. Do an initial review of the new issues for actionable specifications, requesting additional information from issue's author if needed.
    2. Bring issues that require further discussion to the team.
  3. Attend meetings with product owner and stakeholders to learn about new and changing use cases directly.
  4. Participate in work cycles for the project.

See assigned technical liaisons at List of Applications