I am delighted to see another of my articles in the “From the Trenches” column on Microsoft’s TechNet. I’ve been doing these pieces for the Microsoft Project technical area of the the TechNet website for a number of years and am very flattered that they continue to ask for them and, even better, publish them! […]
Many organizations deploy enterprise systems and many of these deployments generate tremendous efficiencies in the organization. However, some organizations get tempted to deploy more than one enterprise system at the same time and this can lead to a tremendous challenge or even failure of both systems. In some cases, the two systems are pushed into one massive project, in other cases, separate teams pull the company into different directions at the same time. This article looks at the particular challenge of doing more than one enterprise system deployment at a time.
Most articles here talk about the strategic intent of enterprise timesheet and enterprise project management systems. But, not doing your homework on the operational side of the house can cause lots of mischief after a system has been implemented. Here are some of the best practices on enterprise systems we’ve encountered over the last few years.