Exam PMP topic 1 question 628 discussion

This is D

D. Three-point estimating.

Three-point estimating involves considering optimistic, pessimistic, and most likely estimates to account for uncertainty. While it's commonly associated with activity duration estimates, it can also be applied to other project aspects, including software development time. In this case, the lack of specific experience might warrant a more probabilistic approach to estimation. Analogous Estimating: It relies on historical data from similar projects to make estimates for the current project. Parametric Estimating: This involves using a statistical relationship between historical data and other variables to calculate an estimate. Suitable when a measurable parameter (like cost per unit) can be identified and applied to the current project. Planning Poker: It is a consensus-based technique used in Agile projects where team members collectively estimate the effort required for user stories.

B. Parametric estimating Parametric estimating involves using statistical relationships between historical data and other variables to calculate an estimate for the work. Since the software developers are new to the company and have no previous experience with a similar application, parametric estimating can be a suitable technique. It relies on parameters such as cost per unit, lines of code, or other relevant metrics to estimate the time required for the project. Analogous estimating relies on historical data from similar projects, which may not be available in this case. Planning poker and three-point estimating are more suitable for situations where team members have some knowledge or experience that can contribute to the estimation process, which may not be the case for new team members working on a new type of project.

D. Three-point estimating Reasoning: Without prior similar projects to draw upon (as would be used in Analogous estimating), Three-point estimating would be a suitable method. It allows the developers to consider optimistic, pessimistic, and most likely scenarios for each task, which can be especially useful when there's uncertainty or limited prior experience with similar projects. This technique provides a range for estimation, taking into account potential uncertainties and risks.

Analogous - Limited amount of info. Less cost and time to make but less accurate. Best to use with people with similar experience. PERT Three-point - many unknown Parametric - Needs details but super accurate. It's PERT. Details from PMBOK

Analogous estimating is a top-down estimation technique that relies on historical data or expert judgment from similar projects Parametric estimating uses statistical relationships between variables to calculate an estimate for the projec Planning Poker: Planning poker is an estimation technique commonly used in agile methodologies like Scrum. It involves team members providing their estimates for user stories or tasks by playing cards with numbers representing the effort required Three-point estimating is a technique that considers the uncertainty and variability of estimates.

A. Analogous estimating

Planning Poker allows the entire team, including the new software developers, to provide their individual estimates for tasks or user stories. It fosters collaboration and discussion among team members, which can be beneficial when there is a lack of experience with a specific task or project. The technique leverages the collective expertise and judgment of the team to arrive at a consensus estimate. It is particularly useful in Agile projects and when there is limited historical data available. On the other hand, the Three-Point Estimating technique might require more historical data or experience to provide reliable optimistic, pessimistic, and most likely estimates. If the team lacks experience and relevant data, the Three-Point Estimating technique might not be as effective in this particular scenario.

Since the developers have had similar experience, they should use 3 points estimating technique

the key of the question is they have never developed a similar application. Analogous and parametric estimate based on historical data, planning poker is to prioritize user story. the answer is D, Pert estimating

Analogous estimating is a technique that uses information from a similar past project in order to estimate the cost and duration of a planned project. This approach is often used when there is limited data available for a project, making it difficult to generate accurate estimates. Just because the developers are new to the company and have never worked on software development as such, doesn't mean that the company didn't do past projects that are similar and can provide an Analogous estimate.

Planning Poker is an estimation technique for Agile to determine the development effort.

Three points estimating (option D) is correct, because analogous estimating (option A) is also based on historical data from similar projects, but since the developers have no prior experience with such projects, this technique may not be applicable.

Given that the software developers are new to the company and have no prior experience with the project, the most appropriate estimation technique would be analogous estimating. This technique involves using similar historical data from previous projects to estimate the time required for the new project. This technique is useful when there is limited information available about the current project, making it difficult to use more detailed estimation techniques. Therefore, option A (Analogous estimating) would be the best estimation technique to recommend in this scenario.

A. Analogous estimating. Analogous estimating is the most appropriate estimation technique to use when the software developers are new to the company and have never developed a similar application. Analogous estimating uses historical data from similar projects to estimate the duration, cost, or effort required for a current project. Since the developers are new to the company and have no prior experience with similar applications, there is no data available to use for parametric estimating or three-point estimating.

If the developers don't have any clue. It is better to use historical info for the estimates. I think the answer will be "A"