Methodology

A controlled route from requirement to operation.

CollectiveIS uses a seven-stage delivery method: Discover, Validate, Design, Build, Test, Deploy and Operate. Each stage produces a defined decision, record or deliverable before the engagement moves forward.

The seven stages

Every stage has activities, controls, outputs and an approval point.

Discover

Establish the business requirement, affected processes, current environment, stakeholders, constraints and expected outcomes.

Key activities

Executive and operational interviews.
Current-state system and process review.
Issue, dependency and risk identification.
Initial scope and information request.

Controls: Confidentiality undertakings, a scope register and documented information requests.
Client responsibilities: Nominate stakeholders and provide access to current documentation and system information.
Outputs: Current-state summary, issue and risk log, and a draft scope statement.
Approval point: Client review and confirmation of the discovery summary.
Handover: Confirmed inputs and open questions passed to validation.

Validate

Confirm that the requirement, authority, data, budget and proposed solution are sufficient for formal planning.

Key activities

Scope confirmation.
Legal, regulatory and contractual checks.
Technical feasibility and partner dependency review.
Budget range and procurement route.
Go, revise or stop decision.

Controls: Decision record, dependency register and procurement-route confirmation.
Client responsibilities: Confirm authority, budget parameters and procurement requirements.
Outputs: Validated scope, feasibility statement and commercial basis.
Approval point: A formal go, revise or stop decision recorded with the client.
Handover: Approved scope, dependencies and constraints passed to design.

Design

Produce the approved functional, technical, security and service design.

Key activities

Solution architecture and component list.
Data, access and integration design.
Security and control requirements.
Implementation plan, roles and acceptance criteria.
SLA and support model.

Controls: Design review, version control and a security-requirements checklist.
Client responsibilities: Review the design and confirm acceptance criteria and operating constraints.
Outputs: Approved design pack, implementation plan, acceptance criteria and support model.
Approval point: Client and delivery owners approve the design and acceptance criteria.
Handover: Approved design and implementation plan issued to the build team.

Build

Configure, develop, integrate or prepare the approved solution in a controlled environment.

Key activities

Configuration and development.
Partner and vendor coordination.
Documentation and register updates.
Change records and version control.
Build review before testing.

Controls: Change records, version control and internal build review.
Client responsibilities: Provide environments, data samples and decisions within agreed timelines.
Outputs: Configured solution, build documentation and updated registers.
Approval point: Build accepted for test after internal review.
Handover: Build package and documentation released to testing.

Test

Verify function, security, performance, data accuracy, recovery and user acceptance.

Key activities

Test plan and test cases.
Defect recording and correction.
Reconciliation and data-quality checks.
Security and access testing.
User acceptance and sign-off.

Controls: Defect log, retained test evidence and retest verification.
Client responsibilities: Provide user-acceptance testers and timely sign-off decisions.
Outputs: Test results, closed critical defects and a recorded acceptance.
Approval point: Formal user acceptance recorded before deployment is authorised.
Handover: Accepted solution and test evidence passed to deployment.

Deploy

Move the approved solution into operation under a controlled cutover plan.

Key activities

Change approval and implementation window.
Backup and rollback readiness.
Cutover checklist and command structure.
Post-deployment verification.
Handover and operational acceptance.

Controls: Change approval, rollback plan and a cutover checklist.
Client responsibilities: Approve the change window and confirm business readiness.
Outputs: Deployed solution, verification results and handover records.
Approval point: Deployment authorised and operational acceptance recorded.
Handover: Service ownership, documentation and support routes transferred to operations.

Operate

Maintain service performance, control changes, respond to incidents and report results.

Key activities

SLA monitoring and service reporting.
Incident, request, problem and change management.
Maintenance and capacity planning.
Risk, audit and compliance evidence.
Continual improvement and roadmap updates.

Controls: SLA measurement, scheduled service reviews and documented escalation.
Client responsibilities: Report incidents through agreed channels and attend service reviews.
Outputs: Service reports, maintenance records and improvement actions.
Approval point: Service reviews confirm performance against the SLA.
Handover: Roadmap updates and improvement actions agreed with the client.

Stage-gate controls

No stage proceeds without its decision.

Gate	Decision requirement
Discovery complete	Stakeholders, current state and primary risks are documented.
Validation complete	Authority, feasibility, scope, dependencies and commercial basis are confirmed.
Design approved	Client and delivery owners approve the design and acceptance criteria.
Build accepted for test	Configuration and documentation meet internal review requirements.
Testing passed	Critical defects are closed and formal acceptance is recorded.
Deployment authorised	Change, rollback, communication and support readiness are confirmed.
Operational handover complete	Service ownership, records, support routes and performance measures are active.