How to show change request details

When we want to see the details of particular change request detail page then you click on particular change request

When you click on highlighted id then it open the change request details page.

Here you can see the detail of that change request .

In the first row you see the different button like , Edit, Delete, Relevant Ticket, Impacted Device, Relevant Task, Info, History and Back

History:-

When you click on history button then you can see the history of that change request

Relevant Task :-

When we want to add the relevant task of that change request so, click on "Relevant Task" Button then it opens a modal where we select the task.

Here we select any of the task. If we select the task, then it adds in that change request and listed in task section as you see in below screenshot.

Impacted Device:-

When we want to add the Impacted device of that change request so, click on "Impacted Device" Button then it opens a modal where we select the device.

Here we select any of the device. If we select the device, then it adds in that change request and listed in device section as you see in below screenshot.

Impacted Ticket:-

When we want to add the Impacted ticket of that change request so, click on "Impacted Ticket" Button then it opens a modal where we select the open ticket.

Here we select any of the ticket. If we select the ticket, then it adds in that change request and listed in device section as you see in below screenshot.

Planning:-

1. Reason for Change

• Purpose: Describe why the change is necessary. Outline the drivers, such as process improvements, compliance requirements, system upgrades, or user demands.

• Objectives: Specify what the change intends to achieve (e.g., enhanced functionality, improved data accuracy, streamlined workflows).

• Stakeholder Benefits: Highlight benefits for users, clients, or other stakeholders, ensuring alignment with CRM objectives.

2. Impact Description

• Affected Areas: Detail which CRM modules, processes, or integrations will be impacted. Describe changes to data flows, UI/UX elements, or reporting features.

• User Impact: Identify which user roles or departments will be affected. Include the degree of impact on their daily activities and anticipated learning curves.

• Resource Implications: Outline how this will affect resource allocations in terms of time, budget, or staffing.

3. Risk Description

• Potential Risks: Identify risks, such as system downtime, data integrity issues, security vulnerabilities, or user resistance.

• Risk Level: Assess the severity of each risk (e.g., high, medium, low) and the likelihood of occurrence.

• Mitigation Strategies: Propose strategies to reduce risks, like additional testing, training, or incremental rollouts.

4. Rollout Plan

• Phased Approach: Define if the change will be implemented in phases or as a single deployment. Phases allow for testing and feedback collection.

• Key Milestones: Set timelines and checkpoints for different stages of the rollout, such as development, testing, pilot testing, and full deployment.

• Stakeholder Communication: Plan regular updates for stakeholders and users about the rollout’s progress, timeline, and any anticipated impacts on their workflows.

5. Fallback Plan

• Reversal Steps: Outline steps to revert the CRM to its previous state if issues arise during or after deployment.

• Data and System Backups: Ensure that comprehensive backups are taken before implementation, and define how the backup will be restored if needed.

• Testing Reversion: Test the fallback plan in a staging environment to verify that the system can revert seamlessly without data or process disruptions.

Comments:-

When leaving comments for a team member on a CRM project, it's helpful to provide clear, constructive, and actionable feedback. Here are some CRM-related comments examples based on different situations:

• If user want to attachment file then user can added file.

• If user want to overall conversation on email then user can select add back-trail conversation on e-mail notification checkbox.

• If user want send to cc-email then select checkbox cc-email and dropdown select email ids.

Approvals:-

CRM approval typically involves reviewing and authorizing requests or actions within a CRM system, ensuring they align with business goals, data standards, and security policies. Here’s a structured approach to CRM approval:

1. Review the Request

• Details: Evaluate the purpose and scope of the request, such as data access, customization, or integration needs.

4. Approve or Reject with Justification

• Approval: If approved, outline any conditions or additional requirements (e.g., testing, phased rollout, additional documentation).

• Rejection: If the request is not approved, provide specific reasons and suggest adjustments if possible to help meet approval standards in the future.

• 

Change Properties:-

Incorporating a structured approach to manage Change Requests (CR) in a CRM with defined properties can streamline the change management process. Here’s a breakdown of each property for change tracking and user updates:

1. Status

• Purpose: Tracks the current phase of the change request.

• Examples: Open, In Progress, Pending Approval, Approved, Rejected, Completed.

• Usage: Users can update the status as the change progresses, providing transparency to the team.

2. Priority

• Purpose: Establishes the urgency or importance of the change.

• Examples: Low, Medium, High, Critical.

• Usage: Assigning and updating priority helps the team allocate resources effectively and address high-priority changes first.

3. Impact

• Purpose: Assesses the effect of the change on the CRM and associated workflows.

• Examples: Minor, Moderate, Major, Critical.

• Usage: Users should update the impact assessment based on the change’s anticipated effect on business processes, data integrity, or user experience.

4. Risk

• Purpose: Identifies potential risks associated with the change.

• Examples: Low, Medium, High, Very High.

• Usage: An initial risk level is set, but users can update it if risks increase or decrease as more information becomes available.

5. Change Type

• Purpose: Defines the nature or category of the change.

* Examples: Enhancement, Minor, Standard, Major, Emergency.

• Usage: Categorizing by change type helps in resource planning, prioritization, and aligning with business needs.

6. Schedule Start Date

• Purpose: Indicates when the change implementation is planned to begin.

• Usage: Users can set and adjust the start date to align with project timelines and team availability.

7. Schedule End Date

• Purpose: Specifies the planned completion date of the change.

• Usage: This date helps track the timeline and ensures alignment with project milestones.

8. Category

• Purpose: Further classifies the change by its specific area within the CRM (e.g., sales, support, analytics). Examples: User Interface, Data Management, Workflow Automation, Reporting, Security.

• Usage: Users can choose a relevant category to quickly identify the impacted area, simplifying tracking and impact assessment.

9. Cost

• Purpose: Estimates the financial cost associated with implementing the change.

• Usage: Users update cost estimates based on the resources required, enabling more informed decision-making and budget management.

10. Close State (Success or Failure)

• Purpose: Marks the final outcome of the change request. Options: Success, Failure.

• Usage: Once a change is complete, the user can update this state to reflect whether the change met its objectives or encountered issues, useful for documentation and future analysis.

Each of these fields in the CRM system allows for detailed tracking, enabling the team to manage changes more efficiently and transparently. Regular updates to these properties provide a clear record of the change lifecycle and facilitate better communication and decision-making among team members and stakeholders.