Team Schedule

Definition

A team schedule is the management work product that documents the schedule for a single team during an endeavor.

Objectives

The typical objectives of a team schedule are to:

• Document the planned dates associated with a single team’s tasks.

Benefits

The typical benefits of a team schedule include:

• Enabling inter-team schedule coordination.
• Providing input to component schedules.
• Providing input to the master schedule.
• Minimizing project risk due to poor scheduling.

Contents

A team schedule typically has the following contents:

• Planned and actual start date of each team task.
• Planned and actual intermediate date of each team task milestone.
• Planned and actual completion date of each team task.

Stakeholders

A team schedule typically has the following stakeholders:

• Producers:
  • A team on the endeavor
• Evaluators:
  • Program Manager or
  • Project Manager
  • Scheduler
  • Technical Leader
• Approvers:
  • Technical Leader
• Maintainers:
  • The team.
• Users:
  • Program Management Team
  • Project Management Team
  • The team.

Phases

A team schedule is typically produced and maintained during the following phases:

• Business Strategy: Completed and Maintained
• Business Optimization: Completed and Maintained
• Initiation: Completed and Maintained
• Construction: Completed and Maintained
• Delivery: Completed and Maintained
• Usage: Completed and Maintained
• Retirement: Archived

Preconditions

A team schedule can typically be started if the following preconditions hold:

• The project has started.
• The project team is properly staffed and trained in component scheduling.
• The relevant requirements are prioritized and specified in the system requirements specification.
• The relevant parts of the system architecture document is complete.

Inputs

A team schedule typically has the following inputs:

• Work Products:
  • System Requirements Specification
  • System Architecture Document
• Stakeholders:
  • Architecture Team
  • Scheduler
  • Technical Leader

Guidelines

• Because of the massive overlap of activities in an iterative, incremental, and parallel development cycle, Gantt and PERT Charts are not very effective for scheduling team tasks.
• Team schedules should be developed by the individual teams based on team estimates.
• Use the procedure in the associated work flow to produce this work product.
• If you tailor this work product, then tailor its associated standard, template, and inspection checklist.

Conventions

A team schedule is typically constrained by the following conventions:

• Work Flow
• Content and Format Standard
• MS Word Template
• XML Template
• Inspection Checklist

Examples

• Example Team Schedule