Four phases, always in the same order
A phase can be short or long depending on scope, but none is skipped. In every phase it is clear what you receive and what we need.
1
Discovery & scoping
What you receive
A scope document, estimates with their assumptions, a risk register, the first increment.
What we need
Access to the people who run the process, sample data, a decision on data location.
2
Build & release
What you receive
The first working version on the agreed date; sprints, CI/CD, release notes; a shared board and repository.
What we need
Regular reviews, a product owner who can make decisions.
3
Operate & maintain
What you receive
Monitoring, patching, tested backups, AI system evaluation; regular reports under the SLA.
What we need
One technical contact and a maintenance window.
4
Handover & knowledge transfer
What you receive
Complete documentation, repository transfer, full access to code, data, and infrastructure; training.
What we need
A receiving team and time for training.
Who holds what
Roles written down from discovery onward. Our access can always be revoked.
| Your organization | sixseven.camp | |
|---|---|---|
| Accounts, credentials, access | In your organization’s name. You appoint an access owner. | Named accounts you provide, recorded in the audit log, revocable. |
| Data | Stored in the location you choose. | Used within the agreed scope. |
| Source code & documentation | Repositories you own; handed over in full at handover. | Written, managed during the project, handed over. |
| Infrastructure | In your name; you decide on changes. | Operated only under a managed services agreement. |
Engineering standards from the first commit
Regardless of project size. We write them down so your IT team knows exactly what it will receive.
Git & code review
Repositories in your name; every change goes through a pull request.
Automated testing
Tests run in the pipeline; the definition of done includes passing tests.
CI/CD & environments
Separate dev, staging, and production; deployments can be rolled back.
Infrastructure as code
Environments can be reproduced and moved to another provider.
Security baseline
RBAC, least privilege, admin MFA, TLS, encryption at rest, secrets management, audit logs.
Backup & recovery
RPO/RTO targets agreed; restores tested regularly, not assumed.
Observability
Centralized logs, metrics, alerting; problems are known before users report them.
Documentation
README, architecture decision records, runbooks, OpenAPI, data dictionary.