After I had reviewed how Monte Carlo simulation could help a team to understand the distribution of potential schedule or cost outcomes for a release or project, one of the learners in the class I was teaching pointed out that while such techniques can be helpful, they are only as good as the inputs provided.
When Monte Carlo is used in project contexts, these inputs are usually expected duration or cost ranges for the activities. If those ranges are inaccurate the resulting outputs will be useless and all it takes is one poorly estimated activity to skew the
source https://coo.systems/a-tool-is-only-as-good-as-the-inputs-and-assumptions-for-its-usage/https://lewissimpson932.blogspot.com/feeds/2848034844913546211/comments/default
