During the initial stages of the project, what do activity attributes include?

Question

Options

• AActivity name, dependencies, assumptions
• BActivity ID, WBS ID, activity name
• CActivity ID, assumptions, constraints
• DActivity name, WBS ID, activity description

• A
  12% (6)
• B
  78% (39)
• C
  6% (3)
• D
  4% (2)

Explanation

During the initial stages of a project, activity attributes are minimal and consist of the most basic identifiers: Activity ID, WBS ID, and activity name - just enough to uniquely identify and locate each activity within the project structure. As the project matures, attributes expand to include things like dependencies, constraints, and resource requirements, but those come later.

• A is wrong because dependencies and assumptions are developed after the initial stage, once activities are better defined.
• C is wrong because assumptions and constraints are also later-stage additions; the Activity ID alone doesn't tell you where the activity lives in the project hierarchy.
• D is wrong because the activity description is typically added in later planning stages, not at the very beginning - and WBS ID without Activity ID is an incomplete identifier.

Memory tip: Think of the initial stage as the "birth certificate" moment - you only need the bare minimum ID info (Activity ID + WBS ID + name) to register the activity's existence, just like a birth certificate captures identity before personality develops.

No community discussion yet for this question.