Introduction to Project Management
•Descargar como PPTX, PDF•
0 recomendaciones•818 vistas
A summary of and introduction to project management for the WIT (http://oit.williams.edu/wit/) program.
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Destacado
Similar a Introduction to Project Management
Similar a Introduction to Project Management (20)
Último
Último (20)
Introduction to Project Management
- 1. Introduction toProject Management Chris Warren cwarren@williams.edu x4323 Jesup 312
- 2. What Is Project Management A formal process for getting things done A scientific approach to the good old To Do list Occasionally, a pain in the butt Usually useful anyway
- 3. What Is Project Management To Do List Intuitive Gravity go shopping eat pizza stare at sky do a little dance sing a little song ...
- 4. What Is Project Management Project Management Scientific Gravity Project: Purple Cow Team Jay Deon Julie Zina Goals song dance chocolate Milestones Hay – due 6/30 sow seeds – Jay water – Jay weed – Deon verify- Zina harvest – Juli Fencing – due 7/05 .... Cow (depends on Hay) – due 7/14 find – Zina get to quad – Jay, Julie, Deon, Zina ...
- 5. Why Project Management Increase likelihood of success Use resources effectively Reduce uncertainty Put work in a larger context Reduce stress
- 6. Traditional PM 4-5 distinct phases Initiation / vision Planning / design Execution / development Monitoring / control Closing / deployment Lots of up-front planning Clean hand-off between phases
- 7. Traditional PM – Yay! Proven track record Easy to understand Easy to apply Well suited to top-down input
- 8. Traditional PM – Boo. Inflexible Known-result oriented High overhead Overwhelming Low benefit for small projects Missing key web / software steps
- 9. Technology Project Issues Exploratory and inventive LOTS of testing and debugging Additional maintenance phase Changing requirements Clients can be.... tricky
- 10. Technology PM - Waterfall Initiation Specification / Requirements Planning Design Execution / development Testing and debugging Deployment Maintenance Then we tweak things just a bit to get...
- 12. Iterfall (Iterated Waterfall) Initiation Specification / Requirements Planning Design Execution / Development Testing and Debugging Deployment Maintenance
- 13. Iterfall Project Management Better, but still has some basic problems In response to the shortcomings of the iterfall model a relatively new style of project management has been developed...
- 14. Agile Project Management A P M !
- 15. Agile Project Management Quick software development Small, tight teams Very flexible Very human-interaction oriented Best for non-critical projects
- 16. APM - Yay! Quick software development Small, tight teams Very flexible Very human-interaction oriented Best for non-critical projects BUT.....
- 17. APM... Boo? Requires experienced developers Relies on VERY frequent feedback Relies on self-organization and self-direction Lack of group expertise can enhance mistakes And yet....
- 18. A Middle Ground Iterfall model provides larger structure over all time frame abstract milestones easily teachable approach clear goals APM provides per-step framework team oriented exploratory flexible
- 19. W I T e r f a l l
- 20. WITerfall Project Management Initiation – done a clear vision is last step of 1 or the first step of 2 Specification (trad) – lots of help Planning (hybrid) – moderate help Design (agile) – minimal help Implementation (agile) – minimal help Testing and Debugging (agile) – minimal help Release & Hand-off (hybrid) – moderate help Maintenance – outside WIT
- 21. Requirements & Specification GOAL 1: Help the sponsor develop and clarify their vision. GOAL 2: Come to a mutual understanding of what the project is. GOAL 3: Make sure the project can be completed!
- 22. Planning Milestones an ordered list of stages points along a path To-Do’s / Items / Steps / etc. often associated with a milestone note especially difficult items note dependencies and paralleliza-whatever... things you can do at the same time (but beware of yak shaving...)
- 23. Workflow Workflows are the checkpoints / sign-offs used to make sure particular tasks are done correctly Graphic Design Team members review ITS signs off Sponsor signs off Databases Chris reviews structure Test data entry Coding Project Architecture Debugging Spec Changes Filming a Movie ...
- 24. Testing and Debugging Tasks / Tickets keep track of problems discovered or enhancements requested What the problem is When it’s due Who’s working on it Notes about the work
- 25. Project Management Tool http://williamswit.comindwork.com
- 26. Sample Web Project Milestones Project management set up Project Specified Documentation framework set up Development environment set up Content organized Base theme chosen (WP) Functioning web site Placeholder content entered Visual mockups approved Media prepared Custom functionality implemented Theme finished Media deployed Final content in place Help docs complete Sponsor approval Released Handed off to sponsor Presentation Done
Notas del editor
- success is not guaranteed; need to know what ‘success’ means for the project; material and human resources; low uncertainty needed for planning; context of other projects, constraints, and events; know what to do when; have reasonable expectations
- arose as a distinct, formal system in the 1950’s; Henrey Gantt; Henri Fayol; Frederick Winslow Taylor;
- recipe-like
- software and technologydevelopment projects often have additional complications that cause problems for traditional project management approaches
- break the project into very small pieces; focus on very short (1-4 week) iterative cycles, each of which is a microcosm of the waterfall system; start and end with a working product; accumulate features; works well for small, tight teams of 5-9 people; gain flexibility but lose certainty
- go over the handout