Create a Guide/Template: Story Points for your project

[NivenPrasad]

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.

• Gather Examples Solo (open in a new tab)
• Gather Examples Collaboratively
• Create a Guide Draft
  • If needed, create a template
• Have your guide peer reviewed
• Present your guide for leadership review

Resources/Instructions

• Google Drive Folder for this Guide’s documents and shortcuts (to documents in other locations) 0071 [DRAFT] Story Points for your project

Use these resources to create your guide:

• Guide for how to format a guide
• Template for creating a guide
• Guide for how to add screenshots and graphics to your guide

Draft guide

• Draft Guide Has been deleted

Projects to Check

Tasks

• This is where you will copy instructions from the wiki page for the step you are currently on.

[Olivia-Chiong]

@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]

Draft Guide

[khushbooshah-PM]

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]

We have gathered examples, now we are creating draft.

[NivenPrasad]

@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]

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

[Olivia-Chiong]

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 #106 and #93

[ExperimentsInHonesty]

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]

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 #71
publish it as a chrome extension so it can easily be installed by team members.