Activity Sequencing
Now that we have a list of activities, we need to put them into some
Mandatory dependencies are called hard logic. Mandatory dependencies often occur because of physical limitations. An example of this would be in construction, where you must complete the framing before you can hang the drywall. However, in IT, there are fewer of these dependencies than you might think at first glance. Most project managers confuse these mandatory dependencies with discretionary dependencies out of habit. Let's discuss the differences. Discretionary dependencies are preferred sequence of activities, sometimes called "Best Practices." In Information Technology, most project managers plan to wait until design is complete before starting coding. But in reality, you can start coding about half way through design. Discretionary dependencies are also known as preferred, preferential, or soft logic.
The answer is B. Milestones are significant events in the project life cycle with zero duration. Milestones show completion of deliverables, phases, and other events you want highlighted. One last dependency to discuss is external dependencies. These are stakeholders' or outside parties' desired sequence of activities (e.g., government, suppliers, etc.).
The answer is D. External dependencies occur because something outside of the project itself causes the need for a task to be done. For instance, a government regulation might require that you report a certain type of information as the first part of a new software package you are writing.
The answer is A. There is no duration for a milestone when you are doing your scheduling. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Network Diagrams
Learning the different network diagram
Figure 10-1. Precedence Diagramming Method (PDM).
The finish-to-start dependency is the most common one, and it is used in Microsoft Project. An example of this dependency would be having to finish buying paint before you can begin to paint a room. The painting of the room is dependent on purchasing the paint. The finish-to-finish dependency occurs when one task must be completed before another task can be completed. For instance, you must finish sanding all the walls before you can finish painting all the walls. The start-to-start dependency means that you must begin a task before another task begins. An example of this dependency would be that you have to start prepping the walls before you can start painting them. The start-to-finish dependency occurs when something must be started before finishing another task. This dependency often occurs when you are installing a new phone system. You must start the new phone system running before you can finish with the old system. It is very difficult to get a perfect switch, so you need to have redundant activities to make sure you can still have a working phone system.
The answer is C. Finish-to-start dependencies are the most common types used in most projects.
The answer is A. In this example, you are starting a new system but protecting your organization by leaving the old system going until you are certain that a comfortable switchover can be made.
Arrow Diagramming Method (ADM) uses arrows as activities, and nodes are used to connect and show dependencies. In other words, the lines in between nodes are where you place the task
Figure 10-2. Arrow Diagramming Method (ADM).
The next methods allow conditional branches (i.e., ifthenelse condition) and
Network templates are useful to speed up network diagramming. Parts of standardized templates can be used in building project networks for repeatable or identical
The answer is D. ADM (Arrow Diagramming Method) or activities on arrows uses dummy activities to correctly show all logical relationships.
The answer is A. The
{% if main.adsdop %}{% include 'adsenceinline.tpl' %}{% endif %} The answer is D. This is the most commonly used method.
The answer is A. The graphical evaluation and review technique can show conditional branches that reflect what happens if a certain action is taken.
After finishing activity sequencing, you will have a project network diagram. The PMBOK describes project network diagrams as "schematic displays of the project's activities and the logical relationships (dependencies) among them" (PMBOK, p. 135). Most project managers use computers to draw network diagrams, but network diagrams can also be
Network diagrams can contain one or more summary tasks. PMBOK also calls these summary tasks hammocks, meaning that they span the beginning and end of the tasks somewhat like a hammock. Summary tasks are a high-level compilation of the tasks below them. You might have to add to or
The answer is C. This is an output from activity sequencing.
The answer is B. The summary tasks do not show detail of all the tasks below them. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||