SDLC Methodologies Phases Analysis Report for WeLoveVideo, Inc

SDLC Methodologies Phases Analysis Report for WeLoveVideo, Inc

With WeLoveVideo, Inc. already growing exponentially, adding a Customer Relationship Management (CRM) system helps manage customer information. It assists in better sales and support operations and knowledge of customer behavior. For this CRM implementation project, the most relevant methodologies from the Software Development Life Cycle are waterfall and Agile. There are different phases and processes, each with its implications for the success of a project. This report will compare the phases of SDLC unraveled within the WeLoveVideo CRM project, contrast the Waterfall and Agile methodologies, and enlist their steps accordingly. Also, a list of 15 business requirements for the CRM project will be represented as user stories.

Comparing Waterfall and Agile SDLCs

The two methodologies, Waterfall and Agile SDLC, have radical differences in their orientation. Exploring these differences will help WeLoveVideo select the right approach for its CRM project.

Waterfall SDLC Phases

The waterfall model is waterfall-oriented SDLC, which is linear and sequential in its model, and it requires that the completion of each phase be done before entry into the next phase (Balaji et al., 2012). It consists of the following phases:

1. Requirement Gathering and Analysis: All the project requirements are gathered up-front. This includes understanding the stakeholders’ needs, which becomes all the more critical in the case of the WeLoveVideo CRM project, considering its multiple department involvements.
2. System Design: The architecture for the system is designed based on the requirements gathered.
3. Implementation: This is the stage when actual coding and development of the CRM system occur.
4. Testing: The developed system would be tested rigorously for bugs, errors, and inconsistencies.
5. Deployment: After the testing, the system gets deployed among the users.
6. Maintenance: After deployment, the issues, updates, or changes are handled in this phase.

The waterfall model’s structured nature is apt for projects where the requirements are precise and do not change over time. Still, the rigidity created by the structured approach becomes a disadvantage, and this might not be best fitted for a project like WeLoveVideo’s CRM, where the requirements may evolve depending upon the users’ feedback.

Agile SDLC Phases

The Agile development model is iterative and incremental, focusing on adaptability and customer feedback. It decomposes the project into small cycles called sprints, after which the same process is repeated many times. The following are some of the most common steps taken while using the Agile method:

1. Project Initiation and Planning: At this step, the project’s vision and goals can be identified. In the case of WeLoveVideo, this would mainly entail seeing how the CRM project will fit into the overall company growth strategy.
2. Requirement Gathering and Prioritization: Collect and prioritize the requirements based on the business value.
3. Sprint Planning: The development team plans the work for the first sprint.
4. Development and Testing: In every sprint, development is done by the development team, and small portions of the CRM system are tested. Due to this iterative process, feedback and adaptation keep going (Schwaber & Sutherland, 2017).
5. Review and Retrospective: At the end of each Sprint, the team reviews progress against the backlog for the iteration, gets feedback, and adjusts the process for the next cycle.
6. Release and Deployment: As soon as the system’s core functionality is in place, the system is deployed to the users incrementally, where incremental improvements can be based on actual usage.

Agile’s iterative nature is beneficial in a project like WeLoveVideo’s CRM, where the goal is to constantly collect customers’ feedback (Boehm, 2008). However, it can be impractical in some environments, which are less flexible and have stringent deadlines.

Waterfall SDLC in the WeLoveVideo CRM Project

The WeLoveVideo’s CRM project would take up the following organized steps in the waterfall SDLC:

Requirement Gathering and Analysis

The first step in the process would involve stakeholders, including Sales, HR, Finance, Operations, and Product Development, who would gather detailed requirements (Royce, 2009). The major TV networks would also have requirements from the licensing and customer access to content perspective. The challenges at this stage would be to ensure that all requirements are fully captured and that there is no room for many changes later in the process.

System Design

In this phase, the WeLoveVideo technical team would design the CRM system architecture, which would include decisions on the database structures, integrations with existing systems like “Adaptive Insights for Finance,” and the user interface that would guarantee ease of use to employees from all departments.

Implementation

After the design, the developers start coding the CRM system. This step would, therefore, be very detailed and coordinated among the developers since migrating data from different databases and spreadsheets and integrating the system with financial and licensing systems requires a lot of work.

Testing

After implementation, the system would then be tested for functionality, performance, and compatibility with existing systems. Usability testing would also be important at this stage since WeLoveVideo cares about enhancing employee work experiences.

Deployment

The CRM system will be deployed to all departments and external partners once the set tests have been completed. This will ensure that employees are taught how to use the system properly, possibly by conducting some training sessions (Foster & Towle Jr, 2021).

Maintenance

It would require maintenance post-deployment in case any issues occurred. It would also be updated to reflect future requirements related to changing business needs.

Agile SDLC in the WeLoveVideo CRM Project

Using Agile for the WeLoveVideo CRM project would involve several cycles: planning, development, testing, and review. The following details how two Agile cycles could be implemented:

Cycle 1: Sprint 1

Planning

The project team meets with stakeholders to identify the CRM’s high-priority features, which will most likely include the core functionality of customer data management, financial system integration, and user interface design.

Development

The team begins working on these features and creates something simple and valuable for the Sales and Finance departments.

Testing

Testing is done at the end of the sprint to ensure that the core functionalities work as expected and that the system interfaces correctly with the existing database.

Review

The project team obtains user feedback from the sales and finance departments. Based on the feedback, they could have realized other requirements or adjustments to be made during the next sprint.

Cycle 2: Sprint 2

Planning

In the second sprint, the team prioritizes features for the Product Development and Operations departments. User feedback obtained in Sprint 1 will also introduce new requirements to the backlog.

Development

The development team works on additional functionalities, such as data analytics about customer behavior and content recommendations.

Testing

This is done at the end to ensure that the new functionalities work as expected and no disruption of existing features occurs, just like in Sprint 1.

Review

The team reviews the feedback of all departments and partners. The feedback is considered, and changes are adapted to it. Then, the cycle starts again with a continuous improvement motive.

This is an iterative process that provides flexibility and allows easier modifications to evolving business needs. Agile methodology also enforces continuous engagement with the users so that the CRM system serves all stakeholders (Pressman, 2005).

Business Requirements as User Stories

To capture the business requirements for the WeLoveVideo CRM project, the individual needs of various stakeholders must be represented by user stories. Below are 15 user stories in the project:

1. As a sales manager, I want access to customers’ real-time data to target potential leads.
2. As a finance manager, I want integration between the CRM system and Adaptive Insights so that I get consistent financial data on boards.
3. As a customer service representative, I want to view a customer’s purchase history so I can provide personalized support.
4. As a product development lead, I want to see an analysis of customer viewing behaviors to use this information when recommending new content offerings.
5. As an HR manager, I want the CRM system to track employee interactions with customers so it can determine their training needs.
6. As a network partner, I want to obtain reports regarding usage of content licensing to help in assessing performance
7. As a sales executive, I want automated email campaigns based on customer demographics so that I am in a position to enhance the effectiveness of marketing efforts.
8. As a finance executive, I want to be able to generate financial reports that include customer lifetime value metrics.
9. As a user interface designer, I want an intuitive CRM system that users across all departments will learn on their own.
10. As a sales representative, I want to see customer feedback inside the CRM to tune my pitch.
11. As a marketing executive, I would like to be able to track each customer’s preference for a particular show so that I can customize promotional efforts accordingly.
12. As an operations manager, I want the CRM to comprise the system performance metrics so that the user experience goes smoothly.
13. As a content partner, I want to be notified when customer viewing trends change so that I can modify the content offerings to stay on top.
14. As a project manager, I would like the CRM system to have the functionality of supporting task management so that progress on customer-related initiatives could be traced.
15. As an IT administrator, I want role-based access control in the CRM system so that sensitive customer data is secure.

Conclusion

The implementation of CRM at WeLoveVideo, Inc. would be critical for the company in terms of the sustenance of growth and improvement in customer engagement. Though the structured Waterfall SDLC and the flexible Agile SDLC both have advantages, each has different methodologies to apply. The Waterfall model is functional in a linear manner; it is useful where the requirements are relatively stable. On the other hand, Agile is iterative, more adaptive, and better positioned within dynamic environments. Properly choosing an SDLC and ensuring user stories guarantee that the CRM system will meet business requirements will be critical to this project’s success.

References

Balaji, S., & Murugaiyan, M. S. (2012). Waterfall vs. V-Model vs. Agile: A comparative study on SDLC. International Journal of Information Technology and Business Management, 2(1), 26-30.

Boehm, B. W. (2008). A spiral model of software development and enhancement. Computer, 21(5), 61–72.

Foster, E., & Towle Jr, B. (2021). Software engineering: a methodical approach. Auerbach Publications.

Pressman, R. S. (2005). Software engineering: a practitioner’s approach. Palgrave Macmillan.

Royce, W. W. (2009). Managing the development of large software systems. Proceedings of IEEE WESCON. Los Angeles, 328-388.

Schwaber, K., & Sutherland, J. (2017). The definitive guide to scrum: The rules of the game. Scrum. Org.

ORDER A PLAGIARISM-FREE PAPER HERE

We’ll write everything from scratch

---

As an IS manager, you must be able to describe the key inputs and outputs that determine a project’s scope. Choosing the right SDLC for the project and defining the milestones that determine when each phase is complete is also part of that process.

For this assessment, you will examine the phases of the SDLC in the context of a case study that you will use for the assignments in this course.

Read the WeLoveVideo Inc. Case Study.

Write a 1,050- to 1,400-word report, analyzing the SDLC methodologies and phases of the WeLoveVideo project. Include the following:

-Compare the phases of waterfall and Agile SDLCs.
– Explain the steps of the WeLoveVideo CRM project in the waterfall SDLC.
– Explain the steps of the WeLoveVideo CRM project in the Agile SDLC. Include a minimum of 2 cycles to show the iterative nature of Agile methodology.
-Create a list of 15 business requirements written as user stories for the WeLoveVideo CRM project.