Create A Microsoft Project File MPP And Build Out The Projec

Create A Microsoft Project File Mpp And Build Out The Project Plan

Create a Microsoft Project file (.mpp) and build out the Project Plan: Before you import your WBS from the prior assignment into MS Project, you must set up your Microsoft Project Options (this information is covered in Chapter 2 of the Ambriz textbook): From the File tab (which takes you to the Backstage), select "Options" and then "Schedule" - verify that the settings on that tab are correct for your project and work environment. Change the scheduling options so that all tasks are Auto Scheduled and that the default Task Type is set to either Fixed Duration or Fixed Work. You want to use the dynamic scheduling capabilities of MS Project. Select whether or not you want to schedule the project from the start date or the end date (regulatory requirements and events that have non-negotiable deadlines should be scheduled from the Project End Date).

Create a calendar for your project or make necessary modifications to the Standard calendar to include any revised schedule days, holidays or non-working days. From the Project Tab, select Project Information and set the Start Date of your project. This can be the actual start date of your project or you can select a fictitious start date if you don't know exactly when the project is going to start. Select the appropriate Calendar for your project based on step 2. On the File tab in the Backstage view, click on Info.

From the right side of the window, select Project Information, Advanced Properties. On the Summary tab, enter the Title of your project, your name and a brief description in the Comments box. Your project name will now appear in the project plan as your Zero Task / Project Summary Task. Using the Work Breakdown Structure that your created in the last assignment, enter your Summary Tasks and Detail Tasks into Microsoft Project. During this exercise, you may identify additional tasks that you didn't initially think of or you may decide to move things around a bit.

That is perfectly acceptable and common when you start building the schedule. It is a living, breathing document and does change throughout the course of planning. Use the Indent Task/Outdent Task buttons on the Task tab to create the hierarchy of your WBS. If you want to turn on the WBS numbering scheme, right-click the column to the right of where you want that column to appear, select Insert Column and select WBS from the list of available columns. Chapter 3 of the Ambriz book includes a lot of detailed information about entering tasks into Microsoft Project.

STEPS: Estimation: Once you have thoroughly decomposed the project's WBS by breaking larger tasks into smaller, manageable tasks you can continue to the next step which is estimation. Using one of the techniques presented in the reference material (your textbooks or the videos), estimate the effort required to complete each task. Determine for each task what the duration and work effort is. If you need to display the Work column in Microsoft Project, right-click the Duration column, select Insert Column and select Work from the list of available columns. Enter your estimates into your Microsoft Project schedule.

Remember, don't assign estimates to Summary tasks , the time necessary to complete the Summary task is based on the estimates of the Detail tasks that roll up to the Summary task. Dependencies: Create appropriate dependencies between your tasks. What tasks control other tasks? Use the Link button on the Task tab (or the predecessor and successor columns) to create dependencies between tasks. Double click the arrow between the tasks to change the dependency type.

You should be attempting to use a mixture of the dependency options offered in the software including: Finish to Start (FS), Start to Start (SS), Finish to Finish (FF), and Start to Finish (SF). Add Lag or Lead (Negative Lag) time where appropriate. Try to avoid adding constraints to tasks. Instead add deadline reminders where necessary. Tasks should have a "Start As Soon As Possible" constraint (default constraint) in order for the software to show the project team the impact of changes to the plan.

Chapters 5 and 6 of the Ambriz book includes a lot of information on linking tasks in Microsoft Project. Resources: Build out the project Resource Sheet and assign all resources to tasks. Add resources to your project using the resources sheet. Please define all type of resources including Work, Material and Cost. At a minimum, complete the following fields for each human resource: Resource Name, Type, Initials, Max, Std.

Rate, Base (Calendar). You can choose to use role names or birth names. For other resource types, complete Cost/Use. Once the resources have been added to the project file, assign those resources to the tasks that you defined in the project schedule. Multiple resources can be assigned to the same task if appropriate but first consider if the task should be broken down into smaller tasks and assigned to individual resources.

Resources should not be assigned to Summary level tasks . Chapters 7 and 8 of the Ambriz book include step-by-step instructions for completing these tasks. Once resources have been assigned to all Detail tasks you may find that some resources have been identified by the software as over-allocated. There is a red icon in the Indicator Column and in the Resource Sheet view the resource is red. Before the plan can be optimized and baselined, it will be necessary for you to address these over-allocations by having the software fix the over-allocations (Resource Leveling feature) or by manually adjusting the plan to alleviate the over-allocations (Resource Usage view).

Optimize and Baseline the Project Plan: a. When you are satisfied that over-allocated resources have been eliminated, you can then begin to review the plan and analyze it for any areas where changes can be made that will optimize the schedule for time and cost. Using schedule optimization strategies, decide which steps you want to take to attempt to shorten your project finish date and decrease project costs. Update your Microsoft Project Schedule accordingly. Through this process you may create new over-allocated resources.

If you do, address those over-allocations. Chapter 9 of the Ambriz book includes step-by-step instructions for optimizing your project schedule. Baseline the Project Plan: When you are satisfied that you have done your best to create the most efficient plan possible, save the baseline for the project plan so that you have a point in time to measure progress against.

Paper For Above instruction

Building a comprehensive project plan using Microsoft Project (.mpp) is a fundamental skill for effective project management. This process involves careful setup, detailed task entry, estimation, dependency creation, resource allocation, and finally, schedule optimization and baseline setting. Each step is critical for ensuring that the project is realistically scheduled, resources are appropriately allocated, and progress can be monitored accurately.

The initial step involves configuring Microsoft Project to align with project requirements. Accessing the Options menu via the File tab allows setting the schedule preferences, including opting for automatic task scheduling and selecting the task type—either Fixed Duration or Fixed Work—based on project characteristics. These choices influence how tasks are scheduled and rescheduled interactively as project variables change. Additionally, setting the project to be scheduled from the start date or the finish date helps establish the framework for subsequent planning activities.

Creating and customizing the project calendar is the next vital step. Modifying the Standard calendar to accommodate non-working days, holidays, or specific schedule constraints ensures that the project timeline aligns with organizational or regulatory calendars. The project start date, set through the Project Information dialog, anchors the schedule. Further, entering project details such as title, author, and brief description in the Advanced Properties section provides contextual information that enhances project documentation and identification.

Once the foundational setup is complete, the next phase involves importing or manually entering the Work Breakdown Structure (WBS). This hierarchical representation of tasks clarifies the scope and provides a structured approach to task management. Using the Indent and Outdent functions, tasks are organized into summary and detailed levels, ensuring clarity and enabling effective scheduling and resource allocation. If WBS numbering is required, it can be activated via the Insert Column function for better tracking and referencing.

Estimating task efforts follows, where each detailed task's duration and work effort are determined based on chosen estimation techniques outlined in course materials. Importantly, estimates should not be assigned to summary tasks, as their durations naturally roll up from their child tasks. Entering these estimates into Microsoft Project ensures that the schedule reflects realistic timelines and resource commitments.

Dependencies between tasks are then established to illustrate task sequences and control flows within the project. Utilizing the Link button or predecessor/successor columns, relationships such as Finish-to-Start, Start-to-Start, Finish-to-Finish, and Start-to-Finish are created, with lag and lead times added as needed to refine scheduling interdependencies. Maintaining constraints at the default “Start As Soon As Possible” ensures maximum schedule flexibility and visibility of the project timeline’s responsiveness to changes.

Resource management is a crucial component, where all relevant human, material, and cost resources are added to the Resource Sheet. For each resource, details such as resource name, type, maximum capacity, standard rate, and base calendar are specified. These resources are then assigned to tasks, ensuring workload and cost estimates are included in the schedule. Over-allocations are identified through indicator icons and resource views, prompting adjustments either through resource leveling or manual schedule modifications.

The final stages involve optimizing the project schedule to reduce time and costs. This includes reviewing resource allocations, adjusting task dependencies or durations, and leveraging schedule optimization techniques from the Ambriz textbook. Once the schedule has been refined to the best possible state, a baseline is saved. This baseline acts as a reference point against which project progress can be measured, enabling effective tracking and control throughout project execution.

In conclusion, building a project plan in Microsoft Project demands meticulous setup, detailed planning, and iterative refinement. By carefully executing each step — from configuration and task entry to resource management and schedule optimization — project managers can develop a realistic timeline, allocate resources effectively, and establish a solid foundation for monitoring project progress and ensuring successful delivery.

References

• Ambriz, J. (Year). Title of the textbook. Publisher.
• Kerzner, H. (2017). Project Management: A Systems Approach to Planning, Scheduling, and Controlling. Wiley.
• Meredith, J. R., & Shafer, S. M. (2019). Project Management: A Strategic Managerial Approach. Wiley.
• Heldman, K. (2018). PMP Project Management Professional Exam Study Guide. Sybex.
• Gido, J., & Clements, J. (2018). Successful Project Management. Cengage Learning.
• Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide). PMI.
• Schwalbe, K. (2018). Information Technology Project Management. Cengage Learning.
• Lock, D. (2020). Project Management. Gower Publishing.
• Leach, L. P. (1999). Critical Chain Project Management. Artech House.
• Lock, D. (2021). Advanced Project Management: A Structured Approach. Routledge.