Overview
Intellectual property created during a Scrums.com engagement belongs to the client. This is a standard contractual commitment across all delivery models.
What clients own
All software, code, documentation, designs, and other work product created by Scrums.com engineers during an engagement is assigned to the client upon delivery, subject to the relevant payment obligations being met.
This includes:
- All source code written during the engagement
- Database schemas, architecture documentation, and technical specifications
- UI/UX designs, prototypes, and design systems
- Test suites, QA scripts, and test documentation
- Technical documentation generated during the engagement
Scrums.com retains ownership of its proprietary platform (SEOP), pre-existing tools, methodologies, and generic components or frameworks that were not created specifically for the client’s engagement.
This includes:
- The SEOP platform and all associated tooling
- Pre-built frameworks, libraries, or boilerplate code that existed before the engagement
- Scrums.com’s delivery methodologies, process templates, and governance frameworks
- AI Agent infrastructure and orchestration layer
If pre-existing Scrums.com components are incorporated into client deliverables, a licence to use those components is granted as part of the engagement agreement.
Access to assets
Clients will not receive access to their assets if payment is in arrears. IP assignment is conditional on all payment obligations in the relevant Order Form or Statement of Work being met.
NDA and confidentiality
All Scrums.com engineers sign confidentiality agreements before accessing client systems, code, or data. NDAs are available in South African and International versions, managed digitally through the platform.
For questions about IP terms in your specific engagement, contact your Enablement Partner or legal@scrums.com.
