![]() ![]() The next time you have this discussion internally, think about these points. You don’t have software assurance, and you’re trying to get the most out of your existing purchase.You would have to incur an additional software or hardware expense to deploy the update.Software bugs have workarounds that you’re satisfied with.If you’re not using Project Server or Project Online, you may not need critical updates to continue running your projects.In my experience, lots of larger corporations upgrade software only every three years.Here are some reasons why you might want to keep the same version: Making the Case for Staying with the Same Version If you’re using Project 2013 Pro or Standard, here are the dates to care about: Here’s how it worked for Project 2007:įor Project 2010 Pro and Standard Project 2010 Server, here are the crucial dates: You have Project Server or Project Online, and you need to keep your Microsoft Project versions aligned with your enterprise software.Ĭurious about end of life for your Project software. ![]() You feel a new feature could solve a problem you’re having or could add business value or.Your current version is out of the support period by Microsoft, which means that service pack updates or bug fixes are no longer available.Your company has software assurance and upgrades are included with this service.You have experienced a software bug that has been fixed in a later version.Here are some reasons why you might want to upgrade: ![]() And why not? As of right now I work with clients who have all of these versions: Microsoft Project 2003, 2007, 2010, 20 as well as Project Pro for Office 365. I receive a lot of questions from customers asking if they should upgrade to the latest version of Microsoft Project.
0 Comments
Leave a Reply. |