Business buy-in is not just helpful -- it is difficult, if not impossible, to have a successful project without it. The business needs to understand the benefit of the new system to participate. It is imperative to understand and document the requirements. That is a complete and valid blueprint.
There is a very real possibility that there may be scope creep. Additional functionality may be included or encouraged, due to reengineering. Is this necessary and beneficial? The project management needs to make that decision, as well as to what extent each can flex, in terms of functionality and resources. What can be Phase II, for example? And what cost overrun or additional time delay may be acceptable to meet the reengineered process?
The bottom line is to remove the barriers to success. Have one vision, agreed upon by functional and technical sides of the project. Set realistic goals and timelines.
SAP gets nod from Microsoft for core HCM
Dig Deeper on SAP HCM
Related Q&A from Sheryl Springer Middleton
An SAP HR users wants to know how to assign a person to two different personnel numbers in SAP HR while generating a single invoice. Continue Reading
SAP HR expert Sheryl Middleton explains how to view data in quota overview tables after running Time Evaluation in SAP HR. Continue Reading
An SAP HR user wants to know if there a way to automatically calculate an allowance in SAP HR that is based on the basic salary of the next higher ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.