Day 17 Outline

I. Risk
    A. Risk Identification*
    B. Projection*
        1. likelihood -- often probability (assumes normal distribution)*
        2. Consequences (nature, scope)*
    C. Risk Referrent Point (Region) -- Go/No Go Decision*
    D. Risk Managment or Aversion*
II. Project Scheduling
    A. People Work Relationships
        1. Can you trade time for people
        2. Putnam Model -- K = L^3/(Ck^3 x td^4)
    B. Task Network
    C. Effort Distribution*
        1. Analysis 20%*
        2. Design 20%*
        3. Coding 15%*
        4. QA 45%*
        5. Maintenance 50 to 90%*
    D. PERT and CPM
        1. Critical Path*
        2. Earliest, Latest, Begin and End
        3. Float
        4. Probabilities
    E. Gantt Charts
    F. Management Tracking 
    G. Software Acquisition -- Cost/Benefit Analysis
III. Orgainization*
    A. Monarchy -- Chief Programmer Team*
    B. Democracy -- Everyone with a vote*
    C. Benevolent Dictator with advisors*
IV. The Software Project Plan*
    A. Estimates - Time, Resources, People*
    B. Risk Analysis*
    C. Schedule*
    D. Resources Available*
    E. Organization*
    F. Tracking and Control Mechanisms*
        1. SCM*
    G. SQA Plan*
    H. Standards*
    I. Development Plan (Analysis, Spec, Design, Coding)*