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


Published on

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

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

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

  1. 1. Michael Belin IT-Architect/Project Manager   Cricket / MCSS
  2. 2. <ul><li>Who am I and why am I here ? </li></ul><ul><li>What do On-Demand and On-Premise Implementations have in common ? </li></ul><ul><li>What sets them apart ? </li></ul><ul><li>Lessons learned </li></ul><ul><li>Q + A ? </li></ul>
  3. 4. <ul><li>What’s the same ? </li></ul><ul><li>(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. </li></ul><ul><li>(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. </li></ul><ul><li>(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. </li></ul><ul><li>(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. </li></ul>
  4. 5. <ul><li>What’s Different </li></ul><ul><li>(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. </li></ul>
  5. 6. <ul><li>What’s Different </li></ul><ul><li>(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’. </li></ul>
  6. 7. <ul><li>What’s Different </li></ul><ul><li>(3) Project Resources ! </li></ul><ul><li>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. </li></ul><ul><li>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. </li></ul>
  7. 8. <ul><li>Q + A : </li></ul>