October 2015

Models and Upgrade Considerations

Engagement Models

Business Agreement Time and Material Fixed Fee

Team augmentation (4 week Guarantee)

Client or Mint led and managed

Access to all services provided across all practices employed at Mint

Co-managed release cycle

Discount to Blended Rate based on Total Agreement Commitment

AGILE

Team augmentation (Best Case)

Client led and managed

Access to specific roles within practices as defined in requirement

Client managed release cycle

Deliverable

Mint led and managed

No direct access to services. Mint employs services to provide deliverable

Mint managed release cycle

Monthly Invoice in advance

Monthly Invoice in arrears

Milestone Invoicing

ALM Required

ALM Recommended

ALM Recommended

20% Project Kick-off Fee Required

Upgrade Principle

CRM is a Business Tool and aligns to provide long term strategic value and

competitive advantage

“How you gather, manage, and use information will determine whether you win or lose.”

-Bill Gates

Upgrade Considerations

Supportability of Changes (Within Guidelines; Plugins; Javascript)

Infrastructure and Technical Changes (Windows Server; SQL Server; Hardware)

Existing Functionality Mapped to New Features (Upgrade vs Reuse vs Rebuild)

Data Consistency, Quality and Accuracy (Migration; Archiving; Loss)

CRM 4.0

CRM 2011

CRM 2013

CRM 2015

CRM 2016

Architectural, Syntax and Structure Changes (SDK; Javascript; Data Models)

In-Place Upgrade Guideline

In-Place Upgrade

Is the data trusted and accurate?

Are the business requirements and objectives the same?

Is the solution native or configuration only?

Is the current version only 1 version away from the target version?

Is there no integration, or no changes to the integrations schema’s?

Is the target environment the same (On-premise versus online)?

Can the business manage / allow for extended downtime during upgrade?

Yes

In-Place Upgrade Overview

Upgrade to next version

Code upgrade on new codebase

New feature fit and review

Data migration

Testing and lock-down

Current Version Are we on the target version?

Legacy

Side-By-Side Upgrade Guideline

Side-By-Side Upgrade / Rebuild

Do new features replace previously built functionality?

Have the business requirements or objectives changed?

Is the target environment different (On-premise versus Online)?

Is the current version more than 1 version behind the target version?

Is the solution highly customised?

Are there a lot of integration points?

Are there any concerns with the data validity and accuracy?

Yes

Side-By-Side Upgrade Overview

•Migrate selected functionality•Migrate required models and data•Retarget specific integration•Deploy & Train

Functional Release

Current Version Target Version

•Migrate selected functionality•Migrate required models and data•Retarget specific integration•Deploy & Train

Functional Release

Preparation

Separate functional areas

Install new target environment

Plan using new features

…

Archive

Legacy

Legacy

Upgrade Comparison (illustrative only)

1 2 3 4 5 6 7 8 9 10

11

12

Upgrade to 2013 Upgrade to 2015Deplo

yDeploy

Base Planning

Prep. Release 1: MVP on 2015

Base Planning

Release 2 …

In-Place

Side-By-Side

Timeframe

Q & A

Mint Management Technologies

@mint_consulting

Mint Management Technologies

@mint_consulting

www.mint.co.za

marketing@mint.co.za

+27 10 003-6743

Thank You