The project charter usually will include assumptions about the risks the project will face. These assumptions may or may not be correct. Once the risks are identified, what do you think would be the way to verify or refute these assumptions?
Other than brainstorming what other techniques or documents could be used to identify risks?
A work breakdown structure (WBS) provides the backbone of the project, giving it a consistent and visible framework. The WBS offers uniformity in definition and consistency of approach. Some might consider that uniformity a benefit; others might see it as restricting creativity. What do you think?
What types of projects are more inclined to experience scope creep?