What is the correct sequence of steps involved in scheduling a threat intelligence program? 1. Review the project charter 2. Identify all deliverables 3. Identify the sequence of activities 4…

Question

Options

• A1-->9-->2-->8-->3-->7-->4-->6-->5
• B3-->4-->5-->2-->1-->9-->8-->7-->6
• C1-->2-->3-->4-->5-->6-->9-->8-->7
• D1-->2-->3-->4-->5-->6-->7-->8-->9

• A
  71% (29)
• B
  17% (7)
• C
  7% (3)
• D
  5% (2)

Explanation

Option A reflects the standard project management scheduling methodology: you begin by reviewing the project charter to establish scope and objectives, then build a WBS to decompose the work, identify deliverables, define specific activities, sequence them, estimate resources, identify dependencies, estimate durations, and finally produce the complete schedule. This logical flow ensures each step informs the next - you cannot sequence activities you haven't defined, and you cannot build a realistic schedule without knowing durations and dependencies.

Option B is wrong because it starts with sequencing activities (step 3) before the project charter is even reviewed - you cannot order work you haven't defined or authorized. Option C is wrong because it places "develop the final schedule" (5) in the middle of the process, before resources (7), activity definitions (8), and the WBS (9) are complete. Option D simply follows the steps in their listed numerical order (1 through 9), which is a trap - the numbering in the question is intentionally scrambled and does not reflect execution order.

Memory tip: Think of it as "Plan → Break Down → Detail → Sequence → Estimate → Finalize" - Charter and WBS come first (foundation), then deliverables and activity definition (discovery), then sequencing and resourcing (logistics), then duration estimation (precision), and finally the schedule (output). The WBS always precedes deliverable identification, which is the key non-obvious ordering that rules out C and D.

No community discussion yet for this question.