Artifact: Work Order










var backPath = './../../';
var imgPath = './../../images/';
var nodeInfo=[{view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_4U33kAILEdq-_NKqZM1EhA", "_qIh6UABuEdqrKcHWz1HoWw", "{EE97A8CD-66CA-4A9B-9871-E3B94CCED528}", "{18DB40A1-6272-467A-AC68-B2C4BE1DCD6C}"]}, {view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_4U33kAILEdq-_NKqZM1EhA", "_U8LVkAIUEdqEutyfYo0quQ", "_C49xgP_UEdmVCcs_BRqacA", "{18DB40A1-6272-467A-AC68-B2C4BE1DCD6C}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_f6_YwN7DEdmsEI4YDGX2ag", "_qIh6UABuEdqrKcHWz1HoWw", "{EE97A8CD-66CA-4A9B-9871-E3B94CCED528}", "{18DB40A1-6272-467A-AC68-B2C4BE1DCD6C}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_EOvXUN7HEdm8G6yT7-Wdqw", "_C49xgP_UEdmVCcs_BRqacA", "{18DB40A1-6272-467A-AC68-B2C4BE1DCD6C}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_jijhYAIaEdqEutyfYo0quQ", "_qUsPIN7REdmjRZts2c4ZjQ", "{18DB40A1-6272-467A-AC68-B2C4BE1DCD6C}"]}];
contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);










Artifact: Work Order















This artifact is the Project Manager's means of communicating what is to be done, and when, to the responsible staff. It becomes an internal contract between the Project Manager and those assigned responsibility for completion.


Domains: Project Management
Work Product Kinds: Project Data






Purpose



The purpose is to turn planning into action within Iterations.



Relationships



RolesResponsible:



Project Manager


Modified By:



Project Manager





TasksInput To:
Output From:



Initiate Iteration


Schedule and Assign Work





Process Usage


Configuration & Change Management
 > 
Manage Baselines & Releases
 > 
Work Order


Configuration & Change Management
 > 
Change and Deliver Configuration Items
 > 
Work Order


Configuration & Change Management
 > 
Manage Change Requests
 > 
Work Order


Project Management
 > 
Monitor & Control Project
 > 
Work Order


Project Management
 > 
Manage Iteration
 > 
Work Order


Test
 > 
Define Evaluation Mission
 > 
Work Order






Description



Main Description The work order is a negotiated agreement between the Project Manager and the staff to perform a particular task, or set of tasks, under a defined schedule and with certain deliverables, effort, and resource constraints. Work Orders become internal contracts between the Project Manager and those assigned responsibility for their completion.


Brief Outline 1. Identification Uniquely identifies the project and the work order. 2. Work Breakdown Structure (WBS) identification Identifies the activity (in the project plan) associated with this work order. Effort expended on this work order will be allocated to this activity for tracking. 3. Responsibility Organizational positions responsible for fulfilling the work order. 4. Associated Change Requests 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). 5. Schedule The schedule covers the estimated start and completion dates, and the critical path completion date. 6. 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. 7. Description of work and expected outputs Describes what is to be done and what is to be produced-references the Rational Unified Process description of the tasks to be performed and work products to be produced, or the development case, as appropriate. 8. 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.



Tailoring



Representation Options The work order is the mechanism by which the Project Manager communicates plans to project members. On small projects this could be as simple as discussing a plan on a whiteboard and then confirming agreements through e-mail. On large, very structured projects perhaps some form of automated activity management is used, where the Project Manager injects formal directions that appear to the team members in to-do lists (maybe with some protocol for agreement). Another option is to use an automated change request management system, extended so that all work on a project (not just defects) is described in change requests, and the directions to perform work are implemented as actions (through, say email, or through an integration with an automated activity management system) that are triggered by state changes in the change request management process. See the Tool Mentor: Establishing a Change Request Process Using Rational ClearQuest for an example of how an automated change management process, which triggers external actions, can be set up.



More Information



Guidelines


Estimating Effort Using the Wide-Band Delphi Technique


Work Order â€" Informal Representation








©  Copyright IBM Corp. 1987, 2006.  All Rights Reserved.







contentPage.onload();