Best practices to improve Resource Engagements performance

There’s been feedback that Project Online customers were experiencing page load delays and timeouts when trying to view Resource Requests. To address this, last month Microsoft published Best practices to improve Resource Engagements performance. This article provides customers with methods of preventing these errors, such as creating views that will help them to display only the proposed Resource Requests for users they manage. 

Training and video links

Here are a number of useful links to help with understanding Project & Project Online in a little more detail.

Useful books – they’re for 2013 but they will cover 98% of 2016

Create and manage up to 30,000 projects in Project Online

I’m pleased to be able to provide details of scaling and performance updates that the product team has announced today (3rd April 2017).  Please review the links below and speak to your deployment Partner, or me, if you have any questions.

30K Project Blog Post

Tune Project Online performance


Project / Project Server 2007 End of Life

The End of life (EOL) for Project 2007 applications and server takes effect on October 10, 2017.

Read the full article: Project Server 2007 End of Life Roadmap

What does End of Life mean?

Project Server, like almost all Microsoft products, has a support lifecycle during which we provide new features, bug fixes, security fixes, and so on. This lifecycle typically lasts for 10 years from the date of the product’s initial release, and the end of this lifecycle is known as the product’s End of Life. When Project Server 2007 reaches its End of Life on October 10, 2017, Microsoft will no longer provide:

  • Technical support for problems that may occur.
  • Bug fixes for issues that are discovered and that may impact the stability and usability of the server.
  • Security fixes for vulnerabilities that are discovered and that may make the server vulnerable to security breaches.
  • Time zone updates.

Your installation of Project Server 2007 will continue to run after this date. However, because of the changes listed above, we strongly recommend that you migrate from Project Server 2007 as soon as possible.

What are my options?

If you are using Project Server 2007, you need to explore your migration options, which are:

  • Migrate to Project Online
  • Migrate to a newer on-premises version of Project Server (preferably Project Server 2016).

Read the full article: Project Server 2007 End of Life Roadmap

Is the Hybrid Methodology the Future of Project Management?

In the past few years, agile methodologies have become more popular. Until recently, the prevalent view in the project management community was that the growth in acceptance of agile has been at the expense of waterfall. In other words, agile and waterfall are two fundamentally different approaches to project management. Each has its strengths and weaknesses, and in different scenarios each is relevant.

David Robins

Read the full article here: Is the Hybrid Methodology the Future of Project Management?

Connecting Project desktop client to Project Online – 2013 deprecated

Update 30th January 2017: Deadline extended to 30th June 2017

As of the 28th February 2017 the following versions of Project will no longer be able to connect to Project Online

  1. Project Professional 2013
  2. Project (Pro) for Office 365 (2013)

You will need to have deployed the following to connect Project to Project Online

  1. Project Professional 2016
  2. Project for Office 365 (2016) aka Project Online Professional / Project Online Premium

You should carefully review and read the full article:

This is what worked for me (I haven’t tried other combinations) from a clean install:

OPP = Office Pro Plus (the click-t0-run version of Office)

  1. Installed OPP2013 (2013) & Project for Office 365 (2013)
  2. Installed Project 2016 which upgraded OPP to 2016 (no choice)
  3. Uninstalled OPP 2016
  4. Re-installed OPP2013
  5. Now I have Project Online Desktop Client 2016 & Office 2013

I have not tried this via SCCM or similar deployment methods.

Updates to follow (5 JAN 17)