Create A Microsoft Project File With Microsoft Project

Microsoft Projectcreate A Microsoft Project File With the Following Ch

Create a Microsoft Project file with the following characteristics using the ‘MS Project Step-By-Step’ guide:

  • Has a project start date of 4/1/2009 and is scheduled forward from that date
  • Shows the WBS numbers for tasks
  • Has a WBS of the following structure:
    • 1. Project
    • 1.1. Task A (realistic estimate is 10, optimistic is 5, pessimistic is 20)
    • 1.2. Task B (realistic estimate is 5, optimistic is 2, pessimistic is 8)
    • 1.3. Task C (realistic estimate is 20, optimistic is 16, pessimistic is 24)
    • 1.4. Task D (realistic estimate is 10, optimistic is 4, pessimistic is 16)
  • Task A must precede Task B
  • Task A must precede Task C
  • Task B must precede Task D
  • Task C must precede Task D
  • Include two resources:
    • Monty Python (cost is $100/hour)
    • Pink Floyd (cost is $200/hour)
  • Assign Monty Python to Tasks A, B, and D
  • Assign Pink Floyd to Tasks C and D
  • Set a project baseline
  • Customize the Tracking Gantt view to include the % complete, CPI, and SPI fields
  • Task A has been completed. It started on time and ended on 4/16/2009
  • Task B has been started on 4/21/2009 and is 50% done
  • Task C has been started on 4/17/2009 and is 15% done
  • Set the project status date to 4/22/2009
  • Save the file and send it via email to the professor

Paper For Above instruction

Microsoft Project is a powerful project management tool that enables project managers to plan, schedule, and control projects effectively. Creating a comprehensive project file that meets specific project parameters involves careful setup of tasks, resources, dependencies, and baseline data. This paper provides a detailed walkthrough of designing a Microsoft Project file based on the outlined requirements, including task structuring with WBS codes, resource allocation, progress tracking, and visualization enhancements.

The first step involves setting the project's start date to April 1, 2009, and configuring the schedule to proceed forward from this date. This ensures that all tasks and durations are anchored to this baseline, establishing a clear timeline for project execution. The WBS (Work Breakdown Structure) is formatted to reflect a hierarchical organization, starting with the main project (1.0) labeled "Project," with four subordinate tasks (1.1 to 1.4). Each task's estimates are carefully inputted, taking into account realistic, optimistic, and pessimistic durations, which can be used for risk analysis and contingency planning.

Task dependencies are critical for establishing the sequence of activities. In this case, Task A precedes Tasks B and C, while Tasks B and C both precede Task D. These dependencies are modeled using predecessor links in Microsoft Project, ensuring the project schedule accurately reflects these constraints. The accurate depiction of dependencies allows for realistic calculations of project duration and identifies critical paths.

Resource assignment is another key facet. The project involves two resources: Monty Python and Pink Floyd, with specified hourly costs of $100 and $200, respectively. Monty Python is assigned to Tasks A, B, and D, while Pink Floyd is assigned to Tasks C and D. Resource allocation is done using the resource assignment view, which also facilitates the setting of costs, enabling budget tracking and cost variance analysis.

Baseline setting in Microsoft Project captures the current project plan, including schedule, costs, and resource allocations. This provides a reference point to measure project performance as work progresses. Once the baseline is set, tracking progress can be entered and the view customized to include key performance indicators, such as percentage complete, Cost Performance Index (CPI), and Schedule Performance Index (SPI). These metrics help monitor project health and deviations from the plan.

The status updates for tasks are entered with specific start and completion details: Task A is completed on time by 4/16/2009; Task B, started on 4/21/2009, is 50% complete; and Task C, initiated on 4/17/2009, is 15% complete. Adjusting the project status date to 4/22/2009 ensures the data reflects current progress. These updates impact project metrics, calculations of remaining durations, and cost variances.

Final steps include saving the project file and exporting it for distribution. The file can be shared via email and used for ongoing project control. The entire process exemplifies how detailed planning and management features in MS Project facilitate efficient project execution and tracking, ultimately increasing the likelihood of project success.

References

  • Kerzner, H. (2017). Project Management: A Systems Approach to Planning, Scheduling, and Controlling. John Wiley & Sons.
  • Microsoft Corporation. (2020). Microsoft Project Step-By-Step Guide. Microsoft Support.
  • Heldman, K. (2018). Project Management JumpStart. Wiley.
  • Meredith, J. R., & Mantel, S. J. (2014). Project Management: A Managerial Approach. Wiley.
  • Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide). PMI.
  • Schwalbe, K. (2015). Information Technology Project Management. Cengage Learning.
  • Gido, J., & Clements, J. (2019). Successful Project Management. Cengage Learning.
  • Exploring Microsoft Project. (2021). TechTarget. Retrieved from https://www.techtarget.com
  • Haughey, D. (2020). Managing Projects with Microsoft Project. Pearson.
  • Turner, J. R. (2014). Handbook of Project-Based Management. McGraw-Hill Education.

Related Assignments