Project Planning Goal 1 - Estimates are documented for use in tracking and planning project. Goal 2 - Project Activities and commitments planned and documented Goal 3 - Affected groups agree to project commitments (e.g. SWE, estimating, test, Sys engr, SQA, SCM, contracts, doc). 4 Estimating for an IT Project

REQUIREMENTS MANAGEMENT PROJECT PLANNING PROJECT CONTROL PROJECT TRACKING PROJECT MANAGEMENT REVIEWS QUALITY ASSURANCE 1 Definition Analysis Project Planning 2 Initial Planning 3 Create Estimates Review Estimates 4 Obtain Commitment and Approval Establish baseline 6 Requirements Status Tracking 5 Compare Actual(s) to Plans Evaluate Status and Performance Monitor risks 7 QA Plan conduct Audits 8 Status Meetings Project Review Commitment Reviews Re-planning needed? Project Complete? 13 Post-mortem 14 Update Enterprise Database 10 Requirements Change Control 9 Re-planning 11 Additional Estimates 12 New Commitment Negotiation Revise Baseline No Yes No Yes CONFIGURATION MANAGEMENT Project Management Process Delivery Point Commitment Point

Project Planning Process Requirements Management Negotiate Commitment Decompose Requirements Estimate Project Resources Estimate Product Size Develop Schedule Does Plan Meet Need? Obtain Commitment and Approval Enterprise Database Project Tracking Estimates Baseline Yes No Negotiated Requirements WBS SLOC Effort Labour Costs Capital Costs Schedule

Project Tracking & Oversight Goal 1 - Actuals (metrics) tracked against plan (estimates). Goal 2 - Corrective actions taken at deviation and managed to closure. Goal 3 - Changes to commitments agreed.

Project Tracking Process 1 Project Planning 2 Obtain Tracking Requirements 3 Obtain Baseline 4 Collect Actual(s) Compare Actual(s) to Plans 5 Evaluate Status and Performance Monitor risks 6 Status Meeting Project Review Commitment Review YesNo Re-planning Needed? Project Complete Yes Post Mortem 7

Reasons For Failure Poor Project Estimates –Unclear requirements –Unclear parameters affecting estimates –Little or no project databank to learn from –Difficult to adjust the estimates once approved (we must plan to re-estimate) –Estimates are rushed –Inability to get acceptance of the estimates –Imposed budgets, time and resources –Lack of training/coaching on estimating techniques (and tools) 8

Basic Rules of Thumb for sanity check of estimates and initial estimates. Effort Distribution: 20% Preliminary design 25% Detail Design 22% Coding and unit test 27% Integration and unit test 6% Management This does not include: 8-12% Analysis or 22% system Engineering.

Basic Software Estimation –Calculates size using a rudimentary sizing algorithm –Adjusts size depending on Problem & Data Complexity, and understanding of requirements –Calculates effort using industry productivity rules of thumb –Calculates simple approximation of the schedule required using COCOMO II equation –Distributes effort using basic rules of thumb Employs simple rules of thumb, published industry experience and project team expertise to calculate estimates:

Estimate Software Product Size Procedure Calculate Functional Size Measure Determine Problem Complexity Determine Data Complexity Determine Language Multiplier Determine Confidence Level Review Estimate Agree on Estimate? Software Product Size Estimate Functional Size Measure Total Functional Size Measure Estimated KSLOC Total KSLOC NO YES

Estimate Project Resources – Schedule Procedure

1 Determine Effort 3 Verify Imposed Schedule 5 Calculate Labor Costs 6 Calculate Capital Costs Size Effort in Person Months Duration in Calendar Months Adjusted Total Effort in Person Months Total Labor Costs Total Capital Costs No Yes Schedule Acceleration Estimate Project Resources / Schedule Procedure Is there an imposed schedule? 4 Adjust Effort to Meet Imposed Schedule 2 Calculate Optimum Schedule (Duration)

Information To Capture In Historical Records Project Characteristics Project Phase Characteristics Project Effort Adjustment Factors Component Characteristics Component Effort Adjustment Factors Build Information Deliverable Document Information Staffing Conditions Error Information Effort Information Schedule Information

Cost-of-Quality Model Project Cost Cost of Performance Cost of Quality Cost of Conformance Cost of Non-conformance Prevention Costs Appraisal Costs Training Methodologies Tools Policy & Procedures Planning Quality Improvement Projects Data Gathering & Analysis Fault Analysis Root Cause Analysis Quality Reporting Reviews  System  Reqts  Design  Test Plan  Test Scripts Walkthroughs (Code Inspection) Testing (First Time) IV&V (First Time) Audits Re-reviews Re-tests Fixing Defects (STRs,Irs)  Code  Documentation Reworking any Document CCB Engineering Changes Lab Equipment Costs of Retests Updating Source Code Patches to Internal code, Delivered Code External Failures Generation of Plans, Documentation Development of:  Requirements  Design  Code  Integration Legend Software Initiative