Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Running Successful University Industry Projects Barcamp 07

1,199 views

Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

Running Successful University Industry Projects Barcamp 07

  1. 1. Running successful industry projects with Software Engineering Students. By Tiang Cheng
  2. 2. <ul><li>Introduction </li></ul><ul><li>Motivation </li></ul><ul><li>Guidelines for choosing a project </li></ul><ul><li>Recipes for Success </li></ul><ul><li>General Project Lifecycle </li></ul><ul><li>Conclusion </li></ul>Contents
  3. 3. <ul><li>Introduction </li></ul><ul><li>Motivation </li></ul><ul><ul><li>Students </li></ul></ul><ul><ul><li>Industry </li></ul></ul><ul><li>Guidelines for choosing a project </li></ul><ul><li>Recipes for Success </li></ul><ul><li>General Project Lifecycle </li></ul><ul><li>Conclusion </li></ul>Contents
  4. 4. Motivation - Students <ul><li>Why do an industry project? </li></ul><ul><li>Encourage young software engineers </li></ul><ul><li>Provide invaluable ‘real’ industry experience </li></ul><ul><li>The goal is the process (How to build a software product) not the product itself </li></ul>
  5. 5. Motivation - Industry <ul><li>Opportunity for R&D </li></ul><ul><li>Finding fresh talent </li></ul><ul><li>Building leadership skills </li></ul><ul><li>The goal is the product. We don’t need to know the process of building software. </li></ul>
  6. 6. <ul><li>Introduction </li></ul><ul><li>Motivation </li></ul><ul><li>Guidelines for choosing a project </li></ul><ul><li>Recipes for Success </li></ul><ul><li>General Project Lifecycle </li></ul><ul><li>Conclusion </li></ul>Contents
  7. 7. Choosing a Project - Guidelines <ul><li>An example of a bad project </li></ul><ul><ul><li>Develop and implement an Artificial Intelligence algorithms for crowd behaviour </li></ul></ul><ul><li>Good projects are: </li></ul><ul><ul><li>Simple </li></ul></ul><ul><ul><li>Cutting edge, but not bleeding edge </li></ul></ul><ul><ul><li>Technically Simple (Have one objective) </li></ul></ul><ul><ul><li>Functionally Flexible (Add functionality) </li></ul></ul>
  8. 8. <ul><li>Introduction </li></ul><ul><li>Motivation </li></ul><ul><li>Choosing a project </li></ul><ul><li>Recipes for Success </li></ul><ul><ul><li>Project scope - Guidelines </li></ul></ul><ul><ul><li>Controlling Scope and risks </li></ul></ul><ul><ul><li>Industry commitments </li></ul></ul><ul><ul><li>Good examples of projects </li></ul></ul><ul><li>General Project Lifecycle </li></ul><ul><li>Conclusion </li></ul>Contents
  9. 9. Project Scope - Guidelines <ul><li>Challenging. Involves research as well as development. </li></ul><ul><li>Solve a real problem </li></ul><ul><li>Know what direction you want to go </li></ul><ul><li>Know your problem domain </li></ul><ul><li>Only 20 to 40 hours development time (Very short) </li></ul>
  10. 10. Controlling Scope and Risks <ul><li>Scope is most common cause of failed projects. </li></ul><ul><li>“ Unable to deliver to client’s expectations” </li></ul><ul><li>Scope is dictated by industry, not students. </li></ul><ul><li>Pick a direction, and be flexible in your requirements and goals. </li></ul>
  11. 11. Industry Commitments <ul><li>Provide 2 to 10 hours a week </li></ul><ul><li>Technical support, advice, and close supervision </li></ul><ul><li>Sense of humour, team spirit, and leadership. </li></ul><ul><li>Strong team commitment and communication </li></ul><ul><li>Be a Mentor </li></ul>
  12. 12. Good Examples <ul><li>Implement and test XYZ algorithm </li></ul><ul><li>Convert ABC application from Perl to .Net </li></ul><ul><li>Develop a Proof of Concept (Process) </li></ul><ul><li>Build a java/c#/Ruby application to autocreate podcasts. </li></ul>
  13. 13. <ul><li>Introduction </li></ul><ul><li>Motivation </li></ul><ul><li>Guidelines for choosing a project </li></ul><ul><li>Recipes for Success </li></ul><ul><li>General Project Lifecycle </li></ul><ul><ul><li>Software Development Lifecycle </li></ul></ul><ul><ul><li>What actually happens in SDLC </li></ul></ul><ul><ul><li>Project Lifecycle </li></ul></ul><ul><li>Conclusion </li></ul>Contents
  14. 14. Software Development Lifecycle <ul><li>Requirements Specification </li></ul><ul><li>Architecture Design </li></ul><ul><li>Implementation </li></ul><ul><li>Test </li></ul><ul><li>Deliver </li></ul>
  15. 15. SDLC - Detailed <ul><li>Initial Requirements meeting </li></ul><ul><li>Team write document Version 0.1 </li></ul><ul><li>Industry review meeting </li></ul><ul><li>Second meeting </li></ul><ul><li>Rewrite document </li></ul><ul><li>Industry review meeting </li></ul><ul><li>Approval, or repeat steps 5 and 6 until Industry is happy. </li></ul><ul><li>Repeat for each stage in the Software Development lifecycle </li></ul>
  16. 16. Project lifecycle <ul><li>Introduction and project presentation to all students </li></ul><ul><li>Pick and choose a team </li></ul><ul><li>Regular project team meetings to assist in SDLC </li></ul><ul><li>Final presentation </li></ul><ul><li>Poster sessions, Seminars </li></ul>
  17. 17. Conclusion <ul><li>Industry projects are a win-win proposal </li></ul><ul><li>Successful projects require pre-planning, and ongoing project management by the industry partner. Treat it as you would an internal project </li></ul><ul><li>Rewarding investment. </li></ul>
  18. 18. Where to go from here? <ul><li>UWA </li></ul><ul><li>Senior Lecturer </li></ul><ul><li>Dr Mark Reynolds </li></ul><ul><li>[email_address] </li></ul><ul><li>Curtin </li></ul><ul><ul><li>Senior Lecturer </li></ul></ul><ul><ul><li>Brian von Konsky </li></ul></ul><ul><ul><li>[email_address] </li></ul></ul>
  19. 19. <ul><li>Thank You! </li></ul><ul><li>Any questions? </li></ul>

×