⏰ ITELECTV3 - Lesson 5

Project Scheduling and Time Management

Week 5

Kristina Basa - Lecturer

Lesson Progress

📋 Project Scheduling and Time Management Overview

🎯 Learning Objectives

By the end of this lesson, you will master the essential skills for effective project scheduling and time management in IT projects.

  • Create and interpret Gantt charts
  • Estimate task durations accurately
  • Develop realistic project timelines
  • Identify critical paths and dependencies
  • Apply schedule optimization techniques

📊 Key Concepts

Gantt Charts

Visual representation of project schedules showing tasks, durations, and dependencies

Task Duration Estimation

Techniques for accurately predicting how long activities will take

Project Timelines

Comprehensive schedules that guide project execution and stakeholder communication

🏗️ Real-World Example: E-Commerce Platform Development

Let's explore how PMBOK Guide scheduling principles apply to a typical IT project:

Phase 1: Planning
  • • Requirements gathering (5 days)
  • • System architecture (4 days)
  • • Technology selection (3 days)
  • • Risk assessment (2 days)
Phase 2: Development
  • • Database design (6 days)
  • • Backend API development (15 days)
  • • Frontend development (12 days)
  • • Security implementation (4 days)
Phase 3: Testing & Deployment
  • • Unit testing (8 days)
  • • Integration testing (5 days)
  • • User acceptance testing (3 days)
  • • Deployment & go-live (3 days)
📚 PMBOK Guide Application:

This example demonstrates the PMBOK Guide's Schedule Management processes: Plan Schedule Management, Define Activities, Sequence Activities, Estimate Activity Durations, Develop Schedule, and Control Schedule.

📊 Project Scheduling Statistics

Research shows the critical importance of effective project scheduling in IT:

68%

IT projects with detailed schedules meet deadlines

45%

Reduction in project delays with visual scheduling

60%

Improvement in team coordination

📊 Gantt Charts: Visual Project Scheduling

🎯 What is a Gantt Chart?

A Gantt chart is a horizontal bar chart that illustrates a project schedule, showing the start and finish dates of project activities, their dependencies, and progress over time. According to the PMBOK Guide (7th Edition), Gantt charts are essential tools in the "Develop Schedule" process, providing visual representation of the project schedule model.

📚 PMBOK Guide: Schedule Management Knowledge Area

The PMBOK Guide defines six key processes for Project Schedule Management:

Planning Process Group:
  • • Plan Schedule Management
  • • Define Activities
  • • Sequence Activities
  • • Estimate Activity Durations
  • • Develop Schedule
Monitoring & Controlling:
  • • Control Schedule
  • • Monitor schedule performance
  • • Manage schedule changes
  • • Update schedule baseline

📋 Key Components

  • Task List: Activities from your work breakdown structure
  • Timeline: Horizontal axis showing dates or time periods
  • Bars: Visual representation of task duration
  • Dependencies: Arrows showing task relationships
  • Milestones: Key project checkpoints
  • Progress: Completion status indicators

✅ Benefits for IT Projects

  • • Clear visual timeline of entire project
  • • Easy identification of critical path
  • • Effective communication with stakeholders
  • • Progress tracking and reporting
  • • Resource allocation visualization
  • • Dependency management

📊 Interactive Gantt Chart: Web Application Development

Task Name
W1
W2
W3
W4
W5
W6
W7
W8
W9
W10
W11
W12
W13
W14
W15
W16
W17
W18
W19
W20
Planning
Design
Development
Testing
Milestone

🏗️ Interactive Gantt Chart Builder

Create your own Gantt chart for a mobile app development project:

Task Name
Duration (days)
Start Week
Depends On
Action

⭐ Gantt Chart Best Practices

✅ Do's

  • • Keep task names clear and specific
  • • Use consistent time units (days/weeks)
  • • Show technical dependencies clearly
  • • Include testing and deployment phases
  • • Update progress regularly
  • • Use color coding for different work types
  • • Include buffer time for technical risks

❌ Don'ts

  • • Don't make charts too detailed initially
  • • Avoid unrealistic development estimates
  • • Don't ignore technical dependencies
  • • Avoid cluttered visual presentation
  • • Don't forget integration and testing time
  • • Avoid static charts - keep them updated
  • • Don't skip code review and QA time

⏱️ Task Duration Estimation

🎯 Why Accurate Duration Estimation Matters in IT

Duration estimation is one of the most challenging aspects of IT project management, yet it's critical for project success. Software development has unique complexities that make estimation particularly difficult.

⚠️ Underestimation Risks

  • • Missed release deadlines
  • • Technical debt accumulation
  • • Developer burnout
  • • Quality compromises
  • • Client dissatisfaction

⚠️ Overestimation Risks

  • • Delayed product launch
  • • Reduced competitiveness
  • • Wasted development resources
  • • Feature creep tendency
  • • Opportunity costs

✅ Accurate Estimation Benefits

  • • Realistic sprint planning
  • • Better resource allocation
  • • Improved team morale
  • • Higher delivery success rates
  • • Stakeholder confidence

🔧 Duration Estimation Techniques for IT Projects

1️⃣ Three-Point Estimating (PERT) - PMBOK Guide Technique

The PMBOK Guide recommends three-point estimating to improve accuracy by considering uncertainty and risk. Uses optimistic, pessimistic, and most likely estimates to calculate expected duration.

PMBOK PERT Formula:
Expected Duration = (O + 4M + P) / 6
O = Optimistic, M = Most Likely, P = Pessimistic
Standard Deviation = (P - O) / 6
IT Example:
Database Migration:
Optimistic: 3 days
Most Likely: 7 days
Pessimistic: 14 days
Expected: (3 + 4×7 + 14) / 6 = 7.5 days
Std Dev: (14-3)/6 = 1.83 days

2️⃣ Analogous Estimating - PMBOK Guide Technique

PMBOK Guide defines analogous estimating as using historical data from similar projects to estimate current project durations. Most reliable when previous projects are similar in fact, not just appearance.

When to Use:
  • • Limited detailed information available
  • • Early project phases
  • • Similar technology stack
  • • Same team composition
IT Example:
Previous CRM System: 120 days
New E-commerce Platform:
• Similar complexity: +0%
• New technology: +20%
• Larger team: -10%
Estimate: 120 × 1.1 = 132 days

3️⃣ Parametric Estimating - PMBOK Guide Technique

PMBOK Guide describes parametric estimating as using statistical relationships between historical data and other variables to calculate estimates. Requires accurate historical data and scalable parameters.

Common IT Parameters:
  • • Lines of code per day
  • • Function points per hour
  • • Test cases per feature
  • • Pages per development day
IT Example:
Web Application:
• 25 web pages required
• Historical rate: 1.5 pages/day
• Complexity factor: 1.2
Estimate: (25 ÷ 1.5) × 1.2 = 20 days

4️⃣ Story Points (Agile Estimation)

Relative estimation technique using Fibonacci sequence for user stories.

Story Point Scale:
  • • 1-2: Simple tasks (bug fixes)
  • • 3-5: Medium complexity features
  • • 8-13: Complex features
  • • 21+: Epic (needs breakdown)
Example:
User Login: 3 points
Password Reset: 5 points
OAuth Integration: 13 points
Team Velocity: 25 points/sprint
Duration: 21 points ÷ 25 = 0.84 sprints

🧮 Interactive Duration Calculator

Practice different estimation techniques with this interactive calculator:

Three-Point Estimation
Story Points to Hours

🎯 Duration Estimation Challenge

Test your estimation skills with this realistic IT scenario:

📱 Scenario: E-Learning Platform - Video Streaming Module

Requirements:
  • • Video upload and processing
  • • Adaptive streaming (multiple qualities)
  • • Progress tracking and bookmarks
  • • Subtitle support
  • • Mobile-responsive player
  • • Analytics and reporting
Team & Constraints:
  • • 1 Senior Full-stack Developer
  • • 1 Junior Frontend Developer
  • • New to video streaming technology
  • • Must integrate with existing LMS
  • • High performance requirements
  • • Deadline: 8 weeks

📅 Project Timelines

🎯 What Makes an Effective IT Project Timeline?

A project timeline is more than just a list of dates - it's a strategic tool that guides development, coordinates teams, and manages stakeholder expectations in IT projects.

✅ Characteristics of Good IT Timelines

  • Realistic: Based on accurate technical estimates
  • Iterative: Supports agile development cycles
  • Flexible: Can accommodate scope changes
  • Testable: Includes adequate QA time
  • Deployable: Considers DevOps requirements
  • Measurable: Includes concrete deliverables

🎯 IT Timeline Components

  • Sprints/Iterations: Development cycles
  • Releases: Deployable software versions
  • Dependencies: Technical and resource constraints
  • Testing Phases: Unit, integration, system testing
  • Code Reviews: Quality assurance checkpoints
  • Deployment Windows: Go-live schedules

🛤️ Critical Path Method (CPM) - PMBOK Guide Approach

The PMBOK Guide defines the Critical Path Method (CPM) as a technique used to estimate the minimum project duration and determine the amount of scheduling flexibility. It identifies the longest sequence of dependent activities that determines the minimum project duration.

📚 PMBOK Guide CPM Key Concepts:

Forward Pass Calculation:
  • • Early Start (ES) = Latest EF of predecessors
  • • Early Finish (EF) = ES + Duration
  • • Determines earliest project completion
Backward Pass Calculation:
  • • Late Finish (LF) = Earliest LS of successors
  • • Late Start (LS) = LF - Duration
  • • Determines latest allowable start times

🔍 Critical Path in IT:

  • • Database design → Backend API → Frontend
  • • Architecture → Core modules → Integration
  • • Development → Testing → Deployment
  • • Any delay affects release date
  • • Focus area for resource allocation

⚡ Managing IT Critical Path:

  • • Assign senior developers to critical tasks
  • • Parallel development where possible
  • • Early integration and testing
  • • Continuous monitoring and updates
  • • Risk mitigation for critical activities

📅 Interactive Timeline Builder

Create a comprehensive project timeline for an IT system development:

Project Scope:
  • • Migrate from legacy system to modern web app
  • • Student enrollment and course management
  • • Grade tracking and transcript generation
  • • Integration with existing university systems
  • • Mobile-responsive design
Constraints:
  • • Must launch before fall semester
  • • Limited development team
  • • Data migration complexity
  • • High availability requirements
  • • Security and compliance needs

📊 Timeline Visualization Types

📈

High-Level Timeline

Executive and stakeholder communication

🏃‍♂️

Sprint Timeline

Development team coordination

🎯

Milestone Timeline

Key deliverables and checkpoints

🛠️ Practice Activities

🧠 Knowledge Check

1. Which estimation technique is most suitable for agile IT projects?

2. In IT projects, what typically represents the critical path?

📊 Practical Exercise: Create Your Project Schedule

Scenario: You're managing the development of a new online learning platform. Create a detailed project schedule.

Required Features:
  • • User registration and authentication
  • • Course catalog and enrollment
  • • Video streaming and progress tracking
  • • Assignment submission system
  • • Discussion forums
  • • Grade management
  • • Mobile responsive design
Team & Resources:
  • • 1 Project Manager
  • • 1 UI/UX Designer
  • • 2 Full-stack Developers
  • • 1 DevOps Engineer
  • • 1 QA Tester
  • • Timeline: 20 weeks

🎉 Congratulations!

You've mastered project scheduling and time management for IT projects! You can now create realistic schedules, estimate durations accurately, and manage project timelines effectively.

📊

Gantt Charts

Visual scheduling and dependency management for IT projects

⏱️

Duration Estimation

Accurate estimates using proven techniques

📅

Project Timelines

Critical path analysis and schedule optimization

Ready to move on to resource management and risk assessment?

📚 References and Further Reading

📖 Primary References

Core Reference

Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK Guide) (7th ed.). Project Management Institute.

Relevant Sections: Chapter 6 - Project Schedule Management, including processes for planning schedule management, defining activities, sequencing activities, estimating activity durations, developing schedules, and controlling schedules.

📚 Additional Academic References

Kerzner, H. (2022). Project Management: A Systems Approach to Planning, Scheduling, and Controlling (13th ed.). John Wiley & Sons.

Comprehensive coverage of project scheduling methodologies and time management techniques in various industries including IT.

Larson, E. W., & Gray, C. F. (2021). Project Management: The Managerial Process (8th ed.). McGraw-Hill Education.

Detailed exploration of project scheduling tools, techniques, and best practices with real-world case studies.

Schwalbe, K. (2019). Information Technology Project Management (9th ed.). Cengage Learning.

Specialized focus on IT project management including agile scheduling, software development lifecycles, and technology-specific estimation techniques.

Cohn, M. (2020). Agile Estimating and Planning (2nd ed.). Prentice Hall.

Comprehensive guide to agile estimation techniques including story points, planning poker, and velocity-based planning for IT projects.

🌐 Professional Standards and Guidelines

IEEE Standard 1058-1998: IEEE Standard for Software Project Management Plans

Provides guidelines for software project scheduling and time management in IT environments.

ISO 21500:2012: Guidance on Project Management

International standard providing guidance on project management concepts and processes, including time management.

Agile Alliance: Agile Project Management Guidelines

Best practices for agile project scheduling and iterative planning methodologies.

🔬 Research Articles and Case Studies

Jørgensen, M., & Shepperd, M. (2007). A systematic review of software development cost estimation studies. IEEE Transactions on Software Engineering, 33(1), 33-53.

Comprehensive analysis of software estimation accuracy and methodologies in IT projects.

Standish Group. (2020). CHAOS Report 2020: Beyond Infinity. The Standish Group International.

Annual report on IT project success rates and the impact of effective scheduling on project outcomes.

Boehm, B., et al. (2000). Software development cost estimation approaches: A survey. Annals of Software Engineering, 10(1-4), 177-205.

Foundational research on software estimation methodologies and their effectiveness in different project contexts.

🛠️ Tools and Software References

Project Scheduling Tools

  • • Microsoft Project (Enterprise scheduling)
  • • Primavera P6 (Complex project scheduling)
  • • Smartsheet (Collaborative scheduling)
  • • Monday.com (Team-based planning)
  • • Asana (Agile project management)

Agile Planning Tools

  • • Jira (Agile project management)
  • • Azure DevOps (Development lifecycle)
  • • Trello (Kanban-style planning)
  • • Rally (Enterprise agile planning)
  • • VersionOne (Scaled agile framework)