Lessons Learned From an International Drupal Project (DrupalCampBaltics 2015)
•Download as PPTX, PDF•
2 likes•514 views
In Aprill 2015 Wunderkraut Estonia launched one of their biggest international projects - website for a well known construction materials brand Gyproc which is aimed to the Scandinavian markets (Sweden, Norway, Denmark). With the presentation I will share lessons learned from the project. Some of the questions that I will answer - how to not kick off an international project? How to not communicate with the client? How to not manage risks? How to not work with the requirements?
Recommended
Recommended
More Related Content
What's hot
What's hot (15)
Viewers also liked
Viewers also liked (11)
Similar to Lessons Learned From an International Drupal Project (DrupalCampBaltics 2015)
Similar to Lessons Learned From an International Drupal Project (DrupalCampBaltics 2015) (20)
Recently uploaded
Recently uploaded (20)
Lessons Learned From an International Drupal Project (DrupalCampBaltics 2015)
- 2. Gyproc Lessons Learned From an International Drupal Project Ivar Laks Drupalcamp Baltics 2015
- 3. 1 Project overview 2 Demo 3 Lessons learned 4 Questions What’s up?
- 5. 170 experts in 9 countries
- 6. CLIENT
- 7. Client
- 8. Client
- 9. MARKET
- 10. MARKET
- 11. Client
- 12. Client
- 13. Client
- 14. GOAL
- 15. 1 More efficient use of internal resources Project goals
- 16. 2 Increase customer satisfaction Project goals
- 17. 3 Increase sales through value added products Project goals
- 20. DEMO
- 23. Start September 2014 Finish April 2015
- 24. LESSONS LEARNED
- 25. 1 Establish playing rules: workflow, process, roles Lessons learned
- 26. 2 Client education at the beginning of the project Lessons learned
- 27. 3 Define the biggest risks (known unknowns) and tackle these at the beginning of the project Lessons learned
- 28. 4 Make risks transparent to the client Lessons learned
- 29. 5 Have face to face meetings Lessons learned
- 30. 6 Have retrospective meetings with the client Lessons learned
- 31. 7 Start with the content creation with real data as early as possible Lessons learned
- 32. 8 Migration > establish guidelines how to provide data Lessons learned
- 33. 9 Make sure all the key team members are involved in the project Lessons learned
- 34. 10 Streamline testing Lessons learned
- 35. 11 Make scope changes visible to the whole team Lessons learned
- 36. 12 Define a format for the client how to write requirements Lessons learned
- 37. 13 When a task is too vague to estimate do not take the commitment Lessons learned
- 38. SUMMARY
- 40. Client