Learn how to document work details in 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.
Bonnie Biafore has always been fascinated by how things work and how to make things work better. In this course, she explains the fundamentals of project management, from defining the problem, establishing project goals and objectives, and building a project plan to managing team resources, meeting deadlines, and closing the project. Along the way, she provides tips for reporting on project performance, keeping a project on track, and gaining customer acceptance.
Lynda.com is a PMI Registered Education Provider. This course qualifies for professional development units (PDUs). To view the activity and PDU details for this course, click here.
The PMI Registered Education Provider logo is a registered mark of the Project Management Institute, Inc.
- Defining the components of a project
- What it takes to be a project manager
- Using project management software like Microsoft Project
- Managing project scope, budget, and schedule
- Managing project resources, including people
- Managing project risk
- Initiating a project
- Identifying and managing stakeholders
- Identifying requirements and deliverables
- Developing a project plan
- Building a project schedule
- Assigning resources to tasks
- Understanding the critical path
- Running the project
- Managing teams
- Monitoring performance
- Closing a project
Skill Level Beginner
Project Management Foundations: Communicationwith Doug Rose1h 47m Appropriate for all
Project Management Foundations: Budgetswith Bob McGannon1h 11m Appropriate for all
1. Getting to Know Project Management
2. Exploring Project Management Knowledge Areas
3. First Things First
How to develop requirements4m 19s
4. Developing a Project Plan
5. Building a Project Schedule
6. While You Run the Project
7. Working with Teams
8. Monitoring and Controlling Progress and Performance
9. Closing a Project
- Mark as unwatched
- Mark all as unwatched
Are you sure you want to mark all the videos in this course as unwatched?
This will not affect your course history, your reports, or your certificates of completion for this course.Cancel
Take notes with your new membership!
Type in the entry box, then click Enter to save your note.
1:30Press on any video thumbnail to jump immediately to the timecode shown.
Notes are saved with you account but can also be exported as plain text, MS Word, PDF, Google Doc, or Evernote.