OKRs! with a clear tie back to the deployment direction
Use the new deployment-direction label on issues and label - make things easier to track
Ensure we break deliverables into epics that can be closed upon completion - all
Create boards that we can look at - @kbychu to follow up
Monthly Async issue summarizing progress (How did we do on deliverable previously, how we are tracking on our OKRs) - @kbychu to follow up
Update Deployment direction and group's direction pages to clearly state what we are working on next, reference async issue - @kbychu@nagyv-gitlab@cbalane
0 of 2 checklist items completed
· Edited by
Chris Balane
@cbalane What I think would be helpful would be insight into which epics on the roadmap are directly related to the Deployment Direction. When I'm asked the question "what progress is being made on deployment direction" it is difficult to answer without that direct mapping to the features/issues we are working on.
Perhaps if we create a parent epic for these direction "milestones" and each group that has related child epics can link them? Also, I know we use the direction label on issues and epics, but should we use a label that directly calls out deployment direction?
**Edit to say that I realize that this comment is very tactical/process oriented, but my main point was visibility and tying these features together to help show that progress on the larger goals
@nicolewilliams thanks for the feedback and tactical suggestions. and by the way, this issue was created to solve for those questions you get about progress since we're definitely making progress
Regarding the deployment direction parent epic and linking child epics idea, the epic feature is too limited in my view since issues/epics are limited to having one parent epic. I'd still want the flexibility to have our own epic structure that's user/feature/problem focused.
@kbychu I like the idea of having a deployment direction label to tag issues and epics. And then perhaps an epic that lays out the plan, strategy, and milestones for the deployment direction and links to the other epics.
@kbychu / @nagyv-gitlab / @cbalane - Question: could we update the issue description with all the epics/milestones we currently have completed or planned?
I added the issues that I'd consider fall under this category (shared with other categories) and were shipped recently.
During this activity, linking issues was often problematic as it would be the epic that I wanted to link. This might be solved in the future as we start using Task more.
Circling back on this issue...I have a proposal on how to better track, report on, and align on progress towards the deployment direction.
I'll create a goal setting issue (much like an OKR or the way OKR should be done). The teams define outcomes they want to achieve...to do so, also define the work you might want to get done in Q3
Once per month, we should get together (async) to see where we are in terms of progress. If needed, we should have synchronous discussion to facilitate a free-flowing discussion
OKRs! with a clear tie back to the deployment direction
Use the new deployment-direction label on issues and label - make things easier to track
Ensure we break deliverables into epics that can be closed upon completion - all
Create boards that we can look at - @kbychu to follow up
Monthly Async issue summarizing progress (How did we do on deliverable previously, how we are tracking on our OKRs) - @kbychu to follow up
Update Deployment direction and group's direction pages to clearly state what we are working on next, reference async issue - @kbychu@nagyv-gitlab@cbalane