Nuxeo World Session: Successful Deployment of Nuxeo Document Management


Published on

Published in: Technology, Business
  • 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
  • Thomas
  • Alain
  • Thomas
  • Alain
  • Thomas
  • --> start with a small «training» session on the product, to start the thinking process.
  • Nuxeo World Session: Successful Deployment of Nuxeo Document Management

    1. 1. Successful Deployment of Nuxeo DM <ul><li>HEC - Educational content distribution with Smile </li></ul>17 Novembre 2010 Thomas Choppy, ECM business manager @Smile Alain Escaffre, Presales Manager @Nuxeo
    2. 2. The customer: HEC <ul><ul><li>World class business school - 4 times in a row the 1 st European business school </li></ul></ul><ul><ul><li>44,000 students in the world </li></ul></ul><ul><ul><li>International students </li></ul></ul><ul><ul><li>Top requirements! </li></ul></ul>
    3. 3. The System Integrator: Smile <ul><li>A strong connection with the vendor, common analysis starting from the presales period </li></ul><ul><li>A dual team with technical and functional experts </li></ul><ul><li>An experienced team with many successful projects. </li></ul><ul><li>A real expertise in information management (learning management for ex.) </li></ul><ul><li>Good knowledge of document management, not only «application development» </li></ul>
    4. 4. The project: educational content distribution <ul><ul><li>Training content, forum, homework deposit, grading system </li></ul></ul><ul><ul><li>Get the right content at the right moment </li></ul></ul><ul><ul><li>Capitalize learning content </li></ul></ul><ul><ul><li>Seamless integration with corporate permissions management </li></ul></ul><ul><ul><li>Dynamic and responsive user interface </li></ul></ul>
    5. 5. The project’s constraints <ul><ul><li>Important requirements for the UI Nice and highly customized user interface required </li></ul></ul><ul><ul><li>Must fit strong business specifications (not just document management) </li></ul></ul><ul><ul><li>Deep integration with the existing IT ecosystem </li></ul></ul><ul><ul><li>Thousands of users (hundreds for regular contribution) </li></ul></ul>
    6. 6.
    7. 7.
    8. 8. The schedule of the project and the agile approach <ul><ul><li>From May to November </li></ul></ul><ul><ul><li>Iterative cycles with pauses - 5 cycles </li></ul></ul><ul><ul><li>Initial zoning and story-boarding </li></ul></ul><ul><ul><li>Ongoing specifications </li></ul></ul><ul><ul><li>Now in production </li></ul></ul>
    9. 9. IT platform <ul><li>Initial validation of the technical platform </li></ul><ul><li>Linux, Oracle, Jboss </li></ul><ul><li>Bipro quadcore, 16Go RAM </li></ul><ul><li>IT synchronization (users, ACL, course lists, sessions…) </li></ul>
    10. 10. Role of Connect subscription <ul><li>Accelerate SI team’s work </li></ul><ul><li>Focus on «generic problems» that can be met, the SI integrator concentrates on «customer requirements». </li></ul><ul><li>20 tickets created during the length of the project </li></ul>
    11. 11. Role of Connect subscription <ul><li>Backport of some bug fixes </li></ul><ul><li>Bug-fixing (minor bugs on tag management) </li></ul><ul><li>Development design advice: JSF validation, Restlet API use </li></ul><ul><li>Technical solutions proposal (Frequent ACL update, portlet authentication) </li></ul><ul><li>Platform configuration help (max size of a field, ...) </li></ul><ul><li>Workaround on blocking bugs </li></ul>
    12. 12. Best practices <ul><ul><li>Use of story boarding </li></ul></ul><ul><ul><li>Define the initial scope at the beginning of the project, for agile managment </li></ul></ul><ul><ul><li>Be concerned by deployment issues at the begining of the project: technical requirements, architecture and required service level </li></ul></ul><ul><ul><li>Testing the various deliveries </li></ul></ul><ul><ul><li>Focus on business value </li></ul></ul><ul><ul><li>Manage each process one by one (user story) </li></ul></ul>
    13. 13. Best practices Use of storyboard
    14. 14. Usual pitfalls Workshops are critical <ul><ul><li>Too many people in the workshop sessions --> limit to 3-4 end users </li></ul></ul><ul><ul><li>No awarness of the product capabilities by the workshop attendees </li></ul></ul><ul><ul><li>No clear and measurable goals to achieve with the project: lost of the main stream </li></ul></ul>
    15. 15. Usual pitfalls Customer team is key <ul><ul><li>No implication of the customer admin sys team: source of many problems and delay </li></ul></ul><ul><ul><li>No team leader able of decision taking: risk of big delays strategic missorientation </li></ul></ul>
    16. 16. Start of a great story <ul><li>HEC is going to capitalise on Nuxeo (as ECM platform) and on content value (findability, reuse, sharging…) </li></ul><ul><li>An global approch of content: everything in one « thing » </li></ul><ul><li>A user friendly interface: more website than ERP </li></ul>
    17. 17. Thank you ! Any questions ?