Based on the CPM chart at the bottom:

• What is the shortest duration that the project can be completed, using the time estimates and dependencies in the table?
• Which tasks have slack, and how much?
• Did creating the network diagram make it easier to track tasks and relationships? Why or why not?
• Does the methodology help you understand the concepts of slack and how understanding where slack exists can help you manage the schedule?
• What options might you consider if you wanted to speed up the project, and why?

I have always liked this methodology and understand why it was so widely adopted. I do prefer AON over AOA as far as diagrams since it easier to visualize the slack, yet I also prefer the probabilistic time estimates used by PERT/AOA since I think it provides more realistic estimates. I appreciate how the text combines the two approaches. (Meredith and Mantel 2011) Overall, it is an effective tool for both managing and communicating the tasks. Visualizing the dependencies certainly helps deciding how to assign staff, knowing what needs to be done sequentially and what could be done concurrently.