ERP software implementation projects are notorious for taking too long, going over budget and failing to deliver. But some manufacturers are having more success by adopting general-purpose project management methodologies, software tools and techniques that bring discipline and greater predictability to projects of any kind -- IT or otherwise. They’ve learned that knowing something about the project management discipline can make the...
difference between ERP success and failure.
The chief benefit of ERP project management is how it brings best practices to formulating project scope and managing change, according to Margo Visitacion, a vice president and analyst at Forrester Research.
“The reason ERP stumbles and falls as a project is you don’t have the appropriate person doing communication throughout the organization, and you don’t have appropriate scope management,” Visitacion said. “There’s a lot of cultural change that comes with ERP. You’ve got to have the right stakeholders involved along the way.”
Scope, time and cost are the three main constraints of any project, and they are often depicted as corners of a triangle: Change one, and the other two are affected. Philosophies about how to manage the constraints seem as numerous as the ERP software options. What all project management approaches have in common is a methodical process for bringing ideas to reality through careful planning, design, execution and testing, all documented in ways that encourage stakeholder cooperation and accountability. Above it all is a software-enabled process for controlling and monitoring work so it stays on task, on schedule and under budget.
What a PMP knows
Most project managers in North America are certified by the Project Management Institute (PMI), receiving the title project management professional (PMP) after training in the Project Management Body of Knowledge (PMBOK -- pronounced “pimbok”). A competing organization called PRINCE2 dominates certification in the United Kingdom and a few other countries.
PMBOK-managed projects have five major phases: initiation, planning, execution, monitoring, and closing.
“It’s a guideline -- it’s not a rule,” said Sanjay Swarup, an electrical engineer and PMP who chairs the PMI’s special-interest group for information systems.
The planning stage includes requirements management as well as identifying tasks and estimating their duration. Execution covers system design and deployment and any development required for custom applications or data integration. In the closing phase, the project manager closes the financial books and handles remaining administrative issues, such as releasing the project team and specifying the vendor’s post-deployment obligations.
Requirements management is one of the most important planning steps because it sets the tone for the entire implementation project.
“It is very important to record all the requirements very early in the document and have the agreement of the customer,” Swarup said. “It can have impact on the scope, the schedule, [and] the cost.”
The process often includes the drafting of a requirements traceability matrix (RTM), a table -- not technically required by the PMBOK -- that shows all project requirements and documents for their design, planning and testing. Swarup said he has seen ERP projects go off track when requirements were piled into documents that exceeded 200 pages without an associated planning document to show how the requirements were to be executed.
“Everything is in trouble at that point,” Swarup said.
Visitacion agreed that poor requirements planning is often where projects go wrong, even at the biggest companies. “If you don’t alert your users to the cultural changes that are coming along, you’re not going to have the right requirements defined,” she said. “A requirement is not just looking at what you want to do, but how you want to do it.”
Where to get good project management
There’s “lowercase” project management that everyone says they do, and then there’s the more rigorous kind, backed by academic research and methodologies and run by people certified to apply them. Is there a middle ground, a way to bring disciplined project management to ERP implementations without hiring PMPs?
“A PMP does not a great project manager make,” Visitacion said, acknowledging the title provides a level of assurance that matters to some companies. “A PMP definitely has the knowledge around the practices, but it doesn’t necessarily mean they’re an experienced project manager. I wouldn’t focus on whether they’re a PMP, but whether they have the track record. Some of the best project managers I know only recently got their PMP.”
Swarup, whose day job is as project manager for the global consulting firm, Cap Gemini, claimed PMPs are more committed to maintaining project discipline. “In our company, getting certified is a job requirement,” he said.
Besides consultants and in-house PMPs, manufacturers can find similar expertise in their ERP vendors, and ERP systems are typically sold with the vendor’s implementation methodology. But consultants seem divided on whether the vendor methodologies are adequate, and PMPs say regardless, they don’t help to manage multiple, often unrelated projects in portfolios that draw on shared resources.
Some companies, especially larger ones, centralize management of all major projects in a project-management office (PMO). But having a PMO doesn’t guarantee the use of formal methodologies and enabling software.
That’s what Sri Donkena, PMP, found when he went to work for Hydro One, a Toronto-based power-transmission company that is implementing mobile ERP connections for its field workers. “Everything is scattered,” Donkena said, referring to the company’s multiple budget spreadsheets. “There’s no way one person can go and see everything.”
However, Hydro One’s PMO puts a business and IT people under the same umbrella -- a best practice, in Donkena’s view -- and he is pushing to consolidate the company’s project systems. “It’s a big cultural change,” he said. “They are used to their own systems and their own applications, and they feel that it’s already there, so why are we making a change now?”
Donkena had previously managed a major ERP software implementation at Apotex, a Toronto-based manufacturer of generic drugs, working with consultants from Deloitte Canada. The project came in on time and under budget even after the scope was enlarged. Donkena instituted a streamlined, 5-10-page “project charter” (another PMBOK document) that described the high-level requirements approved by Apotex’s line-of-business managers. The charter fed into a longer requirements document, and both formed the basis of an RTM.
Donkena attributes the success to the company’s use of formal methodologies and PMPs, know-how Apotex developed over six years by sending around a dozen employees annually to PMP training.
Is all that training really necessary? Donkena said it is hard to learn how to apply the PMBOK just by reading it. Still, he said, many companies can benefit from following at least some of the PMBOK steps to bring more structure to their ERP implementations.