Creating Project Plans: WBS and Gantt Charts

This section reveals the actual losses incurred by both clients and contractors due to inadequate planning, and the structural problems underlying these issues.

At web development company A, a corporate website renewal project initially scheduled for 3 months extended to 6 months, with the budget expanding to 150%. The client representative from company B was puzzled, asking "Why is this so delayed?" while A's director was overwhelmed by "unexpected tasks continuously emerging."

Examining this project's plan revealed that the WBS (Work Breakdown Structure) contained only major items like "requirements definition, design, implementation, testing," with unclear specific work content for each phase. The Gantt chart merely connected major milestones with lines, without organizing work dependencies and sequences.

Contractors create rough plans with the mindset of "just getting started is enough," while clients neglect detailed verification, thinking "leaving it to experts should be safe." This structural problem leads to miscommunication and increased workload during project execution.

According to Project Management Institute (PMI) research, the top three failure factors for IT-related projects are "unclear requirements (39%)," "unrealistic expectations (35%)," and "inadequate project planning (31%)" - all stemming from planning phase deficiencies.

From the contractor's perspective, vague project plans provide weak justification for work estimates, making it difficult to request additional work later. From the client's perspective, progress becomes hard to track, making budget and schedule management challenging.

The most serious problem for both parties is that success criteria and completion quality remain unclear, creating high potential for disputes during completion assessment. This results in what should be a collaborative relationship between clients and contractors becoming adversarial.

This section structurally analyzes the organizational factors that cause planning tools to become formalized and the reasons they aren't utilized in practice.

The reason WBS and Gantt charts become "create and forget" documents in many organizations stems from three fundamental problems.

First is the lack of planning skills. Many practitioners use these tools through trial and error without systematic learning opportunities for WBS creation or Gantt chart development. Particularly in small to medium-sized production companies and freelance environments, there are few professionals with specialized project management education, leading to experience-based planning becoming the norm.

Second is unclear purpose and positioning of project plans. In many cases, the goal becomes "maintaining appearances" using project plan templates, without considering integration with actual project operations. Plans fail to function as baselines for progress and quality management, remaining merely documentation tasks.

Third is the recognition gap between clients and contractors. Contractors think "detailed planning is meaningless because of frequent changes," while clients maintain distance, thinking "it's too technical to understand." This mutual lack of understanding removes incentives for improving planning accuracy.

From an organizational system perspective, improved planning accuracy isn't evaluated. In many companies, project success is judged by final deadline adherence and quality, with planning accuracy itself not being an evaluation target. This creates environments where starting actual work early is valued more than spending time on planning.

Additionally, tool selection presents problems. Even with sophisticated project management tools, teams often revert to simplified Excel or PowerPoint versions when they can't master the functionality. Mismatches between tool capabilities and organizational operational abilities accelerate the formalization of project plans.

Solving these problems requires not just learning tool usage, but reviewing the entire collaborative process centered on project plans.

This section presents specific creation processes from WBS construction through Gantt chart development using progressive elaboration, applicable to actual projects.

Systematic WBS Construction Procedures

Effective WBS creation follows a "top-down approach" with progressive elaboration from higher levels.

Level 1 (Overall Project): Define the project name and final deliverables. For example, with "E-commerce Site Renewal," the final deliverable becomes "construction and operational launch of new e-commerce site."

Level 2 (Major Phases): Divide the entire project into 4-7 major phases. For e-commerce projects, these might include "planning & requirements definition," "design & prototyping," "implementation & development," "testing & verification," and "release & operational preparation."

Level 3 (Work Packages): Break down each phase into units where specific personnel can be assigned. "Planning & requirements definition" might include "current site analysis," "competitive analysis," "user interviews," "requirements specification creation," and "client confirmation & coordination."

Level 4 (Work Items): Subdivide each work package into specific tasks completable within 1-5 days. "Current site analysis" becomes "access analytics data acquisition," "user behavior flow analysis," "technical specification confirmation," and "issue organization & documentation."

The key is clearly defining "deliverables" at each level. Rather than simply listing work content, specifically define "what to create" and "what to decide." This clarifies completion criteria and facilitates quality management.

Practical Points for Gantt Chart Construction

Once the WBS is complete, translate the execution plan into a chronological Gantt chart. Effective Gantt chart creation follows these procedures:

Organizing Dependencies: Classify relationships between work items using four patterns: "FS (Finish to Start)," "SS (Start to Start)," "FF (Finish to Finish)," and "SF (Start to Finish)." While most relationships are FS (next work starts after previous work completes), apply SS relationships for parallel work to reduce project duration.

Work Estimation and Duration Calculation: When estimating time required for each work item, consider worker skill levels and project-specific constraints. For example, with new team members, set 20-30% buffers for learning periods.

Critical Path Identification: Identify the longest path (critical path) that determines overall project duration, paying special attention to work items on this path. Delays on the critical path directly cause project delays, so allocate resources preferentially.

Resource Leveling: Identify periods when the same person has concentrated work assignments, adjusting resource allocation through work advancement, postponement, or transfer to other members.

Client-Contractor Consensus Building Process

To make created project plans effective, incorporate consensus-building processes between clients and contractors.

During project plan reviews, first confirm whether WBS work breakdown is appropriate. Clients should verify "are there unexpected work items?" and "do deliverables for each task meet expectations?" while contractors confirm "are work volumes and schedules achievable?" and "can necessary resources and information be obtained?"

Particularly important is prior agreement on change management processes. Clearly document response procedures, impact range evaluation methods, and approval processes for requirement changes or additional work during project execution.

This section identifies risk points that even experienced practitioners tend to overlook, along with specific avoidance strategies for each.

Typical WBS Creation Pitfalls

Excessive Detail: Over-decomposing work can create situations where management costs exceed work costs. Be particularly cautious when numerous "sub-daily work items" appear. As a guideline, set minimum units at 0.5-1 day, consolidating smaller tasks into higher levels.

Vague Deliverables: Work items ending with verbs like "consider," "confirm," or "coordinate" make completion assessment difficult. Always specify concrete deliverables or state changes like "create XX," "decide XX," or "reach agreement on XX."

Overlooking Skill-Dependent Work: Estimating specialized work requiring specific skills or knowledge with general work hours leads to significant delays. For example, security audits or accessibility compliance requiring high specialization should allow 2-3 times normal implementation work hours.

Underestimating External Dependencies: Elements outside team control - client information provision, external system integration, third-party approvals - are often underestimated. Set buffers of twice normal duration for such work and prepare alternatives.

Gantt Chart Construction Considerations

Optimistic Scheduling: Setting schedules on the premise that "everything proceeds smoothly" guarantees delays. Conduct performance-based work estimates and add the following buffers: 30% for new technology elements, 25% for extensive external integration, 20% for team composition changes as standards.

Overlooking Resource Conflicts: When the same person is assigned multiple simultaneous tasks, actual sequential execution causes significant delays. For key persons or specialized skill holders, plan at 80% or lower utilization rates.

Ignoring Progressive Elaboration: Attempting to finalize all phase details at project start necessitates major plan changes in later phases. Initially set later phases with rough estimates including buffers, then progressively elaborate as the project advances.

Consensus Building Process Pitfalls

Insufficient Technical Premise Sharing: Technical constraints or prerequisites that contractors assume are "naturally understood" often aren't properly communicated to clients. Always document "prerequisites," "constraints," and "risk factors" in project plans, explaining with concrete examples.

Vague Change Management Rules: Ambiguous agreements like "minor changes incur no additional costs" later cause troubles. Define change classification criteria (minor, moderate, major), respective response processes, and numerical impact degrees on costs and schedules.

Inadequate Decision-Maker Involvement: When actual decision-makers don't participate in project plan reviews before approval, major policy changes may occur later. Before plan approval, confirm all client stakeholders understand and agree to the content.

This section presents specific operational methods for continuously utilizing created project plans and improving project management capabilities.

Project Plan Utilization for Contractors

Weekly Progress Review Systematization: Conduct progress checks on the same day and time weekly, quantitatively tracking variances from plans. For delayed work items, analyze causes and formulate countermeasures within 48 hours. Through this process, accumulate company performance work hour databases.

Risk Management Visualization: Regularly review occurrence probability and impact levels for risk factors identified during plan creation. When new risks emerge, analyze impact ranges and develop response measures, sharing information with clients. Record risk response performance for future planning accuracy improvement.

Change Management Process Operation: Establish standard processes from impact range analysis to approval for requirement changes or additional work during project execution. Complete impact analysis within 72 hours of change request receipt, creating materials showing quantitative effects on work hours, schedules, and quality.

Deliverable Quality Pre-Checking: Implement internal quality verification before delivering deliverables at each milestone. Based on quality standards for deliverables defined in the WBS, create checklists and conduct third-party reviews.

Project Plan Management for Clients

Decision Process Transparency: Clarify decision-makers, decision deadlines, and necessary information for project-related decisions, sharing with contractors. For items requiring external approval, communicate standard periods from application to approval to contractors for project plan reflection.

Information Provision Schedule Confirmation: Document information and material provision timing needed by contractors in project plans, establishing internal preparation processes. Quantitatively assess impacts of delayed information provision on overall projects, prioritizing preparation accordingly.

Quality Standards Pre-Clarification: Document quality expectations for deliverables as concrete standards, incorporating into project plans. Rather than abstract requirements like "high quality," set standards with measurable indicators (performance, accessibility, browser support scope, etc.).

Change Request Impact Recognition: When requesting requirement changes or additional work, always confirm impacts on work hours, schedules, and budgets before formal submission. Rather than intuitive judgments like "it's just a small change," make decisions after receiving impact analysis from contractors.

Continuous Improvement Framework

After project completion, analyze plan-versus-actual variances to improve next project planning accuracy.

Quantitative Planning Accuracy Evaluation: Numerically evaluate work estimate accuracy, milestone achievement rates, and quality goal achievement levels, identifying improvement points. Particularly for estimation accuracy, set target achievement rates within ±10%.

Best Practice Documentation: Record successful project planning processes, effective management methods, and useful communication approaches, sharing within organizations. Emphasize learning from failure cases, not just success stories.

Template and Checklist Continuous Improvement: Regularly update project plan templates and work checklists based on performance. Reflect new technology elements, changing market environments, and organizational structure changes to maintain practical usability.

By utilizing project plans as strategic tools - contractors for improving proposal and execution capabilities, clients for investment effectiveness and quality assurance - both parties can achieve improved project success rates and build continuous partnerships.