Short answer
#Dependency register
One row per question that a decision in the next quarter will need. The two columns that matter are how long an answer takes without the usual person and where it is written. Look at it again a month later and see whether both moved.
# Dependency register
Updated: YYYY-MM-DD
| Question about the system | Who can answer | Time without them | Written where |
|---|---|---|---|
| Which services does customer personal data pass through? | | | |
| What runs on a schedule, and who notices if it stops? | | | |
| What breaks if the payment provider changes? | | | |
| Who can renew the domain and the certificates? | | | |
| How does a change reach production, and how is it undone? | | | |
#Handover acceptance questions
Written before the last day of the outgoing team and answered by the incoming one from the handed-over materials alone. Each answer goes into one of three piles, and the overlap is spent on the second and the third.
# Handover acceptance questions
System:
Outgoing team: Incoming team:
Last day of overlap:
Each answer is one of: SOURCE (answered, with what supports it),
MEMORY (answered from a call or walkthrough only), OPEN (not answered).
| # | Question | Answer | Pile | Source or owner |
|---|---|---|---|---|
| 1 | Where is personal data stored and copied, including backups? | | | |
| 2 | How would one customer be deleted completely? | | | |
| 3 | Where are payments, refunds and invoices calculated? | | | |
| 4 | What runs on a schedule, and who notices when it stops? | | | |
| 5 | Which external services does the system call, and which call it? | | | |
| 6 | How does a change reach production, and how is it undone? | | | |
| 7 | Who owns each account the product depends on? | | | |
| 8 | Which parts look wrong and are deliberate? | | | |
Accepted when every MEMORY and OPEN row has a source
or is written down as a known unknown with an owner.
#Account ownership list
Every account the product depends on is owned by the company, registered to a company address, paid for by a company card and recovered by means the company controls. People are members of those accounts, not their owners.
# Account ownership list
| Account | Owner of record | Paid by | Recovery goes to | Members |
|---|---|---|---|---|
| Domain registrar | | | | |
| DNS | | | | |
| TLS certificates | | | | |
| Cloud or hosting | | | | |
| Code hosting | | | | |
| Build and deployment | | | | |
| Payment provider | | | | |
| Email delivery | | | | |
| Error tracking | | | | |
| Analytics | | | | |
Any row where the owner of record is a person rather than
the company goes to the top of the plan.