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

Slides:



Advertisements
Similar presentations
Effort Estimation and Scheduling
Advertisements

Software Quality Assurance Plan
MapleLeaf, LLC SDLC Methodology. MapleLeaf, LLC, has established standard phases and processes in regards to project management methodologies for planning.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Project What is a project A temporary endeavor undertaken to create a unique product, service or result.
Introduction to Project Management Chapter 6 Managing Project Scheduling Information Systems Project Management: A Process and Team Approach, 1e Fuller/Valacich/George.
Project Management.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Degree and Graduation Seminar Scope Management
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
Estimates Uncertainties Unknown  Project development costs  Project development schedules  Team size  Amount of software to be developed  Hardware.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
1 COST ESTIMATION Basics, COCOMO, FP. 2 What is estimated? TIME MONEY TIME: –duration, chronological weeks, months, years –effort, person-month (man-month)
Fundamentals of Information Systems, Second Edition
Project Management Session 7
SOFTWARE PROJECT MANAGEMENT AND COST ESTIMATION © University of LiverpoolCOMP 319slide 1.
Software Test Plan Why do you need a test plan? –Provides a road map –Provides a feasibility check of: Resources/Cost Schedule Goal What is a test plan?
Planning. SDLC Planning Analysis Design Implementation.
Project Management and Scheduling
1 Project Planning CIS 375 Bruce R. Maxim UM-Dearborn.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
Software Testing Lifecycle Practice
Describing Methodologies PART II Rapid Application Development*
CIS 499 Senior Seminar IT project management. Exercise. Write a testable problem statement in subject verb format. Who? Are the people going to use this.
After Lesson 6 next is Lesson 13 to fit topic on Software Development SOFTWARE PROJECT MANAGEMENT.
Estimation Why estimate? What to estimate? When to estimate?
Chapter 6 : Software Metrics
CEN th Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Software Project Planning.
SDLC: System Development Life Cycle Dr. Dania Bilal IS 582 Spring 2007.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Software Estimation How hard can it be? Peter R Hill.
Software cost estimation Predicting the resources required for a software development process 1.
Week 2 Seminar: Project Scope Management
Lecture 6. Review of Lecture 5 Company strategic planning: mission and objective statements and competitive strategy. Planning Methods: Top-down, Bottom-up.
1 Chapter 5 Software Project Planning. 2 Software Project Planning The overall goal of project planning is to establish a pragmatic strategy for controlling,
Quality Software Project Management Software Size and Reuse Estimating.
Systems Analysis and Design in a Changing World, Fourth Edition
Fundamentals of Information Systems, Second Edition 1 Systems Development.
Chapter 3: Software Project Management Metrics
©Ian Sommerville 2000Software Engineering, 7th edition. Chapter 26Slide 1 Software cost estimation l Predicting the resources required for a software development.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
Software Project Estimation IMRAN ASHRAF
Function Points Synthetic measure of program size used to estimate size early in the project Easier (than lines of code) to calculate from requirements.
Estimating “Size” of Software There are many ways to estimate the volume or size of software. ( understanding requirements is key to this activity ) –We.
Effort Estimation In WBS,one can estimate effort (micro-level) but needed to know: –Size of the deliverable –Productivity of resource in producing that.
Information Systems System Analysis 421 Chapter 3 Managing the Information Systems Project.
Cis339 Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design Fifth Edition.
Project, People, Processes and Products Project management skills – schedule, monitoring, risk management, … People management skills – delegation, mentoring,
Software Engineering (CSI 321) Project Planning & Estimation 1.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 2 Managing the Information Systems Project 2.1.
Rating Very Very Extra Cost Drivers Low Low Nominal High High High Product Attributes Required software reliability Database size.
SCOPE DEFINITION,VERIFICATION AND CONTROL Ashima Wadhwa.
Software Project Management
Project Planning Goal 1 - Estimates are documented for use in tracking and planning project. Goal 2 - Project Activities and commitments planned and documented.
SOFTWARE PROJECT MANAGEMENT
Information Technology Project Management, Seventh Edition.
Software project management 3rd Umer khalid Lecturer University of Lahore Sargodha campus.
بشرا رجائی برآورد هزینه نرم افزار.
Project Estimation.
Methodologies and Algorithms
Chapter 3 Managing the Information Systems Project
Chapter 3 Managing the Information Systems Project
Constructive Cost Model
Software Testing Lifecycle Practice
Chapter 2 Managing the Information Systems Project
Chapter 2: Building a System
Chapter 3 Managing the Information Systems Project
Presentation transcript:

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 Statistical application Construction Cost Model COCOMO

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.

Estimates Stepwise Estimation Project Decomposition  Off-the-shelf components  Full-experience components  Partial-experience components  New development

Estimates Estimating New Development Prototype methods Statistical methods

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

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

Estimates EDM

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.

Estimation (EDM)

0 month10 months20 months30 months ED ID CUT SAT IN PI 0 month10 months20 months30 months ED ID CUT SAT IN PI PM Effort

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

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

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

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.

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

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

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.

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.