Support Details

## Requirements
- Someone owning responsibility for maintaining uptime
- Someone owning responsibility for addressing security concerns
- Someone to maintain documentation
## Check-in

> Make sure requirements are still met

```

## ENTRY Criteria

- [ ] Have all critical requirements been addressed?

- [ ] Product Owner or similar role (person) willing to:
- [ ] Maintain uptime
- [ ] Address issues that arise (eg, security)
- [ ] Maintain documentation

- [ ] Documentation has been written and accepted by partner/team, including but not limited to:
- [ ] Problem statement
- [ ] Requirements
- [ ] Architectural components diagram and description
- [ ] Screen shots (if applicable)

- [ ]The project is declared “Shepherded” by project team

- [ ] OR The project has been declared “Shepherded” by Code 4 Denver leadership.

## EXIT Criteria

- [ ] the project requires no more resources from Code for Denver

- [ ] OR the project is declared Inactive by Code for Denver leadership

```

A Shepherded project will require some maintenance, and is also meant to provide for a “handoff” transition from Code for Denver to the partner.

No files, tests, or entry points are identified. Review the requirements and entry and exit criteria with the project team or Code for Denver leadership. Done means ownership, documentation, shepherding status, and the eventual handoff or inactive status are explicitly established.

Written by the indexing model from the issue text.