Introduction to Project Management


Published on

A summary of and introduction to project management for the WIT ( program.

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

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • 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
  • Introduction to Project Management

    1. 1. Introduction toProject Management<br />Chris Warren<br /><br />x4323 Jesup 312<br />
    2. 2. What Is Project Management<br />A formal process for getting things done<br />A scientific approach to the good old To Do list<br />Occasionally, a pain in the butt<br />Usually useful anyway<br />
    3. 3. What Is Project Management<br />To Do List<br />Intuitive Gravity<br />go shopping<br />eat pizza<br />stare at sky<br />do a little dance<br />sing a little song<br />...<br />
    4. 4. What Is Project Management<br />Project Management<br />Scientific Gravity<br />Project: Purple Cow<br />Team<br />Jay<br />Deon<br />Julie<br />Zina<br />Goals<br />song<br />dance<br />chocolate<br />Milestones<br />Hay – due 6/30<br />sow seeds – Jay<br />water – Jay<br />weed – Deon<br />verify- Zina<br />harvest – Juli<br />Fencing – due 7/05<br />....<br />Cow (depends on Hay) – due 7/14<br />find – Zina<br />get to quad – Jay, Julie, Deon, Zina<br />...<br />
    5. 5. Why Project Management<br />Increase likelihood of success<br />Use resources effectively<br />Reduce uncertainty<br />Put work in a larger context<br />Reduce stress<br />
    6. 6. Traditional PM<br />4-5 distinct phases<br />Initiation / vision<br />Planning / design<br />Execution / development<br />Monitoring / control<br />Closing / deployment<br />Lots of up-front planning<br />Clean hand-off between phases<br />
    7. 7. Traditional PM – Yay!<br />Proven track record<br />Easy to understand<br />Easy to apply<br />Well suited to top-down input<br />
    8. 8. Traditional PM – Boo.<br />Inflexible<br />Known-result oriented<br />High overhead<br />Overwhelming<br />Low benefit for small projects<br />Missing key web / software steps<br />
    9. 9. Technology Project Issues<br />Exploratory and inventive<br />LOTS of testing and debugging<br />Additional maintenance phase<br />Changing requirements<br />Clients can be.... tricky<br />
    10. 10. Technology PM - Waterfall<br />Initiation <br />Specification / Requirements<br />Planning <br />Design<br />Execution / development<br />Testing and debugging<br />Deployment<br />Maintenance<br />Then we tweak things just a bit to get...<br />
    11. 11. The<br />Iterfall<br />Model<br />
    12. 12. Iterfall (Iterated Waterfall)<br />Initiation <br />Specification / Requirements<br />Planning <br />Design<br />Execution / Development<br />Testing and Debugging<br />Deployment<br />Maintenance<br />
    13. 13. Iterfall Project Management<br />Better, but still has some basic problems<br />In response to the shortcomings of the iterfall model a relatively new style of project management has been developed...<br />
    14. 14. Agile <br />Project <br />Management<br />A P M !<br />
    15. 15. Agile Project Management<br />Quick software development<br />Small, tight teams<br />Very flexible<br />Very human-interaction oriented<br />Best for non-critical projects<br />
    16. 16. APM - Yay!<br />Quick software development<br />Small, tight teams<br />Very flexible<br />Very human-interaction oriented<br />Best for non-critical projects<br />BUT.....<br />
    17. 17. APM... Boo?<br />Requires experienced developers<br />Relies on VERY frequent feedback<br />Relies on self-organization and self-direction<br />Lack of group expertise can enhance mistakes<br />And yet....<br />
    18. 18. A Middle Ground<br />Iterfall model provides larger structure<br />over all time frame<br />abstract milestones<br />easily teachable approach<br />clear goals<br />APM provides per-step framework<br />team oriented<br />exploratory<br />flexible<br />
    19. 19. W I T e r f a l l<br />
    20. 20. WITerfall Project Management<br />Initiation – done<br />a clear vision is last step of 1 or the first step of 2<br />Specification (trad) – lots of help<br />Planning (hybrid) – moderate help<br />Design (agile) – minimal help<br />Implementation (agile) – minimal help<br />Testing and Debugging (agile) – minimal help<br />Release & Hand-off (hybrid) – moderate help<br />Maintenance – outside WIT<br />
    21. 21. Requirements & Specification<br />GOAL 1: Help the sponsor develop and clarify their vision.<br />GOAL 2: Come to a mutual understanding of what the project is.<br />GOAL 3: Make sure the project can be completed!<br />
    22. 22. Planning<br />Milestones<br />an ordered list of stages<br />points along a path<br />To-Do’s / Items / Steps / etc.<br />often associated with a milestone<br />note especially difficult items<br />note dependencies and paralleliza-whatever... things you can do at the same time (but beware of yak shaving...)<br />
    23. 23. Workflow<br />Workflows are the checkpoints / sign-offs used to make sure particular tasks are done correctly<br />Graphic Design<br />Team members review<br />ITS signs off<br /> Sponsor signs off<br />Databases<br />Chris reviews structure<br />Test data entry<br />Coding<br />Project Architecture<br />Debugging<br />Spec Changes<br />Filming a Movie<br />...<br />
    24. 24. Testing and Debugging<br />Tasks / Tickets keep track of problems discovered or enhancements requested<br />What the problem is<br />When it’s due<br />Who’s working on it<br />Notes about the work<br />
    25. 25. Project Management Tool<br /><br />
    26. 26. Sample Web Project Milestones<br />Project management set up<br />Project Specified<br />Documentation framework set up<br />Development environment set up<br />Content organized<br />Base theme chosen (WP)<br />Functioning web site<br />Placeholder content entered<br />Visual mockups approved<br />Media prepared<br />Custom functionality implemented<br />Theme finished<br />Media deployed<br />Final content in place<br />Help docs complete<br />Sponsor approval<br />Released<br />Handed off to sponsor<br />Presentation Done<br />
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.