Closed Shreyanand closed 2 years ago
:+1: @Shreyanand yes, I think having OKR issues to track is a good approach to quantify OKR progress. : )
Is there a need to create an OKR label that we can use?
Yes I think an OKR label would make our lives easier. @hemajv did you use labels in your initial experiments or some other approach?
@Shreyanand so the labels we had were mainly to differentiate which teams the OKR belongs to what kind of labels did you have in mind?
@durandom pitched that we start without the label "OKR" so that we are not imposing a structure on the repositories. Our first try should be to see If we can measure the progress of a repository based on the quantity and quality of issues and PRs being created. If that doesn't work or in other words if it doesn't effectively reflect the progress of a repository, we can think of imposing a structure in place as a last resort.
As various KRs for objectives focus on metrics, it would be a good time to start defining the process around how a team would approach for having metrics in place for their use case. The process would cater to having feature requests created via issues in this repo highlighting:
@MichaelClifford @Shreyanand @chauhankaranraj @schwesig @codificat @aakankshaduggal @oindrillac @durandom @suppathak thoughts/suggestions?
This issue is created to discuss different approaches that we can take to reflect meaningful progress of a key objective. The comments in this thread can be designs to solve this problem. We can discuss alternative approaches and once we start converging, we can add missing details.
Example solution:
cc @hemajv