search

hackforla / ops

A repository for the OPS Community of Practice
https://github.com/orgs/hackforla/projects/73
MIT License
8 stars 7 forks source link

Create a Guide/Template: Story Points for your project #18

Open NivenPrasad opened 3 years ago

NivenPrasad commented 3 years ago

Overview

We need to create a guide to using Story Points so that teams can estimate work to be done, predict launch dates, track velocity, and report out to stakeholders.

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.

Use these resources to create your guide:

Olivia-Chiong commented 3 years ago

@NivenPrasad and @khushbooshah-PM I discovered today that there is some usage of story points on Food Oasis. Check with @ktjnyc for more information.

NivenPrasad commented 3 years ago

Draft Guide

khushbooshah-PM commented 3 years ago

I and Niven have gathered information from the different teams from HFLA and tried to gain more information about the usage of Story Points industry-wide.

We connected with two teams from HFLA and going to connect with one more next week to know more about their process.

Our idea is to connect Industry practices and implement them in HFLA projects and bridge the gap if any.

The draft guide is attached below. It is still in DRAFT status. We are going to refine it further.

Story Points

khushbooshah-PM commented 3 years ago

We have gathered examples, now we are creating draft.

NivenPrasad commented 3 years ago

@ExperimentsInHonesty @Olivia-Chiong @khushbooshah-PM I'd like to QA/feasibility test these extensions (perhaps with a developer):

  1. https://github.com/brthrs/github-project-story-points
  2. https://github.com/banyan/github-story-points

Potentially even update scripts for HfLA specific context.

Benefit is that task-by-task visualization and easy reporting can be integrated within GitHub project boards.

Olivia-Chiong commented 3 years ago

I think it would be good to test this out on a project. @NivenPrasad Can we try implementing this on 100A?

Olivia-Chiong commented 3 years ago

Hi @NivenPrasad I know we did not implement this on 100A, but is the guide good to go?

It will need to be reformatted to https://github.com/hackforla/product-management/issues/123 and https://github.com/hackforla/UI-UX/issues/55

ExperimentsInHonesty commented 2 years ago

There are a couple of problems with the current guide

  1. It's not in the correct format (less important than items that follow)
  2. The current guide is made from a practice that we don't do at Hack for LA. Its effective in an enterprise environment, but is too much lift for our environment. We have a different methodology that is simplified, and easy to understand and use. - This guide needs to capture the way we have been using story points for the past 6 months on various projects so that we can publish a standardized methodology
Points for Repos Google Sheet: GitHub: Point System Labels label Description
size: 0.5pt Can be done in 3 hours or less
size: 1pt Can be done in 6 hours or less
size: 2pt Can be done in 7-12 hours
size: 3pt Can be done in 13-18 hours
size: 5pt Can be done in 19-30 hours
size: 8pt Can be done in 31-48 hours
size: 13+pt Must be broken down into smaller issues

By using this simplified points system you can evaluate total number of weeks required for a specific role, and divide that by the number of resources you have (people), to determine when you can deliver any given objective (a feature, a milestone, etc.), and if you need to recruit for more resources.

Teams that are using this point system Access the data Open Community Survey

ExperimentsInHonesty commented 2 years ago

Once the guide draft has been made, add the label leadership review and move this issue into the Needs leadership review column on the guides tracker project board (see top right of this issue).

Comments for the leadership review team.

I have tried the installation for https://github.com/banyan/github-story-points on a personal rep to see how it works, and it works great. But if it used labels, it would be better. Talk to developers at hack for la to see if we can't make a different version of it for hackforla use.

Someone has already done it, but it's not published as a Chrome extension. https://github.com/cmcarthur/github-projects-story-points

Next steps: We need to fork the repo, customize it to the label we use hackforla/ops#18 publish it as a chrome extension so it can easily be installed by team members.

ExperimentsInHonesty commented 2 years ago

As per Ava's suggestion that the code be useable if people use different size labels, the script could check a csv

number,label name,description 0.5,size: 0.5pt,Can be done in 3 hours or less

ExperimentsInHonesty commented 2 years ago

Ava is working on this extention here https://github.com/100Automations/futureautomations/issues/49

ExperimentsInHonesty commented 5 months ago

This issue is being moved to the new issue approval column so that a CoP lead can summarize all the notes that are necessary in order for a new person to take on this issue, and add that to the top and hiding all the comments. The goal here is to make the issue clear for a new person, while taking advantage of all the work that went into it so far.

Aditya23soni commented 5 days ago
Prior version of issue

### Dependency ~- This will be picked back up again after Ava finishes her firefox extension~ ~- https://github.com/100Automations/futureautomations/issues/49~ - This is mostly done. It is possible to use the extension on Firefox by following her instructions~ https://github.com/100Automations/github-story-points-calculator/blob/main/README.md ### Overview We need to create a guide to using Story Points so that teams can estimate work to be done, predict launch dates, track velocity, and report out to stakeholders. ### Action Items - [ ]~Gather examples of how other projects have done, adding each example as a link in the resources section~ - [x] Once done, remove the "TG: Gather Examples" label and add the "TG: Create Guide" label - [ ] Create a guide on how to create size labels using the chart in comments below - [ ] 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 ### Resources ~[311 Data](https://github.com/hackforla/311-data/labels)~ ~[Food Oasis](https://github.com/hackforla/food-oasis/labels)~ #### Use these resources to create your guide: - [Guide for how to format a guide](https://docs.google.com/document/d/1-8gmeC-wnfM8C8fVvmTP1BLA2WfNjKH_XJrHB1OAV6Q/edit#heading=h.b0u940yzvl2r) - [Template for creating a guide](https://docs.google.com/document/d/1kV29V-mRPBNRRfIbYHrz05FElC02Dh6egaMANlxaZrM/edit#heading=h.c8tc614ce3iu) - [Guide for how to add screenshots and graphics to your guide](https://docs.google.com/document/d/1OyPfKqUU7ZinhjMoRmsXywyZfME_Oo_hpC2Zdxlb310/edit) #### Draft guide [Draft Guide](https://docs.google.com/document/d/1GSFbnNWI7BsxIN3lPrRMN_qoILJ_ighc5ne-ED4MpKQ/edit)

Aditya23soni commented 5 days ago
Assignee, Labels, Project Board Placement, and Milestones for this issue in the Ops Repo:

Screenshot 2024-10-04 at 6 21 18 PM

Aditya23soni commented 5 days ago
Aditya23soni commented 5 days ago

@NivenPrasad This guide issue is moving to the knowledgebase-content repo. If you would like to maintain edit access to the issue and its associated files, please fill out the Google Drive Access Form.

ExperimentsInHonesty commented 5 days ago

This issue should replace - https://github.com/hackforla/knowledgebase-content/issues/1