Wikimedia Discovery/Portal Team/Roles and responsibilities

Product Manager/Product Owner ("Product Vision and Story Prioritization")

Deborah

Develop, manage, and communicate the Product roadmap and vision
Write user stories based on the Product roadmap
Manage and determine priority of tasks
Keep the backlog groomed and prioritized
Work with UX Lead to conduct both qualatiatve and market research
Unblock team as necessary for internal and external dependencies/coordination
Work with UX engineers to understand level of effort for all stories and tasks
Make final decision if development work on stories has been completed: acceptance
Be light weight in a rapid development environment and encourage effective team practices
Work closely with the whole team to ensure clear multi-way communication in all discussions, demos and reviews
Work closely with comms & community liasons to message about team progress, accomplishments, and questions

Moiz Syed

Provide a UX vision for the team
Explore new avenues through prototyping
Overseeing UX implementation with the help of UX Engineers
Setting up design processes that enables the team to ship a well designed product
Building design patterns that can be used across the team and even within the whole organization
Review and approve patches and builds with Product Owner to maintain product quality
Mentor and support UX Engineers

Kevin Smith

Jan Drewniak and Julien Girault

Engineers build the product and coordinate the construction of supporting infrastructure. Responsibilities include:

Turning user stories/requirements into working features that are designed to meet user needs and are easy to use
Advocate for user needs and good design
Conducting the technical analysis of requirements
Define when features, functions, bug fixes, updates, etc are released into production in coordination with Product Owner
Assisting in the evolution of designs by providing technical feedback and implementing prototypes
Assisting the Data Analysts by implementing code that enables the analysis and testing of design ideas
Coordinating the implementation of supporting architecture/infrastructure
Thoroughly test code to minimize bugs and maintain an acceptable user experience across browsers and devices
Estimating user stories
Escalating risks and issues that impact scope and timeline
Writing code in line with project and organizational standards
Providing code review to other engineers to maintain a high level of code quality
Standing behind architectural decisions, patterns and best practices that the team has agreed to
Signing off on bugs and technical/non-user-facing stories:
- if a bug is resolved in phab, it is automatically considered "signed off"
- for tech tasks, whoever merges the task has indicated that it is signed off on and the tsp can be moved to 'Done'

Architecture and Code Quality

A UX engineer + all this other stuff:

Set standards for code quality and code review
Make architectural decisions
Answer tech questions of developers, or point them to other resources
Be a single point of contact for any questions relating to the engineering and technology of the product +1
Devs can bring specific questions about tasks to the PO

Release

Guillaume Lederrey