Last Updated: January 10, 2024

Activity 2 - Define Constraints

Activity Page Outline

Application 1 - Define Constraints Workflow (25 minutes)

Learn the Define Constraints Workflow (10 minutes)

Update Journal on Define Constraints Workflow (15 minutes) jump to

Application 2 - Define Constraints (2 hours 4 minutes) jump to

Initiate Define Constraints (1 hour 15 minutes) jump to

Exercise 1: Start the Constraints Analysis (30 minutes) jump to

Exercise 2: Write the Constraints Summary (15 minutes) jump to

Exercise 3: Start the Constraints Resister (30 minutes) jump to

Record Primary Constraints and Embed Constraints Related Objects (1 hour 24 minutes) jump to

Exercise 4: Enter Primary Constraints in Microsoft Project (25 minutes) jump to

Exercise 5: Embed Objects in Microsoft Project (10 minutes) jump to

Update Journal on Defining Constraints (15 minutes) jump to

There are three applications on the page. Complete each when directed in the MS Project Master Class Book.

This entire page should take 3 hours and 4 minutes to complete.

Define Constraints Workflow (25 minutes)

A workflow is a set of sequential or parallel processes or steps performed to complete a specific Activity in a project life cycle. It typically involves a series of interdependent tasks that must be completed in a particular sequence, often with specific criteria or conditions that must be met before moving on to the next step. The workflow for each Activity in this MS Project Master Class is the Activity (chapter) outline.

A specific Microsoft Project-defined constraints workflow is unavailable. Nor are there any defined constraints-related features in the software. However, the central focus of Microsoft Project as a project management software tool is to calculate and illustrate the primary project constraints of time, cost, scope, and resources. Essentially, one of the central functions of Microsoft Project is to be used as the validating tool for the primary project constraints.

Learn Define Constraints Workflow (10 minutes)

(jump to the top of the page)

When considering possible constraints for a project, it's essential to evaluate constraints across various categories to ensure comprehensive planning and management. The main categories of constraints to consider are:

1. Scope Constraints: These pertain to the project's boundaries, including what is in and out of scope. This can include specific features, deliverables, or functionalities the project must or must not include.

2. Time Constraints: Time-related constraints involve project schedules, deadlines, milestones, and any time-sensitive factors that may affect the project's completion. This can also include project duration and critical path considerations.

3. Cost Constraints: These constraints relate to the budget available for the project. This includes funding limitations, cost estimates, and financial resources for various project components.

4. Resource Constraints: Resource constraints encompass human resources, materials, equipment, and any other physical or intellectual assets required for the project. Assess availability and limitations in these areas.

5. Quality Constraints: Quality constraints specify the standards, benchmarks, and quality expectations that project deliverables must meet. This ensures that the project meets the desired level of excellence.

6. Technical Constraints: Technical constraints deal with the technology, tools, and infrastructure required for the project. They also include compatibility, hardware/software limitations, and technology constraints that may influence the project.

7. Regulatory and Compliance Constraints: These constraints involve adherence to legal, industry, and regulatory requirements. Ensure the project complies with all relevant laws and standards.

8. Environmental and Ethical Constraints: These constraints involve sustainability considerations, environmental impact, and ethical standards. They may influence the project's design and execution.

9. Stakeholder Constraints: Stakeholder constraints focus on the expectations, needs, and demands of project stakeholders, including clients, customers, sponsors, and team members.

10. Risk Constraints: Identifying and managing potential risks and uncertainties is essential. Risk constraints involve assessing and mitigating threats impacting the project's success.

11. Cultural and Social Constraints: In some cases, cultural and social factors may affect project execution, especially in international or culturally diverse projects.

12. Communication and Reporting Constraints: Establish constraints related to project communication and reporting. Determine how information will be shared and documented.

13. Change Management Constraints: Define how changes to the project scope, schedule, budget, or other constraints will be managed. This includes processes for requesting, approving, and implementing changes.

14. Security and Privacy Constraints: In projects involving sensitive data or information, security and privacy constraints are critical to safeguarding data and ensuring compliance with relevant laws and standards.

15. Supplier and Vendor Constraints: If external suppliers or vendors are involved, constraints related to procurement, contracts, and supplier performance should be considered.

By considering these categories of constraints, project managers can create a well-rounded understanding of the limitations, expectations, and potential challenges that may impact the project's success. This comprehensive evaluation allows for effective planning, risk management, and successful project execution.

(jump to the top of the page)

Define Constraints (2 hours 4 minutes)

In the dynamic realm of project management, understanding and effectively managing constraints is paramount to project success. This Applicaton is designed to guide you through key aspects of initiating and defining constraints for a project, followed by the crucial step of recording these constraints within Microsoft Project.

Section 1: Initiate Define Constraints for a Project

Exercise 1: Start the Constraints Analysis. Begin your journey by delving into the intricacies of constraints analysis. Learn to identify and assess constraints that may impact your project's trajectory.

Exercise 2: Write the Constraints Summary. Craft a concise and comprehensive summary that encapsulates the primary project constraints, clearly understanding their nature and implications.

Exercise 3: Start the Constraints Register. Dive into the practicalities of documenting constraints systematically. Establish a Constraints Register as a central repository for managing and tracking constraints throughout the project life cycle.

Section 2: Record Primary Constraints in Microsoft Project and Embed Constraints Related Objects (Constraints-related documentation)

Exercise 4: Enter Primary Constraints in Microsoft Project Transition from analysis to implementation as you learn to input primary constraints directly into Microsoft Project, ensuring alignment between your project plan and identified constraints.

Exercise 5: Embed Objects in Microsoft Project. Explore the synergy between project objectives and constraints by embedding objectives seamlessly within Microsoft Project. Learn to create a cohesive project environment that fosters successful constraint management.

Use your Master Project in all of these exercises. Finally, journal how you will likely use Microsoft Project to validate constraints and management stakeholder expectations.

Initiate Define Constraints (1 hour 15 minutes)

Conducting a constraints analysis, writing a project summary, and completing a constraints register is a pivotal step in the project management process and is essential for ensuring the project's success. The constraints analysis systematically assesses and categorizes the limitations and parameters shaping the project's scope, timeline, and resources. Project managers gain a comprehensive understanding of the project's operating boundaries by identifying scope constraints, time constraints, cost constraints, resource constraints, and many other factors. This, in turn, allows for better planning, risk mitigation, and the development of strategies to navigate and adapt to potential challenges. Defining constraints is the foundation for a well-informed project plan, enabling project teams to work within established parameters while delivering quality results and meeting stakeholder expectations.

Exercise 1: Start the Constraints Analysis (30 minutes)

First, perform a constraints analysis for your Master Project. Depending on the project, this could take a considerable amount of time. This exercise should take about 30 minutes, but considerably more time if you decide to facilitate a constraints analysis with stakeholders on your Master Project.

Primary constraints are:

• Budget (the total cost for the project)

• Timing (start date, duration, and finish date)

• Scope (these could be just the major phases of the project or major deliverables, or it could be quality or performance-related)

• Work (the total effort for the project in hours, days, or weeks)

You might have difficulty with the Work constraint, so skip that constraint for now if you don’t have a clue. Some organizations that are effort-driven sensitive usually start with estimates of Work because securing the labor determines not only the feasibility of the project but also the schedule. Other organizations tend to know the schedule and budget, and Work estimates or constraints emerge later during the planning phase.

If your Master Project is work-related, consider conducting a constraints analysis meeting with key stakeholders. You will be running many of these sessions during your career; if this is all new, it is an excellent time to start. If you do conduct a session with stakeholders, consider using the weighted voting system.

Using the Constraints Analysis Worksheet.xlsx for your Master Project, define these four primary constraints by listing each constraint and defining the parameters of the constraint. Ask: What are the budget, timing, scope, and work estimates?

You can not validate these primary constraints until you complete several subsequent activities in this MS Project Master Class. If you begin working with stakeholders on your Master Project, a constraints analysis will likely require more than one meeting.

There are four steps to a constraints analysis:

Step 1: Facilitate a brainstorming session with the project team and stakeholders to identify constraints. Explore various aspects such as time, cost, quality, scope, resources, and risk. Ask: Are the stakeholders and team members confident they have identified all constraints?

Step 2: Analyze and categorize the identified constraints based on their characteristics (e.g., time, cost, scope, and risk). Ask: Is each constraint associated with timing, cost, scope (quality or performance), risk, resources, etc.?

Step 3: Validate constraints by taking critical steps, such as engaging key stakeholders, reviewing project documents, consulting experts, etc. A detailed Microsoft Project plan validates timing, cost, scope, work, and resource constraints. Ask: Has each constraint been validated?

Step 4: Prioritize and then rank the constraints based on their significance and potential impact on the project’s success. Ask: What is each constraint’s level of influence and criticality in achieving the project's objectives?

You do not need to use the voting system for your Master Project.

Define the parameters when defining project constraints such as time, cost, and scope. Parameters refer to specific details or attributes associated with each constraint. These parameters help to define further and quantify the limitations and boundaries of the project. Here's how parameters are typically associated with each of the three primary project constraints:

1. Time Constraints:

   • Project Duration: The overall length of time allocated for the project.

   • Milestones: Key points in the project timeline that mark the completion of significant phases or deliverables.

   • Deadlines: Specific dates by which certain tasks, phases, or the entire project must be completed.

2. Cost Constraints:

   • Budget: The total amount of funds allocated for the project.

   • Resource Costs: The costs associated with labor, materials, equipment, and other resources required for the project.

   • Contingency Budget: Additional funds set aside to cover unexpected expenses or changes.

3. Scope Constraints:

   • Project Scope Statement: A detailed description of the project's objectives, deliverables, boundaries, and acceptance criteria.

   • Inclusions and Exclusions: Clearly defined items or features that are within or outside the project scope.

   • Scope Change Control: Procedures for managing and approving changes to the project scope.

These parameters help project managers and stakeholders understand each constraint's specific limitations and requirements. By clearly defining these parameters, the project team can work towards achieving project goals within the established boundaries and ensure that any changes are properly evaluated and controlled through the project management processes.

In the following figure, the primary constraints are defined for the Apollo Space Program as an example in the Constraints Analysis Worksheet Example. In this example, Scope consists of definitions for Safety, Technical, and Legal.

(jump to the top of the page)

Exercise 2: Write the Constraints Summary (15 minutes)

Write a constraints summary for your Master Project. The following are four examples of constraint summaries for different types of projects:

Construction Project 

"Commence the construction of a LEED-certified, 20-story office building in Manhattan for $100 million in 24 months, based on the architectural design and local building codes, starting on 1/1/2025."

Software Development Project:

"Develop a secure mobile banking app for iOS and Android platforms within 12 months, with a budget of $3.5 million, and adhering to defined functionalities and security standards. This project involves an estimated 25,000 person-hours of software development, testing, and quality assurance work, encompassing user-friendly features such as account management, fund transfers, secure authentication methods, and regulatory compliance."

Infrastructure Project

"Initiate the upgrade and expansion of the city's water treatment plant for $50 million, with a 36-month timeline, and focusing on a 20% capacity enhancement, environmental compliance, and water 50% increase in quality improvement, to be started by the second quarter of 2025."

Marketing Campaign:

"Launch a digital marketing campaign to generate 50,000 leads with a 200% ROI in six months, within a budget of $3.7 million, emphasizing digital channels and target audience reach. This project involves an estimated 15,000 person-hours of work in marketing strategy development, content creation, campaign execution, and analytics, and it must finish by the deadline of 6/1/2025."

(jump to the top of the page)

Exercise 3: Start the Constraints Register (30 minutes)

The project constraints register is a comprehensive repository of all the limitations, restrictions, and boundaries that can impact the project's scope, schedule, budget, work, and quality. There are several compelling reasons for establishing and continuously updating this resister. First and foremost, the constraints registry acts as a risk management tool. Project managers and teams can proactively plan and allocate resources to mitigate potential issues by identifying and documenting constraints early in the project. This foresight enables the team to develop contingency plans, minimizing the likelihood of costly delays or deviations from the project's objectives.

In addition, the constraints register promotes transparency and communication between the project team and stakeholders. It provides a shared understanding of the limitations that everyone must work within, reducing misunderstandings and conflicts. When all parties know the constraints, they can make informed decisions and adjust expectations accordingly, fostering a more collaborative and harmonious project environment.

There are three parts to this Constraints Register:

1. The constraints summary. This statement summarizes the primary constraints of time, cost, scope (major deliverables, quality, and/or performance), and work. This is the summary you wrote in the preceding exercise.

2. Constraints (most constraints have two or more parameters). For example, in the Apollo program, there was the Presidential Deadline: The program was under immense pressure to meet the ambitious deadline set by President John F. Kennedy to achieve a lunar landing "before the decade's end," which defines the program’s timeline. But there was also the aspect that achieving the deadline was critical for political and national prestige, as the program's success was closely tied to the Cold War space race and the desire to demonstrate American leadership in space exploration.

3. The plan or process for revisiting and communicating constraints to stakeholders.

For this exercise, complete all three sections for your Master Project:

• The constraints summary has been written; enter it in the Constraints Register.docx file.

• Then, use the constraints of time, cost, scope, and possibility work in the Constraints Analysis Worksheet, note different parameters for each one, and rank them in this document.

• Finally, create a plan for revisiting and communicating constraints.

The Planetary Society and an article titled An Improved Cost Analysis of the Apollo Program published in Space Policy provide a detailed analysis of the cost of the Apollo Program.

(jump to the top of the page)

Record Primary Constraints and Embed Objects in Microsoft Project (1 hour 24 minutes)

In this next section, you transition from analysis to implementation as you input primary constraints directly into Microsoft Project, ensuring alignment between your project plan and identified constraints. In addition, having learned how to embed constraints documentation within Microsoft Project, you will embed two additional objects (files).

At this point, it would help if you learned more about specific features in Microsoft Project. Those features are Views, Tables, Fields, the Organizer, and the Baseline. All of these features will be covered in-depth in this MS Project Master Class.

Exercise 4: Enter Primary Constraints in Microsoft Project (25 minutes)

As mentioned throughout this Activity or chapter, a central purpose of Microsoft Project is to validate the primary constraints of time, cost, scope, work, and resources.

In the initiation phase, time, cost, and work constraints can be entered into Microsoft Project. As the project plan is developed during the planning phase, the project manager can compare those initial constraints and what Microsoft Project calculates as the plan is developed. For instance, when the project is planned and cost calculated, that cost can be used to validate the cost or the budget constraint.

In this exercise, you will enter your initial time, cost, and work constraints. Scope and resource constraints are validated as the plan is developed.

In addition, this will be your first introduction to several features in Microsoft Project, such as:

• Views

• Tables

• The Organizer

• The Baseline

When you open a file in Microsoft Project, a particular view is always applied. When you open the Primary Constraints file a Gantt Chart view is active. With this particular type of view, a table is also applied to the view.

For the Primary Constraints.mpp file, the name of the view applied is visible in the view bar to the left of the display. In this case it is the Validating Constraints view.

A considerable amount of time will be spent working with views in this MS Project Master Class since views constitute a significant feature in Microsoft Project. For now, think of Microsoft Project as a database tool more than a spreadsheet and that there are two primary records in this database: tasks and resources. This particular Validating Constraints view shows a list of tasks, so it is a task-based view. There are 17 different types of views in Microsoft Project, all of which are either task-based or resource-based.

This Validating Constraints view is a Task Sheet type of view. This sheet type of view always has a table applied to it. A table is a collection of fields. Views and tables are also called Elements, and they are highly customizable. Current views and tables can be modified, and a practically unlimited number of new ones can be created. Also note, tables, like views, are either task or resource-based.

Because elements, like view and tables, are customizable and shareable, there is a tool in Microsoft Project for organizing all elements, and this tool is called the Organizer.

Before reading further, review the following definitions.

After reviewing these MS Project definitions, you will:

• Review the primary constraints compared to the data calculated by Microsoft Project in the Primary Constraints.mpp file.

• Take a closer look at the views, tables, and the Organizer.

• Share the Validating Constraints view and associated table with your Master Project.

• Enter your primary constraints for your project in the baseline fields of your Master Project.

Three groups of Project and Task fields are highlighted in the Validating Constraints view displayed in the figure below.

• Yellow: The fields in yellow are the calculated fields for the project. For example, 106 calendar days is the total calculated project period. These calculated fields are Duration, Start, Finish, Cost, and Work.

• Red: These are the baseline fields used to enter the initial constraints for the project.

• Green: These variance fields show the difference between the current calculated project data and the baseline.

The data in these fields provides the following information:

• The current duration is 106 working days, the original constraint was five months, and the variance is six days, meaning the project is shorter than the original constraint.

• The current start date is 1/1/25, and the original constraint was 1/16/25. The variance is -11 days, so the project is scheduled to start 11 days early.

• The current finish date is 5/28/25, and the original constraint was to finish by 5/1/25. The variance is 19 days, meaning the project finishes 19 working days, or working days defined by the project calendar rather than calendar days.

• The project's current cost is $15,200, and the original budget was $17,000. The project is currently under budget by $1,800.

• The current work, or effort, is almost 1,9991 hours, and the constraint was 1,500 hours. The project is 491 hours over the work or effort constraint.

In summary, the project started early, took less time, but finished almost a month later than wanted. It also takes 491 hours of more work but costs $1,800 less.

These fields in the figure above, along with the Task Name, Task Mode, Indicator, and ID fields, are called a table. The name of the table is not displayed anywhere in the display, but if you select the View tab on the ribbon and then Tables and More Tables, the name of the table is selected in the More Tables dialog box. Click the Edit button, and the table can be edited, inserting or deleting files, formating, etc. In the figure below, note that Task Name is a custom Title for the Name field in the table.

In this exercise, you could duplicate these fields in any table or create a new table to enter constraints for your project. But, an easier way is to take a few seconds and copy the view and table from the Primary Constraints.mpp file to your Master Project (your name).mpp file and then apply the Validating Constraints view to your Master Project. This involves the following steps:

• Ensure you have the Primary Constraints.mpp and your Master Project (your name).mpp files open.

• Open the Organizer by selecting File on the ribbon, click Info, and then click the Organizer to copy these elements to your Master Project.

• In the Organizer, ensure the Primary Constraints.mpp and your Master Project (your name).mpp files are selected on each side of the Organizer. It doesn’t matter which side of the Organizer a project is selected.

• Click the Validating Constraints view in the Primary Constraints project, and click the Copy button to copy the view to your Master Project.

• Click the Tables tab and Copy the Validating Constraints to your project like you copied the view.

• Close the Organizer and return to your project.

When you save your project, the copy of these two elements is saved to your Master Project.

Before moving on to the next step in this exercise, let’s quickly review some of the central views in Microsoft Project.

First, to follow along in this section on views, ensure the Primary Constraints project is the active project in Microsoft Project. You might have several of projects open; the active project is the one selected.

• The view currently applied is the Validating Constraints view. Note the following:

  • This view is task-based showing both Project and Task records.

  • This is a Task Sheet type of view. In this particular case, the naming convention for the view is the same as the type of view it is based on.

  • It has a table assigned with a theme of current, baseline, and variance for timing, cost, and work. Filter and Group elements are also applied.

  • There is no graphical display.

• Next, select the View tab on the ribbon, the Gantt Chart drop-down arrow, and then select Gantt Chart from the list. Note the following characteristics of this view:

• This view is task-based showing both Project and Task records.

• This is a Gantt Chart type of view.

• The Gantt Chart view is the central display in Microsoft Project because most people use this view (you can have unlimited Gantt Chart type of views) most of the time.

• Taskbars are graphically displayed.

• This type of view has a table applied along with Filter and Group elements.

Next, select the View tab on the ribbon and then the Resource Sheet command. Note the following:

• This view is resource-based.

• This is a Resource Sheet type of view. In this particular case, the naming convention for the view is the same as the type of view it is based on.

• This view is used primarily for defining resources.

• This type of view has a table applied along with a filter and group. If you look at the Data group on the ribbon in the figure below, the labels say [No Filer] and [No Group]. These labels are misleading, as you discover in later Applications where we spend more time on views. These labels should read, [All Resources] and [No Group Group]. In a View, there is always a filter and group selected.

Next, select the View tab on the ribbon and then the Network Diagram command.

• This view is task-based showing both Project and Task records.

• This is a Network Diagram type of view. Previously named PERT Chart. In this particular case, the naming convention for the view is the same as the type of view it is based on.

• This view is used primarily for viewing relationships between tasks and different task flows like critical path.

• This type of network in Microsoft Project is calculated as “Activity on Node,” vs. “Activity on Arrow.” The arrows in the following figure are dependencies or links.

• There is no table for this type of view even though you can view and edit tables. You just can’t apply any tables. The [All Tasks] filter and the [No Group Group] are applied.

Next, select the View tab on the ribbon and then the Task Usage command.

• This view is task-based. Project, Tasks, and Assignment records are shown.

• This is a Task Usage type of view.

• This view is used primarily for viewing project, task, and assignment records. For these three records, data is cross-tabulated, or to use Microsoft’s term, timephased.

• A Table, the [All Tasks] filter, and the [No Group Group] are applied.

Next, select the View tab on the ribbon and then the Resources Usage command.

• This view is resource-based. Resource and Assignment records are shown.

• This is a Resource Usage type of view.

• This view is used primarily for viewing resource and assignment records. For these records, data is cross-tabulated, or to use Microsoft’s term, timephased.

• A Table, the [All Resources] filter, and the [No Group Group] are applied.

To continue the exercise:

• Next, select your Master Project and apply the Validating Constraints view by selecting the View tab on the ribbon, the Gantt Chart drop-down arrow, finding the Validating Constraints view, and clicking the Apply button.

• Last, for your Master Project, and using the baseline fields on the Project Summary level:

  • If you have a project duration constraint, enter that duration in years, months, weeks, days, hours, or minutes in the Baseline Duration field.

  • If you have a project start date constraint, enter that date in the Baseline Start field.

  • If you have a project finish date constraint, enter that date in the Baseline Finish field.

  • Enter the cost constraint in the Baseline Cost field.

  • If you have a work constraint, enter that work in the Baseline Work field in years, months, weeks, days, hours, or minutes.

(jump to the top of the page)

Exercise 5: Embed Objects into Microsoft Project (10 minutes)

In the first Activity on Clarifing Objectives, you embed two spreadsheets in the notes field for the project summary task.

For this exercise, embed your constraints analysis worksheet and constraints registry documents in the notes field for the project summary task:

• Open the Notes field for the project summary task. Task Information / Notes tab.

• Click the Insert Object button.

• Select the Create from File radio button.

• Don’t select the Link button when you want to embed the object.

• Check the Display As Icon checkbox.

• Click OK three times.

Save the project. Remember, the files are embedded in the project. The only way to view or edit the embedded files is to open the project file and then the embedded file of interest by double-clicking the inserted object icon.

(jump to the top of the page)

(jump to the top of the page)

Review Microsoft Project Features Covered on Define Constraints (15 minutes)

This review delves into vital technical features of Microsoft Project. The Object Linking and Embedding (OLE) integration stands out by facilitating seamless interaction with external objects and fostering enhanced data interoperability, which is crucial for collaborative project environments. The software's provision of diverse views, including customizable Gantt Charts and Network Diagrams, ensures tailored data presentation to meet varied stakeholder needs.

The Organizer Tool efficiently manages project elements, templates, and macros, promoting organizational consistency across projects. Furthermore, Microsoft Project allows for granular customization of tables and fields, empowering project managers to focus on specific metrics for precise tracking and reporting.

A cornerstone in effective project management, the Baseline Functionality offers a snapshot of the project's original plan. This feature facilitates accurate tracking and enables proactive decision-making, ensuring projects stay on course. In summary, these technical features underscore Microsoft Project's commitment to precision, collaboration, and adaptability in project management.

OLE

OLE (Object Linking and Embedding) is a technology used by Microsoft Project to allow users to link or embed data from other applications, such as Microsoft Excel, Word, or PowerPoint, into their project files.

Views

Views in Microsoft Project play a crucial role in how project data is displayed and analyzed. They offer project managers a variety of perspectives on project information, aiding in decision-making, monitoring progress, and communicating project status. 

Views make a project multidimensional. The project manager uses views to walk around a project suspended in air and look at it from many perspectives. 

The following is a summary of views in Microsoft Project.

Overview of Views: In Microsoft Project, a view is a particular way of displaying project data. These views are designed to present project information in a manner that is most relevant and useful for specific records like the project, task, resource, and assignment. They are instrumental in creating a visual representation of project data, making it easier to understand and work with.

Standard Views: Microsoft Project offers a range of common views, including but not limited to:

• Gantt Chart - The Gantt Chart view is popular and widely used. It visually represents tasks, their start and end dates, and their dependencies, allowing project managers to see the project schedule at a glance.

• Task Sheet - The Task Sheet view displays project data in a tabular format, making it easy to enter and edit task details, such as task names, durations, and resources.

• Task Usage - This view is task-based, but the assignment records are provided, and data like work and resource availability are cross-tabulated (timephased) over time.

• Resource Sheet - This view focuses on resources, showing resource names, definitions, and allocation details, which helps manage resources.

• Resource Usage - This view is resource-based, but the tasks each resource is assigned are provided. Data like work and baseline work are cross-tabulated (timephased) over time.

• Network Diagram - The Network Diagram view illustrates task relationships and dependencies in a graphical format, visually representing how tasks are interconnected.

Custom Views: Beyond the standard views, Microsoft Project allows users to create custom views tailored to their specific project management needs. Custom views enable you to define and arrange columns, filters, grouping, and sorting options according to your project's unique requirements.

Customization and Configuration: Views can include specific columns, sort orders, filters, and grouping options. This allows users to adapt views to their unique project management needs. Customized views can then be saved and reused, which is especially beneficial when managing similar projects.

Switching Between Views: Microsoft Project lets users switch between different views easily, ensuring you have the proper perspective. Views can be accessed through the "View" tab, and users can switch between them as needed.

Reports and Printing: Views are a foundation for creating reports and printing project data. Users can generate reports that showcase project information in a structured and understandable format by selecting the appropriate view.

Data Analysis and Decision-Making: Views are indispensable for data analysis, enabling project managers to make informed decisions. The visual representation of data helps spot critical tasks, identify delays, manage resources, and assess project progress.

Views in Microsoft Project are a central feature, offering many ways to visualize and interact with project data. They enhance project planning, tracking, and reporting, enabling project managers and teams to make informed decisions, collaborate effectively, and ensure successful project outcomes.

Fields

Fields in Microsoft Project are data containers that encompass standard and custom fields. Standard fields cover essential project details like task names, dates, and resource assignments. Custom fields allow for project-specific data collection. These fields serve multiple functions, from data entry to calculations and analysis. They're crucial for tracking project progress, allocating resources, and creating tailored reports. Customizing fields and adhering to data consistency standards ensures that project management practices remain flexible and standardized across various projects by deciding which data is included in reports and how they are structured.

Tables

Tables in Microsoft Project are essential tools for organizing and displaying project data. They provide users with a structured, customizable way to view, edit, and analyze project information. Here's a summary of tables in Microsoft Project:

Data Organization: Tables in Microsoft Project serve as a structured framework for organizing and presenting project data in different themes. They determine which fields and data points are displayed in various views, making it easier for users to access and work with project information.

Customization: Microsoft Project offers a variety of built-in tables designed for different project management needs, such as "Entry," "Cost," and "Tracking." Users can also create custom tables tailored to their specific project requirements. Customization options include adding or removing columns (fields), adjusting column order, and applying filters.

Columns (Fields): Tables are composed of columns, which represent project data fields such as name, duration, start date, resource names, and cost. The choice of columns in a table can be adjusted to display the most relevant information for a particular task or objective.

Data Entry and Editing: Tables facilitate data entry and editing by providing a clear and organized layout for inputting or modifying project details. Users can update task durations, dependencies, resource assignments, and other project data directly within the table.

Views and Reports: Tables are closely linked to views and reports in Microsoft Project. When you select some views, they are associated with a table that determines how data is displayed. Tables play a critical role in generating reports by deciding which data is included in reports and how it is structured.

Switching Between Tables: Microsoft Project allows users to switch between tables quickly and easily. Selecting an appropriate table depends on the specific task or project aspect you are focusing on. Users can access tables through the View tab in the software.

Custom Tables for Unique Needs: Custom tables are valuable when managing projects with unique requirements. Users can create tables displaying fields relevant to their industry, project type, or organization, helping streamline data entry and analysis.

Data Analysis and Decision-Making: Tables are crucial in data analysis and decision-making. By presenting relevant project information in an organized manner, they enable project managers to assess progress, identify issues, allocate resources effectively, and make informed decisions.

Consistency Across Projects: Organizations can maintain standard data management practices by consistently creating and using custom tables across multiple projects. This ensures consistency in project reporting and analysis.

Tables in Microsoft Project are a fundamental component of effective project management. They provide an organized structure for displaying and manipulating project data, allowing users to tailor their views to their specific project needs. Tables enhance data entry and editing, facilitate data analysis, and contribute to better decision-making in project management.

Tables are applied to various views, such as the Gantt Chart or Resource Usage views. Any number of tables can be applied to any particular view.

In the figure below:

A - The name of the applied view.

B - The name of the applied table to that view.

C - Fields selected for the table.

Organizer

The Organizer in Microsoft Project is a tool that allows project managers to efficiently manage and maintain project-related elements such as custom views, tables, filters, groups, fields, and even macros. Here's a detailed summary of how the Organizer functions in Microsoft Project:

Purpose of the Organizer: The Organizer is a central feature in Microsoft Project designed to help users organize, store, and manage project-related custom elements. It is beneficial when you want to maintain consistency across multiple projects or share custom elements with other users.

Accessing the Organizer: To access the Organizer, open Microsoft Project and go to the File tab on the ribbon. From there, choose "Info" and then select Organizer. 

Transferring Custom Elements: One of the critical functions of the Organizer is to enable the transfer of custom elements from one project to another. This is especially valuable when you have standard templates or custom configurations that you want to apply to multiple projects.

Ensuring Consistency: The Organizer promotes consistency in project management. It ensures that the same views, tables, filters, groups, fields, and macros are used across projects, reducing errors and streamlining workflows.

Time-Saving and Efficiency: The Organizer saves time and enhances efficiency by allowing users to store and share custom elements. Project managers can access pre-configured views, filters, and other elements, eliminating the need to recreate them for each project.

The Organizer in Microsoft Project is essential for maintaining consistency, enhancing efficiency, and promoting collaboration in project management. It allows users to store, manage, and transfer custom elements like views, tables, filters, groups, fields, and macros, making it an invaluable tool for project managers working on multiple projects.

Baseline

There is a general idea or understanding of a baseline and its use in project management. All of the following baseline uses are for various types of reference. 

Constraints Validation: Primary constraints, such as time, cost, and work, can be entered in the baseline on the summary level. Once the project plan is fully developed, those constraints are validated. 

Initial Project Snapshot: A baseline represents the initial project plan, capturing key parameters such as task durations, start and finish dates, resource assignments, and costs at the project's outset. This snapshot provides a benchmark for project performance.

Performance Comparison: Throughout the project's execution, the baseline compares against the current schedule and resource allocation. Project managers can assess whether the project is on track or if there are delays, cost overruns, or resource allocation issues.

Variance Analysis: By comparing the baseline to the current project data, Microsoft Project calculates variances in task durations, costs, and other factors. This variance analysis helps project managers identify deviations from the original plan and take corrective actions.

Performance Tracking: The baseline allows for effective progress tracking, as it highlights discrepancies between planned and actual project performance. This enables project managers to make informed decisions to keep the project on course.

Communication and Reporting: The baseline data is instrumental in generating reports and communicating project status to stakeholders. It provides a transparent and standardized reference point for the project's health and progress.

Change Management: When changes occur during the project, the baseline can help evaluate their impact on the project's original plan. This information aids in deciding whether to accept or reject changes and their implications.

Risk Management: Identifying deviations from the baseline early in the project allows project managers to promptly address potential issues and risks. This proactive approach helps in risk mitigation and avoiding last-minute crises.

Forecasting and Planning Adjustments: Project managers can make informed forecasts and adjust the project plan based on baseline data and variance analysis. This adaptability is essential for addressing evolving project requirements and uncertainties.

Audit Trail: The baseline provides an audit trail by documenting the initial project plan and subsequent changes. This historical record can be valuable for post-project analysis, audits, and lessons learned.

Project Closure: When the project is completed, comparing the final project data to the baseline helps evaluate the project's success, highlighting achievements and areas where lessons can be applied to future projects.

Backup: Eleven baselines can be saved.

The baseline in Microsoft Project serves as a foundational reference point for project management. It measures, analyzes, and tracks project performance, detects variances, facilitates communication, guides decision-making, and provides valuable insights throughout the project's life cycle.

In this Activity, we entered baseline values to validate primary constraints when we plan our project. We did not review the baseline; Activity 12 is all about saving and using the baseline. In the figure below:

A - Duration Variance (current duration - baseline duration).

B - Start Variance (current start - baseline start).

C - Finish Variance (current finish - baseline finish).

D - Visual representation of the current schedule vs. the baseline schedule.

(jump to the top of the page)

(jump to the top of the page)