Skip to content
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

Create change management plan for revision log requirement #12173

Closed
2 of 9 tasks
EWashb opened this issue Jan 4, 2023 · 4 comments
Closed
2 of 9 tasks

Create change management plan for revision log requirement #12173

EWashb opened this issue Jan 4, 2023 · 4 comments
Assignees
Labels
CMS Team CMS Product team that manages both editor exp and devops User support Workstream: The customer journey of CMS users, from onboarding to support services, etc.

Comments

@EWashb
Copy link
Contributor

EWashb commented Jan 4, 2023

Description

Related to #12157. We must determine what level of change management to implement for this new workflow for VAMC editors all editors. Teamsite required revision logs and Vet Center editors are currently required to use revision logs as well.

Change management for this newly required workflow could include communication (emails, Teams messages, office hours, etc.) from stakeholder partners, KB articles, etc.

User Story

As a CMS editor subject to a newly required revision long, I would like to have change management around this new workflow.

Acceptance Criteria

  • Choose a date for live revision logs
  • Share with PO/VHA Digital Media

CMS Team

Please check the team(s) that will do this work.

  • Program
  • Platform CMS Team
  • Sitewide Crew
  • ⭐️ Sitewide CMS
  • ⭐️ Public Websites
  • ⭐️ Facilities
  • ⭐️ User support
@EWashb EWashb added Needs refining Issue status CMS Team CMS Product team that manages both editor exp and devops labels Jan 4, 2023
@EWashb EWashb added the User support Workstream: The customer journey of CMS users, from onboarding to support services, etc. label Jan 31, 2023
@EWashb EWashb mentioned this issue Feb 1, 2023
49 tasks
@EWashb EWashb changed the title Create change management plan for revision log requirement Create change management plan for VAMC revision log requirement Feb 1, 2023
@EWashb
Copy link
Contributor Author

EWashb commented Feb 1, 2023

Just set the date and let VHA Digital Media know when it happens so that they have the time to CM with editors.

@EWashb EWashb removed the Needs refining Issue status label Feb 1, 2023
@EWashb EWashb changed the title Create change management plan for VAMC revision log requirement Create change management plan for revision log requirement Feb 14, 2023
@EWashb EWashb mentioned this issue Feb 14, 2023
48 tasks
@EWashb EWashb self-assigned this Feb 14, 2023
@EWashb
Copy link
Contributor Author

EWashb commented Feb 16, 2023

I am meeting with Blake Scates tomorrow, 2/17 to let him know this is upcoming during Sprint 78. We will provide the updated KB article for editors, however the impact is small. Teamsite required revision logs and this would not be new to those editors that previously worked in the teamsite prior to migration

@EWashb
Copy link
Contributor Author

EWashb commented Feb 24, 2023

Plan:

  • Merge code on 2/28 (end of sprint)
  • code includes an update to this editorial workflow KB article with the new revision log reqs
  • Erika has alerted Sitewide Content + IA on Slack on 2/22 (they are already doing this as a part of their workflow regardless of field validation)

Emailed JHL, Blake, Justine cc'd Dawn and Dave about this on 2/21. JHL will give her editors a heads up on this, but asked that we also send out an email from the Drupal team on the technical ask. We will email editors before the code merges on 2/28 (unless something comes up that I am unaware of).

@EWashb
Copy link
Contributor Author

EWashb commented Feb 28, 2023

Dave has mentioned to hold off on deploy of code for 2/28, however, the change management plan is complete

@EWashb EWashb closed this as completed Feb 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CMS Team CMS Product team that manages both editor exp and devops User support Workstream: The customer journey of CMS users, from onboarding to support services, etc.
Projects
None yet
Development

No branches or pull requests

1 participant