Requires Free Membership to View
When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.
Hannah Smalltree, Editorial Director
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.
This was first published in November 2009
Join the conversationComment
Share
Comments
Results
Contribute to the conversation