ERP Project Management Chapter 8

True (A)

False (B)

False (B)

<p>False (B)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

FoxMeyer, a large pharmaceutical distributor, experienced a major failure implementing an enterprise-wide software and automation project in the 1990s. This led to significant financial problems and ultimately bankruptcy.

FoxMeyer claims vendors exaggerated the capabilities of the software and automation solutions they were selling. This led to unrealistic expectations and ultimately contributed to the project failure.

The implementation schedule for FoxMeyer's project was significantly too short and aggressive. Modules were to be implemented much faster than reasonable and practical.

FoxMeyer faced significant challenges integrating the new systems with their existing ones. These integration problems led to extensive delays and cost overruns.

FoxMeyer's management is implicated in making poor decisions concerning the scope, timeline, and resources of the project, potentially contributing to the project failure.

FoxMeyer faced challenges with its ERP system, including capacity issues with the mainframe, problems balancing system traffic, delayed information, incorrect shipments, and customer volume shortfall.

The ability of an enterprise resource planning system to handle the expected workload and data volume.

Difficulties in connecting different software systems (e.g., accounting, manufacturing, warehouse) within an ERP project.

Elements that can negatively impact a software project, including organizational issues, management support, software design, user involvement, project scope, and technology implementation.

How a company's business strategies (like high volume, low price) can affect the success or failure of an ERP project.

Elements contributing to successful ERP implementation, such as considering customizations, using consultants, managing supplier relationships, establishing metrics, and handling change management.

Using experts outside the company to assist in the design, implementation, or management of a project, such as system optimization or user training.

Strategies for managing adjustments in processes and practices required for a new system to be effectively implemented.

Successful ERP projects involve careful planning, effective communication, strong leadership, and a focus on user needs. Key factors include minimizing customizations, leveraging external consultants, managing supplier relationships, and effectively addressing change management.

ERP projects face various risks, including organizational factors like scope changes, resource availability, departmental conflicts, and user experience. Management support, software design issues, and user involvement also play a crucial role.

ERP implementation risks include technology compatibility, organizational impacts like customization, human resource factors like IT staff skills, and the overall project size.

A project champion is a high-level executive who actively supports and advocates for the success of an ERP project.

User training is essential for ERP projects because it ensures that employees understand the new system, its features, and how to utilize it effectively.

Customization can increase the time and cost of an ERP project, but it can also be necessary to adapt the software to specific business requirements. It's important to strike a balance.

External consultants offer expertise in cross-functional business processes, providing valuable insights and support during ERP implementation.

Change management is crucial for ERP projects because people are naturally resistant to change. Successful implementations require open communication, fostering a positive organizational culture, and providing clear guidance to employees.

Business measures are specific metrics defined at the start of an ERP project to track progress, evaluate performance, and assess the success of the implementation.

Dividing a larger ERP project into smaller, manageable subprojects facilitates better control, allows for independent progress, and simplifies the overall implementation process.

Focusing on user needs during an ERP project ensures that the system is designed and implemented to meet real-world requirements, improving user adoption and ultimately, project success.

FoxMeyer's project suffered due to poor communication, unrealistic expectations, and technical issues. Dow Chemical, despite initial problems, managed to adjust scope, maintain control, and foster open communication, leading to a more successful outcome.

Management reporting requirements often necessitate the addition of query and reporting tools to the ERP system, enabling effective data analysis and decision-making.

Technological challenges in ERP projects include data conversion, interface development, and ensuring compatibility with existing systems.

Slack time built into a project schedule provides buffer for potential delays and unforeseen circumstances, preventing significant disruptions and missed deadlines.

FoxMeyer, a major pharmaceutical distributor, faced catastrophic failure with their ERP implementation in the 1990s due to aggressive timelines, vendor misrepresentation, and integration problems. The project resulted in significant financial losses and the company filing for bankruptcy.

FoxMeyer's ERP implementation schedule was drastically too short and aggressive. Modules were scheduled to be implemented much faster than reasonable, leading to problems and delays.

FoxMeyer struggled to integrate their new ERP system with existing systems, leading to significant delays and cost overruns. This is a common challenge in ERP implementation projects.

Connecting different software systems, like accounting and warehouse, within an ERP project, to ensure data flows smoothly between them.

Potentially negative impacts during implementing ERP, including technology compatibility, organizational impacts like customization, human resource factors like IT skills, and project size.

Potential threats that can hinder an ERP project's success, categorized as organizational factors (scope changes, resource availability), management support, software design, user involvement, and technology implementation issues.

A high-level executive who actively supports and advocates for the successful implementation of an ERP project, driving its progress and overcoming obstacles.

Training that ensures employees understand the new ERP system, its features, and how to utilize it effectively, crucial for user adoption and smooth implementation.

Adapting the standard ERP software to meet specific business requirements, balancing the need for flexibility with potential increased cost and time.

Experts from outside the company assisting in ERP project design, implementation, or management, providing expertise in cross-functional business processes.

Strategies to manage employee resistance to change during ERP implementation, fostering open communication, a positive organizational culture, and clear guidance for employees.

Specific metrics defined at the start of an ERP project to track progress, evaluate performance, and assess the success of implementation.

Breaking down a large ERP project into smaller, manageable subprojects, allowing for independent progress, improved control, and simpler overall implementation.

Prioritizing the system design and implementation to meet real-world requirements and needs of users, leading to better user adoption and overall project success.

A case study of a successful ERP implementation, despite initial challenges, demonstrating the importance of strong leadership, open communication, and adaptable project management.

The requirement for detailed management reports often necessitates the addition of query and reporting tools to the ERP system, facilitating effective data analysis and decision-making.

Difficulties faced in integrating the ERP system with existing technology infrastructure, including data conversion, interface development, and ensuring compatibility.

Built-in buffer time in the project schedule to accommodate potential delays or unforeseen circumstances, preventing major disruptions and missed deadlines.