Senior SAP Project Advisors to oversee your SAP implementation with strategic and tactical approach. Minimize project risks and ensure success by engaging independent advisors in your project leadership to advise on governance, execution, management, change control, organisational change and technical implementation of your new SAP system.
Our executive SAP project advisor brings in-depth SAP project management and technology expertise to oversee your SAP implementation. We provide executive oversight to your SAP project leadership and manage your systems integrator, solution delivery and project risks.
Our SAP Project Advisor will serve in your project leadership and be there for you right from project kick-off, blueprint and thru the go-live. With our depth and breadth of experience in SAP, we verify all PMO, business and technical deliverables including review of ECC/BI/PI SAP system implementation to help ensure success of your SAP project.
With our methods and tools, our SAP Project Advisor analyzes your stakeholders expectation and org structure to build a strategy and custom plan to navigate your organisation through the change in a effective way.
40,000+ SAP projects worldwide with lots of best practices and lessons learned to make every SAP project successful. CIO-VP best practices for SAP will not only result in significant cost savings but reduce project risks and ensure successful go-live.
Make sure that your project executive sponsor has verified that contract (SOW) has a well defined scope that include high level business requirements that must be fulfilled to transform your business successfully to SAP.
Interview and select your SAP systems integrator resources have the right level of expertise to deliver a high quality SAP solution. Some key roles on the project that must be interviewed include Delivery Executive (prior SAP solution delivery expertise), Project Manager (SAP project management experience), Solution Architect (2 or more full cycles SAP solution expertise) and SAP functional/technical leads (relevant SAP functional or technical expertise).
Project work plan should have a detailed work breakdown structures (WBS) that show tasks, activities and milestones that provide accurate visibility of project progress to the leadership. Ensure that the plan is properly resource levelled to ensure key essential resources are not over allocated.
All business requirements should be traced to a business process or non-functional attribute. SAP fit gap analysis should be performed on each requirement and should either have a standard SAP process covering the requirement or a RICEFW objects covering the gap. Finally every business requirement should be covered by at least one test scenario. This approach will ensure that the business requirements are covered with a solution and also tested thoroughly.
Business leads and business process owners should validate that each business process is tested adequately with all possible variations. Variations may be to different originating or destination applications, input or output criteria, etc. Business process variations can be tested in one test case or there can be multiple test cases covering the variations.
SAP project key deliverables such as BPRD (or BPD), fit gap analysis, RICEFW inventory, project charters, test plans, solution architecture, functional specifications, technical designs and other important project documents should be signed and approved by designated persons only after these deliverables are thoroughly reviewed by subject matter experts (and project advisor or program manager if needed). Under no circumstances should the project deliverables be conditionally approved without being "done-done".
We strongly recommend that large complexity (or effort) solution gaps indentified during blueprint should be verified with SAP America or SAP AG. This could help your team check if SAP has an alternate solution or one being built in a release that project could leverage. Thus your project could avoid building some high cost enhancements in the event an alternative exists with SAP.
A significant portion of SAP project realization effort is design, build and testing of RICEFW objects. Verify estimates and challenge effort with RICEFW objects in regards to assigned complexity and negotiate the priority of questionable or less business relevant RICEF objects. Make sure your systems integrator has provided you with effort matrix for high, medium and low complexity object of each RICEFW object type.
It is very important that OCM team has a actionable organisational change plan that incorporates feedback and action items from each business stakeholder. "Organisational Change Management Guide" document should be prepared that includes detailed strategy and execution plan to transform each unit of your organisation to SAP. This document along with periodic stakeholder satisfaction survey should be reviewed and approved by all stakeholders and approved by the executive sponsor of the project.
Every project should deploy a Change Control Review Board (CCRB) to ensure minimal "pain and suffering" on the project due to excessive change requests. The CCRB should be chaired jointly by the project executive sponsor and the project advisor. Project Advisor should review and challenge change requests that are questionable or otherwise could be avoided. Always look for alternatives to avoid or simplify the work effort or financial impact associated with each change request.