1 / 21

Estimates

Estimates. Estimates Uncertainties Unknown Project development costs Project development schedules Team size Amount of software to be developed Hardware resources. Estimates. Estimation techniques Historical data Stepwise Estimation Counting product features Functional point Analysis

guido
Télécharger la présentation

Estimates

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

  1. Estimates • Estimates • Uncertainties • Unknown • Project development costs • Project development schedules • Team size • Amount of software to be developed • Hardware resources

  2. Estimates • Estimation techniques • Historical data • Stepwise Estimation • Counting product features • Functional point Analysis • Statistical application • Construction Cost Model COCOMO

  3. Estimates • Stepwise Estimation • Divides a large problem into numerous smaller problems. • The basic approach decomposes the project into well-defined components, then to iterate step-by-step until only small units remain, which can be easily estimated.

  4. Estimates • Stepwise Estimation • Project Decomposition • Off-the-shelf components • Full-experience components • Partial-experience components • New development

  5. Estimates • Estimating New Development • Prototype methods • Statistical methods

  6. Estimates Charter Approval Plan Approval Pre-Launch Launch Execute Size Estimates (Macro) Task-based Estimates Project Schedule +/- 35% range +/- 15% range +/- 10% range

  7. Estimates • Sizing techniques /models • Used to generate high-level effort, duration, and cost projections at a point when little is known about the project • Effort Distribution Models (EDM) • Deliverables-Based Estimates • Functional Point Estimating Models • Used for new development mostly

  8. Estimates • EDM

  9. Estimation (EDM)

  10. Estimation (EDM) • Converting effort hours into estimate durations. • Convert the estimated phase effort hours to work months by dividing the total hours by the average production hours per month per person. • 6.5 work-hours per day and 17.5 work-days per month • Determine the Optimal Full-time Equivalent (OFTE) team members for each phase by taking the square root of the work months computed above • Compute the estimated phase duration as • Phase duration = work months / OFTE • Develop a phase-base Gantt – depict the order of phase execution and appropriate phase overlaps and determine the duration estimate in terms of work-days, works weeks, or work-months. • Problems • Effort for user participation are usually not included • A full-time PM for a 7 FTE team member. That is one FTE will consume 15% of PM’s time.

  11. Estimation (EDM)

  12. Estimation (EDM) 0 month 10 months 20 months 30 months ED ID CUT SAT IN PI PM Effort 0 month 10 months 20 months 30 months ED ID CUT SAT IN PI

  13. Estimation (EDM) • When to use EDM • Medium to large projects • Projects based on a well defined lifecycle methodology • Major enhancements

  14. Size Estimate (Deliverables-based) • Deliverables-based estimates • Project description • Project phases • Project deliverables • List of deliverables by phases • Descriptions of deliverables • Resource assumptions • Number of resources, skill levels, percentage assignment • Deliverable estimates (effort, cost, duration) • Estimate project duration

  15. Size Estimate (Deliverables-based) • Deliverables Sample list • Approved vendor • Data conversion plan • Data definitions, data dictionary, etc • Development strategy • Disaster recovery plan • Program specifications • Regression test data • Risk analysis • Test plan, test data, etc • Usability testing • Training

  16. Size Estimate (Functional Point) • Functional Point Estimate • Used to size size system application from an end-user perspective. • From business or logical point of view • Independent of hardware, programming language, techniques, and tools used to developed the final system • A functional point is defined as one end-user business function. • The amount of functionalities in the project determines the project problems’ size.

  17. Size Estimate (Functional Point) • FPA Problems • Any functional point based estimate developed prior to the end of logical design are questionable • FPA does not often consider non-business features of the systems e.g. • Walk-throughs, inspections, team training, PM, etc • Converting FP estimates into project duration and schedules can produce dubious results and lead to poorly defined plans

  18. Size Estimate (COCOMO model) • COCOMO model • Level of personnel • PL = ƒ (∑EP,N, KSLOC) • Level of complexity • SEM = class of complexity * (KSLOC) • Project size • Reliability factor • Development environment

  19. Task-based Estimate • Task-based estimates • Task effort • The number of work hours needed to complete a given task. It depends on task complexity and skill of the person assigned to the task • Task Duration • Elapsed time needed to complete a given task. Measured in days, weeks, or months.

  20. Task-based Estimate • Getting a reliable task-based estimate • Ask the person to whom the task is assigned to estimate its duration • The PM estimates the duration of various tasks, keeping in mind the team skill, knowledge, interruptions, and productivity environment • The PM gathers a representative group of team members and they collectively estimate task effort and/or duration • Use historical data from a similar project.

More Related