Scribd
Upload
758 views72 pages

Chapter 6-PM Answers

The document discusses key differences between a work breakdown structure (WBS) and project network. A WBS breaks down work into deliverables and tasks, while a project network shows the sequence and dependencies of tasks. It asks why create a WBS instead of just a network, and describes importance of slack time and different types for project managers. Questions provide examples of using a WBS for a wedding to build a project network diagram, including technical dependencies between tasks from start to finish.

Uploaded by

Khuetu Nguyenhoang
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
758 views72 pages

Chapter 6-PM Answers

The document discusses key differences between a work breakdown structure (WBS) and project network. A WBS breaks down work into deliverables and tasks, while a project network shows the sequence and dependencies of tasks. It asks why create a WBS instead of just a network, and describes importance of slack time and different types for project managers. Questions provide examples of using a WBS for a wedding to build a project network diagram, including technical dependencies between tasks from start to finish.

Uploaded by

Khuetu Nguyenhoang
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Chapter 6

1. How does the WBS differ from the project network?

2. How are WBS and project networks linked?


3. Why bother creating a WBS? Why not go straight to a project network and forget the WBS?

4. Why is slack important to the project manager?


5. What is the difference between free slack and total slack?
6. Why are lags used in developing project networks?
7. What is a hammock activity, and when is it used?
Creating a Project Network
1. Here is a work breakdown structure for a wedding. Use the method described
in the Snapshot from Practice: The Yellow Sticky Approach to create a network for this project.
Note: Do not include summary tasks in the network (i.e., 1.3, Ceremony, is a
summary task; 1.2, Marriage license, is not a summary task). Do not consider
who would be doing the task in building the network. For example, do not
arrange “hiring a band” to occur after “florist” because the same person is
responsible for doing both tasks. Focus only on technical dependencies between
tasks.
Hint: Start with the last activity (wedding reception), and work your way back to the
start of the project. Build the logical sequence of tasks by asking the following question: In order to have
or do this, what must be accomplished immediately before this?
Once completed, check forward in time by asking this question: Is this task(s) the
only thing that is needed immediately before the start of the next task?
Work Breakdown Structure
1. Wedding project
1.1 Decide on date
1.2 Marriage license
1.3 Ceremony
1.3.1 Rent church
1.3.2 Florist
1.3.3 Create/print programs
1.3.4 Hire photographer
1.3.5 Wedding ceremony
1.4 Guests
1.4.1 Develop guest list
1.4.2 Order invitations
1.4.3 Address and mail invitations
1.4.4 Track RSVPs
1.5 Reception
1.5.1 Reserve reception hall
1.5.2 Food and beverage
[Link] Choose caterer
[Link] Decide on menu
[Link] Make final order
1.5.3 Hire band
1.5.4 Decorate reception hall
1.5.5 Wedding reception
Question 2
Question 3
Question 4

Question 5
Question 6
Question 7
Question 15
Question 16
Question 17

You might also like