Explore chapters and articles related to this topic
Evolve II
Published in Günther Ruhe, Product Release Planning, 2010
The critical task of providing reliable effort estimates is addressed in Step 6. For that purpose, collective knowledge and experience can be utilized by asking multiple experts for their opinion. For effort estimation, candidate stakeholders would be developers, domain experts or project managers. Instead of a single point-wise estimate, three-point estimation can be applied. This is defined as the optimistic, most likely, and pessimistic estimates. For feature f(n) and stakeholder stake(p), these estimates are denoted by opt_effort(n,p), likely_effort(n,p), and pess_ effort(n,p), respectively. Their integration into an overall effort estimate effort(n,p) per feature is done following the Program Evaluation and Review Technique (PERT) [Elmaghraby ‘77]:
Towards a human factors and ergonomics integration framework in the early product design phase: Function-Task-Behaviour
Published in International Journal of Production Research, 2018
Xiaoguang Sun, Rémy Houssin, Jean Renaud, Mickaël Gardoni
Considering the initial duration of each task is only an estimated value, on the purpose of increasing the system’s flexibility, planning a reasonable time schedule of the correlative sub-functions, and eliminating the conflicts of sub-functions within the system, the Programme Evaluation and Review Technique (PERT) was applied to analyse and represent the tasks involved in completing a given project. Classical PERT uses the three-point estimation and beta distribution for the duration of the task. Then it was questioned and criticised by many researches, and several new methods have been brought in, which produce an estimated value that is more closely to the real value of duration and easier to calculate from mathematical viewpoint (Lootsma 1989; Shipley, de Korvin, and Omer 1997; Hajdu and Bokor 2016).