1 / 13
Télécharger la présentation

IT Project Planning and Estimating: Achieving Commitments and Tracking Progress

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

Playing audio...

  1. Project Planning Estimating for an IT Project • 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

  2. Project Management Process PROJECTMANAGEMENTREVIEWS PROJECTCONTROL PROJECTTRACKING QUALITYASSURANCE REQUIREMENTSMANAGEMENT PROJECT PLANNING • 1 • Definition • Analysis • Project Planning • 2 • Initial Planning • 3 • Create Estimates • Review Estimates • 4 • Obtain Commitment and Approval • Establish baseline Commitment Point • 7 • QA Plan • conduct Audits • 5 • Compare Actual(s) to Plans • Evaluate Status and Performance • Monitor risks • 6 • Requirements StatusTracking • 8 • Status Meetings • Project Review • Commitment Reviews Re-planningneeded? Yes No • 9 • Re-planning • 11 • Additional Estimates • 10 • Requirements ChangeControl No ProjectComplete? • 12 • New CommitmentNegotiation • Revise Baseline Delivery Point Yes • 14 • Update Enterprise Database 13 Post-mortem CONFIGURATION MANAGEMENT

  3. Project Planning Process 1 RequirementsManagement 2 NegotiateCommitment NegotiatedRequirements 3 DecomposeRequirements • • WBS 4 EstimateProductSize • 5 EstimateProject Resources SLOC • Effort Labour Costs Capital Costs 6 DevelopSchedule • No Schedule DoesPlanMeet Need? • 7 8 ProjectTracking ObtainCommitmentand Approval Yes Baseline Enterprise Database Estimates

  4. 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.

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

  6. 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

  7. 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.

  8. 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:

  9. Estimate Software Product Size Procedure CalculateFunctional Size Measure 1 Functional Size Measure DetermineProblemComplexity 2 DetermineDataComplexity 3 Total Functional Size Measure DetermineLanguageMultiplier 4 Estimated KSLOC 5 DetermineConfidenceLevel Total KSLOC 6 Review Estimate AgreeonEstimate? NO YES SoftwareProduct SizeEstimate

  10. Estimate Project Resources – Schedule Procedure

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

  12. 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

  13. Cost-of-Quality Model Project Cost Cost of Quality Cost of Performance • Generation of Plans, • Documentation • Development of: • · Requirements • · Design • · Code • · Integration Cost of Conformance Cost of Non-conformance • 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 Appraisal Costs Prevention Costs • Reviews • · System • · Reqts • · Design • · Test Plan • · Test Scripts • Walkthroughs • (Code Inspection) • Testing (First Time) • IV&V (First Time) • Audits • Training • Methodologies • Tools • Policy & Procedures • Planning • Quality Improvement • Projects • Data Gathering & • Analysis • Fault Analysis • Root Cause Analysis • Quality Reporting Legend Software Initiative

More Related