Project Planning, Risk Estimation and Project Tracking

Project Planning (Chapter 4 (Chapter 5 6th ed))

• We need balance in our project planning.  Refining the plan to a degree of detail that allows us to execute it.
  • Fight for detail.  Resist the urge to let issues be TBD
  • "It is the mark of an instructed mind to rest satisfied with the degree of precision which the nature of a subject admits, and not to seek exactness when only an approximation of the truth is possible."  Aristotle
  • "Risk is measured by the degree of uncertainty in the quantitative estimates established for resources, cost and schedule.  If the project scope is poorly understood or the project requirements are subject to change, uncertainty and risk become dangerously high."  Pressman
• Estimates should attempt to bound the best and worst case scenarios
  • Estimation Alternatives (sec 26.5, pg 697 (6th ed sec 25.5, pg 648))
    1. Delay
    2. Based on similar projects
    3. Decompose
    4. Empirical models

Risk Estimation (Ch 28 (6th ed Chapter 25)

• Risks need to be managed
  • "If you don't actively attack the risks, they will actively attack you."  Tom Gilb
  • Types of Risk (that matter to you)
    • Project - Threaten the project plan (schedule, personnel, requirements)
    • Technical - The problem is harder than we thought
• Managed means MONITORED and MITIGATED
  • Monitor - If you think you think there is a risk, watch out for it.  Have you taken a look at your risk plan lately??  Any changes??
  • Mitigated - Have a plan before something bad happens.  If something bad happens, take action (generally according to your plan).

Project Scheduling and Tracking (Ch 27 (6th ed Chapter 24)

• Reasons for late or undelivered software (sec 27.1, pg 722 6th ed sec 24.1, pg 674)
  • Unrealistic deadlines, changing requirements, underestimate of effort, unconsidered risk, technical difficulty, personnel difficulty, miscommunication among team, poor project management
  • Any familiar??
• General Project Management Activity (recommended)
  1. Scope task(s)
  2. Estimate resources (people, time, effort)
  3. Estimate risks
  4. Plan work schedule and milestones
  5. Work
  6. Monitor and evaluate
  7. Adjust as necessary
• Tracking (i.e., monitor and evaluate)
  • Built-in
    • Project presentations (three reviews)
    • Advisor meetings (weekly)
    • Customer meetings (generally twice before each project presentation)
  • Other
    • Management review (weekly)
    • Self critique (bi-weekly)
    • Team meetings
    • Technical reviews