Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Roadmap work to be done before a feature is released #387

Open
9 tasks
shmonks opened this issue Sep 20, 2024 · 0 comments
Open
9 tasks

Roadmap work to be done before a feature is released #387

shmonks opened this issue Sep 20, 2024 · 0 comments

Comments

@shmonks
Copy link
Member

shmonks commented Sep 20, 2024

Dependencies

  • PD has a feature to be released

Overview

We need to drive the process for completing and releasing a feature so that:

  • Progress towards completion can be secured and assessed, including the removal of obstacles
  • Progress is visible to all stakeholders
  • Progress can easily be reported to stakeholders

Action Items

  • Consider creating a consistent rule for renaming Issues on the PD project board, so it's immediately clear at the beginning of the issue name who needs to work on them. For example, 'Create...' (for Dev), 'Implement...' (for Dev), 'Design...' (for Design) 'Usability testing...' (for Research)
  • Consider creating a series of ranking labels like the following (used by TDM) to be applied to issues in the Prioritized Backlog:
  • time sensitive - issues with this label go to the top
  • priority: must have - for MVP features
  • priority: should have - for MVP features
  • priority: could have
  • priority: won't have this time
  • On PD project board, create a new view formatted as a roadmap and with filters similar to this example from the TDM project board, including some variation of is:open label:"p-feature: My Projects Page" "p-feature: My Project Page-Admin view" "p-feature: Admin Tools" label:"priority: MUST HAVE" -label:"p-feature: snapshot"
  • When plotting the end dates for issues, remember that an issue with the label size: 1pt should represent about one week's work for a developer
  • Do a regular audit of the whole PD project board filtered for unassigned issues,
    • Is there a reason why they can't be worked on? Reach out to someone holding the relevant role: and ask
    • Assign issue(s) if there's no reason why they can't be worked on
  • Do a regular audit of issues in the Ice Box, as per Ice Box review #386, to see if any dependencies have been released and those issues can therefore be put into the Prioritized Backlog:

Resources/Instructions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🧊Ice Box
Development

No branches or pull requests

1 participant