• Save
Lessons Learned: Implementation / Migration to Callidus On-Demand v5.2
Upcoming SlideShare
Loading in...5
×
 

Lessons Learned: Implementation / Migration to Callidus On-Demand v5.2

on

  • 3,279 views

presented at the TrueConnection 2008 Sales Performance Management Conference, hosted by Callidus Software

presented at the TrueConnection 2008 Sales Performance Management Conference, hosted by Callidus Software

Statistics

Views

Total Views
3,279
Views on SlideShare
3,257
Embed Views
22

Actions

Likes
0
Downloads
0
Comments
0

4 Embeds 22

http://www.callidussoftware.com 16
http://www.slideshare.net 4
http://compensationtechnology.com 1
http://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Lessons Learned: Implementation / Migration to Callidus On-Demand v5.2 Lessons Learned: Implementation / Migration to Callidus On-Demand v5.2 Presentation Transcript

  • Michael Belin IT-Architect/Project Manager   Cricket / MCSS
    • Who am I and why am I here ?
    • What do On-Demand and On-Premise Implementations have in common ?
    • What sets them apart ?
    • Lessons learned
    • Q + A ?
  •  
    • What’s the same ?
    • (1) DEFINE SUCCESS: Step back and consider exactly what constitutes success – you won’t know when you reached it if you don’t have it defined and laid out ahead of time.
    • (2) START AT THE END: Start at the end, not the beginning. – First consider what it is that you need in the way of system outputs – Then walk those backwards through the system and ensure that they are available and accounted for at each step in the process.
    • (3) GO BACK TO THE START: Perform a detailed review of available data and systems – ensure that all necessary data is available before finalizing you Compensation Plans.
    • (4) CHANGE CONTROL: Change is a constant – do everything possible to reduce change occurring between design and roll-out – This is best accomplished by breaking up the overall goals into smaller chunks and employing ‘Divide and Conquer’ to deploy a series of smaller, successful milestones rather than one, ‘Big Bang” deployment.
    • What’s Different
    • (1) Access to Data ! Access to large data sets via the ‘CSV export utility’ is slow when performed over the wire – I highly recommend purchasing a Site VPN connection and having this in place before going into your UAT Testing phase. This will make your Testing effort much easier.
    • What’s Different
    • (2) What goes Where - Preprocessing Pre-processing – Functional requirements that are not completely supported ‘out of the box’ by TrueComp ® can be addressed by deploying special, pre-processing logic. If this pre-processing logic is required, I would recommend that this take place in the source system, or in an environment on the client side, before the data is transmitted over to the On-Demand environment. This will support greater control, transparency, and ability to change as requirements change down the road. The On-Demand environment is one that values homogeneity and strives to enforce this – this enables the OD team to support various customers more efficiently. Consider this when you are making the decision where to place any ‘custom code’.
    • What’s Different
    • (3) Project Resources !
    • Ensure that the dedicated project resources assigned to your project have experience with On-Demand project deployment. We made a decision to switch from On-Premise to On-Demand relatively late in the process (i.e. we violated the change principal big-time!), and this definitely impacted our timeline.
    • We had an OUTSTANDING On-Premise project team, but in hindsight, using this team and re-deploying On-Demand caused several issues that could have been avoided had we switched to a dedicated On-Demand project team earlier in the process.
    • Q + A :