CRM Implementation Project Work Breakdown Structure (WBS)

Part A – Work breakdown structure

**Phase Save Time On Research and Writing Hire a Pro to Write You a 100% Plagiarism-Free Paper. Get My Paper	Task no.	Task name	Milestones
1. Internal Analysis Save Time On Research and Writing Hire a Pro to Write You a 100% Plagiarism-Free Paper. Get My Paper	1.1	User process development	Develop an overview of the user processes for collecting, entering, analyzing and using CRM data
1.2	Data requirement identification	Identify the data requirements for the CRM
1.3	Stakeholder need analysis	Analyse stakeholder needs
1.4	Business process review	Review current business processes
2. System configuration	2.1	Purchasing CRM Sage	Purchase Sage CRM
2.2	Determine hardware and peripheral needs	Determine hardware and peripheral requirements
2.3	Obtaining peripherals and hardware	Obtain hardware and peripherals
2.4	Customization requirement and specifications	Determine customisation requirements and specifications
2.5	Getting approval	Approve and finalise customisation specifications
2.6	Customisation	Develop the customisation
2.7	Reviewing customisation	Review the customisation
2.8	Training	Conduct training
3. Data Preparation and Cleansing	3.1	Client data review	Review existing client data to fill gaps and remove duplications
4. Development	4.1	System settings configuration	Configure system settings such as date formats and currency
4.2	Setting rules	Set up rules for email tracking
4.3	Creating business units	Create business units and teams for permissions and security
4.4	Configuration of client settings	Install clients and configuring clients’ settings as required
4.5	Developing personal and system views	Create personal and/or system views
4.6	Setting up dashboards	Set up dashboards to drive user behaviour and improve business performance
4.7	Integration	Integrate with Sage 300
5. Testing	5.1	Infrastructure testing	Conduct infrastructure testing
5.2	System testing	Conduct system testing
5.3	User Acceptance Testing (UAT)	Conduct User Acceptance Testing (UAT)
5.4	Pilot group testing	Conduct pilot group testing
5.5	Customization	Finish customisation
6. Training and Support	6.1	Delivering administrator training	Schedule and deliver administrator training
6.2	Delivering user training	Schedule and deliver user training
6.3	Development of process flows	Develop process flows for the overall use of the CRM to be incorporated into IAJ quality manuals
6.4	Development of policies and procedures	Develop specific user policies and procedures
6.5	Development of quick help guides	Develop quick help guides
6.6	Ongoing help desk support	Provide ongoing help desk support
7. Go Live Activities	7.1	Data migration	Migrate data
7.2	Releasing deliverables	Release final deliverables
8. Close Down and Review	8.1	Technical support handover	Conduct technical support handover
8.2	Post implementation review	Conduct post-implementation review
8.3	Preparing communication plan	Review final communication plan
8.4	Preparing project report	Produce end of project report
8.5	Reviewing change management	Perform a change management review
8.6	Preparing documentation	Ensure all documentation required for the project is distributed
8.7	Decision assessment	Ensure the stakeholders have been involved in the decision and assessment that the project is complete
8.8	Project closedown	Perform project closedown

Provide an estimate of duration and effort for each task of your project, as well as task sequences and dependencies.

Task no. (WBS)	Task Name	Predecessor relationship	Duration	Resources required
Days	Human	Material	Equipment
1.	Internal Analysis		60 days
1.1	User process development		15 days	Business analyst	NA	NA
1.2	Data requirement identification	2	15 days	IT manager	NA	NA
1.3	Stakeholder needs analysis	3	10 days	Resource manager	NA	NA
1.4	Business process review	4	20 days	Business analyst	NA	NA
2	System Configuration		40 days
2.1	Purchasing CRM Sage	5	2 days	Resource manager	Sage CRM	NA
2.2	Determine hardware and peripheral needs	7	5 days	IT manager	Hardware peripherals	NA
2.3	Obtaining peripherals and hardware	8	10 days	IT manager	Hardware	NA
2.4	Customization requirements and specifications	9	5 days	Project manager	NA	Customization equipment
2.5	Getting approval	10	1 day	Technical team	NA	NA
2.6	Customisation	11	5 days	IT manager	NA	NA
2.7	Reviewing customization	12	2 days	Project manager	NA	NA
2.8	Training	13	10 days	Trainer	NA	NA
3	Data Preparation and Cleansing		100 days
3.1	Client data review	14	100 days	IT manager	NA	Software tools
4	Development		30 days
4.1	System settings configuration	16SS+34 days	2 days	Workers	NA	NA
4.2	Setting rules	18	3 days	Technical team	NA	NA
4.3	Creating business units	19	5 days	Application manager	NA	NA
4.4	Configuration of client settings	20	5 days	Developer	NA	NA
4.5	Developing personal and system views	21	6 days	Technical team, Developer	NA	NA
4.6	Setting up dashboards	22	4 days	Application manager, Developer	NA	NA
4.7	Integration	23	5 days	Application manager	NA	NA
5	Testing		30
5.1	Infrastructure testing	24	5 days	Tester	NA	NA
5.2	System testing	26	5 days	Tester,	NA	Testing tools
5.3	User Acceptance Testing (UAT)	27	5 days	Tester	NA	NA
5.4	Pilot group testing	28	5 days	Tester	NA	NA
5.5	Customization	29	10 days	Developer	NA	NA
6	Training and Support		20
6.1	Delivering administrator training	30	5 days	Trainer	NA	NA
6.2	Delivering user training	32	5 days	Trainer	NA	NA
6.3	Development of process flows	33	3 days	Developer	Training manuals	NA
6.4	Development of policies and procedures	34	2 days	IT manager, Project manager,	NA	NA
6.5	Development of quick help guides	35	2 days	Resource manager, Documenter, Project manager	NA	Testing tools
6.6	Ongoing help desk support	36	3 days	Documenter manager	NA	NA
7	Go Live Activities		20
7.1	Data migration	37	15 days	IT manager	NA	NA
7.2	Releasing deliverables	39	5 days	Project manager	NA	NA
8	Close Down and Review		20
8.1	Technical support handover	40SS	2 days	Application manager, IT manager	NA	NA
8.2	Post implementation review	42	3 days	IT manager	NA	NA
8.3	Preparing communication plan	43	4 days	Project manager	NA	NA
8.4	Preparing project report	44	5 days	Project manager	NA	NA
8.5	Reviewing change management	45	4 days	IT manager, Workers	NA	NA
8.6	Preparing documentation	46	7 days	Documenter	NA	NA
8.7	Decision assessment	47	4 days	IT manager, technical team	NA	NA
8.8	Technical support handover	40SS	2 days	Application manager, IT manager	NA	NA

Project schedule for implementing Sage CRM for Indo Aust Jaya

As per the schedule that is provided below, the total time that is needed for implementing the sage CRM is around 275 days.

Figure 1: Gantt chart

(Source: Created by Author)

You are to provide an updated project schedule reflecting a variation and a progress report, and this includes a project schedule reflecting the variation and the Project status report
The project involves implementing a Customer Relationship Management (CRM) system.
Refer to the case study context below for responding to Part D; the Gantt chart is recommended.

Context:

Gary Jazgar manages IAJ’s IT department. The IT Department at IAJ is responsible for:

supporting IAJ staff
planning and coordinating infrastructure
performing website maintenance
testing and planning for disaster recovery
adhering to the strategic plan for keeping hardware and software up to date
monitoring and maintaining computer hardware operating systems and applications
troubleshooting system and network problems and diagnosing and solving hardware/software faults
providing procedural documentation to users
evaluating and running projects as required
ensuring the security of the network

During the conversation, Gary requested a change to the schedule. The change is an extension of time for a specific task/phase due to the following reasons:

unavailability of a staff member involved in the task; and
delays in being able to purchase the required hardware

You are to provide an updated project schedule reflecting a variation and a progress report.

This includes a project schedule reflecting the variation, a Gantt chart is recommended, and the Project status report

The system configuration phase gets delayed due to the unavailability of the staff members as well as because of delays in purchasing the needed hardware. The status report that is provided below showcases that the project is 29% complete, which means that the project is running late. As the project is running late, it would be quite difficult to deliver the goals and objectives of the project within the assumed time and budget. The below-provided status report helps in showcasing the variation that occurs during the project and as per which the system configuration phase gets delayed by around two days which is reflected below and due to which the final delivery date of the project also gets extended. The below-provided status report also showcases which of the activities of the project are complete and which are late. The information that is provided is quite helpful for the project managers to take the right initiative when they identify that the project has lost track.

Figure 2: Status report

(Source: Created by Author)

Project information

Project name: Implement Sage CRM for Indo Aust Jaya

Date:

Prepared by: Project manager

Distribution list:

Recent project progress, activities, and highlights:

The status report that is provided showcases that the project is 29% complete, which means that the project is running late. It is identified that the internal analysis phase is complete, and the system configuration phase of the project is in progress

Project performance

Refer to Overview: colour status criteria – project status report and project registry at the end of the report

Date	Timeline	Budget	Communication	Scope	Resources	Risks		Overall project
30th May 2022			l	l		l

Performance areas	Issues / concerns
Timeline	The total time of the project configuration phases increases by two days.
Budget	The total expenses of the project would increase by $3,000.
Communication	The project team does not experience any communication issues during the project.
Scope	Due to changes in time and budget, the scope of the project also gets impacted negatively.
Resources	As the total time of the project increases, a greater number of resources are required during the project.
Risks	The status report reflects that currently, the project is experiencing schedule slippage and budget shortfall.
Overall project	Due to delay, the project is at risk and therefore, it is necessary to manage both time and budget.
Other	N/A

Timeline:

Milestones	Deliverables	Due date	Actual completed date	Reason for early delivery or slippage	Actions and resolutions
User process development	Process development document	Thu 27/01/22	Thu 27/01/22	On schedule	NA
Data requirement identification	Data requirement files	Thu 17/02/22	Thu 17/02/22	On schedule	NA
Stakeholder needs analysis	Stakeholder analysis document	Thu 03/03/22	Thu 03/03/22	On schedule	NA
Business process review	Process review document	Thu 31/03/22	Thu 31/03/22	On schedule	NA
Purchasing CRM Sage	CRM Sage	Wed 06/04/22	Thu 07/04/22	Lack of staffs	Hiring new stakeholders
Determine hardware and peripheral needs	Hardware	Wed 13/04/22	Fri 15/04/22	Lack of hardware	Asking suppliers to deliver hardware on time.
Obtaining peripherals and hardware	Hardware	Wed 27/04/22	Fri 29/04/22	Lack of hardware	Asking suppliers to deliver hardware on time.
Customization requirements and specifications	Project requirement details	Wed 04/05/22	Fri 06/05/22	Lack of staffs	Hiring new stakeholders
Getting approval	Approval document	Thu 05/05/22	Mon 09/05/22	Lack of staffs	Hiring new stakeholders
Customization	Customization document	Thu 12/05/22	Mon 16/05/22	Lack of staffs	Hiring new stakeholders
Reviewing customization	Customization document	Mon 16/05/22	Tue 17/05/22	Lack of staffs	Hiring new stakeholders
Training	Training document	Mon 30/05/22	Wed 01/06/22	Lack of staffs	Hiring new stakeholders

Planned activities/deliverables for the next time period:

Activity	Deliverables	Due date	Comments
Client data review	Reviewed data	Mon 31/10/22	Client data review will be undertaken after successful completion of system configuration, and it further requires 100 days.

Write a short reflection discussing the changes you could make to your time management control mechanisms/project schedule in order to manage project time more effectively.

After reviewing the project, I have identified that if I had used a few time control mechanisms, then the project would have been managed very well. It is necessary to track the schedule of the project on a regular basis for controlling the schedule of the project and for avoiding delays during the project. Additionally, the use of EVM also helps in determining schedule variances and further helps in reflecting the changes that would occur during the project so that the project team can make the right decision at the right time for handling the situation well. Furthermore, setting priorities during the project not only helps in the easy execution of the project activities but also assists in controlling the total time of the project for avoiding issues like schedule slippage and delay. Moreover, it is also important to avoid conflicts and interruptions during the project as conflicts and interruptions would be time consuming, and as a result, it would increase the total time.

Aanbari, F.T. and Kwak, Y.H., 2018, June. Impact on project management of allied disciplines. Project Management Institute.

Ahmed, S., 2019. A review on using opportunities of augmented reality and virtual reality in construction project management. Organization, Technology and Management in Construction: An International Journal, 11(1), pp.1839-1852.

Bjorvatn, T. and Wald, A., 2018. Project complexity and team-level absorptive capacity as drivers of project management performance. International Journal of Project Management, 36(6), pp.876-888.

Chen, T., Fu, M., Liu, R., Xu, X., Zhou, S. and Liu, B., 2019. How do project management competencies change within the project management career model in large Chinese construction companies?. International Journal of Project Management, 37(3), pp.485-500.

Filippetto, A.S., Lima, R. and Barbosa, J.L.V., 2021. A risk prediction model for software project management based on similarity analysis of context histories. Information and Software Technology, 131, p.106497.

Larsson, J. and Larsson, L., 2020. Integration, application and importance of collaboration in sustainable project management. Sustainability, 12(2), p.585.

Picciotto, R., 2020. Towards a ‘New Project Management’movement? An international development perspective. International Journal of Project Management, 38(8), pp.474-485.

Puška, A., Stojanovi?, I., Maksimovi?, A. and Osmanovi?, N., 2020. Evaluation software of project management used measurement of alternatives and ranking according to compromise solution (MARCOS) method. Operational Research in Engineering Sciences: Theory and Applications, 3(1), pp.89-102.

Turn in your highest-quality paper
Get a qualified writer to help you with

“ CRM Implementation Project Work Breakdown Structure (WBS) ”

Get high-quality paper

NEW! AI matching with writer

Order an Essay Now & Get These Features For Free:

Turnitin Report

Formatting

Title Page

Citation

Outline

Place an Order