Hello Everyone, I am Stephaneva,it's my first post. I have connected to this forum to add here own views about project time estimation.
ok, please provide your views
My ASQ Certified Software Quality Engineer (CSQE) Certification training batch is starting on July 11 2016. Details and 6 VERIFIABLE RECOMMENDATIONS for my training at www.facebook.com/PickTechnologies
Maintain an ongoing "actual hours" database of the recorded time spent on each aspect of your projects. Use the data to help estimate future projects and identify the historically accurate buffer time needed to realistically perform the work. Create and use planning documents, such as specifications and project plans. Duration of a project's terminal element is the number of calendar periods it takes from the time the execution of element starts to the moment it is completed.
Duration should not be confused with work. E.g. it takes three days for a snail-mail letter to arrive at point B from point A, whereas the work put into mailing it may be 0.5 hours.
Strictly speaking, the phrase Duration of terminal element X is 5 days is incomplete. It fails to specify the following:
the probability with which the completion is expected in the time allotted (since any estimate is only a prediction about the uncertain future, see critical chain)
the resources to be used (sometimes using more resources or different resources speeds things up)
the assumptions which were made
the author of the estimation
the date the estimate was made
the work schedule of the resources
2 Main ways.. By decomposition, or by Analog
Decomposition, you look at the big picture, break it down into smaller chucks, then make estimates on the smaller chunks, and add them up. Bottom up is great for better accuracy and if you need to do detailed resource planning.
EX: To make this new iOS app, we'll need a backend with an API and a Database, a iOS app which has a communications piece and a UI..
Analog, you look at similar projects, then make adjustments based on perceived differences. Top down is great for people like consultants and management that need to make quick snap decisions.
Ex: This new app is similar to what Uber was 1 year ago, if Uber 1 year ago took a team of 20 to build in 9 months, but we only have 10 engineers.. Then...
Last edited by dlai; 05-05-2016 at 09:27 AM.
Estimation of Project/Task is important thing for whole team as every project has due date and with that due date , QUALITY cannot be compromise also within Budget.If Time is reduced then Quality can Impact. If Time is increased then COST can impact.In 1 way or other time is directly proportional to Quality and Cost.
Now we come to estimation:
1. Estimation of time is done at every step of Project.
2.Initially, High level estimation that in which iteration/Sprint we will be providing which modules of project.
3. Then at Iteration level , which module will be done based on Priority.
4. After that in how much time we need to finish this Module.
5. Then estimating that with given resources and time line can we finish module on time If not then again we need to estimate if we can add resource/time or we can move some modules to another iteration.
Conclusion-It is all estimation and without good estimation , we can never get Quality.