Master thesis presentation


Published on

Applying Agile Methodologies to Design and Programming

I successfully defended my master thesis in May 2012. It was assessed with A, which is the highest grade according to a six-point grading scale of Tallinn University. I believe that not only my paper, but also its presentation was clear and logical, which helped me to receive fair, adequate questions from the judges.

I hope, these slides will help future students to make their own presentations for theses. Sometimes presentation becomes a decisive factor when judges argue about your grade.

Good luck!

Published in: Education
  • Be the first to like this

Master thesis presentation

  1. 1. Tallinn University Institute of InformaticsApplying Agile Methodologies to Design and Programming Master Thesis Tatjana Pavlenko (author) David Lamas (supervisor) Tallinn 2012
  2. 2. “We get too soon old and too late smart”, Pennsylvania Dutch proverb ? “Everybody has an idea for an app”, Shawn Welch, App developer
  3. 3. How to get there? Transforming outdated Windows software to an App ?Technical knowledge Management strategy
  4. 4. What is Scrum?Iterative incremental software development methodology Not a strict methodology Team-based frameworkRelies on self-organizing and cross-functional teams
  5. 5. Agile Crystal Scrum Lean KanbanFeature Driven Extreme Development Programming (XP)
  6. 6. Agile = Scrum?
  7. 7. Research problem How to design aneffective Scrum approach for Company Sigma
  8. 8. Research strategy1. Working environment2. Obstacles3. Scrum approach proposal4. Implementation
  9. 9. MethodologyDesign research
  10. 10. Company Sigma 8 team members 20 years in software development Windows based Sales Force Automation tool Plans 7 iOS Apps Distributed team Full-time, part-time, freelance No experience in user interface design Serious clients
  11. 11. Obstacles 1) Team is not self-organizedIDEAL REAL
  12. 12. Obstacles2) Designer does not support Scrum
  13. 13. Obstacles Distributed team Unawareness No common understanding Wasting time during the meetings Designer prefers traditional approach Designer’s contributes are not regularDesigner needs documented information
  14. 14. Improvements Online collaboration Team motivating presentations Prototypes Plan in advance Special Scrum methods for DesignerMediator between Designer and the Team Iterative information for Designer
  15. 15. Designing effective Scrum approach The goal is to imagine “something better than what exists”. Design Research Through Practice (2011)
  16. 16. 4 cyclesDecember 2011 – April 2012 Lessons Learned
  17. 17. 1st cycle – a good start
  18. 18. 2nd cycle – challenges
  19. 19. Interview codes Settings Acts Activities Meanings Participation Relationships Retrieving Visualization of information; interface; Freelancer;Role in the Collecting grain by No need in full-time Designers are also Responsible for There are no project grain; designer; usability testers usability; mockups; Beat someone if Front-end; needed; Should have job Need a person who User stories were experience; will push the whole not clear to Constant process of A-la demo version; project;Attitude to Doing something by anybody; changing everything Processes are all the Leader; Scrum certain deadline; My task is to make a simultaneously; same; It’s a common good, convenient Three ways of Project and nice product; managing design; Management; Hierarchy and Constant presence is Searching for organization is Everyone is Current No concrete plan; not required; concrete broken; responsible for hissituation Good ideas; Good people, good information; Weird mess is work; company; happening; Group report; The whole work can Product Owner is Someone distributes Plan program; be done in 2 someone fromTowards the tasks; Prepare for the months; developers; Job experience; ideal Designer plans with future; Responsible people; Software architect Senior developer senior developer; Stick to planned and Junior should besituation Make back-end first; mockup; developer report to responsible for I need information; Senior Developer; Junior
  20. 20. Tag Clouds
  21. 21. Interviews
  22. 22. 3rd cycle – wind of change
  23. 23. 4th cycle – effective
  24. 24. Results Successful Partly successful Not successful1 Scrum Master Task Board Pilot User Stories Contact Designer2 Sprint Burndown Chart Fixed Sprints regularly Fibonacci Numbers to3 Improvised mockups More frequent meetings evaluate tasks Paper prototypes of More clear and simple4 Kanbanery online tool application User Stories Kanbanery tool doubled Involve people into using Educative presentation5 on the wall prototypes about Scrum Adopt some methods of6 Dropbox Scrum specially for Designer Preplanned topics for7 Daily Standups meetings
  25. 25. ResultsINITIAL FINAL
  26. 26. Conclusions Team is self-organized Designer is left out of Scrum• Involve as much team members as possible• Keep tracking others and slack their resistance• Team should not be forced to use Scrum• Leave designer alone as long as he successfully does the job
  27. 27. Designing effective Scrum approach The goal is to imagine “something better than what exists”. Design Research Through Practice (2011)
  28. 28. Thank you for your attention! Looking forward to hearing your questions