<Project Name>

Work Orders (dd/mm/yy to dd/mm/yy)

Version <1.0>

[Note: The following template is provided for use with the Unified Process for EDUcation. Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the document. A paragraph entered following this style will automatically be set to normal (style=Body Text).]

[To customize automatic fields in Microsoft Word (which display a gray background when selected), select File>Properties and replace the Title, Subject and Company fields with the appropriate information for this document. After closing the dialog, automatic fields may be updated throughout the document by selecting Edit>Select All (or Ctrl-A) and pressing F9, or simply click on the field and press F9. This must be done separately for Headers and Footers. Alt-F9 will toggle between displaying the field names and the field contents. See Word help for more information on working with fields.]

Revision History

Date	Version	Description	Author
<dd/mmm/yy>	<x.x>	<details>	<name>

Table of Contents

1. Introduction.. 4

1.1 Purpose. 4

1.2 Scope. 4

1.3 Definitions, Acronyms, and Abbreviations. 4

1.4 References. 4

1.5 Overview... 4

2. Identification.. 5

2.1 Week of work.. 5

2.2 Work Orders ID convention.. 5

2.3 Iteration identification.. 5

2.3.1 Iteration name. 5

2.3.2 Iteration objectives. 5

2.4 Responsibilities. 5

2.4.1 Team Members. 5

2.4.2 Document responsible. 5

3. Work Orders Reports and Schedule. 6

Work Order ID: <>. 6

Work Orders (dd/mm/yy to dd/mm/yy)

1. Introduction

[The introduction of the Work Order provides an overview of the entire document. It includes the purpose, scope, definitions, acronyms, abbreviations, references, and overview of this Work Order.]

1.1 Purpose

[Specify the purpose of this Work Order.]

1.2 Scope

[A brief description of the scope of this Work Order; what model it is associated with and anything else that is affected or influenced by this document.]

1.3 Definitions, Acronyms, and Abbreviations

[This subsection provides the definitions of all terms, acronyms, and abbreviations required to properly interpret the Work Order.  This information may be provided by reference to the project's Glossary.]

1.4 References

[This subsection provides a complete list of all documents referenced elsewhere in the Work Order.  Identify each document by title, report number if applicable, date, and publishing organization. Specify the sources from which the references can be obtained. This information may be provided by reference to an appendix or to another document.]

1.5 Overview

[This subsection describes what the rest of the Work Order contains and explains how the document is organized.]

2. Identification

2.1 Week of work

[State the week of work: Week number and dates (dd/mm/yy to dd/mm/yy) to which these work orders apply]

2.2 Work Orders ID convention

[Explain briefly the naming convention for the work orders ID. Example:

All work orders ID use the following convention:

<RR-IT#-W##-##> where:

RR: Resource (Work Order Holder) initials

IT#: Related Iteration Number

W##: Week of work Number

##: Unique work order number

On week of work #1, John Smith has been assigned his 1^st work order. It is related to Iteration #1. Work Order ID would be: <JS-IT1-W01-01>]

2.3 Iteration identification

2.3.1 Iteration name

[State the name of the related iteration to which these work orders apply]

2.3.2 Iteration objectives

[Briefly describe the main objectives of this iteration. Then refer to the Iteration Plan Document for detailed information]

2.4 Responsibilities

2.4.1 Team Members

[List all team members and their role. List only team members implied in this Work Orders Document]

2.4.2 Document responsible

[State the responsible for this document (Project Manager, Configuration Manager...)

3. Work Orders Reports and Schedule

Work Order for <Project Name>				Created on: <6/6/2002>
Identification
Work Order ID: <>		WBS ID: <>
Responsibility (Holder)
Associated Change Reports
Schedule
Start: <dd/mm/yy>	Completion: <dd/mm/yy>		Critical Path: <dd/mm/yy>
Efforts and Other Resources
Staff Hours:		Other Resources:
Description
Work Description:
Expected Output(s):
Signature Agreement
Project Manager: x _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Signed on: <dd/mm/yy>		Work Order Holder: x _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Signed on: <dd/mm/yy>

[The following is a brief outline on the work order report]

1. Identification

Uniquely identifies the work order and identifies the work package (Work Breakdown Structure (WBS) identification) associated with this work order: effort expended on this work order will be allocated to this work package for tracking.

2. Responsibility

Organizational positions responsible for fulfilling the work order.

3. Associated Change Requests

If any, references to Change Requests that are associated with this work order (those that were the stimulus for it or those that will be fixed coincidentally).

4. Schedule

The schedule covers the estimated start and completion dates, and the critical path completion date.

5. Effort and other resources

Addresses the staff-hours, total and over time, as well as other resource budgets; for example, development environment time, test environment time.

6. Description of work and expected outputs

Describes what is to be done and what is to be produced—references the Unified Process for EDUcation description of the activities to be performed and artifacts to be produced, or the development case, as appropriate.

7. Indication of agreement between Project Manager and responsible staff

The work order should be signed and dated by the holder of the responsible position (usually a team lead) and the Project Manager.