Key factors of success
 
 
The successful outcome of a project depends on a variety of factors. Hereafter is a list of principles which we believe critical, and which we live by in executing our assignments (some of these principles are specific to information system implementation projects) :
  1. Set out precise and realistic project goals, leading to business added value;
  2. Forecast the project Return on Investment where relevant;
  3. Carefully document the project objectives and stakes, and have them formally approved by all executives involved;
  4. Provide for an alternative project plan (in case the objectives are not met);
  5. Appoint a skilled and available Project Manager (PM) ;
  6. Appoint a representative, available and skilled project team;
  7. Identify within the Management Board a project sponsor (to back up and foster the PM);
  8. Split the project in consistent sub-projects;
  9. Set out a project structure where possible including the three following levels: workshops, follow-up committee (for operational monitoring), steering committee (for major decisions);
  10. Work out an overall project schedule (task types / month) for its entire lifespan, and have it approved by all executives involved;
  11. Set the meeting dates of all different project structures in advance;
  12. Implement a project communication directed to the general management, to users and to others concerned;
  13. Set out priorities for the needs identified by the detailed specification studies, set aside needs that have a low added value / cost ratio (example : intricate automation to avoid light manual processes);
  14. Check the consistency between needs and the initial project objectives;
  15. Anticipate future needs so that their fulfilment is not hindered by the current project;
  16. Have the final version of the detailed specification document approved by users and others concerned;
  17. From the outset define any needs for software development: tailor made processes, links between applications, data migration programs, etc.;
  18. Check the correct processing of your critical functionalities before you choose a software package;
  19. Check the appropriateness of the software package to existing systems and data volumes to be processed;
  20. Check the sustainability and references of your suppliers before signing;
  21. Stick as much as possible to the standard versions of packaged software;
  22. Document all decisions and specifications (using templates);
  23. Work out the list of tasks, quantify them, appoint people in charge, and define appropriate resources;
  24. Work out and update a detail schedule to monitor the project's progress (tasks/week/responsible people/resources) for each phase of the project, which will serve as the working tool of the follow-up committee;
  25. Provide for alternative solutions in case a key task runs into a serious difficulty;
  26. Build set-up prototypes of software, and test them with actual data;
  27. Ensure participation in tests of users and other people concerned;
  28. Work out acceptance test scripts and document user acceptance;
  29. Manage the change through : communication, procedures and training;
  30. Project closure: after initial roll-out, allow for time to attain project targets that have not yet been met, assess the project results, dissolve the project team and start the maintenance phase.
© 2002 ESOPE - Conception/Réalisation : Les passagers du web