Unit 3 - Practice Quiz

The planning phase is where the project's roadmap is created. This includes defining the scope, setting objectives, and detailing the course of action to achieve the project goals.

Project Schedule Management includes all the processes required to manage the timely completion of the project, from planning the schedule to controlling it.

Sequencing activities is the process of arranging project tasks in the logical order they need to be performed, defining their dependencies.

This process estimates the number of work periods (like hours or days) required to complete each scheduled activity, which is a crucial input for creating the project schedule.

A constraint is a limitation or restriction. A fixed deadline is a common time-based constraint that the project schedule must adhere to.

A network diagram is a flowchart that graphically represents the project's activities and the logical relationships (dependencies) between them.

A lag is a deliberate, required delay in the start of a successor activity. For example, you must wait 24 hours for concrete to cure before starting the next task.

Analogous estimating uses historical data from a similar previous project to estimate the duration or cost of the current project, making it a form of top-down estimation.

Three-Point estimating and PERT use three estimates—Optimistic (O), Pessimistic (P), and Most Likely (M)—to account for uncertainty and risk when calculating a task's duration.

Bottom-up estimating involves estimating the cost or duration of individual work packages or activities and then summing them up to get a project total. It is generally more accurate but more time-consuming.

A Gantt chart is a type of bar chart that illustrates a project schedule, showing the start and finish dates of tasks and their dependencies over time.

Crashing is a technique used to shorten the schedule duration for the least incremental cost by adding resources (like more staff or equipment) to critical path tasks.

Project Cost Management includes the processes involved in planning, estimating, budgeting, and controlling costs so that the project can be completed within its approved budget.

Expert judgment, which relies on the knowledge of experienced individuals, is a common and fundamental technique used in many estimation processes.

The project budget is the total authorized funding allocated for completing the project. It serves as a baseline against which project costs are measured and controlled.

Procurement management deals with obtaining goods and services from external sources like vendors, suppliers, or contractors.

An RFP is a formal document that a buyer issues to potential suppliers to request proposals for a specific product or service, outlining the project's requirements.

Earned Value (EV) measures the work performed in terms of the budget authorized for that work. It represents the value of what has been accomplished so far.

Supplier management involves ensuring that suppliers meet their contractual obligations, monitoring their performance against those obligations, and maintaining a good working relationship.

A lead allows a successor activity to begin before its predecessor activity is fully complete, effectively overlapping the tasks to save time.

The PERT formula gives more weight to the most likely estimate. The calculation is , so days.

The Schedule Performance Index (SPI) is EV/PV = 50,000 = 0.9, which is less than 1, indicating the project is behind schedule. The Cost Performance Index (CPI) is EV/AC = 60,000 = 0.75, which is also less than 1, indicating the project is over budget.

A 'lead' allows a successor activity to begin before its predecessor activity is finished. Since 'Testing' starts before 'Development' finishes, it is a lead time applied to a Finish-to-Start dependency.

Crashing is a schedule compression technique where cost and resources are added to the project for the greatest compression of the schedule for the least incremental cost. Fast tracking involves performing activities in parallel that would normally be done sequentially.

Parametric estimating uses a statistical relationship between historical data and other variables (e.g., cost per unit) to calculate an estimate. Analogous estimating would use the total cost of a previous similar project as a single data point.

The critical path is the sequence of scheduled activities that determines the duration of the project. It is the longest path through the project network and has the least amount of total float, which is typically zero. Any delay on this path directly delays the project completion date.

Bottom-up estimating involves estimating the cost or duration of individual work packages or activities at the lowest level of the WBS and then summing them up to get a project total. It is generally the most accurate but also the most time-consuming estimation method.

A baseline is the approved version of a work product that can be changed only through formal change control procedures and is used as a basis for comparison to actual results. The schedule baseline is the standard against which schedule performance and variance are measured.

The dependency is external because it involves an entity outside the project (the government). It creates a date-driven constraint where the construction activity cannot begin before the permit is approved on June 1st, making it a "Start No Earlier Than" (SNET) constraint.

The 'Conduct Procurements' process involves obtaining seller responses, selecting a seller, and awarding a contract. Activities like issuing RFPs, receiving proposals, and holding bidder conferences to clarify requirements are central to this process.

The correct option follows directly from the given concept and definitions.

The Cost Baseline is the approved, time-phased project budget, excluding any management reserves. It is the sum of the project cost estimates and the contingency reserves for identified risks. The full Project Budget is the Cost Baseline plus the Management Reserve.

While selecting the supplier and negotiating are crucial upfront, during project execution the focus is on 'Control Procurements'. This involves actively monitoring supplier performance to ensure they meet contractual obligations, managing the relationship, and making changes and corrections as needed.

The triangular distribution formula for a three-point estimate is a simple average of the three estimates: Expected Duration = (Optimistic + Most Likely + Pessimistic) / 3. So, hours. The PERT estimate would be 25.8 hours.

A Finish-to-Start (FS) dependency is a logical relationship in which a successor activity ('Write User Manual') cannot start until a predecessor activity ('Finalize Software Code') has finished. This is the most common type of dependency.

Fast tracking is a schedule compression technique where activities or phases normally done in sequence are performed in parallel for at least a portion of their duration. This technique is chosen when there is no extra budget for more resources (as in crashing) but often increases risk and can result in rework.

Analogous estimating uses the actual cost, duration, or other values from a previous, similar project as the basis for estimating the same parameter for a future project. It is a form of expert judgment and is most useful when detailed information is not yet available, making it suitable for early-phase ROM estimates.

In the project planning lifecycle, after defining activities and their sequence (network diagram), the next logical step is to estimate the resources (people, equipment) needed for each activity and then estimate the time (duration) each activity will take. This information is required before the final schedule and cost baseline can be developed.

Contingency reserves are budgeted funds for identified risks and are part of the cost baseline, controlled by the PM. Management reserves are an additional amount of budget withheld for unforeseen work ("unknown unknowns") and are not part of the cost baseline; using them requires approval from senior management.

On a Gantt chart, a milestone is a significant point or event in a project. It is typically represented as a diamond shape and has zero duration because it marks a point in time (e.g., "Design Approved," "Phase 1 Complete") rather than an activity that takes time to complete.

The correct option follows directly from the given concept and definitions.

The correct option follows directly from the given concept and definitions.

1. Compress by 2 days: To make the critical path (CP) equal to the near-critical path (NCP), crash the cheapest CP task (Task X) by 2 days. Cost = 2 * 4,000. Both paths are now 58 days. \n2. Compress by 3 more days: Now, both paths must be crashed simultaneously for the remaining 3 days. \n - Day 3: Crash Task X (1 day left, 3,500). Cost = 3,000) and NCP (3,000 + 6,500 = 4,000 + 13,000 = $22,500.

Fairness and transparency are paramount in procurement. A verbal clarification is insufficient as it may not reach all potential bidders and lacks formal standing. Asking for assumptions makes bids non-comparable. Using the incentive fee to cover a major SOW ambiguity is improper and high-risk. The only correct action is to formally amend the procurement documents to ensure all bidders are bidding on the exact same, unambiguous scope.

The fundamental prerequisite for Bottom-Up estimating is the ability to decompose the project scope into small, manageable, and well-understood work packages. In a high-uncertainty R&D project, this level of decomposition is impossible at the outset. Attempting to do so would be based on flawed assumptions, invalidating the accuracy of the resulting estimate. The other options are relevant concerns, but this is the primary reason the method itself is inapplicable.

Changing from FS with a lag to SS with a lead converts a sequential, buffered relationship into a parallel, tightly coupled one. In the original FS+10 relationship, problems in A had a 10-day buffer before affecting B. With the SS-12 relationship (interpreted as B starts 12 days before A starts, which is unusual, let's assume it means B starts 12 days after A starts, SS+12. If it's a lead, B starts 12 days before A finishes - this implies parallelism), a delay in the start of A immediately impacts the start of B. This creates a risk of cascading delays without the buffer that the lag provided.

The choice of EAC formula depends on assumptions about future performance. \n- EAC = BAC / CPI assumes future cost performance will be the same as past performance. The manager believes it will not be. \n- EAC = AC + (BAC - EV) / (CPI * SPI) is used when both cost and schedule performance are expected to impact future costs. \n- EAC = AC + (BAC - EV) assumes future work will be completed at the originally planned rate (i.e., future CPI will be 1.0). This aligns perfectly with the manager's assessment that the past cost overruns were atypical and will not continue.

1. Initial state: Cost Baseline = 100k Contingency Reserve). Management Reserve = Total Budget - Cost Baseline = 1.2M = 40k cost is covered by the Contingency Reserve. This is its purpose. The reserve drops to 150k market shift is an 'unknown unknown' and is a change in scope. It is funded from the Management Reserve. When an approved change request uses the management reserve, the cost baseline is formally updated to include the new scope. The new baseline becomes 150k = 0.

When faced with a hard constraint and a schedule that exceeds it, simply trying to compress the schedule (crashing/fast-tracking) is one tool, but not the first step. Rejecting the constraint is often not an option. Accepting over-allocations creates risk. The most strategic approach is to re-plan by starting from the mandatory deadline and working backward (reverse phase scheduling or 'back-passing'). This method forces a re-evaluation of dependencies, durations, and, most importantly, scope, to determine what is realistically achievable within the fixed timeframe, leading to a discussion about trade-offs (scope, cost, quality) with stakeholders.

Since there is no formal breach of contract, legal or punitive actions are premature and likely to fail. Simply accepting the problem and using contingency funds abdicates the PM's responsibility to manage the supplier. The most effective professional action is to address the issue collaboratively. A good supplier relationship is a key tool. By explaining the business impact, the PM can negotiate a solution that benefits both parties (e.g., the supplier improves quality to secure future business, the project avoids rework), which is the essence of effective supplier management beyond just contract administration.

This scenario requires a hybrid approach. The strong statistical relationship from 19 previous projects makes Parametric estimating (e.g., cost per sq. foot) ideal and highly accurate for the known components. However, there is no direct historical data for the new cooling technology, making Parametric estimating for that part invalid. The best approach for the new component is to use Analogous estimating (comparing it to similar, but not identical, technology installations) and heavily supplement it with expert judgment from engineers familiar with the technology. A full Bottom-Up is too time-consuming at this stage, and relying solely on one method is inappropriate given the mix of known and unknown elements.

When a significant and approved change fundamentally alters the scope, schedule, and cost of a project, the original baseline ceases to be a realistic benchmark for performance measurement. Continuing to track against it would show a persistent, large, and meaningless variance. The proper procedure is to perform a formal re-baselining. This creates a new performance measurement baseline (PMB) that reflects the revised project plan, allowing for meaningful tracking of variance from that point forward.

While applying lags to both incoming links to D is possible in some software, it can be ambiguous. The clearest and most technically correct way to model a many-to-one dependency with a lag is to use a milestone. The milestone 'M' represents the event 'Both B and C are complete'. By having B and C finish before M can start, and M finish instantly, M's finish time is determined by the latest finishing predecessor (C). You then apply the 5-day lag to the single, unambiguous link from M to D.

This scenario is a classic case for fast-tracking using parallel activities. A simple FS relationship is too restrictive. An SS relationship allows the UI team to start work with mock data as soon as the API team has defined the API contracts (the lag allows for this initial definition work). The addition of an FF dependency is crucial; it ensures that final UI integration and testing cannot be completed until the API is fully built and available, thus maintaining the logical integrity of the end product. This dual-dependency model accurately reflects the real-world workflow.

This is a complex make-or-buy decision. First, the financial risk must be quantified. The EMV of the 'make' option is: (0.80 * 150k + 120k + 170k. This is cheaper than the 'buy' option's fixed price of $180k. However, the decision isn't purely financial. The 'opportunity cost' is the value of the opportunity lost by choosing one alternative over another. In this case, by buying, the company loses the strategic opportunity to gain valuable expertise. The core conflict is weighing the slight financial advantage and risk of making it in-house against the significant, non-financial strategic loss (opportunity cost).

Rolling wave planning is based on the principle of progressive elaboration. Its main benefit is agility; the team avoids detailed planning for distant work that is likely to change, thus reducing waste. However, this creates a significant integration challenge. If the initial, high-level planning (e.g., system architecture, epic definitions) is not sound, future iterations may reveal that the foundational design cannot support the detailed features planned for them, leading to costly and time-consuming architectural refactoring.

Effective project management requires proactive control, not just planning. The integration between schedule and communications is most critical at the control points. The schedule management plan sets the rules for control (e.g., 'a schedule variance exceeding 10% on a critical path activity must be reported'). The communications plan then executes this rule by defining who gets the report, how (email, dashboard alert, formal meeting), and when. This linkage ensures that schedule deviations are not just tracked but are communicated effectively to the right people for timely decision-making.

During the project initiation phase, very little detail is known about the project scope. Therefore, a highly accurate estimate is impossible. The appropriate tool is a Rough Order of Magnitude (ROM) estimate, which is based on very high-level information or analogies. Its purpose is to provide a preliminary assessment for decision-making (e.g., go/no-go). The characteristic wide accuracy range of -25% to +75% reflects this high level of uncertainty. Definitive and Budgetary estimates are created later in the planning process when more detail is available.

While all the options are potential benefits of an EPPM, the core justification for its use on a large, complex project like this lies in its advanced analytical power. Standard desktop tools often have limited or no capability for true Monte Carlo simulation, which is essential for understanding the likely range of completion dates and costs in a high-risk environment. Furthermore, managing and leveling resources across thousands of activities is a computationally intensive task where the sophisticated algorithms of an EPPM system provide far more optimal solutions than simpler tools, directly impacting schedule feasibility and cost.

Parkinson's Law and Student Syndrome are behavioral phenomena that explain why safety time embedded in individual tasks often gets wasted. If a task has a buffer, the work will either expand to consume it (Parkinson's) or the buffer will be wasted at the beginning before work even starts (Student Syndrome). The Critical Chain Project Management (CCPM) methodology directly addresses this by asking for aggressive (e.g., 50% probability) estimates, removing the hidden safety buffers from tasks, and pooling that saved time into a single, explicit project buffer that the project manager controls. This protects the project's end date without inflating individual task durations.