services-hub-hero

Delivery Methodology

Success begins with building a team of experts who understand your project vision.

Delivery Methodology illustration

How It Works

You need to know there are clear, mutually understood project standards, as well as measurable information to demonstrate progress. You also need the flexibility to evolve requirements as they’re better understood — and a team with the flexibility to adjust course. From project inception to final hand-off, the MarkLogic Consulting Services Delivery Methodology addresses these needs.

We leverage an agile Delivery Methodology that enables customers and partners to successfully implement, develop in-house knowledge and skills, and gain real Return On Investment (ROI) with the rapid deployment of mission-critical applications. We’ll keep you engaged in all aspects of project planning, building, and launch. Using defined, repeatable processes, we comprehensively cover all aspects of application development and platform adoption — keeping you apprised of progress and eliciting your feedback throughout the process.

Core Implementation Team Customer Developers and Testers MarkLogic Developers and Admins Project Sponsor Project Manager Account Team Data SMES Support Stakeholders MarkLogic University Business Analysts Product SMES Solution Architects

Three Phased Approach

Our delivery methodology is comprised of three phases — Design, Develop, and Launch. Throughout all phases of the project, we will deliver weekly status reports and have weekly status reviews that evaluate progress, as well as identify risks and issues.

Design

  • Vision
  • Architecture
  • Prototype

Develop

  • Prioritize
  • Build
  • Demo
  • Feedback

Launch

  • Test
  • Handoff
  • Final demo

Phase 1

Design

Our delivery methodology is comprised of three phases — Design, Develop, and Launch. Throughout all phases of the project, we will deliver weekly status reports and have weekly status reviews that evaluate progress, as well as identify risks and issues.

Vision

In a kickoff meeting, we’ll discuss the following:

  • Introductions and Background
  • Roles and Responsibilities, Key Success Criteria, and Target Timeframes
  • Change Prioritization, Communication, and Risk Management Plans
  • Requirement-gathering and Development of Use Cases
  • Project-plan Checklist
  • MarkLogic Training Courses that fit both your team’s requirements and the project schedule

Architecture

To establish architecture within the context of general software design and integration with other technologies, we learn about your environment and the applications to be built on MarkLogic. Based on your requirements and environment, we’ll produce the following, as applicable:

  • Cluster Installation
  • Security Design
  • High Availability and Disaster Recovery Plan

Prototype

Prototyping is the most efficient way to gain early feedback from stakeholders and ensure development will focus on the right scope. We’ll use the prototype step to perform any of the following that are applicable to your project.

  • UI Mockups and Human Computer Design (HCD) Paper Prototype
  • Preliminary Interface Specifications and Data Model
  • Sample Data Creation

Phase 2

Develop

After establishing your vision, we’re ready to begin application development in a four-part phase.

Prioritize

From the get-go, we’ll work with you on prioritizing development activities. After assessing a task list based on your feedback and our experience, we can engage stakeholders for their prioritization of tasks and milestones.

Build

Working in 2-4 week sprints may include UI implementation, data transformation and migration, database scripting, and other tasks. If possible, we use continuous integration to automate builds and tests to stave off headaches.

Demo

At the end of each iteration, we’ll hold demonstrations with stakeholders. Early iterations may be demonstrated to internal teams, while subsequent iterations may be demonstrated to a broader audience of stakeholders.

Feedback

We recognize the need for regular assessments to better guide sprints and make them truly iterative. After demonstrations and iterations, we solicit stakeholder feedback to update task lists in subsequent cycles.


Phase 3

Launch

After design and development comes the anticipated launch. We’ll see you through into production, and help you plan post-production support and the next phase of implementation.

Test

Testing is an iterative process of Quality Assurance testing and bug fixes, as well as final performance testing and any other testing identified in the Design phase.

Handoff

We’ll deliver documentation, complete train-the-trainer sessions, and perform any knowledge transfer necessary to move your project into operations and maintenance.

Final Demo

The final demonstration is an important transition step for the entire team. It provides the opportunity for the end customers to provide feedback and plan for future implementation phases if appropriate.

Services prefooter banner

After Delivery

Fear not! We’ll always be available after delivery to provide continued support and mentorship of your staff as needed.