Glossary
Software proposals are full of terms that sound alike and mean different things: MVP, sprint, technical debt, SLA, discovery, scope. This glossary gives plain-English definitions with a note on how each term changes what a buyer should ask, so a proposal can be read and compared with confidence.
Start your project
Why a glossary helps buyers
Vocabulary is where proposals hide differences. Two suppliers may both promise an MVP, but one means a clickable prototype and the other a product real customers can use. Knowing what each word commits a supplier to is a quick way to compare offers fairly.
Scope and planning terms
Scope
The agreed list of outcomes and features a project will deliver, and, just as important, what is excluded.
MVP
A first release that is deliberately small but usable by real users, chosen to test the biggest assumption.
Backlog
The ordered list of work remaining. A healthy backlog is visible to the client and reprioritised regularly.
Acceptance criteria
Written conditions that must be true for a piece of work to count as done.
Discovery
A short, structured phase that turns a goal into a scope, risk list and cost range.
Delivery and engineering terms
Sprint
A fixed period, often one to two weeks, in which the team completes and demonstrates a slice of work.
CI/CD
Automated building, testing and release of code, so that changes reach users in small, checked steps.
Technical debt
Shortcuts in design or code that save time now and cost more later; sometimes sensible, but should be recorded.
Refactoring
Restructuring code without changing behaviour, to make it safer to change.
Staging environment
A copy of the live system used to rehearse a release before real users see it.
Share the outcome you need and Renvric will recommend the smallest useful next step.
Contract and commercial terms
- Fixed price: a set sum for a defined scope; changes are priced separately.
- Time and materials: payment for effort spent, usually with a reporting cadence and an agreed ceiling or review point.
- Dedicated team: a stable group working on your priorities for a recurring fee.
- SLA: a service level agreement describing support hours, response expectations and remedies, agreed per contract.
- IP assignment: the transfer of ownership of bespoke work to the client.
- Change request: a written, sized proposal to alter scope after it was agreed.
Quality and security terms
Regression testing
Re-running tests to confirm that new work has not broken existing behaviour.
Penetration test
An authorised attempt to find exploitable weaknesses in a system, performed by a specialist.
Observability
The ability to understand what a running system is doing from its logs, metrics and traces.
RTO and RPO
How quickly a service must be restored and how much recent data may be lost in a failure.
Using the terms in a conversation
When a proposal uses a term, ask what artefact will exist because of it. If a supplier promises sprints, ask what you will see at the end of each one. If it promises an SLA, ask where the terms are written down. A definition that cannot be tied to something you can inspect is probably marketing.
Related areas to explore: AI Integration Services and Artificial Intelligence Development.
Common questions
Who is the glossary for?
It is for non-engineers reading proposals, contracts and status reports, and for engineers who need to explain terms to colleagues. Definitions are short and avoid jargon, with a note on what each term should make you ask.
Are the definitions standard across the industry?
Many terms have no single official meaning. MVP, for example, is used loosely. The glossary gives the meaning Renvric uses and flags where others differ, so you can ask a supplier to confirm which definition applies to its offer.
What should I do when a supplier uses a term differently?
Ask for it in writing, tied to a deliverable. If a proposal says testing is included, ask which kinds, who writes them and what you will see. Differences in meaning are common and entirely resolvable if raised before signing.
Can I suggest a term to add?
Yes. Send it to info@renvric.com with the context in which you met it. Terms that cause confusion for buyers are the best candidates, and a plain-language explanation can be sent directly to you in the meantime.
Who can explain a term in the context of my project?
A delivery lead can walk through any proposal with you. Send the document or the terms in question to info@renvric.com. This is offered as general help, and no commitment to engage is implied.
Keep exploring
If a word in a proposal is unclear, send it to info@renvric.com and it will be explained in plain language, whether or not you work with Renvric.