Part 2. Answers to Questions in Microsoft Word Read and think through the options and alternatives suggested by these questions before building the Project Plan. When the Project Plan is completed, answer the following questions, and submit them as a Microsoft Word document. “Yes” or “No” answers with no explanations or discussions are not appropriate answers. 1. What are the names of the first and last tasks in the Project Plan? What are their durations? 2. Was the team able to view the Project Plan’s critical path? Explain what it showed. 3. Do any Summary Tasks or Sub-tasks show as manually scheduled ( in the Task Mode column)? If yes, list the task ids and explain what caused that. If not, explain how that was avoided. 4. Do any Summary Tasks or Sub-tasks show as constrained? (Name of the constraint in the Constraint Type column, or date in the Constraint Date column)? If yes, list the task ids and explain what caused that. If not, explain how that was avoided. 5. Did the team approach the WBS graphically (like an organization chart, tabularly (like a list or table), or something else? Why?

1. The names of the first and last tasks in the Project Plan are not stated in the given information. In order to determine this information, we would need to analyze the Project Plan that was completed. The durations of these tasks would also need to be identified, as they are not provided in the question.

2. In order to determine whether the team was able to view the Project Plan’s critical path, we would need access to the Project Plan and knowledge of the software used to create it. However, assuming that the team utilized a project management software such as Microsoft Project, it is likely that they were able to view the critical path. The critical path shows the sequence of tasks that must be completed in order to finish the project on schedule. It helps identify tasks that have no flexibility and any delays on these tasks could cause the overall project to be delayed.

3. Without access to the Project Plan, we cannot determine whether any Summary Tasks or Sub-tasks show as manually scheduled. The Task Mode column in a project management software displays the scheduling mode for each task. Manually scheduled tasks are those where the start and finish dates are entered directly by the project manager or team members, without any dependencies or constraints dictating the scheduling. If any Summary Tasks or Sub-tasks were manually scheduled, it would be necessary to list the task ids and explain what caused that.

4. Similarly, without access to the Project Plan, it is not possible to determine whether any Summary Tasks or Sub-tasks show as constrained. Constraints are limitations or restrictions placed on a task, such as a specific date by which it must be completed. The Constraint Type column or Constraint Date column in a project management software would indicate if any tasks have constraints. If any tasks were constrained, it would be necessary to list the task ids and explain what caused that.

5. The approach taken by the team in creating the Work Breakdown Structure (WBS) could vary depending on their preferences and the specific requirements of the project. They may have chosen to present the WBS graphically, using an organization chart format, to visually represent the hierarchical structure of the project and its various components. This format allows for easy identification of major deliverables and their associated tasks. Alternatively, they may have presented the WBS tabularly, like a list or table, to provide a more detailed breakdown of tasks and corresponding information such as task durations, responsible parties, and dependencies. The team may have also utilized a combination of graphical and tabular formats to achieve the desired level of clarity and comprehensiveness in their WBS. The specific choice would depend on factors such as project complexity, team preferences, and the need for clear communication and understanding among stakeholders.