There are three distinct deployment models for a DataMiner project, each with its own distinct set of terms and conditions, both commercially and from a practical or process point of view.

The table below summarizes the three methodologies and how the nature of the project at hand defines the type of methodology that needs to be applied to be successful and effective:


Good for basic monitoring-only projects, classic applications like management of an earth station, monitoring of a DTH network, etc.

Clearly defined and very exact project scope and user requirements.

Low level of uncertainty and ambiguity regarding user expectations.

Low risk for changes, both from a requirement and technical implementation perspective.

Offered at fixed price and with mutually agreed deployment time frame.

The project is typically offered in two commercial stages, i.e. consultancy & implementation.

The implementation uses a typical waterfall methodology managed by a Project Manager.

Any changes during implementation are governed by a formal Change Request procedure.

Agile Scope-based

Good for SRM orchestration projects, automation projects, complex integration projects, complex MoM and end-to-end OSS/BSS solutions, etc.

High-level requirements and scope-/goal-oriented.

Uncertainty about exact expectations and considerable unknowns.

Changes throughout the execution are expected, both because of changed user requirements and expectations, as well as to deal with unknowns that emerge during the technical implementation.

Offered at fixed price and with agreed time frame based on the high-level requirements and scope.

Scope is agile but will be balanced in terms of time expenditure (i.e. budget & timing are defined).

Time budget is fixed and is continuously managed by the Project Squad throughout execution.

Agile Time & Materials

Good for SRM orchestration projects, automation projects, complex integration projects, complex MoM and end-to-end OSS/BSS solutions, etc.

Scope is undefined or not required to start execution.

Maximum agility as compared to Agile Scope-Based, as budget is not necessarily a limiting factor.

Primary objective is to achieve maximum value delivery.

Delivery of expertise at hourly rate.

Time expenditure, goals and priorities are fully managed by the user.

The Project Squad chooses the exact methodology depending on project specifics (Scrum, Kanban, etc.).

Clear agreement is required on expected mid- and long-term availability of Skyline resources.

Comparative table of methodologies:

Fixed agreed time frameFixed agreed time frameContinuous progress
Fixed agreed time budgetFixed agreed time budgetFixed chosen budget
Clear and very specific requirements, no room for interpretationHigh-level requirements, well-defined goals and objectivesGoal- and objective-driven
Process- and tool-orientedFocus on individuals and interactions with constraints on available timeFocus on individuals and interactions
Comprehensive documentation and specificationsContinuously evolving high-level documentation and maximum focus on working softwareDelivering working solutions early on
Contract- and specification-drivenCollaboration-driven towards an agreed well-defined goal within a set time frameCollaboration-driven
Executing the planWorking towards the goal, with flexibility to easily respond to change, with time constraints in mindResponding to change

Want to learn more about our DataMiner deployment methodology?