Seven principles for buying  packaged software Gebaseerd op de presentatie van: Jan Damsgaard, department head and profess...
<ul><li>Huidige pakketselectie aanpak leidt tot slecht passende software pakketten </li></ul>Probleem customer support ? a...
Standard Software Packages <ul><li>Definition </li></ul><ul><ul><li>Software developed for sale to more than one customer ...
<ul><li>Een aanpak ontwikkelen op basis van bewezen principes  </li></ul>Oplossing
De  principes <ul><ul><li>When you buy a software package you join its network </li></ul></ul><ul><ul><li>Take a long-term...
<ul><li>Principle 1 </li></ul><ul><ul><li>When you buy a software package you join its network </li></ul></ul><ul><ul><li>...
<ul><li>Principle 2 </li></ul><ul><ul><li>Take a long-term perspective: Look ahead and reason back </li></ul></ul><ul><ul>...
<ul><li>Principle 3 </li></ul><ul><ul><li>There is safety in numbers </li></ul></ul><ul><ul><li>Commitment moves from loca...
<ul><li>Principle 4 </li></ul><ul><ul><li>Focus on compatibility and avoid false gold </li></ul></ul><ul><ul><li>There are...
<ul><li>Principle 5 </li></ul><ul><ul><li>Choose a standard with an accessible  base of knowledge Network of technology mu...
<ul><li>Principle 6 </li></ul><ul><ul><li>Choose software with the right type of standardization </li></ul></ul><ul><ul><l...
<ul><li>Principle 7 </li></ul><ul><ul><li>Every journey starts with the first step </li></ul></ul><ul><li>Why not wait and...
<ul><li>Conclusions </li></ul><ul><ul><li>Novel mechanisms for acquiring software </li></ul></ul><ul><ul><ul><li>Strike a ...
Upcoming SlideShare
Loading in...5
×

Software packaged software principles publiek

459

Published on

Seven principles for buying
packaged software

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
459
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Software packaged software principles publiek

  1. 1. Seven principles for buying packaged software Gebaseerd op de presentatie van: Jan Damsgaard, department head and professor Department of IT Management http://www.cbs.dk/staff/damsgaard Bron: http://www.ecis2011.fi/wp-content/uploads/2010/11/JanDamsgaard.pdf Richard Claassens | Platform Architectuur Producten SNS Reaal 28-2-2012  
  2. 2. <ul><li>Huidige pakketselectie aanpak leidt tot slecht passende software pakketten </li></ul>Probleem customer support ? action management?
  3. 3. Standard Software Packages <ul><li>Definition </li></ul><ul><ul><li>Software developed for sale to more than one customer </li></ul></ul><ul><ul><li>In addition the main functionalities are common to all adopters </li></ul></ul><ul><li>Configurable via parameter adjustments, add-on modules, system integration, etc. </li></ul><ul><li>Customization is more radical yet it used to be popular </li></ul>
  4. 4. <ul><li>Een aanpak ontwikkelen op basis van bewezen principes </li></ul>Oplossing
  5. 5. De principes <ul><ul><li>When you buy a software package you join its network </li></ul></ul><ul><ul><li>Take a long-term perspective: Look ahead and reason back </li></ul></ul><ul><ul><li>There is safety in numbers </li></ul></ul><ul><ul><li>Focus on compatibility and avoid false gold </li></ul></ul><ul><ul><li>Choose a standard with an accessible base of knowledge Network of technology must be matched by a network of individuals </li></ul></ul><ul><ul><li>Choose software with the right type of standardization </li></ul></ul><ul><ul><li>Every journey starts with the first step </li></ul></ul>
  6. 6. <ul><li>Principle 1 </li></ul><ul><ul><li>When you buy a software package you join its network </li></ul></ul><ul><ul><li>Long-term relationship measured in decades not years </li></ul></ul><ul><ul><ul><li>Indirect dependencies (e.g. training of IT users) </li></ul></ul></ul><ul><ul><ul><li>Users of a package share common interests in its survival and evolution </li></ul></ul></ul>
  7. 7. <ul><li>Principle 2 </li></ul><ul><ul><li>Take a long-term perspective: Look ahead and reason back </li></ul></ul><ul><ul><li>Look ahead – which technologies and standards are expected to arrive and gain foothold </li></ul></ul><ul><ul><li>Which technologies have the most powerful supporters willing to jump start their band wagon </li></ul></ul>
  8. 8. <ul><li>Principle 3 </li></ul><ul><ul><li>There is safety in numbers </li></ul></ul><ul><ul><li>Commitment moves from local producers to (keeping track of) global standards </li></ul></ul><ul><ul><li>Two pitfalls of standards evolutions: </li></ul></ul><ul><ul><ul><li>Picking a loser may lead to “blind alley”scenario </li></ul></ul></ul><ul><ul><ul><li>Picking a market winner (because of flocking behavior) may </li></ul></ul></ul><ul><ul><li>lead to “one-way street” scenario. </li></ul></ul><ul><ul><ul><li>Micro motives Vs. Macro behavior </li></ul></ul></ul><ul><ul><ul><li>Stay on the broad boulevards for non-core business functionality – unless you really have a desire to explore the unknown </li></ul></ul></ul>
  9. 9. <ul><li>Principle 4 </li></ul><ul><ul><li>Focus on compatibility and avoid false gold </li></ul></ul><ul><ul><li>There are often multiple implementations of a standard and compatibility is not a straight forward issue </li></ul></ul><ul><ul><ul><li>Producers add proprietary/non-standard elements to differentiate their products </li></ul></ul></ul><ul><ul><ul><ul><li>Microsoft´s kiss of death: “Embrace, extend, extinguish” </li></ul></ul></ul></ul><ul><ul><ul><li>False gold raises switching costs </li></ul></ul></ul>
  10. 10. <ul><li>Principle 5 </li></ul><ul><ul><li>Choose a standard with an accessible base of knowledge Network of technology must be matched by a network of individuals </li></ul></ul><ul><ul><li>Misalignment of networks problematic (ERP) </li></ul></ul><ul><ul><li>Gateway between rivals packages </li></ul></ul><ul><ul><ul><li>Word and WP </li></ul></ul></ul>
  11. 11. <ul><li>Principle 6 </li></ul><ul><ul><li>Choose software with the right type of standardization </li></ul></ul><ul><ul><li>Standardization of output </li></ul></ul><ul><ul><li>Standardization of user interface </li></ul></ul><ul><ul><li>Standardization of skills (specific or generic) </li></ul></ul>
  12. 12. <ul><li>Principle 7 </li></ul><ul><ul><li>Every journey starts with the first step </li></ul></ul><ul><li>Why not wait and see what happens? </li></ul><ul><li>No, because </li></ul><ul><ul><li>Only if the you make an adoption decision will you help determine which standards software wins </li></ul></ul><ul><ul><li>The package development may not follow the “right” track </li></ul></ul>
  13. 13. <ul><li>Conclusions </li></ul><ul><ul><li>Novel mechanisms for acquiring software </li></ul></ul><ul><ul><ul><li>Strike a balance between active use and wait for market forces </li></ul></ul></ul><ul><ul><li>Today’s success tomorrow’s constraint – technological monopolies however established are always challenged </li></ul></ul><ul><ul><ul><li>E.g. the French Minitel </li></ul></ul></ul><ul><ul><li>Unless you really have to, stay clear of the teenage technologies and let the market discipline them and pick the winner </li></ul></ul><ul><ul><li>the vocabulary for standard software packages must be expanded to include their networked properties </li></ul></ul>Minitel: voorloper van het internet stopt donderdag 28 juli 2011
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×