Component Schedule

Definition

Component Schedule

the management work product that documents the schedule for the development of a single data, hardware, or software component of an application

Objectives

The typical objectives of a component schedule are to document the planned dates:

• Start of component development.
• Completion of component design.
• Completion of component implementation.
• Completion of component testing.
• Successful integration of the component into the application.
• Completion of component integration testing.

Benefits

The typical benefits of a component schedule include:

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

Contents

A component schedule typically has the following contents:

• Component identification.
• Start date of component development.
• Completion date of component design.
• Completion date of component implementation.
• Completion date of component testing.
• Date of successful integration of the component into the application.
• Completion date of component integration testing.

Stakeholders

A component schedule typically has the following stakeholders:

• Producers:
  • Architecture Team
• Evaluators:
  • Management Inspection Team
  • Architecture Inspection Team
• Approvers:
  • Technical Leader
• Maintainers:
  • Architecture Team
• Users:
  • Program Management Team
  • Project Management Team
  • Architecture Team
  • Software Development Team
  • Integration Team

Phases

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

• Business Strategy: Not Applicable
• Business Optimization: Not Applicable
• Initiation: Completed
• Construction: Completed
• Delivery: Completed
• Usage: Not Applicable
• Retirement: Archived

Preconditions

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

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

Inputs

A component schedule typically has the following inputs:

• Work Products:
  • System Requirements Specification
  • System Architecture Document
• Stakeholders:
  • 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 component development.
• Component schedules should be developed by the responsible 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 component schedule is typically constrained by the following conventions:

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

Examples

• Example Component Schedule