Create a new issue template: Initiative Review

[ExperimentsInHonesty]

Overview

We need a new template for evaluating initiatives to determine status, and next steps if any so that we can display, prioritize and measure our initiatives.

Action Items

• [x] Draft a template in the comments below containing:
  • [x] name (the name you want to appear on this page: https://github.com/hackforla/civic-opportunity/issues/new/choose)
  • [x] about (the user story for when we use the template)
  • [x] title: name that matches the label [INSERT NAME OF X] (e.g., Initiative Review: [INSERT NAME OF INITATIVE])
  • [x] labels (what labels that an initiative should have when it is first opened. This is not all the labels it will have over time, just the ones necessary for the starting of the issue - specifically the role of the first person who will work on it, and then the type of initiative or feature.)
  • [x] assignees (do not put anything here, we do not automatically assign anyone to new issues, rather we use the role labels to indicate what type of role should work on the item when its in the prioritized backlog)
  • [x] regular format

    ### Overview
    ### Action Items
    ### Resources/Instructions

• [ ] Get signoff by all team members that they understand how it works
  • [ ] Revise as needed
  • [ ] Repeat until done
• [ ] Get signoff by Bonnie that it meets the Overview objective
  • [ ] Revise as needed
  • [ ] Repeat until done
• [ ] Make a Template out of it. Requires Admin access to add it via the button method, anyone else can add using the PR method.

Resources/Instructions

Admins on the repo can add new templates to the repo. You know you are an admin if:

you see the gear at the top of the repo


and then the button marked "setup templates"


[ExperimentsInHonesty]

There will likely be more Action Items added to this template after we have used it once. So once the template is approved and created, please don't make all the initiative issues at once. Make 1 and then we can revaluate after we have used it through the defined steps.

---

name: Initiative Review about: template for evaluating initiatives to determine status, and next steps if any so that we can display, prioritize and measure our initiatives. title: Initiative Review: [INSERT NAME OF INITATIVE] labels: Initiative Review, role: UI/UX research assignees: ''

Overview

We need to Review the [INSERT NAME OF INITATIVE] to determine determine status, and next steps, if any, so that we can display, prioritize and measure impact of this initiative

Action Items

• [ ] UI/UX Research Identifies the assets (including documentation) for this initiative and add them to the Resources section below. Check the following and any other resources you can think of:
  • [ ] wiki
  • [ ] team google drive
  • [ ] cards on the project board review column,
  • [ ] other issues, etc.).
• [ ] remove the label "role: UI/UX research" and add the label "role: org" and put into the prioritized backlog
• [ ] Org rep self assigns, reviews and adds any additional notes (including Status)
  • [ ] add the label "role: UX" and put into the prioritized backlog for meeting scheduling
• [ ] UI/UX Research and Org rep meet to discuss next steps

Resources

[ExperimentsInHonesty]

@alexilee @Arjayellis Please have the whole team review this to see if they have anything they want to add, clarify, etc. - notes, including signoff if applicable should be noted in the comments here.

[Arjayellis]

@patrickm-tan @Jackie-UX please see above and add any feedback/comments as necessary

[ExperimentsInHonesty]

How will we prioritize initiatives? Please brainstorm below:

• Time
  • Currently in constant, must be kept updated
  • Currently in occasional use, update as needed
  • Future use, define when
  • On hold, why
  • Closed, will not be used again - needs documenting
  • Closed, will not be used again documented
• Impact (directly quantified by how it meets the Objective of Civic Opportunity Project one sheet)
  • ?
• Effort
  • ?

[alexilee]

Team brainstormed a few ideas:

• Stakeholder Input (How important does Org rep believe an initiative to be?)
• Effort (t-shirt sizing)
• Impact (rough rating system 1-5?)
• Team Bandwidth - do we have the right people to execute on the initiative?

[alexilee]

Created issue template Review Initiative.

[Arjayellis]

How do we assess initiatives in order to assign status and prioritize:

Labels: Status: Impact: Effort:

• Status

  • Active (at least one member is actively working on it)
  • On hold (no one is working on it, but we plan to at a future date)
  • Why?
  • Next steps
  • Closed (no one is working on it, and we do not plan to work it moving forward)
  • Why?

• Impact (1-5 rating?)

  • Reach (how many people is it affecting) (monthly and annually as a percentage of membership) - we will probably need data on what community of practice percentages make up HfLA.
  • Does it affect one or multiple parts of the organization (which parts of the organization does it affect)
  • How many types of stakeholders does it benefit (which stakeholders does it benefit)

• Effort (1-5 rating?)

  • How much time will it take
  • How many people are required to complete it (tasks, approvals, etc.)
  • What kind of work/skill is included
  • How technically difficult is it (dependencies, technologies, etc.)

• Stakeholder Input

  • Org Rep - aka, Bonnie, Olivia
  • CoP Leads
  • Members

[ExperimentsInHonesty]

Randall and I made this board to manage the Initiative reviews: https://github.com/hackforla/civic-opportunity/projects/3