-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Separate the tasks into educational or administrative #94446
Comments
this ticket was not intended to be added to the Oct 10-23 sprint |
@allison0034 Created a draft and separated all the tasks here let me know what you think! |
@KKitagawa-Bosch looking good! I agree with all the placement of items. Made a few comments. |
@allison0034 @shiragoodman could you look and confirm for me I think these comments are a bit out of scope of this ticket. The goal here as I understood it was just to bucket out the tasks, not to rewrite the ticket/add headings/etc. |
I think by changing and adding "Administrative" and "Educational" headings, the rest of the headings need to be looked at to make sure they still make sense and are still inline with accessibility, but I will default to whatever you and Shira decide.. |
@allison0034 @KKitagawa-Bosch responding to reiterate what I said at standup. The headings are out of scope for this ticket. We're only focused on the tasks, and will be updating the ticket design for the administrative tasks in #94448 (Allison) and will redesign the education tasks for Platform Website in #94449. |
@KKitagawa-Bosch I am still seeing the missing "note" and extra space... I commented in the doc. |
Closing this as this ticket's acceptance criteria have been met (removed that extra space for posterity and commented about the note) Just including it here to be clear: anything I removed from the VFS ticket body was NOT a judgment call on whether or not that information should be in the final ticket in #94448 and #94449. I just trimmed all the fat so we could focus only on bucketing for this ticket. |
@KKitagawa-Bosch the "note" is currently part of the task. I see you have the task, but not the note part. You may want to make a comment in your draft to use the task verbiage in the GH ticket and not in your draft if you are removing parts of tasks. I just don't want who ever works on the GH ticket to think you trimmed any content on purpose. I could see how they could easily copy/paste your text and then the stuff you trimmed is left off. |
Thanks for the clarification, @allison0034 . I also was a bit unsure what you meant by "note". Heads up - you're working on the gh ticket! via #94448 |
User Story
As a Governance team member supporting Platform Orientation, I want to determine which tasks in the New VFS Team member ticket are educational and which tasks are administrative so that I can move the tasks to their appropriate future home.
Assignee: @KKitagawa-Bosch
Peer Reviewer: @allison0034
Description
Now that we have defined our preferred terms via ticket , we must now sort through the New VFS Team Member gh issue ticket to determine which tasks fall in which bucket. We will NOT be validating whether or not the task/linked guidance is still appropriate within this ticket, so please focus on just determining whether it fits the definition of educational or administrative.
Educational: tasks that teach new VFS team members about the various processes in the VA.gov Platform organization and how their role and purpose fits into the broader organizational structure.
Administrative: housekeeping tasks used to gather information on new VFS team members, provide them with access to technologies, and maintain professional and legal compliance between VA.gov and its various contractors.
Impacted Artifacts
New VFS Team Member gh template
Please note that you are NOT making any changes to the gh template within the scope of this ticket.
Tasks
Peer Review
To be completed by peer reviewer
Acceptance Criteria
Team Notification
How to prepare this issue
Refinement
Planning
If this ticket is picked up from the Backlog mid-sprint, connect with Shira to ensure the below items are completed correctly
The text was updated successfully, but these errors were encountered: