Project Scenario 1: CRM Rewrite

Note: This scenario will provide the material needed to create the artifacts as specified in the Project page. Though you will not develop the actual system, it may be good idea to familiarize yourself with the required technology in order to produce more accurate plans.

Problem Statement

A Customer Relationship Management (CRM) producer, Sell-IT, has fallen behind and failed to right itself after being outpaced in features and service by other competitors. After cleaning house, the new CEO has hired your team to completely rewrite their existent and outdated CRM product, trying to emulate a start-up culture. They hope to increase their clients' satisfaction, implement easier use of the system, attract more high-profile clients, and provide an in-depth analysis of system functions, for both the business itself and its clients. The CEO wants the new system to be cutting-edge and competitive, as well as easy to use and maintain. The new system must be able to be marketed and deployed as a minimum viable product as soon as possible.

At this time, there are a number of enterprise systems that the existing clients rely upon, making it necessary that the new product be designed with built-in integrations. This is a trend throughout the CRM industry and will need to be maintained. The old system had these integrations but also included a hard set of features, some of which some clients never used and couldn't remove; the CEO wants the new system to have modular features which can be built up over time. This will allow the business to cater and shape product instances to a client's needs, as well as sustain business through future features.

The requirements for this system are given in the list below as either minimum viable features or desired features for the overall system. The list is neither exhaustive nor definitive. It is up to your team to develop a list of features that best fit the scope of your application. Remember, the feature set is meant to be modular and that this company is currently in flux, so new features and their priorities could be added, removed, or changed.

Minimum Viable Features (MVF)

  1. Workflows
  2. Contact & Sales Management
  3. Salesforce, SharePoint, & Oracle ERP (HR) Integration

Desired Features

  1. Sales Analytics & Forecasting
  2. Email Integration & Analytics
  3. Additional Workflows
  4. Automation
  5. Lead Management
Remember, these are suggestions. Feel free to add to or modify these requirements based on the design of your system, research and your domain analysis. Your instructor may assist you and clarify if need be.