Podcast
Questions and Answers
Explain the potential advantages and disadvantages of using a consulting partner to manage an ES implementation project versus attempting an internal implementation.
Explain the potential advantages and disadvantages of using a consulting partner to manage an ES implementation project versus attempting an internal implementation.
Consulting partners bring expertise and manage complexity, but can add costs. Internal implementation can be more cost-effective but may lack specialized knowledge.
What are the three main parties typically involved in an ES implementation project, and what role does each play?
What are the three main parties typically involved in an ES implementation project, and what role does each play?
The three parties are the vendor, implementation partner, and buyer (beneficiary). The vendor provides the software, the implementation partner assists with the implementation, and the buyer is the company implementing the ES.
What are the key differences between Vanilla Implementation and Customized Implementation strategies of an ERP system and the impact each has on integration with new versions?
What are the key differences between Vanilla Implementation and Customized Implementation strategies of an ERP system and the impact each has on integration with new versions?
Vanilla implementation follows standard vendor processes and is easier to integrate, whereas customized implementation is tailored to specific needs, increasing time/cost and reducing ease of integration with new versions.
Explain different types of go-live strategies (Big Bang, Parallel Adoption, Mini-Big Bang) and discuss which one is the riskiest for large companies.
Explain different types of go-live strategies (Big Bang, Parallel Adoption, Mini-Big Bang) and discuss which one is the riskiest for large companies.
Describe the 'cutover phase' in an ERP implementation project, and list at least three critical activities that occur during this phase.
Describe the 'cutover phase' in an ERP implementation project, and list at least three critical activities that occur during this phase.
Define what constitutes a 'project' and 'project management'.
Define what constitutes a 'project' and 'project management'.
List five roles a Project Manager must undertake to ensure the successful completion of the project.
List five roles a Project Manager must undertake to ensure the successful completion of the project.
Explain the 'Three Factors of Success' in project management and how they are related.
Explain the 'Three Factors of Success' in project management and how they are related.
Identify at least three key sources of risk that can impact an implementation project.
Identify at least three key sources of risk that can impact an implementation project.
Explain how a risk prioritization chart (impact vs. probability) is used in risk management and why it is important.
Explain how a risk prioritization chart (impact vs. probability) is used in risk management and why it is important.
Give the names of at least three different 'Risk Management Approaches' and provide a short description of each.
Give the names of at least three different 'Risk Management Approaches' and provide a short description of each.
List at least five factors that significantly influence the success of a project.
List at least five factors that significantly influence the success of a project.
Identify at least five distinct factors that can lead to project failure.
Identify at least five distinct factors that can lead to project failure.
Explain why the 'Poor technical specifications' can influence project failure. Please provide examples.
Explain why the 'Poor technical specifications' can influence project failure. Please provide examples.
Describe the impact resistance to change might have on a project. Give two examples of ways in which resistance to change might present itself.
Describe the impact resistance to change might have on a project. Give two examples of ways in which resistance to change might present itself.
In the context of ERP implementation, what does 'sizing' refer to?
In the context of ERP implementation, what does 'sizing' refer to?
Why is the task of 'sizing' important and what could lead to failure in hardware server i.e., system unavailability during go-live?
Why is the task of 'sizing' important and what could lead to failure in hardware server i.e., system unavailability during go-live?
What needs to be in place so that the task of 'sizing' does not lead to system unavailability during go-live?
What needs to be in place so that the task of 'sizing' does not lead to system unavailability during go-live?
In an ERP implementation what does documentation consist of and why is it important?
In an ERP implementation what does documentation consist of and why is it important?
What could be the consequences of a lack of documentation of a project?
What could be the consequences of a lack of documentation of a project?
Flashcards
Implementation project
Implementation project
The start of a new ES system after selection, typically managed by a consulting partner.
Go-live (production system)
Go-live (production system)
The point at which an ES goes live and becomes the production system.
Beneficiary (Buyer)
Beneficiary (Buyer)
The company or organization that will benefit from the ERP system.
Vendor Role
Vendor Role
Signup and view all the flashcards
Implementation Partner
Implementation Partner
Signup and view all the flashcards
Vanilla Implementation
Vanilla Implementation
Signup and view all the flashcards
Customized Implementation
Customized Implementation
Signup and view all the flashcards
Best-of-breed
Best-of-breed
Signup and view all the flashcards
Big Bang Adoption
Big Bang Adoption
Signup and view all the flashcards
Parallel Adoption
Parallel Adoption
Signup and view all the flashcards
Mini Big Bang (Phased)
Mini Big Bang (Phased)
Signup and view all the flashcards
Cutover Phase
Cutover Phase
Signup and view all the flashcards
Project Definition
Project Definition
Signup and view all the flashcards
Project Management
Project Management
Signup and view all the flashcards
Risk Management: Avoid It
Risk Management: Avoid It
Signup and view all the flashcards
Risk Management: Accept It
Risk Management: Accept It
Signup and view all the flashcards
Risk Management: Transfer It
Risk Management: Transfer It
Signup and view all the flashcards
Risk Management: Mitigate It
Risk Management: Mitigate It
Signup and view all the flashcards
Influencing Project Success
Influencing Project Success
Signup and view all the flashcards
Influencing Project Failure
Influencing Project Failure
Signup and view all the flashcards
Study Notes
Managing an Implementation Project
- ERP vendors include SAP, Oracle, Odoo, Microsoft Dynamics 365, Jeeves, Salesforce, Abas, and Zoho
- An implementation project normally commences once a buyer or beneficiary chooses an Enterprise System (ES)
- Most companies require a consulting partner for implementation, with few opting for internal implementation
- Successful implementation projects result in the ES being live and refered to as a production system
Parties involved in ES implementation project
- Beneficiary (Buyer)
- Vendor
- Implementation Partner (Consultancy)
- Vendors: SAP, Oracle, Odoo, Jeeves, etc
- Implementation Partners: Accenture, Jeeves, CapGemini, Satyam, KPMG, HP and sometimes the vendor handles the implementation
- Buyers: Nike, Nestle, Volvo, Swedish Army, Unilever, Sony, Coca-Cola, Dell, etc
ERP Implementation Strategies
- Vanilla Implementation is easy, by following the vendor's methodology, and usually, is on time and within budget
- Customized Implementations increase time and costs, and are not easily integrated into new versions
- Best-of-breed implementations can be expensive
- Maintaining legacy systems and adding ERP modules is cost-effective and less disruptive, but integration can be a problem
Go-live strategy
- Big bang adoption requires many resources, not recommended for large companies because it’s risky
- Parallel adoption requires the old and new systems to run simultaneously for some time, afterwards the old system is disabled if criteria are met
- Mini big bang / phased-out adoption is phased by module on a module-by-module basis
- Mini big bang / phased-out adoption is phased by site with a location-based implementation
Cutover Phase
- The final phase before going live with an ERP system, and describes the process of transitioning from one to a new system
- Activities during cutover phase include:
- Reviewing and updating all system-related procedures like backup policies and system monitoring
- Assigning ownership of the ERP's functional processes to function owners
- Performing a "Go-live" check
- Locking system, barring more changes to the ERP system
Project and Project Management
- A project is defined as work with a specified beginning and end and that produces a unique output
- Project management involves planning, organizing, scheduling, leading, communicating, and controlling work activities to achieve time and budget goals
The Role of Project Manager
- Leader
- Planner
- Organizer
- Controller
- Communicator
- Negotiator
- Peace Maker
- Risk Manager
- Knowledgeable
Three Factors of Success
- Cost
- Time
- Quality
- All within the scope of work
Sources of Risk
- People
- Technology
- Organization
- Finances
- Law/Contract
- Physical
Risk Management Approaches
- Avoidance occurs when work is done to ensure a risk never occurs, e.g redundancy in case of Power outages
- Acceptance involves living with the consequences, e.g technology obsolescence or salary increases
- Transfer involves sharing risk, e.g project go-live overrun with fixed cost
- Mitigation involves preparing through contingency planning, e.g assigning assistant project manager if the ERP project manager resigns
Factors Influencing Project Success
- Degree of customizations
- Effective communications
- Authority to make project implementations
- Top management commitment
- Quality of end-user training
- Data conversion
- Organizational Change Management OCM
Factors Influencing Project Failure
- Insufficient resource allocation to the project
- Keep-changing requirements
- Poor technical specifications (e.g., sizing)
- Lack of user engagement
- No clear authority on OCM
- Resistance to change
- Lack of project documentation
- Overruns
Sizing
- Appropriate hardware selection for enterprise system implementation projects is important
- Choosing the correct hardware is important as it could lead to failure in the hardware server, and/or system unavailability during go-live
- The process is conducted through coordination between enterprise systems customers, implementation consultants, and hardware vendors
- ERP implementation history includes project failures from implementing Oracle ERP system at Cisco arising from poor sizing
Studying That Suits You
Use AI to generate personalized quizzes and flashcards to suit your learning preferences.