Skip to content

Product manager and owner

Each of the resources below can be considered a work-in-progress. These resources will evolve and adapt as the team and team needs change. Feel free to open an issue with a link to whichever resource needs improvement and a description of the suggested change.

  1. Learn how we setup our GitHub Kanban boards.

  2. Review the Project Terminology.

  3. Review the Software Lifecycle Diagram.

  4. Review our success metrics.

  5. Communicate with other product team members and Leadership to discuss project priorities and strategic direction.

  6. Review the Project Management Board and identify an actionable backlog item.

  7. Review Hack for LA document templates.

Documents for Product Managers#

Dashboard#

Project Board by#

Ongoing Tasks#

Current estimate is 5 hours 1. 20 2. 87 3. 48 4. 39 5. 75 6. 100

  1. Label Check (15-20 minutes)
  2. Check the issues in following columns to see if they are assigned and find out why/take action: (3 minutes per issue) Search is:open NOT prework or ignore
  3. Ice box
  4. New issue approval column
  5. Prioritized backlog column
  6. Check the status of new Pre-work issues in the new issue approval column (3 minutes per issue)
  7. Check the Questions & Review Column for new or not documented items (3 minutes per issue)
  8. Process the items in the QA column (3-5 minutes per issue)
  9. Review items in the icebox to see if any dependencies are completed (3 minutes per issue).
  10. Issues with Issues Numbers as their dependencies (10 issues per min)
  11. Issues that need review to see if they need other issues made or judgement calls on if the criteria have been met (3-5 per issue)
  12. Check to see if there are any overlap between technology and languages https://www.hackforla.org/projects-check/ (5 min)