OKR FY20-Q2: Make sure we're proactively addressing the most valuable doc improvements and corrections in every stage group. => 80%
Drawing from a combination of customer-submitted and GitLabber-submitted issues for documentation improvements deemed to be of a high priority by the technical writer (and as confirmed by the product manager):
Proactively identify and resolve high-impact documentation changes for every stage group:
- Identify 3 Manage stage issues and completely resolve.
- Identify 4 Plan stage issues and completely resolve.
- Identify 5 Create stage issues and completely resolve.
- Identify 3 Verify stage issues and completely resolve.
- Identify 2 Package stage issues and completely resolve
- Identify 4 Secure stage issues and completely resolve.
- Identify 4 Release stage issues and compleely resolve.
- Identify 3 Configure stage issues and completely resolve.
- Identify 2 Monitor stage issues and completely resolve.
The distribution of these 30 issues across stages was chosen based on the stages' average category maturity level targets for end of FY20-Q2.
Details
Use this board https://gitlab.com/groups/gitlab-org/-/boards/1086766?&label_name[]=docs-only to identify and prioritize open issues for your stage.
Use this table to paste issue references in the last 3 columns, including those you may have already completed this quarter that fit the criteria.
| Tech writer | Stage (issue board) | Goal (# issues) | Issues | Est by July 31 | Done |
|---|---|---|---|---|---|
| @eread | devops::manage | 3 | X | 3 | |
| @rdickenson | devops::plan | 4 | X | 4 | |
| @marcia,@axil | devops::create | 5 | X | 2 | |
| @eread | devops::verify | 3 | X | 3 | |
| @MattPennaThe3rd | devops::package | 2 | X | 0 | |
| @axil | devops::secure | 4 | X | 4 | |
| @marcia | devops::release | 4 |
|
X | 6 |
| @eread | devops::configure | 2 | X | 2 | |
| @axil | devops::monitor | 2 | X | 0 | |
| @axil, @eread | devops::enablement | 1 | X | 1 |
Add a comment and ping @mikelewis to propose issues and request for approval. Keep each stage in its own thread.
Ping @mikelewis about issues you may want to assign to @MattPennaThe3rd or @marcel.amirault, as they can help, but are not yet assigned to stages/groups.
* = At risk; likely to reassign.
Score
80%
24/30 merged by end of quarter: 80%
Review
GOOD:
- Good score, many high priority issues tackled.
BAD:
- Score could have been better; lowered in part due to one team member's vacation and due to getting started later in the quarter, generally.
TRY:
- Continual triage and assignment (incl. earlier in the quarter for OKRs) will help us meet deadlines generally and also reallocate work due to PTO. Remind team that when planning PTO to review assigned issues and determine (perhaps by checking with stakeholders) whether they need to be rescheduled or reassigned.
Designs
Relates to
- gitlab-foss #6321012.1
Activity
assigned to @mikelewis
mentioned in issue #382 (closed)
@mikelewis I'll have to figure out what stage Geo belongs to: https://gitlab.com/gitlab-org/gitlab-ce/issues/63210.
@eread Feel free to add a column with Enablement>Geo as the Stage (but really a Stage>Group) and add 1 or 2 issues, then decrement your other rows by that number of issues.
mentioned in issue gitlab-com/Product#363 (closed)
@mikelewis the Defend stage doesn't have anything yet. Can we replace that with Distribution? It's not a stage, but there are some issues I'd like to resolve, like this Gitaly one gitaly#1386 (closed).
I added issues for the Secure stage. 3 of them in the proposed column, 2 in the completed ( with an MR being reviewed and close to be merged).
Edited by Achilleas Pipinellis@axil The Gitaly group is listed as being under the Create stage.
But yes, for the purposes of this OKR I think we could shift the Defend work requirement elsewhere. I'm OK with adding a Gitaly item under Create (and incrementing the Group cell for Create to 6), or if you think the specific work counts as Distribution, you can add an Enablement row to the table.
To Christie's point, we should follow up about the coverage of Enablement, which is currently split by group among @axil, @eread, and me. See this TW assignment table for clarity. (Note that this sheet is a one-off copy for some recent analysis, not a SSOT. I'd love to automatically generate this for our Handbook section based on stages.yml in the future.)
-
I'll keep
Enablementseparately called out for clarity. I've combined it withConfigure, for now.Edited by Evan Read -
@eread maybe split Enablement again? I have this one I want to tackle https://gitlab.com/gitlab-org/gitlab-ce/issues/53606.
mentioned in issue gitaly#1684 (moved)
@mikelewis - I have reviewed the related issues board, reviewed those for the Plan stage, and identified 4 which I believe fit within this issue's criteria. Please review those I have listed, and approve them if you agree.
-
@mikelewis review plan stage here.
-
@mikelewis OKR FY20-Q2 status update for Plan stage.
The 4 Plan issues I assigned to myself are each still waiting on me. I will be working on https://gitlab.com/gitlab-org/gitlab-ce/issues/39964 today.
Thank you both. (I approved the issues during my June 25 meeting with Russell.)
@rdickenson there is still a duplicate issue link for you to resolve/replace.
-
FYI - I've noted that https://gitlab.com/gitlab-org/gitlab-ce/issues/53510 is at risk because I need help from an SME answering technical questions. In this instance, I need help because I don't have access to the software in question - Jira.
What kind of help do you need, @rdickenson?
-
I have added https://gitlab.com/gitlab-org/gitlab-ce/issues/57902, because I had intended working on https://gitlab.com/gitlab-org/gitlab-ce/issues/60160 but this issue is assigned to Marcel.
-
OK, great @rdickenson. If you have any trouble getting info, let me know and I can help find folks for you to talk to.
@mikelewis could you pls review/approve the two issues I added to "release"?
-
@mikelewis review release stage here.
@marcia looks like you need at least two more issues for that row, but this one (that we'd discussed as applicable to this OKR) closes multiple issues https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/30363, so perhaps you can add as many of those issues to the table as you think qualify / are not complete duplicates of another? (It is OK to exceed the # of requested issues for your row if applicable.)
-
I've removed the Defend stage which had 1 item and added it to Secure, which now has 4. Defend is a new stage and doesn't have any existing docs.
Edited by Achilleas Pipinellis -
@mikelewis can we drop the completed column? We can see which ones are completed since the closed issues/MRs show as
(closed). -
Also, I think it would be easier if each one of us had a thread where we discuss our proposals with you and when we come to a conclusion we add them in a new Issues column (effectively deprecating the Proposed/Approved ones).
This would mean less editing of the table which can be cumbersome.
Edited by Achilleas Pipinellis
@eread can you find another couple of high priority issues to add for Manage?
@gl-docsteam I added columns for estimates of # issues completed by end of the month (hopefully this matches the goal) and # issues done. Please keep this updated, and update me if your estimate is less than the goal (so we can talk about reassigning a couple of issues -- I'd rather do that, than have you select a lower priority issue that you can complete faster).
mentioned in issue gitaly#1386 (closed)
@axil Removed https://gitlab.com/gitlab-org/gitlab-ce/issues/53606 from this OKR; see latest comment there.
-
I am out of office from 2019-07-17 until 2019-07-31. Any mentions during this period will be ignored, and any todos will be marked as done automatically. Should you want me to review any merge requests or provide any feedback, I recommend that you ask one of my team members instead.
marked the checklist item @rdickenson as completed
marked the checklist item @rdickenson as incomplete
-
Although I researched the topic of GitLab<->Jira integration, and collated a lot of useful information, issue https://gitlab.com/gitlab-org/gitlab-ce/issues/57902 remains Open. I would like to carry that over into the next quarter.
-
@mikelewis - Can you please score this OKR and add a Good, Bad, Try section?
mentioned in merge request gitlab-foss!30615 (merged)
