Journey Brief

Overview

Lately, we have been facing several issues such as lack of customer follow up, missing or incorrect customer data, and in some cases department data clash which are all directly related to customer relationship management. Adam added that in the last management meeting, all the stakeholders have agreed that our current CRM system is not compatible with our business needs anymore. Hence, after discussion, management has decided to authorize a certain budget for us to build a CRM application that would serve us in a better way.

Objectives

Our objective is to solve the problems the company is facing with the current approach. The team decided to use Domain Driven Design (i.e. DDD) and eventstorming to discover our domains and the required entities and from that build an application that should fit our business requirements closely.

Optional features

We have agreed that while we want to focus on the core CRM responsibilities like customer and customer interactions, we might optionally also look into how opportunities are supported by our applications if time and resources permit.

Success criteria

To define the bold lines, the team has agreed that our goal is an easy to use application that supports all of the CRM capabilities that our colleagues need in their daily routine to run our business in a more efficient way avoiding all the current problems and aiming for better functionalities to ease the Customer Relationship Management.