Successfully reported this slideshow.

Professional Graduation Project


Published on

This lecture was created by Mashro3na team in PiTechnologies.
Session aims to illustrate common mistakes, problems and drawbacks in graduation projects with the expected reasons and the recommended solutions

Published in: Education, Technology, Business

Professional Graduation Project

  1. 1. Professional Grad. Project PiTechnologies AhmedYossef
  2. 2. About PiTechnologies‣ Egyptian startup company‣ PiTechnologies is specialized in ‣ Mobile applications development ‣ Web applications development ‣ Embedded systems ‣ Wireless communications
  3. 3. About Mashro3na‣ It is an initiative of PiTechnologies‣ Mashro3na aims to provide graduation projects technical and managerial support‣ Mashro3na aims to enhance: ‣ The graduation projects ‣ The senior year student skills (technical, managerial, team working ..)
  4. 4. Agenda‣ What is GP ?‣ Why are you working on GP ?‣ GP Team‣ Common mistakes‣ Meetings‣ Tools ‣ SVN ‣ Project Management
  5. 5. Region 1 Region 2 200 150 100 50 2007 2008 2009 0 2010Survey ..What is GP ?
  6. 6. Main Categories Space ship ? Product ? Smart Home ? GPS + MATLAB + Java + Linux + MC + ..don’t forget web application and mobile end :)
  7. 7. Product Space ship Out of scope Low technical experience Lake of support Waste of time connecting others Ends as bike ..It is not accepted as GP in most time Nothing new It is not a project You are traditional for interviewer You make enological things Smart Home Assembler
  8. 8. Best ProjectNew Idea - Old Idea (added Value) Phases Applicable (Product) Independent - learn technologies
  9. 9. Why GP ?
  10. 10. Reasons‣ Todo something you should know why you are doing it ‣ Learn new technologies ‣ Apply theoretical concepts ‣ Work as for real ‣ Show the world something
  11. 11. GP Team
  12. 12. Team work‣1 +1=2 Accepted‣1 +1=3 Expected‣1 +1=0 Actually
  13. 13. 1+1 = 3‣ Different tasks require different skills‣ Different players .. different minds .. new solutions‣ More motivation‣ Work review‣ Focus more on similar tasks
  14. 14. 1+1 = 0‣ Different tasks requiretasks .. meskills I will work on all different too‣ Different players .. different minds .. new i Think .. you work solutions More arguments .. More problems‣ More motivation‣ Work reviewmy errors .. i will discover yours You discover‣ Focus more on similar tasks .. again I am working on all tasks
  15. 15. Solutions‣ Changing the previous attitudes‣ It is business not personal ‣I don’t like your idea .. but i respect you ‣ You are right your idea is better than mine ‣I don’t like team decision .. i will execute it ‣Idiscuss only when it is good for my team not to prove my point of view
  16. 16. Common Mistakes
  17. 17. Team Homogeneity‣ All A+ team‣ All F- team‣ All developers team‣ A+ and F- team
  18. 18. Team Homogeneity‣ All A+ team Team should be miscellaneous‣ All F- team Different skills Same goal‣ All developers team‣ A+ and F- team
  19. 19. Courses Mistake‣ Dividethe project requirements to a group of courses‣ Attending courses till the last moment
  20. 20. Courses Mistake Define requirements to a group of‣ Divide the project courses you need courses Define self study you need Restrict courses time and dealines‣ Attending courses till the last moment
  21. 21. Specs Mistakes‣ Undefined specs .. Undefined project ..Undefined results‣ Definedspecs .. Undefined manners ofexecution
  22. 22. Specs Mistakes IdeaUndefined project ..‣ Undefined specs .. is not enough You should have full specs of the system before Undefined results starting‣ Defined specs .. Undefined manners of execution
  23. 23. Time Mistakes‣ Unplanned‣ Wrong plan ‣ Too much time for learning ‣ Too much time for working ‣ No backup plan and no margins
  24. 24. Time Mistakes‣ Unplanned Time should be well divided‣ Wrong plan should be divided into phases Project Delay means missing features not project failure ‣ Too much time tasklearning planned Each simple for should be Learn, Design, Implement, Test, Document ‣ Too much time for working Keep margins ‣ No backup plan and no margins
  25. 25. Meetings
  26. 26. Teamwork and Meetings‣ Meeting is the most important part of the teamwork‣ As during meeting: ‣ Work is divided into tasks ‣ Tasks are assigned ‣ Completed tasks are delivered
  27. 27. Agenda‣ Leadershould announce the agenda before the meeting‣ Members are free to add any topics before the meeting‣ Leader should state the agenda as check list of tasks, decisions and deliverables
  28. 28. Apology‣ If you will be delayed, you should report before the meeting starts.‣ If you will not be able to come, you should delegate your vote and work to some one else.
  29. 29. During Meeting‣ No argument‣ Limited discussion‣ IfA and B has different point of views, each one would separately explain his, then leader should terminate discussion to start voting.‣ In dark situations, leader can make a decision, and you should accept it.
  30. 30. After the Meeting‣ During the meeting, leader should have written notes about the discussions and the decisions.‣ Leader should send MoMs to the team‣ Leadershould make the agenda and the time of the next meeting
  31. 31. Apology for deliverables‣ Youshould report any errors or blocking breaks just when they appear.‣ Always report and make your leader updated‣ Don’t change your task without confirmation
  32. 32. Tools - Version Control
  33. 33. What is VC‣ Version control - Source control - Revision control‣ It is a software enables you to keep history of changing in documents, code files, ..‣ It can be centralized or distributed
  34. 34. Why Version Control‣ No conflict‣ No project_last, project_final, project_finaaaal‣A change in a single file within the project, generates a new version with number, timestamp, creator and comment‣ Noneed to merge copies and move code on flash memory
  35. 35. Check Out‣ It is an operation to request a copy of the project to work on‣ You can check out the latest version or any older version you like
  36. 36. Check in‣ Check in - Commit -Submit‣ It is an operation done after checking out and making some modifications‣ Youcommit your changes to save them as a new version with timestamp and comment
  37. 37. Branching‣ It is an operation to make a sub-project/parallel project‣ Youmake this operation when you want to test a new feature.
  38. 38. Test ScenarioCurrent Version Current Version Branch Check Out Check Out Check out Test Code Check In Test Code Real Code Check Out Real Code Real Code
  39. 39. Examples‣ SVN‣ CVS‣ (online)‣ Git‣ (online)
  40. 40. Tools - Project Management
  41. 41. What is PM ?‣ It is the process of ‣ Diving work into phases and tasks ‣ Identifying execution percentage ‣ Finding critical issues ‣ Finding alternative solutions
  42. 42. Project Phase Task Task Task Task Phase Task Task Task Task Phase Task Task Task Task
  43. 43. Phases‣ You should divide your project into phases‣ Each phase represents a percentage of total project‣ Phaseis a milestone, with defined date you should measure your progress
  44. 44. Task‣ It is the building block of the project‣ Each task should have the following ‣ Major phase Task the basic element in the project.. ‣ Type If you could manage tasks .. you will manage your project .. otherwise ! ‣ Dead line ‣ Assigned player(s) ‣ Reviewer and/or supervisor
  45. 45. Task Types Planning Learning Execution• To define tasks • To know about• Involves a lot of something • To get something estimation and lack done. of info • Undefined time • Defined goal• Usually involves • Should has a • Estimated time deadline learning tasks
  46. 46. Examples‣ Codendi (Web application)‣ Redmine (Web application)‣ Planner‣ QDPM (Web application)
  47. 47. Contacts Website: Fan Page: Twitter: @pitechnologiess My mail: ayossef@pitechnologies.netThanks and best of luck .. AhmedYossef