Wikimedia Discovery/Portal Team/Roles and responsibilities

Product Manager/Product Owner ("Product Vision and Story Prioritization")
Deborah
 * Develop, manage and communicate the Product roadmap
 * Write user stories based on the Product roadmap
 * Manage and determine priority of tasks
 * Make final decisions or trade-offs when conflicts arise over desired functionality and scope
 * Work closely with the team to understand level of effort for all stories and tasks
 * Work closely with the team to ensure clear multi-way communication in all discussions, demos and reviews
 * Make final decision if development work on stories has been completed: acceptance
 * Define when features, functions, bug fixes, updates, etc are released into production
 * Be the single point of escalation for competing priorities among stakeholders (internal and external)
 * Be agile in a rapid development environment and encourage effective team practices

UX Lead ("UX Design and Vision, and leading UX engineers")
Moiz Syed
 * Hiring, and building a design team, including UX engineers and designers
 * Worrying about how we can be the best damn designed product in the organization
 * 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
 * Overseeing UX implementation with the help of Front-end engineers
 * Explore new avenues through prototyping
 * Provide a UX vision for the team

Tech Lead ("Architecture and Code Quality")
Julien
 * An 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
 * Represent the views and perspective of the engineering team in broader discussions
 * Ensuring that the team is represented at Scrum of Scrums (so far Stas has been representing search at SoS)
 * Supporting recruiting & hiring

Agile Coach ("Facilitation and Process Improvement")
Kevin Smith
 * Arrange and facilitate meetings (e.g. standups and retrospectives)
 * Produce artifacts such as burn-down charts, as needed
 * Assist PO with backlog grooming
 * Help clear any blockers; raise awareness of risks
 * Suggest process improvements
 * Support quarterly planning meetings

UX Engineer
Jan Drewniak

Engineers build the product and coordinate the construction of supporting infrastructure. Responsibilities include:
 * Turning user stories/requirements into working software
 * Conducting the technical analysis of requirements
 * Assisting in the evolution of designs by providing technical feedback and implementing prototypes
 * Assisting the analytics team 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'