# Product Owner ## Goals * Make sure Deep Teams operates adequately * Cover user’s needs and prioritise resources for the software development ## Hazards * Features might be broken * Interface might not be understandable * Users might experience friction when using it and drop off ## Workflow ### Keep track of user feedback The first step is to get a clear understanding of the requirements of the users and make sure that with each sprint, it is clear which stakeholder is being addressed. Identify bugs and thoroughly test the application. ### Ensure implementation-ready designs Communicate updates to the person responsible of[Software Product Design](/teams-departments/software/roles/software-product-design.md) and provide context on the necessary updates. Sketch concepts on paper if necessary. Double check results to confirm they are implementation ready. ### Create engineering ticket in Notion If an update is not urgent, write a ticket in the TODO section of [this Notion](https://www.notion.so/deepworkstudio/7cb0046a3cb1419d82b464de03b07740?v=4c33cd9fa17d42f4884139a2e61ed8c0\&pvs=4) page. If something is urgent (functionally bug, etc), please write it directly in the Discord to #deep-teams. ### Scope monthly sprint Every month, review with the Backend and Frontend developer the scope of work and prioritise the most important tickets for the next sprint. ### Evaluate technical constraints and reprioritize sprint-tickets Based on the feedback from the engineering team, review if any of your suggested design solutions have technical limitations or constraints. If they do, reprioritize the tickets to ensure consistent progress of the following sprint. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.deepwork.studio/teams-departments/software/roles/product-owner.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.