Project Overview

Project Name: Implementation of a new Customer Relationship Management (CRM)

System
Project Manager: John Smith
Project Start Date: January 1, 2022
Project End Date: June 30, 2022

The implementation of a new CRM system was initiated by a mid-sized organization to

improve customer satisfaction by streamlining and automating customer interactions, and
enhancing data analysis capabilities. The project aimed to be completed within six months
with a budget of $200,000 and was managed by John Smith with a team of 10 members.

PROJECT GOALS AND OBJECTIVES

The goals of the project were to:
• Implement a new CRM system to enhance customer satisfaction.
• Streamline and automate customer interactions.
• Improve data analysis capabilities.
• Ensure timely completion of the project within the allocated budget.
• Achieve a high level of end-user adoption.

PROJECT SCOPE
The project scope included:
• Defining and implementing a new CRM system.
• Conducting user research to identify user needs and preferences.
• Developing user personas and use cases.
• Designing the CRM system interface and user experience.
• Integrating the new system with existing systems.
• Developing a data migration plan.
• Conducting training sessions for end-users.

PROJECT BUDGET
The project budget was $200,000.

PROJECT SCHEDULE
The project was scheduled to be completed within six months, from January 1, 2022, to June
30, 2022.

PROJECT TEAM
The project team consisted of the following members:
Project Manager, Business Analyst, CRM Developer, User Experience Designer, System
Integrator, Data Migration Specialist, Quality Assurance Tester, Training Specialist, and two
End-User Representatives.

PROJECT RISKS AND CHALLENGES

The project faced several risks and challenges, including:
• Difficulty managing scope creep.
• Lack of end-user engagement and participation.
• Limited resources and budget.
• Integration challenges with existing systems.
• Lack of expertise in implementing a new CRM system.

The project team was able to overcome these risks and challenges by:
• Developing a clear scope statement and change control process.
• Prioritizing end-user engagement and participation.
• Optimizing resource allocation and managing the budget effectively.
• Collaborating closely with IT teams to address integration challenges.
• Seeking external expertise and training to enhance project outcomes.

PROJECT SUCCESS AND FAILURES

The project was successful in many ways, including:
• The new CRM system improved customer satisfaction and engagement.
• The project was completed within the scheduled timeframe and budget.
• The project team addressed integration challenges effectively.
• The team sought external expertise and training to enhance project outcomes.

However, the project also faced several challenges, including:

• The project scope was not fully achieved, leading to reduced functionality and adoption by
end-users.
• The lack of end-user engagement and participation led to reduced adoption rates.
• The project team had to rush through the final stages of the project to meet the deadline,
leading to quality issues and a lack of proper testing.

PROJECT MANAGEMENT METHODOLOGY

The project was managed using a traditional waterfall approach, where each phase of the
project was completed sequentially, starting with requirements gathering, design,
development, testing, and deployment. This methodology is suitable for projects where the
requirements are well-defined and fixed, and there is limited need for adaptability or
flexibility during the project's lifecycle. However, due to the lack of adaptability and flexibility
inherent in this approach, the project team faced challenges with scope management and
end-user engagement.

The waterfall approach is a linear and sequential model where each phase of the project is
completed before moving on to the next. This model ensures that each phase is completed
before moving on to the next, providing a structured and predictable process. However, this
approach can be rigid, and any changes made during one phase may impact subsequent
phases, leading to increased time and cost.

In this project, the waterfall approach was used to manage the project. However, this
approach faced several challenges, including scope creep, limited end-user engagement and
participation, integration challenges with existing systems, and a lack of expertise in
implementing a new CRM system.
 PROJECT IMPROVEMENT
CATEGORY ISSUE PROBLEM/SUCCESS IMPACT RECOMMENDATIONS
Define a clear scope
Reduced statement upfront, develop a
functionality change control process, and
Project Scope Project scope not and adoption manage scope creep
Management Management fully achieved by end-users proactively
Prioritize end-user
engagement and participation
throughout the project
Lower lifecycle by conducting user
customer research, developing user
Lack of end- satisfaction personas, and involving end-
User user Reduced adoption and users in the design, testing,
Engagement engagement rates engagement and feedback processes
Reduced
reliability and
Quality issues Rushing through accuracy of the Adopt agile methodology to
Project and lack of final stages of the new CRM increase collaboration,
Delivery proper testing project system adaptability, and flexibility
Delayed
project
completion or
reduced
Limited quality of Improve resource
Resource resources and Struggle to optimize project management practices and
Management budget resource allocation outcomes manage the budget effectively
Disruption of Collaborate closely with IT
Integration existing teams to address integration
challenges Difficulty in business challenges and seek external
with existing integrating the new processes and expertise and training to
Integration systems system workflow enhance project outcomes

The CRM system implementation project faced challenges in five categories, including
project management, user engagement, project delivery, resource management, and
integration. The issues included scope management, a lack of end-user engagement, quality
issues and lack of proper testing, limited resources and budget, and integration challenges
with existing systems. These issues had impacts on customer satisfaction, adoption rates,
reliability, and accuracy. Improvement recommendations include defining clear scope
statements, prioritizing end-user engagement, adopting agile methodology, improving
resource management practices, collaborating with IT teams, and seeking external expertise
and training.

SYMPTOMS AND CAUSES OF PROBLEMS

The project faced several challenges, including scope creep, limited end-user engagement
and participation, integration challenges with existing systems, and a lack of expertise in
implementing a new CRM system. These issues were caused by poor scope management
practices, a lack of prioritization of end-user engagement, and limited resources and
expertise.

Scope creep occurs when the project's scope expands beyond its original requirements,
leading to additional work, increased cost, and delayed schedules. This challenge can occur
when requirements are not adequately defined or communicated, leading to unclear project
goals and objectives. Additionally, scope creep can result from poor change management
practices, where changes are not adequately controlled or managed, leading to uncontrolled
changes in the project's scope.

Limited end-user engagement and participation can lead to reduced adoption rates,
decreased user satisfaction, and increased resistance to change. This challenge can occur
when end-user needs are not adequately prioritized or communicated, leading to a lack of
understanding of end-user needs and requirements. Additionally, limited end-user
engagement can result from poor communication and collaboration practices, where end-
users are not adequately engaged throughout the project's lifecycle.

Integration challenges with existing systems can occur when the project team lacks the
necessary expertise or resources to integrate new systems with existing ones. This challenge
can lead to delays in project schedules, increased costs, and decreased project outcomes.

The lack of expertise in implementing a new CRM system can result from insufficient training
or lack of knowledge in implementing new systems. This challenge can lead to quality issues,
delayed schedules, and increased costs.

ROOT-CAUSE ANALYSIS TOOLS

To identify the root causes of these issues, the project team used several tools, including:

Fishbone diagrams: This tool was used to identify the underlying causes of scope creep and
integration challenges. The fishbone diagram, also known as the Ishikawa diagram, is a
cause-and-effect diagram that helps identify the root causes of a problem. By breaking down
the problem into its component parts, the fishbone diagram helps identify potential causes
of the problem and provides a framework for developing solutions.

Root cause analysis (RCA): This tool was used to identify the underlying causes of the lack of
end-user engagement and participation. RCA is a method used to identify the root cause of a
problem. This technique involves asking "why" questions to identify the underlying causes of
a problem and develop solutions to address them.

Pareto charts: This tool was used to identify the most significant causes of project issues. A
Pareto chart is a graphical representation that shows the relative frequency or size of
problems in descending order of importance. By using this tool, the project team can focus
on the most significant causes of project issues and prioritize their efforts to address them.
ACTION POINTS

To address these issues, the project team developed the following action points:
• Adopt agile methodology to increase collaboration, adaptability, and flexibility.
• Develop a clear scope statement upfront and manage scope creep proactively.
• Prioritize end-user engagement and participation throughout the project lifecycle.
• Seek external expertise and training to enhance project outcomes.

COMPARISON OF THE ACTUAL AND PLANNED RESULTS

Aspect Actual Results Planned Results

Timeframe
Budget
End-User Engagement
Functionality
Quality
Customer Satisfaction
Streamlining and Automation of
Customer Interactions
Data Analysis Capabilities
Completed within scheduled
timeframe
Completed within budget
Limited participation, reduced
adoption rates
Reduced functionality due to
scope not fully achieved
Quality issues due to rush to meet High quality and proper
deadline
Partially improved
Partially achieved
Partially improved
Completed within
scheduled timeframe
Completed within budget
High engagement and
participation
Full functionality achieved
testing
Significant improvement
Significant improvement
Significant improvement

The actual results of the CRM system implementation project were mixed, with reduced
adoption rates and limited functionality due to a lack of end-user engagement and rushed
project delivery. The planned results were more optimistic, but only partially achieved. To
improve future projects, the team should prioritize end-user engagement, adopt an agile
approach to project management, and seek external expertise and training. These actions
can help ensure successful project outcomes that meet stakeholder needs.

IMPROVEMENT RECOMMENDATIONS

To improve project outcomes, the following recommendations are suggested:

• Adopt agile methodology to increase collaboration, adaptability, and flexibility.
• Improve scope management practices by defining a clear scope statement upfront,
developing a change control process, and managing scope creep proactively.
• Prioritize end-user engagement and participation throughout the project lifecycle by
conducting user research, developing user personas, and involving end-users in the design,
testing, and feedback processes.
• Prioritize training and support for end-users to ensure that they are fully prepared to use
the system and provide feedback.

CONCLUSION

The implementation of a new CRM system was a strategic initiative for the organization,
aimed at improving customer satisfaction and engagement. Despite facing several risks and
challenges, the project was completed within the scheduled timeframe and budget.
However, the project outcomes were limited by the lack. the organization implemented a
new CRM system to improve customer satisfaction and engagement. The project faced risks
and challenges, but was completed within schedule and budget. However, the outcomes
were limited due to a lack of effective training and adoption by employees.

REFERENCES

Agile Alliance. (2001). Manifesto for Agile Software Development. Retrieved from
https://agilemanifesto.org/.

Cohn, M. (2014). User Stories Applied: For Agile Software Development. Addison-Wesley
Professional.

Finkelman, J. (2018). Best practices in project management. Nursing management, 49(2), 22-
27.

Ishikawa, K. (1990). Quality control handbook. JUSE Press Ltd.

Kerzner, H. (2017). Project Management: A Systems Approach to Planning, Scheduling, and

Controlling. Wiley.

Kueng, P., & Pfister, T. (2018). The impact of agile methods on project management. Journal
of Information Technology, 33(3), 186-200.

Osterwalder, A., & Pigneur, Y. (2010). Business model generation: a handbook for visionaries,
game changers, and challengers. John Wiley & Sons.

Pareto Chart. (2021). ASQ Quality Glossary. American Society for Quality.
https://asq.org/quality-resources/pareto-chart.

Project Management Institute. (2013). Practice Standard for Project Risk Management.
Project Management Institute.

Project Management Institute. (2017). A Guide to the Project Management Body of

Knowledge (PMBOK Guide) (6th ed.). Project Management Institute.

Reddy, P. A., & Cragg, P. B. (2018). Critical success factors for the implementation of CRM
systems. Information & Management, 55(1), 21-30.
Root Cause Analysis. (2020). ASQ Quality Glossary. American Society for Quality.
https://asq.org/quality-resources/root-cause-analysis.
Zawawi, N. A., Yusoff, W. F. W., Abdullah, Z., Ahmad, N., & Mohamad, R. (2018). Factors
influencing CRM system implementation success: A review of literature. Journal of
Information Systems and Technology Management, 15(3), e201815001.