Product - hackforla/tdm-calculator GitHub Wiki
Hi PMs!
This page is a work in progress (we just started it 2025-03-24). Tell us what you need to know and we will add it here
Recurring Issues
- Weekly Label Check:
Issue templates
https://github.com/hackforla/tdm-calculator/wiki/Issue-Templates
Backlog Prioritization
Backlog prioritization is a structured process of ranking features, bug fixes, enhancements, and tasks based on strategic alignment, user impact, urgency, and technical complexity. The goal is to ensure teams focus on the highest-impact work. Product Managers lead and own this process.
How to prioritize the backlog:
- Time-Sensitive first (ordered by milestone)
- Remaining issues are prioritized by the MoSCoW method (Must, Should, Could), by milestone.
- If issues have the same MoSCoW category and milestone, prioritize based on their relative importance.
What is the MoSCoW method?
- Must-Have: Non-negotiable core functionality and compliance requirements without which the MVP cannot launch.
- Should-Have: Important but not critical for the MVP. These are high-impact enhancements that boost usability or operational efficiency once the core is stable.
- Could-Have: Nice-to-have features that can be added later without affecting the core functionality. Value-add or experimental features that enrich the product but won’t block launch
- Won’t-Have: Clearly out-of-scope items for this release; parked for future roadmap cycles pending user feedback, policy shifts, or data maturity.
Icebox Management Process
- Define Dependencies: For each icebox issue, record a clear dependency (link to a related issue or criteria for removal).
- Weekly Review: Every week, review dependencies—if satisfied (e.g., linked issue closed), remove the issue from the icebox.
- Transition to Approval: Move dependency-free items to “New Issue Approval”; ensure drafts are finalized and fully written items remain relevant.
Meeting Agendas
- TDM: PM meeting agenda (Wednesday) #2086
- TDM: Design Lead meeting agenda (Wednesday) #2088
- TDM: All Team meeting agenda (Wednesday) #1311
- TDM: Leads prep for Stakeholder meeting agenda (Thursday) #975
Prep for Meetings
Prework to prep for meeting
- Weekly label check #890
- Leave a thumbs up for PMs who have left an update on their issue.
- If PMs haven't left an update on their issues by [Name of Day] morning, tag their GitHub handles ask them to give an update.
- Create or update the agenda for the following meetings:
- TDM: All Team
- TDM: Leads prep for Stakeholder
- offboard team members that need it. See TDM-Calculator Team Roster for members that have changed status
- make sure there is a slide deck for stakeholder meeting #888 and there is a link to it in the agenda below
- Make sure that all items in the New Issue Approval column either have someone assigned and its a draft, or a
ready for...label. If this link has any issues, then they need to be labeled with the appropriate "ready for..." label - Make sure that all items in the Questions column have a
ready for...label. If this link has any issues, the issues will need to be labeled with the appropriate "ready for..." label - Review the issues with the following labels on the project board and address issues, or add to this agenda to discuss.
- P: TDM: project board, label:
Ready for Product - P: TDM: project board, label:
Ready for Prioitization - Check to see if there are any new questions on https://github.com/hackforla/tdm-calculator/issues/1938. If there are any new questions, add the link to the comment to the New Items in the agenda below
- P: TDM: project board, label:
- finish adding labels to the issue that are still missing them (see audit links above)
- review issues with epic label and define how to break down further
Recurring items:
All Completed Issues Should have Assignees
- Product: Make sure that all issues get properly attributed weekly #2525