Project Sample

553 views
503 views

Published on

Project Sample

Published in: Education
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
553
On SlideShare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • Project Sample

    1. 1. Project Management Superfactory Excellence Program™ www.superfactory.com
    2. 2. Outline <ul><li>PM in today’s environment </li></ul><ul><ul><li>rapid change </li></ul></ul><ul><ul><li>BPR </li></ul></ul><ul><li>The project plan </li></ul><ul><li>Management & communications </li></ul><ul><li>Organizational, people, political issues </li></ul><ul><li>Stakeholders </li></ul><ul><li>Tools & methodologies </li></ul>
    3. 3. Three Disciplines
    4. 4. Why Projects Succeed <ul><li>User involvement </li></ul><ul><li>Exec management support </li></ul><ul><ul><li>unequivocal sponsorship </li></ul></ul><ul><li>Clear understanding & statement </li></ul><ul><li>of requirements </li></ul><ul><li>Effective planning </li></ul><ul><li>Realistic expectations </li></ul><ul><li>Standish Group survey of IT execs </li></ul>
    5. 5. Customers = Needs/Requirements <ul><li>Needs analyst traits: </li></ul><ul><ul><li>strong ability to deal with customers </li></ul></ul><ul><ul><li>political skills </li></ul></ul><ul><ul><li>technically competent </li></ul></ul><ul><ul><li>open-minded & imaginative </li></ul></ul><ul><ul><li>high tolerance for ambiguity </li></ul></ul><ul><ul><li>articulate </li></ul></ul><ul><li>Technicians tend to produce Mercedes not the Hyundai that = s wanted </li></ul>
    6. 6. Attaining Political Credibility <ul><li>Establish mission </li></ul><ul><ul><li>what products/services we provide </li></ul></ul><ul><li>Identify customers </li></ul><ul><ul><li>functional (direct) </li></ul></ul><ul><ul><li>political (indirect) </li></ul></ul><ul><li>Survey customers </li></ul><ul><ul><li>what expectations/perceptions exist? </li></ul></ul><ul><ul><li>criteria for measuring them? </li></ul></ul><ul><ul><li>triggers for them? </li></ul></ul>
    7. 7. Sources of Project Risk <ul><li>General sources </li></ul><ul><li>environmental (largely uncontrollable) </li></ul><ul><ul><li>external, e.g. government regulations </li></ul></ul><ul><ul><li>internal, e.g. new division VP </li></ul></ul><ul><li>technical </li></ul><ul><li>market </li></ul><ul><li>financial </li></ul><ul><li>people </li></ul>
    8. 8. Realistic Estimating <ul><li>Lots of reasons for poor estimates </li></ul><ul><ul><li>inexperience, technical problems, changes optimists, low-balling, politics </li></ul></ul><ul><li>Bottom-up cost estimating </li></ul><ul><ul><li>rollup the WBS packages </li></ul></ul><ul><li>Top-down or Parametric estimating </li></ul><ul><ul><li>from experience to complex models </li></ul></ul>
    9. 9. Configuration Management (CM) <ul><li>Resist change via bureaucracy </li></ul><ul><li>Change control via CM </li></ul><ul><ul><li>Rigorously screen changes </li></ul></ul><ul><ul><ul><li>formal process for assessing merit </li></ul></ul></ul><ul><ul><ul><li>major or minor impact? </li></ul></ul></ul><ul><ul><ul><li>if major goes to Change Control Board (CCB) </li></ul></ul></ul><ul><ul><li>document changes </li></ul></ul><ul><ul><li>update baseline </li></ul></ul>
    10. 10. Earned Value Approach <ul><li>Developed in 1960s for large defense projects; now used in smaller projects </li></ul><ul><li>50-50 rule assumes task 50% complete when started, 100% when completed </li></ul><ul><li>Compare earned value to planned costs </li></ul><ul><li>Collecting data </li></ul><ul><ul><li>large projects employ cost account managers </li></ul></ul><ul><ul><li>for smaller projects, use 50-50 rule, take advantage of milestones, or can guess using experience </li></ul></ul><ul><li>Limitations of earned value </li></ul><ul><ul><li>availability of accurate, timely data </li></ul></ul><ul><ul><li>educational; need organizational understanding </li></ul></ul>
    11. 11. Post-Implementation Audit <ul><li>Evaluate project’s achievements against plan </li></ul><ul><ul><li>budget, deadlines, specifications, quality of deliverables, client satisfaction </li></ul></ul><ul><li>Six questions: </li></ul><ul><ul><li>Project goal achieved? </li></ul></ul><ul><ul><li>On time, within budget & per specs? </li></ul></ul><ul><ul><li>Client (stakeholder) satisfied? </li></ul></ul><ul><ul><li>Business value realized? </li></ul></ul><ul><ul><li>PM lessons learned? </li></ul></ul><ul><ul><li>What worked, what didn’t? </li></ul></ul>

    ×