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

Create a Guide/Template: Weekly Label Check for your project #88

Open
7 tasks
ExperimentsInHonesty opened this issue Jan 18, 2022 · 3 comments
Open
7 tasks
Labels
Complexity: Missing CoP: Product feature : guide creation Phase: 1 - Gather Examples Solo size: missing status: 1.1 needs wiki examples Gathering examples by checking each team's wiki status: 1.2 needs issues examples Gathering examples by checking each team's issues status: 1.3 needs project board examples Gathering examples by checking each team's project board cards status: 1.4 needs slack examples Check each team's slack channel for examples

Comments

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Jan 18, 2022

Overview

We need to create a guide to performing Weekly Label check on a project so that teams can stay focused on their roadmap

Action Items

The phases in the guide-making process are listed below. Each phase displayed in blue is linked to a wiki page with instructions on how to complete that phase. Open the wiki page in a new tab, copy the instructions for each part into the section labeled 'Tasks' at the bottom of this issue, and complete each task listed.

Resources

Template

Projects to check

Tasks

  • This is where you will copy instructions from the wiki page for the step you are currently on.
@ExperimentsInHonesty
Copy link
Member Author

The following can be copied into a template to use. It has a template inside it, so I choose to put it in this comment instead of a copy box

Dependency

[insert next weeks date] (Check gets done weekly)

Overview

We need to perform a weekly check on issues to make sure they all conform to our label and milestone schema.

Action Items

  • Check the following to make sure that they are all 0/0 (Links for checking to make sure that all issues either have a ___ or a ____ missing label)
    • Role
    • size
    • feature
      • Add any label missing (e.g., a new feature label go added to the project, but didn't yet get added here) and update link
    • issues that have not yet been added to project board
      • add to project board
  • if changes were made, recheck to make sure all links ended up 0/0
  • Audit for issues with Missing labels (to determine if we are making progress)
    • Copy this audit report format to a comment below
Date: 
- [ ] Did you have to update the 0/0 links above?  if yes, please say what you did (e.g, Added features to the features check above or added an issue to the project board that has not been added yet).
- [ ] Report what the numbers are on issues that are missing labels (e.g., size, ending at 12/5)
   - [ ] role, ending at
   - [ ] size, ending at
   - [ ] features, ending at
   - [ ] milestone, ending at

Icebox issue

@fchan218
Copy link
Member

Prior version of issue

Overview

We need to create a guide to performing Weekly Label check on a project so that teams can stay focused on their roadmap

Action Items

  • Gather examples of how other Hack for LA projects have done, adding each example as a link in the resources section
    • Once done, remove the "TG: Gather Examples" label and add the "TG: Draft Template" label
  • Create a draft template, either in markdown format in this issue or a google doc in the old product management google drive new product management google drive>Product Management Guides
    • Once done, remove the "TG: Draft Template" label and add the "TG: Create Guide" label
  • Create a guide on how to use the template
    • Once done, remove the "TG: Create Guide" label and add the "TG: Review Guide" label
  • Review the guide with product management communities of practice
    • Once done, remove the "TG: Review Guide" label and add the "TG: Leadership Review" label
  • Present to Hack for LA leadership team for sign off
    • Once approved, remove the "TG: Leadership Review" label and add the "TG: Place Guide" label
  • Possibly create an issue template on .github
    • Include link to template under resources if you add it as a template in .github

Resources

Projects to check

Template

@fchan218
Copy link
Member

Assignee, Labels, Project Board Placement, and Milestones for this issue in the Product Repo:

Screenshot 2024-10-18 at 4 25 33 PM

@fchan218 fchan218 transferred this issue from hackforla/product-management Oct 18, 2024
@fchan218 fchan218 added Phase: 1 - Gather Examples Solo status: 1.1 needs wiki examples Gathering examples by checking each team's wiki status: 1.3 needs project board examples Gathering examples by checking each team's project board cards status: 1.2 needs issues examples Gathering examples by checking each team's issues status: 1.4 needs slack examples Check each team's slack channel for examples size: missing Complexity: Missing feature : guide creation and removed documentation labels Oct 18, 2024
@fchan218 fchan218 added this to the 06.01 MVP Knowledge milestone Oct 18, 2024
@fchan218 fchan218 moved this from Properly Labeled and not yet ready for Guides Team Review to Needs to be Triaged in P: Guides: Tracker of issues in CoPs Oct 18, 2024
@fchan218 fchan218 moved this to Needs to be Triaged in P: Guides: Knowledgebase Content Tracker Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Missing CoP: Product feature : guide creation Phase: 1 - Gather Examples Solo size: missing status: 1.1 needs wiki examples Gathering examples by checking each team's wiki status: 1.2 needs issues examples Gathering examples by checking each team's issues status: 1.3 needs project board examples Gathering examples by checking each team's project board cards status: 1.4 needs slack examples Check each team's slack channel for examples
Projects
Status: Needs to be Triaged
Status: Needs to be Triaged
Development

No branches or pull requests

4 participants