System Requirements & CRM Design Proposal Presentation

Part 1: System Requirements

As you learned in the previous course content, requirements are a fundamental component of any project. Depending on the SDLC applied, requirements can be written in different forms. For example, some requirements will be very technically focused (technical requirements) and are written in a manner that dictates what a stakeholder expects the system to accomplish. Another approach taken, often with Agile-run projects, is to create a user story. A user story focuses on different types of system users and outlines more of a workflow that organizations expect.

Review the Comp 1 Reflection about what makes well-written requirements.

The WeLoveVideo project team met with the business owners last week in a structured requirements gathering meeting. In this meeting, they discussed that the requirements should focus on certain users, such as customer support representatives and inside sales representatives, as well as be geared toward the system supporting the job function.

Create 15 to 20 system requirements based on the scope of the project discussed in the requirements meeting.

Apply Agile or Waterfall methodologies in creating requirements that meet quality standards in priority order, addressing how the SDLC will impact the form of the requirements

Justify the prioritization of the system requirements within the document 

You may use any Microsoft® program, such as Excel® or Word, to create the list of requirements.

Part 2: CRM Design Proposal Presentation

The stakeholders at WeLoveVideo are interested in understanding what the CRM will look like prior to development. There are a variety of ways the project team can approach design, some being more effective in terms of giving the stakeholders a view into what the final product will look like. Some of the approaches include a storyboard and presentation. The storyboard provides a visual display, while the presentation provides the necessary information.

Develop a proposal presentation of how you will approach the design for the WeLoveVideo CRM project.

Create an 8- to 10-slide multimedia-rich (charts, images, graphics, video, or audio) presentation with speaker notes.

Identify the recommended design approach (e.g., user experience design, bottom-up design, or one of your choosing) and explain why this approach was chosen over others

Propose steps and processes that will be adhered to, along with the output expected from the approach

Design a storyboard that represents general screen layout and user flow within the system

Explain the pros and cons of the chosen approach against other options

Cite at least two reliable references 

Format your citations per APA guidelines.

Presentation Note: The slides in your multimedia-rich presentation should only contain essential information and as little text as possible. Do not design a slide presentation made up of long bullet points. Your speaker notes must convey the details you would give if you were presenting. 

The following scenario will be used for all assessments in this course:

WeLoveVideo is a mid-sized entertainment corporation providing streaming video services to its customers globally. The company has become very successful, growing from 10 to 200 employees in the past 5 years and gaining significant traction in the market. In addition, their sales have grown from $100,000 to $40,000,000.

The primary services provided are streaming videos, primarily focusing on major network shows along with current and past movie releases. They are seen as an alternative service provider to local cable and satellite TV.

As the company has grown in size and revenue, they have found that the database they use to track customer data has become obsolete. The sales team has a hard time determining both its prospective customer demographics and its current customer preferences. Sales is in desperate need of a customer relationship management (CRM) system, but is currently well positioned to invest in improving the internal systems.

The company has a functional organizational structure. The departments include Sales, Human Resources, Finance, Operations, and Product Development. Each of these departments is influenced by customer data and will be potential users of the new CRM. In addition to its internal users, it has partnered with all the major networks to license and make its shows available to customers.

A CRM system will be no small undertaking. Currently, customer data is being managed through multiple spreadsheets that will need to be migrated. In addition, Finance uses a system called “Adaptive Insights for Finance,” which will need to interface with the CRM to ensure the integration of financial data.

Beyond this, WeLoveVideo has focused on improving its employees’ overall worker experience in terms of applications, workflow, and user interface. This new CRM will need to account for this, ensuring that the user interface and design lead to strong adoption across its users.

Speed of implementation will be critical, as the company senses it is losing money daily due to the lack of centralized customer information. WeLoveVideo is hoping that this CRM implementation will not only streamline Sales and Support, but will also provide valuable insights about its customers’ viewing and buying behaviors that will lead to increased market share.