department-of-veterans-affairs / va.gov-team

Public resources for building on and in support of VA.gov. Visit complete Knowledge Hub:
https://depo-platform-documentation.scrollhelp.site/index.html
282 stars 199 forks source link

New VFS Team VA Notify #42412

Open mjones-oddball opened 2 years ago

mjones-oddball commented 2 years ago

Welcome and Introduction

We are excited to welcome your team to VA.gov. As a new VFS team, this template should be completed by your teams Product Owner and/or Product Manager.

User Stories

As the leader of a new VFS team, I need to share basic info about my team with Platform so that Platform teams can have knowledge of my team for future collaboration.

As the leader of a new VFS team, I need to ensure my team follows the instructions for new VFS team members so that they're aware of Platform policies and processes, and Platform is aware of who supports my team for future collaboration.

As the leader of a new VFS team, I need to ensure my teams product information is correct so that Platform can have an accurate list of VA.gov products.

As the leader of a new VFS team, I need to complete ATO orientation so that VA.gov continues to be a secured and approved application within the VA.

New Team Info

Add your team's practice and contact information below.

VA Notify is a centralized notification platform for the VA designed to serve VA business lines who need to notify veterans in the manner that is most convenient for them. We're currently listed as a minor system on the va.gov's ATO. VA Notify is built up of 2 teams: Forms Strike Team and VA Notify (platform).

We offer a notification API to send notifications through multiple channels. This is available within and outside the VA Network.

We also offer an internal Self Service UI that allows business lines to design and manage their notification templates.

The strike team offers addition services within va.gov and vets-api to create the notification trigger code and content.

Contact info:

Person Role Team Email
Beverly Nelson VA Product Owner VA Notify - All beverly.nelson@va.gov
Emily Allan Program Manager VA Notify - All emily@oddball.io
Melanie Jones Product Manager Platform melanie.jones@oddball.io
Megan Siddle Product Manager Strike megan.siddle@oddball.io
Zachary Law Delivery Manager/Scrum Master VA Notify - All zack.law@oddball.io
Elissa Folk UX Lead/Researcher Platform elissa.folk@oddball.io
Ian Hilton UX Lead/Researcher Strike ian@oddball.io
Kyle MacMillan Tech Lead Platform kyle.macmillan@oddball.io
Ian Rickey Perera Engineer Platform ian@docme360.com
Jesse Anderson Engineer Platform jesse.anderson@oddball.io
Jacob Cheriathundam Engineer & Digital Notification SME VA Notify - All jacob@docme360.com
Nathan Wright Tech Lead Strike nathan.wright@oddball.io
Olaf Minkowicz Engineer Strike ominkowicz@rise8.us
Andrew Mauricio Engineer Strike andrew@docme360.com
David Kalbfleisch Engineer Platform david@docme360.com
Maham Saleem Engineer Platform maham@docme360.com
Evan Parish Engineer Platform evan.parish@oddball.io
Jake Uhteg QA VA Notify - All jacob.uhteg@oddball.io

Platform Orientation for your team members

In addition to providing information to Platform and completing necessary tasks at the team level, there are also tasks that need to be completed at the individual level. As a team leader, you will need to:

Review and update your team's product information

ATO (Authorization to Operate) orientation

Platform Checklist

The items in this checklist are for Platform to complete. If you are ready to close the ticket and the Platform Checklist section has not been completed, please reach out to Platform via the guidance provided in Getting help from Platform in Slack.

Eallan919 commented 2 years ago

@bevnobev hi! Working on the list of those who attended. I also crossed off the ATO team orientation as some of us attended. Would you like everyone to attend the ATO orientation?

Eallan919 commented 2 years ago

Jake and Ian are signing up for orientation. I will update when the rest of the crew logs on

jonathan-epstein13 commented 2 years ago

@mjones-oddball I believe the VANotify team has already been added to the VFS Team roster, unless there is another distinction for the VANotify team.

mjones-oddball commented 2 years ago

@jonathan-epstein13 We were told on another ticket: https://github.com/department-of-veterans-affairs/va.gov-team/issues/42409#issuecomment-1147924892 that we were missing from the roster. Can you confirm that all the team members in this ticket are present for VA Notify? Would be great news if this is already done.

jonathan-epstein13 commented 2 years ago

@mjones-oddball so the team itself [VANotify] was already on the VFS Team roster, but the individuals within the team, need to be added via that comment that states the if you are newly joining the team or haven't filled out the Platform Orientation template, please follow along with this platform orientation guide. When the individual fills out the 'Share your info with Platform' section on the Platform Orientation template, we will add those individuals to the VFS Team Roster. Let me know if this makes sense and if you have any other questions, please feel free to reach out.

shiragoodman commented 2 years ago

thank you @jonathan-epstein13 ! 100% correct.

FYI - Platform onboards new teams and new team members separately. SOCKS access is managed at the team member level, meaning the team member requesting access was not on the VFS Team Roster, not the whole VA Notify team. To remedy that, the new individual needs to submit the Platform Orientation template and provide their individual info.

If there's still questions about this process, please feel free to reach out on #vfs-platform-support.

Eallan919 commented 1 year ago

@mjones-oddball do we need to update this? Or is it somewhere else now?

shiragoodman commented 1 year ago

@Eallan919 if your team-level information has changed, then yes, either update or submit a new ticket. If your team members have changed, then the comment above from Jonathan Epstein is still accurate.