Workrole Owners
What problem(s) will it solve?
We don't have a way to identify who owns the addition, removal, or modification of workrole requirements. Therefore we are being looked at to curate requirements on positions we're not qualified to do so on. We need to shift this responsibility to individual work role owners so they are masters of their own destiny. Additionally, this should give a sense of empowerment and control to the qualified members of a workrole so they feel empowered to shape their qual as needed for their mission.
Who is the intended user(s)?
This ticket should create a new Persona for our issues as well
The senior/master workrole performers in each workrole. This would be the cadre for product owners and the Sr developers for other workroles.
Need to determine who would own Basic (Probably CYT).
Lay out the expected user experience
- A new employee identifies that they were never trained on something for their workrole and so submits a ticket to create a KSAT and apply it to their workrole.
- The workrole owner would be prompted to review that ticket and either approve or deny that additional KSAT for their workrole.
Proposal
Segregate the requirements of each workrole into individual files and use the CODEOWNERS feature in Gitlab to enforce it.
Further details
There may be ambiguity of whether or not folks know they are responsible (or have the official job to) manage their own workroles requirements. This needs to be captured in another ticket.
Permissions and Security
CODEOWNERS is a type of permission on who can approve changes to certain files.
Documentation
-
Update User Documentation
- New Page?: How KSATs get reviewed, approved, and merged.
-
Update Developer Documentation
- Document the new TTL JSON Schema's and other developer documentation: https://gitlab.com/90cos/mttl/-/wikis/Home
-
Update CYT Overview briefing
- Update any slides relevant to this workflow/responsibility, etc. https://gitlab.com/90cos/training/cyt-overview-brief
Availability & Testing
We'll want to test that the approval process for changes to these requirements files works.
- Submit change to file with codeowner
- Ensure no others can approve except code owner
- make sure codeowner CAN approve
What does success look like, and how can we measure that?
Workrole owners have taken positive control of their own requirements. They self manage and maintain the necessary files for their job.