1 / 4

Discussions about Quick Plan

Discussions about Quick Plan. Part 1: Project Description and Deliverables A brief ( 2 – 3 sentences) summary of functional requirements to describe the end product and any associated characteristics (such as performance, security, ease of use, etc.). The deliverables you plan to generate

meris
Download Presentation

Discussions about Quick Plan

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. Discussions about Quick Plan • Part 1: Project Description and Deliverables • A brief ( 2 – 3 sentences) summary of functional requirements to describe the end product and any associated characteristics (such as performance, security, ease of use, etc.). • The deliverables you plan to generate • For internal consumptions (e.g. high level design, prototype, test cases, plan, etc.) • For external or client consumption (e.g. requirements spec., code, user guide, etc.) • Any constraints and assumptions about the project For this class ---- most of the people were close to this, except for some: a) no differentiation of internal and external deliverables b) final project report and presentations were not included ---- will take effort

  2. Discussions aboutQuick Plan • Part II: Cost Estimate (in the form of effort) • Past experience and association to other projects method: • Estimate the effort required for each of the deliverables and list the assumptions. • Consider & discuss any special situations that you are aware of for this project and include the necessary extra buffer needed. • Roll-up (sum up) all the efforts into one estimate. • Use some other estimation technique such as COCOMO I • Look at all the deliverables and the functional requirements and estimate the loc for each of the major functional areas. Roll-up the total loc estimates • Go through the 8 project characteristics and choose the project mode. • Go through the 15 cost drivers and come up with the adjustment factor. • Compute the COCOMO I effort estimate. • Consider the extra effort required for requirements activities • If you have some extra-ordinary deliverable such as user training, then estimate and add that extra effort For this class --- some common problems in using COCOMO I include : a) source of loc estimate not clear b) the choice of mode, or the cost drivers not well discussed

  3. Discussions aboutQuick Plan • Part II: Cost Estimate (in the form of effort) • If you choose to use Function Point: • Discuss and decide on the type of project (simple, average, complex). • Use the weights from the type of project for each of the 5 type of items considered. • Discuss and estimate how many of reach of the 5 items( inputs, outputs, queries, etc.) are needed for this project. • Multiply the number of each of the 5 estimates by the respective weights to come up with an unadjusted FP. • Then consider 14 factors and compute the complexity factor. This complexity factor will allow you to adjust the initial unadjusted FP. • Convert the function points to effort by dividing with a productivity factor such as 20 or 22 function points per person-month. (Explain why you chose to use an aggressive number or a more conservative productivity number.) For this class ---- very few people considered FP and for those who did: a) no clear reason given for choice of type of project (e.g. simple) b) did not use this to compare against COCOMO I estimate

  4. Discussions aboutQuick Plan • Part III: Time and Schedule • Before you start on the schedule do a little sanity test • Estimate the total amount of resources (in effort) left and compare against the estimated effort. • Depending on the result from the above step, you may • Consider how much parallelism may be needed and how to assign people • Go back and re-consider the effort estimate • Go back and reconsider the project content and the number of deliverables • Go on to the next step • Consider the pre-requisite/co-requisite conditions among the deliverables and tasks. • Lay the activities out in the pre-req/cor-req sequences. • Determine the relative amount of time by activities/deliverables via • If you have effort estimation for each deliverables, convert the estimate of effort for each deliverable to elapsed time by assigning # of people • If you have a single, high level effort estimate, then discuss and determine the ratio of efforts by deliverable or activity first. Then breakdown the effort estimates and consider the number of people you plan to assign to each of the activity before converting to an elapsed time. • For this class ---- the most common problem is the breakdown of schedule: • without any explanation • without considering or assuming the number of people to be assigned

More Related