Professional services in a DataMiner project deployment are offered either Scope-based or Agile-based. Scope-based (waterfall) type of deployments are more traditional, with a design phase, a project plan, an execution plan, etc. Agile-based deployments are more used in complex projects where IT paradigms rule the implementation flow. Both methodologies can have advantages and disadvantages, depending on the type of project. With our expertise, we can help you decide which deployment type fits your goals based on variables such as time, cost, scope, internal resources, expertise at hand. etc.
Good for more traditional deployments with design phase,
project plan, execution plan, etc.
- Deliverables and project deploy path are clear and unlikely to change.
- All requirements and technical details are clear and can be mapped beforehand.
- Standard apps/solutions will be deployed according to Skyline best practices.
- Little or no changes will be needed after the design/architecture phase.
- Functional Design Specifications (FDS) and Scope Of Work (SOW) are securely defined.
- During the implementation phase, there is little room to intervene.
- Fixed deployment cost.
- Any functional change request is handled separately and may lead to extra costs.
- Timing is guaranteed.
- Defined scope rules must be fulfilled in order to avoid delays (e.g. dependencies must be managed in time, involvement in testing must occur as planned, etc.)
- FDS can be enriched with Skyline’s standard best practices, standard apps and solutions.
- A delta period is required for FDS design, so the actual implementation can potentially only start several weeks after the contract.
- Little input will be required from you during implementation.
- Subject matter experts are needed to sign off during the design phase.
- Our project management offices manages the execution hand in hand with your project manager.
- Technical people are less involved in administration tasks.
- Alignment between all stakeholders could be a point of attention.
- A full all-inclusive package of engineering services is offered.
- All risks are included in the offer, which means the offered package can potentially have a higher cost than the actual service cost.
Good for more complex deployments where IT paradigms
rule the implementation flow
- Several variables are unknown or may change, and requirements can change or even grow incrementally.
- Dependencies need to be solved while the project is ongoing.
- Brand-new technology.
- IT paradigms are important.
- A general scope contract is possible.
- Cost and timing are more difficult to predict, but the flexibility in deployment ensures the result is tuned to the latest insights and operation processes.
- Fixed budget contract is possible.
- Deliverables can be tuned (e.g. prioritizing must-haves vs. nice-to-haves) at fixed checkpoints to maintain the budget.
- A hard-deadline proposal is possible, but then the scope is in constant flux to meet this deadline (choice between must-haves and nice-to-haves).
- A broad description of the project is sufficient, ensuring a quick start with value being delivered from day 1.
- “Fail quick” could potentially have a limited cost impact (e.g. a deployed sprint turning out to be unnecessary), though this is rare and the impact is limited because it handled at an early stage.
- You will need to closely cooperate with Skyline to tackle possible bumps in the road related to technology, environment, etc.
- Your involvement is needed throughout the deployment cycle.
- Incremental delivery contract possible, with changes at fixed checkpoints based on the latest insights.
- The scrum team is fully aligned and handles work, testing & review with almost daily meetings.
- Value is returned very quickly.
- You need to subscribe to the Agile principles, e.g. be part of the scrum sprint team, have a key stakeholder appointed, etc. Note that Skyline can assist you with best practices and clarifications on Agile working.
- Service cost maps the actual time spent on the project, for optimal transparency, with the possibility to adjust where necessary.
- Based on the type of Agile contract and the deployment dependencies/requests, there can be a potential impact on scope, cost, and/or time.