Why is 'starting with dates' instead of building a WBS first considered risky?

Question

BlackTom AI · Accepted Answer

When you start with dates rather than a Work Breakdown Structure (WBS), the project planning dynamics shift in a few problematic ways. 
Option 1: 'It delays execution start' — While early dates might push activities, the core issue isn’t just delaying work; it’s that schedules built from dates can prematurely anchor work without understanding dependencies, making subsequent adjustments disruptive. This statement touches on a consequence, but doesn’t address the root cause about dependencies and logic being obscured. 
Option 2: 'It hides real dependencies and logic under arbitrary deadlines' — This is the key flaw with dating early. By anchoring to dates first, you bypass the natural sequencing of tasks and the logical relationships between them, so dependencies (which tasks must precede others) and critical paths are obscured or misrepresented. This leads to brittle plans that crumble when reality doesn’t align with the presets. 
Option 3: 'Dates reduce accountability for tasks' — Deadlines can influence accountability, but this option oversimplifies accountability and incorrectly implies that dates themselves inherently lessen responsibility. In practice, it’s not the dates themselves that reduce accountability, but the way planning is structured around them rather than around a clear task hierarchy. 
Option 4: 'It inflates cost estimates by default' — While schedules can impact cost estimates, the primary risk of starting with dates is the loss of accurate logical sequencing and dependency visibility. Cost inflation is more of a downstream effect and not the central issue described by this approach. 
Overall, the core risk lies in the misalignment between early dates and the true work structure: without a WBS to reveal dependencies and logical task flow, deadlines can mask how tasks truly relate, making the plan fragile. This makes option 2 the most precise and explanatory critique among the choices.

BU.300.620.51.FA25 Managing Complex Projects – Final Exam (35Q)

Why is 'starting with dates' instead of building a WBS first considered risky?

View Explanation

Log in for full answers

Similar Questions

An IT project is established to develop a new internal reporting tool. Once the tool is successfully built, tested, and implemented, the project team is disbanded. This scenario illustrates which fundamental property of a project as defined in the source?

Which statement BEST captures the overall goal of managing complex projects?

Mitigation for aggressive deadlines:

Question at position 13 Specialized, narrower skills are required for Project processes.TrueFalse

Question at position 3 In Project processes many different skills need to be coordinated.TrueFalse

A project Blank ______ is an individual who is an expert in project planning and management, defines and develops the project plan, and tracks the plan to ensure the project is completed on time and on budget.

More Practical Tools for Students Powered by AI Study Helper

Homework AI Solver

Stylized AI Paper Writer

Plagiarism Checker Assistant

Citation AI Academic Writing Tool

In-Class Translation Assistant

AI Note Generator

AI Quiz Answers

Past Exam Questions from University Test Bank

Smart Practice Assistant

Adaptive Practice

Making Your Study Simpler