Merge pull request #7799 from GSA/cms/resources/how-to-transition-a-t…

…eam-off-of-a-project

Create Resource “how-to-transition-a-team-off-of-a-project”

content/resources/how-to-transition-a-team-off-of-a-project.md

@@ -0,0 +1,98 @@
+---
+# View this page at https://digital.gov/resources/how-to-transition-a-team-off-of-a-project
+# Learn how to edit our pages at https://workflow.digital.gov
+
+date: 2024-07-19
+title: "How to transition a team off of a project"
+deck: "A template for transitioning projects to another team"
+summary: "Use this template, shared at the 2024 Spring Community Summit, to improve your own service delivery."
+
+# Redirects: Enter the paths of the old URLs that you want redirected to this page.
+aliases:
+  - /resources/service-delivery-transition-plan/
+
+# See all topics at https://digital.gov/topics
+topics:
+  - digital-service-delivery
+
+# See all authors at https://digital.gov/authors
+authors:
+  - jessica-marine
+
+slug: how-to-transition-a-team-off-of-a-project
+
+primary_image: 
+
+# Controls how this page appears across the site
+# 0 -- hidden
+# 1 -- visible
+# 2 -- highlighted
+weight: 1
+
+---
+
+When bringing in a short-term project team, it’s important to formally transition them off the project, once their part of the project ends. This transition helps to prepare the long-term team for success.
+
+Use this resource to serve as a hand-off document when a short-term project team is transitioning off of a project. You can modify the template to meet your team’s needs.
+
+You can also use this resource to remind folks of project goals, provide links to all the deliverables over the course of the project, and outline the goals that both teams want in place before the short-term team transitions off. These goals can include things like having an empowered product owner in place, the ability to run a full agile sprint cycle without assistance, being able to get code from inception to production, and having redundancies in place, among other things.
+
+You can also use this as a visioning tool by thinking about what success and failure might look like a year from now. This helps set the mindset that this work is a continuing process and will be ongoing. 
+
+{{< box >}}
+
+### Transition plan for &#91;project name&#93;
+
+**Dates**: &#91;start date - end date&#93;<br />
+**Teams**: &#91;long-term team&#93; + &#91;short-term project team&#93;
+
+#### Background
+
+Over the last &#91;&#35;&#93; months, the &#91;name of the short-term project team&#93; team has partnered with &#91;name of the long-term team&#93; for &#91;purpose from project proposal and a link to project proposal&#93;.
+Together, we accomplished these deliverables [work done to date and outcome&#93;:
+
+- Description of Activity 1 &#91;link as appropriate&#93;
+- Description of Activity 2 &#91;link as appropriate&#93;
+- Description of Deliverable &#91;link as appropriate&#93;
+
+#### Goals
+
+&#91;copy from project proposal&#93;
+
+#### Scenarios and acceptance criteria
+
+In the table below are some scenarios and acceptance criteria that both teams can use to define success and signal when it’s time for the &#91;name of the short-term project team&#93; team to roll off the project.
+
+<table class="usa-table">
+<caption></caption>
+<thead>
+<tr>
+<th scope="col">Priority and sequence</th>
+<th scope="col">Scenario</th>
+<th scope="col">Acceptance criteria</th>
+<th scope="col">Status</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<th scope="row"></th>
+<td></td>
+<td></td>
+<td></td>
+</tr>
+<tr>
+<th scope="row"></th>
+<td></td>
+<td></td>
+<td></td>
+</tr>
+<tr>
+<th scope="row"></th>
+<td></td>
+<td></td>
+<td></td>
+</tr>
+</tbody>
+</table>
+
+{{< /box >}}