1. 12015-09-17 Taraxacum Anne Jon Schoonhoven Magdalena Jurić Final Prototype

2. Make sharing of learning materials easy –Teachers can view, add, remove and edit shared resources E-learning environment –Students can view, browse and comment/discuss resources shared with them 22015-09-17 Project Recap

3. 32015-09-17 Today’s Hats CustomerProject ManagerSystem Architect

4. 42015-09-17 Today’s Outline Project Metrics Project Experiences –Communication –Work Deviation –Project Result

5. 52015-09-17 Project Metrics Deliverables –On time and fulfilled Features –Implemented 66 out of 72 Dropped 2 customer requirements Dropped 4 additional requirements

6. 62015-09-17 Project Metrics Communication –Weekly Team meetings –Daily IM / Skype –Documentation –Redmine (project management software)

7. 72015-09-17 Project Metrics Spend Hours - Ratio

8. 82015-09-17 Project Metrics Spend Hours – Time Line

9. 92015-09-17 Project Metrics

10. 102015-09-17 Project Taraxacum 1.Fresh Start –Focus on Process 2.Productive –Focus on Development 3.Challenging –Focus into Oblivion

11. 112015-09-17 Project Taraxacum 3 rd Iteration went worser than planned. –Blame the Project Manager Other suspects –Communication –Holidays

12. 122015-09-17 Communication Distance of Communication –Culture –Medium (F2F, Skype, Mail, IM, Redmine, SVN)

13. 132015-09-17 Case “ Create an simple WYSIWYG editor for the plaintext resource. As an attachment you will find a custom version of TinyMCE editor [..] “

14. Cultural Differences Type of CommunicationMostly Digital Towards Shallow (!) Notion Of Time“Finish by Sunday” Type of ThinkingTask Minded & Goal Minded 142015-09-17

15. 152015-09-17 Product Status Shift of context use –Hierarchical –Community Product is “in between”

16. 162015-09-17 Initial Requirements Teacher –Browse –Manage courses and topics –Share resources –Create exercises –Search Student –Browse shared materials –Take and print notes –Share flashcards –Practice exercises and get results –Ask questions –Signal errors –Search

17. 172015-09-17 Design decisions Domain Driven Development Separation of concerns Layered architecture (MVC) Good it was easier to extend system independent development of layers Bad initially time consuming

18. 182015-09-17 Solution structure

19. 192015-09-17 Backend design Data access layer –Repository –Unit of Work –EF mapping to DB Model layer –POCO classes Service layer –Implements functionalities –Hides details

20. 202015-09-17 Backend design - Model

21. 219/17/2015 Frontend design Controller –Using service functions –Data provider for views View –Razor views (HTML + CS code) –Used to preview pages

22. 229/17/2015 Integration with other tools TinyMCE –Javascript WYSIWYG text editor Disqus –Comments community platform

23. 232015-09-17 System Demo –Registration of new user –Create Course –Create Exercise –Perform Exercise –Kudo Course –Comment –Perform Search

24. 242015-09-17 System Demo http://ec2-184-73-21-178.compute- 1.amazonaws.com/ http://dsd.skoonhoven.net/mvc/

25. 252015-09-17 System Demo Plan B – Video

26. 262015-09-17 System Demo Plan C – Screenshots

27. 272015-09-17 What’s Next? Strengths Well documented Flexible in features Weaknesses Red Code Performance Opportunities Niche Market Threads Not the only player on the market

28. 282015-09-17 Conclusion Requirements Struggling Level of Knowledge Different Effort Consuming

29. 292015-09-17 Discussion Target minded or Process minded –Running Late –Efficiency Task explanation vs execution

30. 302015-09-17 Discussion What was the biggest gap in the project? –Knowledge –Distance –Culture