Successful Project Presentation
•Télécharger en tant que KEY, PDF•
2 j'aime•6,259 vues
This is a presentation I gave to the Rensselaer Center for Open Source Software about setting goals and such.
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (12)
Similaire à Successful Project Presentation
Similaire à Successful Project Presentation (20)
Dernier
Dernier (20)
Successful Project Presentation
- 2. Success?
- 3. Success? • Our aims are each different
- 4. Success? • Our aims are each different • Wide adoption
- 5. Success? • Our aims are each different • Wide adoption • Learning experience
- 6. Success? • Our aims are each different • Wide adoption • Learning experience • Proud of code
- 7. Success? • Our aims are each different • Wide adoption • Learning experience • Proud of code • Benefit RCOS
- 8. Success. Do what you set out to do.
- 10. Setting Goals Effectively • Helps:
- 11. Setting Goals Effectively • Helps: • Transparency
- 12. Setting Goals Effectively • Helps: • Transparency • NOT over committing
- 13. Setting Goals Effectively • Helps: • Transparency • NOT over committing • Efficiency
- 14. Setting Goals Effectively • Helps: • Transparency • NOT over committing • Efficiency • So, how do you practically:
- 15. Setting Goals Effectively • Helps: • Transparency • NOT over committing • Efficiency • So, how do you practically: • Stay transparent
- 16. Setting Goals Effectively • Helps: • Transparency • NOT over committing • Efficiency • So, how do you practically: • Stay transparent • Without committing to too much
- 17. Setting Goals Effectively • Helps: • Transparency • NOT over committing • Efficiency • So, how do you practically: • Stay transparent • Without committing to too much • Keep goals manageable
- 19. 3-Tier Semester Goals • Level 1 goals: • Bare minimum
- 20. 3-Tier Semester Goals • Level 1 goals: • Bare minimum • Level 2 goals: • Would be cool, should be achievable
- 21. 3-Tier Semester Goals • Level 1 goals: • Bare minimum • Level 2 goals: • Would be cool, should be achievable • Level 3 goals: • Ideal conditions, everything works out
- 22. 3-Tiers
- 23. 3-Tiers • Helps:
- 24. 3-Tiers • Helps: • Transparency
- 25. 3-Tiers • Helps: • Transparency • Not committing to too much
- 26. 3-Tiers • Helps: • Transparency • Not committing to too much • Implementation priority
- 27. Example: Concert • Level 1: • Audio organization page is fully functional • Manage collections page is fully functional • Dashboard page is fully functional • Level 2: • Color scheme developed and implemented • Buttons & Icons developed and implemented • Level 3: • Pretty start page with information about application • UI is reliably responsive • Loading notifications
- 29. Iterative Development • SD&D is awesome
- 30. Iterative Development • SD&D is awesome...but it kind of sucks
- 31. Iterative Development • SD&D is awesome ...but it kind of sucks • Tons of writing about your “process”, not really practical
- 32. Iterative Development • SD&D is awesome ...but it kind of sucks • Tons of writing about your “process”, not really practical • Iterative Development: epitome of practical
- 33. Iterative Development • SD&D is awesome ...but it kind of sucks • Tons of writing about your “process”, not really practical • Iterative Development: epitome of practical • Constant revision/re-evaluation of project & goals
- 34. Iterative Development • SD&D is awesome ...but it kind of sucks • Tons of writing about your “process”, not really practical • Iterative Development: epitome of practical • Constant revision/re-evaluation of project & goals • Choose an applicable iteration duration
- 35. Iterative Development • SD&D is awesome ...but it kind of sucks • Tons of writing about your “process”, not really practical • Iterative Development: epitome of practical • Constant revision/re-evaluation of project & goals • Choose an applicable iteration duration • Lots of code to get something working:
- 36. Iterative Development • SD&D is awesome ...but it kind of sucks • Tons of writing about your “process”, not really practical • Iterative Development: epitome of practical • Constant revision/re-evaluation of project & goals • Choose an applicable iteration duration • Lots of code to get something working: • Longer iterations (2-3 weeks)
- 37. Iterative Development • SD&D is awesome ...but it kind of sucks • Tons of writing about your “process”, not really practical • Iterative Development: epitome of practical • Constant revision/re-evaluation of project & goals • Choose an applicable iteration duration • Lots of code to get something working: • Longer iterations (2-3 weeks) • Project already working/smaller scope:
- 38. Iterative Development • SD&D is awesome ...but it kind of sucks • Tons of writing about your “process”, not really practical • Iterative Development: epitome of practical • Constant revision/re-evaluation of project & goals • Choose an applicable iteration duration • Lots of code to get something working: • Longer iterations (2-3 weeks) • Project already working/smaller scope: • Shorter iterations (1 week)
- 39. Each Iteration
- 40. Each Iteration • Starting a project?
- 41. Each Iteration • Starting a project? • First iteration:
- 42. Each Iteration • Starting a project? • First iteration: • Attempt an end-to-end (probably terrible) solution
- 43. Each Iteration • Starting a project? • First iteration: • Attempt an end-to-end (probably terrible) solution • In general:
- 44. Each Iteration • Starting a project? • First iteration: • Attempt an end-to-end (probably terrible) solution • In general: • Refine goals based on lessons learned
- 45. Each Iteration • Starting a project? • First iteration: • Attempt an end-to-end (probably terrible) solution • In general: • Refine goals based on lessons learned • Choose next high-level goals to tackle
- 46. Each Iteration • Starting a project? • First iteration: • Attempt an end-to-end (probably terrible) solution • In general: • Refine goals based on lessons learned • Choose next high-level goals to tackle • Create granular tasks
- 47. Each Iteration • Starting a project? • First iteration: • Attempt an end-to-end (probably terrible) solution • In general: • Refine goals based on lessons learned • Choose next high-level goals to tackle • Create granular tasks • Contributors can make clear commitments
- 48. Example: Concert
- 49. Example: Concert • High level goal:
- 50. Example: Concert • High level goal: • Audio organization page is fully functional
- 51. Example: Concert • High level goal: • Audio organization page is fully functional • Tasks:
- 52. Example: Concert • High level goal: • Audio organization page is fully functional • Tasks: • Retrieving list of a collection’s audio files should be available via REST api
- 53. Example: Concert • High level goal: • Audio organization page is fully functional • Tasks: • Retrieving list of a collection’s audio files should be available via REST api • Audio files panel retrieves and lists the files • ...
- 54. Success! completion of goals == measure of success