How to define work packages

- [Voiceover] The short names in a WBS typically aren't enough to tell team members what they're supposed to do. To give your team the info they need, create work package documents that describe, in detail, the work identified in the WBS. The level of detail you include in the work package document depends on things like how familiar the work is and the experience of the person assigned to the task. For example, a work package document might include a detailed description of the work for a less experienced person.

On the other hand, you could include a checklist of things to do to serve as a reminder for a more experienced individual. If the specifics of the work are described somewhere else, you can refer to the other document that contains the information. A work package document does more than describe the work. It also identifies how you know the task is complete and whether it was completed correctly. For some tasks, you can include the corresponding deliverable and success criteria in a work package document.

Otherwise, write up a description of what you will have when the task is complete and what it should look like. You've probably figured out that you, the project manager, don't know enough about every aspect of the work to produce these detailed task descriptions. Turn to the people who helped you build the WBS, team leaders for the groups that will work on the project, or other knowledgeable people to help fill in the details. Work packages help your team members to deliver what they're supposed to.

Go ahead, try defining some work packages for work that you're familiar with.