PM artifacts

Some of the major artifacts that we created during the project implementations are listed below.

Staffing plan: This linked example was developed to aid in creating the staffing plan (Tab 1) as it is derived from the project's work breakdown structure (Tab 2). Click here to view.

RACI: Governance requires transparency throughout the project plan phases in conjunction with ASAP methodology. Click here to view.

Development objects tracker: Development objects are ranked by priority, with estimates for each of the phases (analysis, technical specification creation, build, unit test and approval) based on the object type and complexity level. Click here to view.

Macro to load the build timeline into MS Project: This macro when executed in MS Project uploads the Development objects timeline as a project plan where it is easier to perform resource leveling and assignment. Click here to view.

Cutover planning: This is one of the most important sub-phase during the SAP implementation. Task falls under IT, Business continuity and OCM domains. The optimal time to kick this off is right after exiting UAT test cycle. By that time we should know what tasks, resources, timelines and duration are required to make it go live. It also gives the business partners enough time to start non-IT tasks such as letting their vendors and other partners know to plan the transition on their side. At some clients a Dry run is performed two weeks prior to the Go live to execute the Cutover plan and fine tune it further. Click here to view the sample SAP Upgrade cutover plan.

Testing agenda: This is created a several of weeks before exiting the build phase. We get buy-in from all the stakeholders and their commitment to participate in UAT phase. It has tabs to cover each area of an enterprise such as FICO (Treasury, Tax, BPC, Capital and Corp a/c, AP, AR), BI, MM, HR, EAM and more. Click here to view a snapshot of the agenda. We also employed 100% Data validation test process (all the loaded records were compared against the load files on key and important fields) using VBA macros. Only when we met a threshold or had remediation identified we moved to the business validation phase. Click here to view our Test approach details.