Reasons to Upgrade to Microsoft PPM 2013 That you May Not have Known

If your using a Project Server 2010 solution and are restricting the ability to ‘Set a Baseline’ to a particular ‘Group’ of people, you may have noticed that Project Mangers that don’t have permissions to ‘Save a Protected Basline’  you will find that they are able to update attributes found in the ‘Baseline’ table (or they can insert these baseline values into any view).

In Microsoft PPM 2013 this is now not possible; if you do not have access to save a baseline you will also not be able to change any of the ‘Baseline’ values.

You may have also found that the Team Planner feature would create constraints on tasks if you reassigned work in the team planner even if you didn’t change any dates.  This is now fixed in 2013, to learn more see the blog below.

In Microsoft Project 2010 when the ‘Critical Tasks’ highlighting was turned on the names of the assigned resources would disappear.  I always assumed that this was a bug in 2010 as I couldn’t think of a logical reason for this, perhaps it was to make the critical tasks stand out more. However, in 2013 this is fixed and the Resource Names remain visible when the ‘Critical Tasks’ highlighting is in place.

Project 2010 Before:

Project 2010 After

Project 2013 Before

Project 2013 After

Please let me know if I missed something, I would be very happy to hear it!

Hope this helps!  If you need some help with upgrading to 2013 we would be happy to help you with that please get in contact with us or check out the rest of our website.

Happy Upgrading!

Interested in how EPMA can help your schedules? Contact us today at 1.888.444.EPMA or enroll for one of our training classes.

Please feel free to leave comments below or check out our other blogs on Microsoft Project, Project Server, SharePoint and Project Management Methodology.

Follow us at @EPMAinc, linkedin, or facebook