This article was what kicked off the Microsoft TechNet “From the Trenches” column which I still write for. It addresses a key question: When deploying an EPM system should you a) make a big bang type of approach to release all designed EPM functionality at once or b) go with a more phased approach. And, if so, why?
Microsoft has published another article of mine on TechNet. This article is called “Cancelling your project without cancelling your career and will be of interest to both project managers and timesheet administrators as well, of course, to those managing stage gating processes, project management offices and project portfolios
Microsoft has published another of my articles, this one on Enterprise Systems Best Practices. This article looks at some of the key success/failure criteria to any enterprise system including, of course, EPM Systems. Those factors include: finding a business owner, knowing what problem the system is supposed to solve, making sure it’s part of your enterprise technical architecture and implementing change management.
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.
Microsoft maintains a column that I write on TechNet called “From the Trenches. My latest column there is entitled “Creating an EPM Deployment Plan” and discusses the elements of an EPM Deployment that are not just technical. From getting management on board with the original decision making requirements to ensuring that the solution solves the problem it was purchased for, this article opens the door to the many things that need to be considered in deploying an EPM solution.
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.
All too often project managers working on an EPM deployment get enthralled by their ability to do something and forget to ask “Should I do it?”.
I had the opportunity to be interviewed on my career and my views of the project management industry recently. Samir Penkar runs the Future of Project Management site at futureofprojectmanagement.com You’ll find the interview on the site just look for A few Key Decisions to take a look. It’s great to talk to others in the industry about trends and where things have been, where they are and where they’re headed in the coming years.
I was working with a large Canadian company recently, helping with their enterprise project management processes. As part of my work, I got to watch while a project control officer prepared a report for the Chief Financial Officer. It was a work of art. First data was grouped together from multiple projects in the desktop version of a popular project management system. That data was copied and then pasted into a massive Excel spreadsheet as…