ensure projects are being handed off to partners

afeld commented 4 years ago

Background information

When partner projects end, TTS needs to ensure various things happen:

Repositories are transferred or archived
TTS is no longer paying for any infrastructure
TTS is no longer paying for of the contact on domain name registrations
The site is no longer using TTS DNS
...

This applies to both handoff (the partner is continuing with the project) and decommissioning (the project is being shut down).

User stories

As a member of the Tech Portfolio, I don't want to be responsible for code/costs/risks that are no longer TTS's responsibility so that they don't take our time/money down the road.
As a TTS partner, I want to ensure I have control of all resources related to my project so that I can continue it (or not) as I choose.

Implementation

[ ] Think through all the things that need to happen (build on list above)
[ ] Decide/determine canonical documentation for project handoff
[ ] Reconcile with various existing documentation
- Decommissioning
- Various Handbook pages, such as archiving GitHub repositories
[ ] Review by PIF
[ ] Review by CoEs
[ ] Review by 18F

Acceptance criteria

List of project handoff steps is documented

Relevant links

Slack conversation

its-a-lisa-at-work commented 4 years ago

Mind if we keep this in the Backlog? I think things that are already Sprint Planned for shouldn't go back into Icebox so they stay as something that gets picked up as soon as possible.

afeld commented 3 years ago

18F Project Closeout Checklist from @hannahkane, which seems like the thing to build from. @keithpif @adam-grandt-tts would you be ok with adopting that checklist for PIF and COEs, respectively?

JJediny commented 5 months ago

Determined with team that these orgs should document their own project transferring process

GSA-TTS / tts-tech-operations