Project Management and Implementation

EBMS assigns a Project Manager to each new project who works with clients and the EBMS staff to expertly deliver the final product. The Project Manager will keep the client and EBMS stakeholders updated on the status of the project, and will manage the implementation process.

The method chosen depends on the type and size of the project: our Core Solutions follow the BRIDGE methodology while the Custom Solutions use the Nimblex SIMPLE methodology.

Nimblex Core Solutions: BRIDGE Project Methodology

The BRIDGE implementation approach is used in the delivery of our Core Solutions. Core Solutions are mature solutions that require little configuration. They are off-the-shelf applications, yet they remain flexible and configurable.

The word bridge refers to 'bridging the gap' which encapsulates the main emphasis of this approach - we do a gap analysis between your current needs and the Core Solutions you are implementing.

Key benefits of this implementation approach:

  • Starting with a mature framework:
    Our Core Solutions enable you to start with a framework and we will help you to correctly identify your needs using this framework as a guide.  
      
  • Quick and Easy:
    This way of implementation will ensure we get you up and running in a short lead time with a best-fit solution. 

The BRIDGE Process

Stage 1: Introduction to the Project (Guide)

Stage 2: Gap Analysis (Guide)

Stage 3: Tailoring (Guide)

Stage 4: Launch (Guide)

Nimblex Custom Solutions: SIMPLE Project Methodology

We at EBMS use our own process called SIMPLE to develop and implement solutions. The SIMPLE implementation approach is used for the successful delivery of customised and complex solutions. It has been designed to fit the flexibility offered by Nimblex, starting from a 'blank canvas', for the creation of a new and unique solution.

SIMPLE method

Key benefits of this implementation approach:

  • Clarity:
    All your questions about who, what, when, where, how, etc. are well defined throughout the methodology.
  • Low Risk:
    The iterative review process gives our clients ample time to suggest changes, which is also well accommodated by the flexibility Nimblex offers.
  • Fixed Price:
    Subject to a confirmed scope, this approach help us to successfully implement fixed price projects making it super easy for you to manage your budget obligations. 

The above comes with field guides and resources to make it easy for our clients to journey with us to success.

How and why we developed SIMPLE

SIMPLE differs from other methodologies because it has been designed to fit the flexibility offered by Nimblex.

It is also a blend of the well-known application creation methodologies, Agile and Waterfall. It is our way of delivering projects and over the years has proven to be a winning recipe for the delivery of Nimblex applications of all levels of complexity.

The main aim is to simplify, standardise and then to digitise. The SIMPLE journey will help our clients to achieve these goals.

Over time, we have experimented with various processes for managing projects.

1. Ad-hoc

2. Agile

3. Bringing in elements of the waterfall model

The Agile process proved to be difficult to follow on a fixed schedule and budget. We found that vanilla waterfall does not take appropriate advantage of Nimblex’s level of flexibility and time reduction during implementation.

For these reasons we follow a methodology related to the traditional waterfall model with some variations:

• Waterfall is the base.

• A phase of wireframing implementation in the Requirements phase is added.

• Implementation is performed in short iterations (approximately 2-3 weeks) before giving back to the client for feedback.

• Implementation time is reduced when compared to custom IT implementation projects.

SIMPLE project delivery stages

Stage 1: Introduction to the Project (Guide) Onboarding, Project Kick-off, Wireframe Development and the Functional Requirements.

This part of the project is normally the bulk of the total project time and involves the most commitment and input from the client.

Stage 2: Requirements (Guide) Details about what will be included in the finished product, the Detailed Requirements and the Functional Specifications.

Stage 3: The Build (Guide) This is the actual building and integration stage of the project and involves a series of iteration builds, which progressively leads to the Final Iteration and might involve some data migration to test for accuracy and data integrity.

Stage 4: The Launch (Guide) – The final stage revolves around User Acceptance Testing, final data migration, client training and the solution handover to our client.

Our project methodology caters for special check-ins from Account Managers at every milestone. This ensures the quality and customer satisfaction.