mythes van erp implementaties
DESCRIPTION
Martin van Wunnik - Finance Projects Manager ARSIMA Projects Mythes van ERP implementaties: Is er iets veranderd sinds 1999?TRANSCRIPT
1
Mythes van ERP implementaties:
Is er iets veranderd sinds 1999?
Martin VAN WUNNIK [ Financial Projects Contractor ]
(+32) 0475/96.95.91 [email protected]
2
23 mei 2012
www.slideshare.net/MvanWunnik
www.arsimaprojects.wordpress.com
4 augustus 1999
3
4
Myth: A complete, detailed planning guarantees
a fluid installation of new software.
5
Reality: The pre-defined planning will not be respected.
What to do:
Best-case & Worst-case
‘Switching’ moment
‘Boetes’ (bv. extra ‘resources’)
« Partiële leveringen » <> « Prioritaire leveringen »
6
Myth: All aspects of the new software are documented.
7
Reality: The documentation is incomplete.
What to do:
Handleidingen +
Finale documentatie set (‘deliverable’)
Intern: Bekwaam persoon, onvoldoende tijd
Formaten & continuïteit?
8
Myth: The new software works.
9
Reality: The new software does not work.
What to do:
Beta-versies / Test / Parametrisatie
Bug-fixing procedure
Parallele werelden !
(dumps naar Excel)
10
« Scope creep »
Prioriteiten
11
Conclusie
Scenarii + “boetes”
Finale documentatie
Debugging & support structuur
ERP : Standaardpakket Oplossing op maat
Quid met onze bedrijfsprocessen ?!
Extra acronym: BI
12
Nothing, or almost nothing, is so enjoyable to say after a difficult
implementation brought to a good end:
“Well, we finally made it…It was a piece of cake”.
“ERP is 20% technologie
en 80% change management”
13
Mythes van ERP implementaties:
Is er iets veranderd sinds 1999?
Martin VAN WUNNIK [ Financial Projects Contractor ]
(+32) 0475/96.95.91 [email protected]