Penny PM talks about How to best “Orchestrate” your acquisition project by aligning business requirements with legacy applications and SAP system requirements.
As we continue our Project Managers workshop this month, we will focus on the key business processes required to successfully orchestrate your acquisition project. Penny PM says, “Just like an orchestra contains many sections of string, brass, woodwind, and percussion instruments, an acquisition project contains many sections including people, culture, technology, day-to-day business and operations.”
Penny PM says, “As we’ve discussed, the most important thing to our customers is to be on-time, within scope and within budget; a Quality Management Plan provides the processes to ensure we have a successful project and a happy client.”
Our first step will be to define an Acquisition Project Plan by following five key project management business processes:
- Scope definition
- Project resources
- Project methodology
- Project timeline
- Organizational readiness
Helping our Business Stakeholders understand the importance of the following project management business processes will help to minimize the risk to both the project team and to the organization.
- Project Scope: Define strategic objectives, business drivers and guiding principles
- It is important to define corporate objectives and project scope for your business teams, non-SAP technical teams, SAP support teams and the project team.
- Are you merging the acquired employees into existing business and technical processes or are you going to accommodate the acquired companies policies and procedures?
- Guiding principles should be defined early to avoid confusion and duplication of work effort amongst all organizations and business and technology teams.
- Project Resources: Define governance structure, business teams by organization and project team by organization
- Reinforce the importance of defining the governance structure, communication and escalation procedures early in the project to avoid delays
- Teams to be defined: OCM, Business Structure, Governance Structure (Steering Committee, Senior Leadership, Key Stakeholders), as well as an SAP Project team for acquisition and sustain environment
- Project Environment should be created to support team requirements
- Project Methodology: Define approach and methodology used for the project and delivery
- Define the PMO procedures for Governance Reporting, Communication and Escalation procedures early in the project to avoid delays
- Define the approach for each project phase assuming use of ASAP methodology
- Integration Process and Communication: Define the communication plan to keep all teams engaged, informed and included through the decision process
- Project Timeline: Define Timeline considerations regarding operations, regulatory, employee union contract and non-contract requirements
- Types of things to consider:
- Operational transition
- Union transition/CBA
- Regulatory business requirements
- Training considerations
- Network integration
5. Project and Organizational Readiness: Define communication and readiness plans for the organization and employees to ensure successful transition
- Communication plan
- Employee training (business/operation)
- System access readiness
- Security access (building, network)
Penny PM states, “As our AspireHR Quality guidelines outline, we must understand our business objectives as well as our technical objectives to be successful. As the conductor of the Acquisition Orchestra, your role is to stress the musical pulse so that all the performers can follow the same metrical rhythm. In this case, it would be to keep the business, technology and the organization in sync to keep all the notes in line and the music sounding sweet.”
Click on this link to read more about our partnership with SAP as a certified member of the global quality accreditation program and diagram below.