New And Deprecated Features For Project Server 2016 Compared To Project Server 2013


In this article, I will explore the new and deprecated Project Server 2016 features compared to Project Server 2013.

What are the new features?

Create New Project Wizard Experience.

In Project Server 2016, you can easily create a new project through a wizard consisting two steps.

  • The first step is to select the Project Type.

    • Enterprise Project.
    • SharePoint Task List.

  • The second step is to fill the basic project information (PDP).

In Project Server 2013, the new Project Wizard Experience is not available. Meanwhile, you can also easily and quickly create your project by

  • Clicking on "Create and Import Project".

  • Then, provide your Project name.

  • The project should now be listed in Project Center and you can fill its project information later.
New TimeLine Options

The timeline is a graphic design showing the project summary as a long bar labeled with dates, the project managers are using the timeline to easily compare between multiple projects at one place.

Multiple TimeLine

In Project Server 2016, you can easily add multiple timelines to can group similar projects/tasks at the Project Center or schedule page.

Set Date Range

You can use set Date range option to customize the timeline to show only a specified date range.

In Project Server 2013, you can only add one timeline at Project Center or Schedule page, and there is no option to set Date range.

Project ellipsis

In Project Server 2016, specifically in Project Center, you can easily show the project information summary like

  • Percentage Complete.
  • Owner.
  • Last Published Date.
  • Open, Share and more option.

In Project Server 2013, the project ellipsis is not available, and to show the project details you have two option:

  • Configure the required columns in project center grid, then scroll horizontally to show it.
  • Click on the project name and show the project information at the project page detail.

Resource Engagements

Project Server 2016 Resource Engagements is a replacement of the old Resource Plan in Project Serve 2013. It helps project/resource managers to easily manage resources on the specific amount of work and time periods through an approval process.

In Resource Center, the Project Manager can request a new resource to his project.

And Resource Managers can easily manage the engagement accuracy and efficiency.

Also, there are new efficient views like Resource Utilization.


Resource Plans are not supported in Project Server 2016. Meanwhile, it's supported to migrate Project Server 2013 Resource Plans to work as Resource Engagements in Project Server 2016.

Project Standard 2016 & Project Professional 2013 did not include resource engagements. it's only available if you're using Project Professional 2016, connected to Project Online or Project Server 2016.

Resource engagements support approval requirements. Meanwhile, the project manager can assign a resource without approval.
In Project Server 2013, there is no approval engagement process. there is a simple toolbar without resource request option.

Limited views capability.

Project client compatibility

In Project Server 2016,

  • Project Professional 2016.
  • Project Online Desktop Client.
  • Project Professional 2013.(Not support resource plan)

In Project Server 2013,

  • Project Professional 2016.
  • Project Online Desktop Client.
  • Project Professional 2013.
Hardware and software requirements

Since Project Server 2016 runs as a service application in SharePoint Server 2016. so you just need to checkHardware and software requirements for SharePoint Server 2016 . see also Is SQL Server 2016 SP1 supported for SharePoint 2016?

In Project Server 2013, Check Hardware and software requirements for Project Server 2013 .

One installation

One of the biggest changes in Project Server 2016 is the installation process. where

  • A separate installation is no longer required as it was in previous versions of Project Server.
  • The SharePoint Server 2016 MSI file will contain the installation files for Project Server 2016 as well.
  • Project Server 2016 runs as a service application in SharePoint Server 2016.

  • Project Server 2016 is only available on SharePoint Server 2016 Enterprise.

Although Project Server 2016 is included as part of the SharePoint Server 2016 Enterprise installation, it still requires a separate license. See also, Install and Configure Project Server 2016

In Project Server 2013, a separate installation is required, the project server 2013 has its independent installation files.

Base installation languages and language packs

Individual language packs for Project Server 2016 are not available, SharePoint Server 2016 language packs will match languages for both Project Server 2016 and SharePoint Server 2016.

In Project Server 2013, Project Server 2013 and SharePoint Server 2013 language packs were installed separately.

There is no a ProjectWebApp Database

In Project Server 2016, a single database (SharePoint Content Database) holds the project data and the content to facilitate the database operations, such as backup and restore, migration, etc.

In Project Server 2013, A separate Project database is created for each Project Web App instance.

  1. Project Web App database.
  2. Content database.

In Project Server 2010, there are 5 databases:
  1. Draft Database.
  2. Archive Database.
  3. Publish Database.
  4. Reporting Database.
  5. Content Database.
Custom fields limit

To improve performance in Project Server 2016 reporting, there are limits to the single-value custom field.

Project / Timesheet / Tasks / Resource custom fields limits.

  • 450 text fields.
  • 450 lookup tables.
  • 450 of all other custom field types (cost, date, duration, number, flag).

What's deprecated or removed?

Resource Plans

As we mentioned above, In Project Server 2016, Resource Plans has now evolved into Resource Engagements.

My Tasks

Because of The Work Management Service Application has been removed in SharePoint 2016, The My Tasks and associated Exchange Task Sync features have been removed.

Project Server Interface web service

PSI is not supported in Project Server 2016.

Manage Project Web Apps

In Project Server 2013, you can create a PWA instance theough Central Administration as shown below.

In Project Server 2016, you can’t provision a PWA instance theugh Centeral Administration.

In this case, The PWA instance should be provisioned via PowerShell cmdlets as mentioned below,
  • Open the SharePoint 2016 Management Shell as Administrator.
  • Type the below cmdlet to create a PWA instance in Project Server 2016:
  1. New-SPSite -ContentDatabase PWA_Content -URL http://SiteCollectionURL/PWA Jump -Template pwa#0 -OwnerAlias "domain\useraccount"
  • Type the below cmdlet to enable ‘pwasite’ feature to turn on Project Web App site collection features.
  1. Enable-SPFeature pwasite -URL http://SiteCollectionURL/PWA


In this article, we explored the new and deprecated Project Server 2016 features compared to Project Server 2013.


Simply, what’s new and deprecated in project server 2016?

See Also

Configure Project Server 2016