Please enable JavaScript.
Coggle requires JavaScript to display documents.
Resource and Schedule estimating - Coggle Diagram
Resource and Schedule estimating
Resource planning.
The resource you plan its your own time, you used the method describe to to estimate the time the work will take and judge the accuracy
The software planning framework
For estimating the resources and producing a schedule you need to relate the time you spend on prior projects to the estimate sizes of the programs.
Productivity
For calculating productivity, the the unique conditions for each job must be considered and the quality of the resulting product, lumping all project activities in a global productivity number is a bad practice.
Planning development time
You have to use estimations for every LOC you have written, its you have to use your historical data used in previous programs LOCS. You also must consider if your historical data is enogh for a linear regretion among other considerations.
Estimating task time
In case you are facing a new task to wich you dont have an established planning process these are the decisions to proceed.
Ensure you have clear statement of the requirements.
If you dont have a defined process you should produce a simple process definition in any other case you need measures both to plan your work and record your result.
You need some quantitative historical basis judging the size of the job, even if you dont have it you can identify some similarity between jobs and judge how long they took
You must have an explicit size measure, this measure must have a correlation, must have historical data on at least one similar historical case
Determine maximum and minimum times the job will likely require.
Combining multiple estimates
The prediction intervals used for this procedure are Lower prediction interval, upper prediction interval, standard deviation, variance and estimated hours.
The prediction interval for combined resources estimates
if you have calculated the prediction interval for each case and every one have been generated the same way you can treat them as standard deviation and combined them.
Earned Value Tracking
Is a way to evaluate project progress, it stablishes a relative value for every task and credits that value when you complete the task.
Establishing the earned value
Provides a common value scale for every task regardless of the type of the work involved, total hours are estimated and every task is given an earned value based on its estimated percentage.
Alerting management to changes
By tracking your plans, you can see where you are, if you are ahead you may want to provide early warning of the improvement, if you have a delay you can warm management and possibly even get some help
Earned value and motivation
Once you established an earned value tracking you will tend to avoid starting task that do not earned credit if you find you have partially completed something no longer necessary you can drop it from your plan.
Using multiple regression
Enables you to estimate the relative contributions of the work on the new, reused and modified code in the total development hours
Multiple regression parameters
The estimates for the B parameters are obtain by solving the simultaneous equations, these equations are solved using standard algebraic techniquesfor simultaneous linear equations.
Multiple regression prediction interval
This interval is calculated estimates of the variance terms, a larger value of O indicates a poorer linear regression fit to the actual data
Schedule estimating
Requires a detailed estimate of the hours needed to do the total job, then alocate this hours project phases.
Direct project time
The purpouse is to recognize how much time you spend on casual interruptions and other diversions, you will better understand what percentage of your normal day is really available for the things you plan to do.
The unplanned time cushion
You will be able to meet many of your schedules, you can defer all your other work and devote from 100% to 150% of your normal work time to the priority task.
Making the schedule
Resource estimate is the total estimated hours, estimate for the hours each project phase will likely require, estimate how much productive time you can expect to spend on this project, you must account for the fact that some task have prerequistes.
Estimating Accuracy
Measure and track your planning process, you need to establish measures to wich the plan matches the actual result.
Small task estimating errors
Most of the task are subject to considerable variations and also so routine that you can predict the time required to do them, the need is to understand as many of the causes of this variations as you can to attemot to reduce them.
Composite estimates
if you estimate the job in many parts even if the estimate has a random error the total will be much accurate, if your productivity is gradually changing you migth to adjust your plans to reflect your most recent experiences
Over compensation
If you dont make estimations consistenly, you may not be using appropiate historical data, closely observe your work and understad the factors that causes some task to take longer
Estimating judgement
The regression calculations indicate a relative low effect of size on development time, when the regression parameters have any sort of problem you should use simple LOC per hour.