Create project and CoP Accomplishment Epics

[Rabia2219]

Overview

We need to create epic issues for each project and CoP so that we can get the project accomplishments onto the website.

Details

Management includes

• identifying missing issues
• creating new issues
• prioritizing for the website team

Action Items

• [x] Create template
• [x] Test template by creating one issue for a single project
• [x] Get sign-off by org rep
• [x] Turn into issue template, add to Resources section (2.01)
• [ ] Create an epic issue for your project or CoP by using the template issue (resource 2.01)
  • Customize epic issue by adding
  • [ ] project name in title
  • [ ] project name in resources (under Links created by working on this issue)
    • [ ] 2.01
  • project repo issue tab link on resource 2.01
    • [ ] Go to the list of label spreadsheet (this issues resource 1.01)
    • [ ] copy URL from column D (Main Repo URL, Issues tab)
    • [ ] Paste URL on resource 2.01
• [ ] Click on Submit New Issue
• [ ] Replace P or CoP missing label with the relevant P or CoP label
• Replace the PA and S missing labels with their values from (resource 1.01)
  • [ ] PA (column E)
  • [ ] S (column G)
• Add new epic issue to the following boards
  • [ ] CoP: Admin: Project Board
  • [ ] HfLA: Project Team Tasks
  • [ ] Your team's project board
• [ ] Move issue to New issue approval column
• [ ] Add the label ready for prioritization
• [ ] Add link to epic created (resources 2.02 in this issue), unless you are doing this in the product-management CoP meeting, in which case, paste it into the chat so that one person can do all the updates.

Resources

Provided by this issue

• 1.01 List of Project Name Labels
• 1.02 Hack for LA About page, accomplishments section: https://www.hackforla.org/about/#accomplishments

  Created by working on this issue

• 2.01 Issue Template Create Accomplishment Epic for your Project or CoP
• 2.02 Epic issues created
  • https://github.com/hackforla/admin-accomplishments/issues/4
  • https://github.com/hackforla/admin-accomplishments/issues/5
  • https://github.com/hackforla/admin-accomplishments/issues/6
  • https://github.com/hackforla/admin-accomplishments/issues/7
  • https://github.com/hackforla/admin-accomplishments/issues/8
  • https://github.com/hackforla/admin-accomplishments/issues/9
  • https://github.com/hackforla/admin-accomplishments/issues/10
  • https://github.com/hackforla/admin-accomplishments/issues/11
  • https://github.com/hackforla/admin-accomplishments/issues/12
  • https://github.com/hackforla/admin-accomplishments/issues/13
  • https://github.com/hackforla/admin-accomplishments/issues/14
  • https://github.com/hackforla/admin-accomplishments/issues/15
  • https://github.com/hackforla/admin-accomplishments/issues/16

[Rabia2219]

Template Draft

Template Title

Accomplishments Epic: [Name of Project]

Labels

pa: Missing
s: missing

Template Body

### Overview
We need to manage the accomplishment issues for our project or CoP, so that the website team can publish the yearly accomplishments for our project on the Hack for LA website.

#### Details
Where the accomplishments will be published (see resource 1.02)

- Accomplishments on the Hack for LA website are:
   - readable even if you don't know anything about the project
   - short
   - clearly articulated achievements that funders would care about
   -  list partners if available

### Action Items for all accomplishments 2020-2024
#### Create an issue on your repo to gather/draft project accomplishments
- Add the epic issue to the following project boards:
   - [ ] your project
   - [ ] HfLA: Project Team Tasks
- Search the project's repo for any accomplishment issues, add any links you find to a comment
  - [ ] Go to the project repo issue tab (resource 2.01) and look for any issues previously created for writing accomplishments for the Hack for LA website. It might have the label feature: accomplishments or be named ...Accomplishment Summary for HfLA Website...
-  If there is an issue, compare it to the Accomplishment Issue Template (resource 1.03.01), and update it, so that it has the same steps and resources.
-  If there is no issue called `...Accomplishment Summary for HfLA Website 2020-2024` (or an issue you already made that does the same thing), create the issue now
   - [ ] open a new blank issue on your repository
   - [ ] copy in the title and body from resource 1.03.01
   - [ ] add it to your project board
   - Customize the resources
      - [ ] resource 1.01 with the link to the epic
      - Customize resource 1.04.01 with the link to your one sheet
        - [ ] go to resource 1.05.01 on this epic,
        - [ ] find the file name that corresponds to your project (if there is one there)
        - [ ] add link to resource 1.04.01 on the issue you created.
      - [ ] Customize resource 1.03 with Google Drive for your project and add project name
      - Customize resource 1.04.02 with the Overview link from your project page on hackforla.org
        - [ ] go to [hackforla.org/projects](https://www.hackforla.org/projects)
        - [ ] find your project card
        - If there is an Overview link for your project
           - [ ] add it to 1.04.02
        - If there isn't an Overview link for your project
           - [ ] write `none` after 1.04.02 One sheet link from Hack for LA website (Overview):
      - [ ] Customize 1.04.03 with Project Name
      - Customize 1.05 by adding issue tab link
         - [ ] Copy resource 2.01 in this epic to 1.05 in the new issue
   -  Add the appropriate labels by replacing missing series labels with
      - [ ] size: (Number of years since your repository was created)
      - [ ] role: product or if you have a marketing person marketing role: marketing
      - [ ] p-feature: accomplishments
      - [ ] complexity: large
      - [ ] time sensitive
   -  Add the appropriate milestone
      - [ ] org requirements (if you have this)
      - [ ] project management (if you don't have org requirements)
- Link the issue to this epic
   - [ ] add the issue number to resource 2.02.01
- put the issue you just created in the prioritized backlog
- Put the issue you just created in the prioritized backlog
   - [ ] Place in the prioritized backlog.  Issues with time sensitive labels jump the queue, and are prioritized with other time sensitive issues
- Let the Admin team know that you are finished creating this epic and the child issue
   - [ ] Add a `ready for prioritization` label to this issue

#### work on the issue
- [ ] once the issue has drafts or questions for PM CoP then do the rest of the steps
- Prepare the epic for discussion with Product Management CoP
   - [ ] add a label `ready for product management lead`
   - [ ] move to the questions / review column
   - [ ] add to cop product management agenda for discussion (resource 1.04.01)
- Discussion with Product Management CoP
   - [ ] review the findings and accomplishment drafts in the `...Accomplishment Summary for Website 2020-2024` issue to provide feedback for revision or sign-off
   - [ ] Org rep sign-off
- [ ] Unassign everyone from the issue, add dependency label, and move issue to icebox with the following text

October [YYYY] or sooner if there are accomplishments to share

### Action items for subsequent years (2025 onward)
- [ ] copy the following into a comment on this epic 
<details><summary>copy block</summary>

Action items for subsequent 2025 onward

Create an issue on your repo to gather/draft project

• create Accomplishment Summary issue for this year
  • [ ] open a new blank issue on your repository
  • [ ] copy in the title and body from resource 1.03.02
  • [ ] add it to your project board
  • Customize the resources
    • [ ] resource 1.01 with the link to the epic
    • Customize resource 1.04.01 with the link to your one sheet
    • [ ] go to resource 1.05.01 on this epic,
    • [ ] find the file name that corresponds to your project (if there is one there)
    • [ ] add link to resource 1.04.01 on the issue you created.
    • Customize resource 1.04.02 with the Overview link from your project page on hackforla.org
    • [ ] go to hackforla.org/projects
    • [ ] find your project card
    • If there is an Overview link for your project
      • [ ] add it to 1.04.02
    • If there isn't an Overview link for your project
      • [ ] write none
    • [ ] Customize 1.04.03 with Project Name
    • Customize 1.05 by adding issue tab link
      • [ ] Copy resource 2.01 in this epic to 1.05 in the new issue
• [ ] Click on the Submit new issue button
  • add the appropriate labels
    • [ ] size: 1pt
    • [ ] role: product or if you have a marketing person marketing role: marketing
    • [ ] p-feature: accomplishments
    • [ ] complexity: medium
    • [ ] time sensitive
  • add the appropriate milestone
    • [ ] org requirements (if you have this)
    • [ ] project management (if you don't have org requirements)
• link the issue to this epic
  • [ ] add the issue number to resource 2.02.02 (or the next number in this series as every year gets added)
• put the issue you just created in the prioritized backlog
• Put the issue you just created in the prioritized backlog
  • [ ] Place in the prioritized backlog. Issues with time sensitive labels jump the queue, and are prioritized with other time sensitive issues
• Let the Admin team know that you are finished creating this epic and the child issue
  • [ ] Add a ready for prioritization label to this issue

work on the issue

• [ ] once the issue has drafts or questions for PM CoP then do the rest of the steps
• Prepare the epic for discussion with Product Management CoP
  • [ ] add a label ready for product management lead
  • [ ] move to the questions / review column
  • [ ] add to cop product management agenda for discussion (resource 1.04.02)
• Discussion with Product Management CoP
  • [ ] review the findings and accomplishment drafts in the ...Accomplishment Summary for Website [YYYY] issue to provide feedback for revision or sign-off
  • [ ] Org rep sign-off

    
    </details> 

Resources

Links provided by this issue

• 1.01 This issue is a subset of: Create project and CoP Accomplishment Epics #3
• 1.02 Hackforla.org website, about page, accomplishments section: https://www.hackforla.org/about/#accomplishments
• 1.03 Issue Templates:
  • 1.03.01 Project Accomplishment Summary for HfLA Website 2020-2024
  • 1.03.02 Project Accomplishment Summary for HfLA Website [YYYY]
• 1.04 Product Management CoP Agendas
  • 1.04.01 2024: https://github.com/hackforla/product-management/issues/379
  • 1.04.02 [YYYY] see the pinned issue in the repo https://github.com/hackforla/product-management/issues/
• 1.05 One Sheets for projects
  • 1.05.01 Approved One Sheet Directory of PDFs: https://github.com/hackforla/product-management/tree/master/project-one-sheets
  • 1.05.02 Guide: How to Write a One Sheet - which includes how to update the one sheets, where they are located, etc.

Links created by working on this issue

• 2.01 [Replace with PROJECT or CoP NAME repo, Issues tab]
• 2.02 Accomplishment Summary issues
  • 2.02.01 2020-2024:
  • 2.02.02 2025:

[Rabia2219]

Template Draft

Template Title

[PROJECT NAME]: Accomplishment Summary for HfLA Website 2020-2024

Template Body

### Overview

We need to write brief summaries of project accomplishments for each year of the project's life, to go on the website's accomplishments page.

### Action Items
- Review the accomplishments on resource 1.02 to see how they are worded, and note the following: Accomplishments on the Hack for LA website are:
   - readable even if you don't know anything about the project
   - short
   - clearly articulated achievements that funders would care about
   -  list partners if available
- Find and review all previous onesheets
   - [ ] Find all the one sheets (check Project's Google Drive resource 1.03) and link the folder to resource 1.04.03
   - [ ] Review all previous project onesheet drafts under 1.04 (including edit history)
- Search the project's repo for any accomplishment issues, add any links you find to a comment
  - [ ] Go to the project repo issue tab (resource 1.05)
  - [ ] review all closed issues, looking for details of your project's progress that you could use in your accomplishment summary, noting the accomplishment and date of completion
  - [ ] Put the links relevant to that search under the below heading in chronological order

Project or CoP's repo issue searches

- for each search you perform, indicate what you searched in the filter bar to get the result and link it to the URL (e.g.,)

Searches

• [Replace with what you searched for in the Filter bar]
• [Replace with what you searched for in the Filter bar]
• [Replace with what you searched for in the Filter bar]

  
  - [ ] Draft a brief paragraph describing what the project accomplished for each year
  - Update the epic issue (resource 1.01)

• [ ] Add the following comment

  We have completed the accomplishments for 2020-2024

• [ ] Add the label updated
• [ ] Add the label ready for org rep
• [ ] Move to the questions/review column on the Team Tasks project board

Resources/Instructions

• 1.01 Accomplishments epic:
• 1.02 Hackforla.org website, about page, accomplishments section: https://www.hackforla.org/about/#accomplishments
• 1.03 [[PROJECT NAME] project Google Drive]
• 1.04 One Sheets:
  • 1.04.01 One sheet from product-management repo:
  • 1.04.02 One sheet link from Hack for LA website (Overview):
  • 1.04.03 [Folder with One sheet drafts on [PROJECT NAME]'s Google Drive]
• 1.05 [Replace with LINK 2.01 FROM EPIC]

[ExperimentsInHonesty]

• [x] labels to add to the accomplishments repo:
  • pa and
  • s

[ExperimentsInHonesty]

• [x] Add instruction to https://github.com/hackforla/admin-accomplishments/issues/3#issue-2564623165 to add the project name label to the epic the project lead is creating

[ExperimentsInHonesty]

• we were working on this draft https://github.com/hackforla/admin-accomplishments/issues/4

[ExperimentsInHonesty]

• [x] Create size labels

[ExperimentsInHonesty]

Bonnie to review the epic made for website to see if it makes sense in connection with the next issues that would need to be made. It does not, and needs to be fix

epic does not ask them to create the next issue - it should the original marketing epic was to find issues in the marketing repo, but those are not a factor here.

[ExperimentsInHonesty]

Need to do the following:

Update the Epic template

• draft: https://github.com/hackforla/admin-accomplishments/issues/3#issuecomment-2391974466
• test: https://github.com/hackforla/admin-accomplishments/issues/4
• add instructions for customizing the child issue on their repo with:
  • [x] project name
  • [x] Google Drive link
  • [x] GitHub one sheet directory
  • [x] link to the issue tab from the epic
  • [x] change instructions so that it tells them to make sure the child issue has the same steps as our template

Update the child issue

• [x] https://github.com/hackforla/admin-accomplishments/issues/3#issuecomment-2392016349

update the Accomplishments wiki

• https://github.com/hackforla/admin-accomplishments/wiki
  • [x] add content to 2020-2024 when the child issue draft is finished
  • [ ] add content to 2025 when the child issue draft is finished

Publish the Epic template

• in the accomplishments repo
• [x] add the epic template above to the available templates on this repo
  • [x] use the example issue to grab labels from https://github.com/hackforla/admin-accomplishments/issues/4