Create GH/ZH and Scrum standards for all the platform teams to follow

[andreahewitt-odd]

Currently, there is no documented standards for Platform teams to follow in regards to how individual teams use GH/ZH. That was ok when we were immature and building the platform from scratch, but as we've grown so greatly the last 6 months, that's impeded leadership from being able to dive in and quickly find answers to questions.

Draft

AC:

• [ ] Draft the guidelines for Tickets, Initiatives, Boards
• [ ] Draft Guidelines for how teams run Scrum (ceremonies, expectations)
• [ ] Gather feedback from Leadership on the Draft
• [ ] Introduce the changes to TLs and PMs in a meeting and allow them to ask questions
• [ ] Test it out with a couple teams so we can iterate (at least one experience and one engineering)
• [ ] Publish
• [ ] Each team has it's own zenhub board
• [ ] Each team is estimating tickets
• [ ] Each team is using the sprint fied

[andreahewitt-odd]

Might think about breaking this down into pieces -- automated sprint aspect

[raywangoctova]

@andreahewitt-odd @little-oddball Can you guys provide platform teams with instructions on how to do the estimate for Q3? How to do estimation using the same method for issue and epic tickets?

How to estimate story points in ZenHub To get started with estimation in ZenHub, head to any Issue. Once in an Issue, on the sidebar will be a section for setting an Estimate.

By default, ZenHub comes with default story point values that follow the Fibonacci sequence: 1, 2, 3, 5, 8, 13, 21, and our own twist on the sequence to symbolize the largest story point value of 40.

The Fibonacci sequence is a popular Scrum method to follow when estimating work to be done as the agile story point values get significantly larger numbers. Going from quite small values to significantly large numbers reflects the uncertainty of estimating larger items.

A high estimate usually means that the work being estimated is not well defined. This uncertainty can create misunderstanding. Work that gets assigned a high story point value should be broken down in detail or transformed into multiple, smaller pieces of work.

Once you have an estimated value in mind for an Issue, simply click on an estimated value from the Estimate dropdown.

https://blog.zenhub.com/how-to-estimate-software-development-projects-with-story-points/#:~:text=How%20to%20estimate,the%20Estimate%20dropdown.

[raywangoctova]

@andreahewitt-odd and @little-oddball I shared this ZenHub estimation article with the Governance team and requested Chase to follow up with Andrea.