Fluent Essays

Assignment Content     After consideration of your proposal from Week 1, the WeLoveVideo, Inc. CIO is having a hard time envisioning how the project would be executed based on your recommendations. She has asked your company to develop a project plan in both waterfall and Agile so she can better understand the implications to her team.  Using Microsoft® Excel®, Project, or another project management tool of your choice that is approved by your instructor, develop one milestone-level project plan using the waterfall SDLC and a second milestone-level project plan using Agile SDLC that does the following: Describes the inputs and outputs for each phase of a project within each milestone based upon the SDLC applied. Contains at least one clear milestone at the end of each project phase and milestones within phases where applicable. Incorporates comprehensive SDLC phases based on each SDLC type.  Submit your assignment. Wk 1 - Signature Assignment SDLC Comparison SDLC Comparison Introduction The paper seeks to provide an SDLC comparison for two SDLC models of system developments. This comparison will help implement the CRM systems for WELoveVideo, Inc by proposing a recommendation of the best model based on the findings. The two mains SLDC models of focus in the waterfall and agile SDLC. Phases of a waterfall and agile SDLC Waterfall and agile are two distinctive models of processes that help to complete a project. The two models have several phases that help the project teams document their business effectively and successfully. Foremost, waterfall models come with six different phases. The first phase is the Requirements, where project teams understand what is required and needed for design, functions, and purposes. System design comes next and involves preparing project design after studying requirements specifications (Olorunshola & Ogwueleka, 2021). Implementation is the third phase, where the writing of the source code happens as per the requirements. The third phase is testing. Here, the testing team checks the code for any potential problems. Lastly, its the Deployment and maintenances where the project is released into the markets for installation, and modifications are made on the system if need be. Agile also comes with its distinctive phases. This includes the concept where the project scope is determined by the owner and presented to the organization. Inceptions follow where the project team creates a mock-up of the user interface and architecture (Shaikh & Abro, 2019). The third phase is the Iteration, where construction of the source code occurs, and the products functionality is built. The fourth phase is Release, where the Quality assurances team performance tests on the product, which is then released. The last two stages, maintenance, and retirement. At this stage, the software is now fully deployed and made avoidable to end-users, but replacement of the project can happen if it becomes obsolete. Documentation differences The main difference in the models documentation is that Waterfall documentation adopts a sequential methodology where tasks are handled in a liners process. In contrast, Agile documentation adopts an iterative methodology that incorporates a collaborative and cyclic process (Shaikh & Abro, 2019). Each of the methods gets to be used depending on the preferences and nature of the project Stakeholder’s expectations The mains stakeholder expectations revolve around three groups of individuals. The first group is the project team who expects the time, support, and tools needed to complete the project (Olorunshola & Ogwueleka, 2021). Management and executive expect the project to end successfully, and it will save on company finances. The last group is the clients who expect all the requirements to be executed and followed. Pros and cons The mains pros for waterfall is that it has no financial surprises, and the testing work is made easy. However, it has a longer delivery time and lacks flexibility (Shaikh & Abro, 2019). The model can be used when the projects outcome is crystal clear and in are with low uncertainty. On the other hand, the agile model is highly flexible, and the products tend to get to the market faster—however, its hard to measure progress and predict. The model can be used when the client wants to be highly involved and the company wants to quickly finish the projects. Attributes WeLoveVideo has several attributes that can dedicate the SDLC model to recommend. The company loves better, faster, and cheap approaches to quickly meeting customers demands and increasing team productivity. It also handles projects with aggressive deadlines, a high degree f novelty, and a higher degree of complexity (Olorunshola & Ogwueleka, 2021). Lastly, the company have a very skillful team that can work on sophisticated projects Conclusion In conclusion, depending on the company attributes, the differences presented by the two models. The best model for the company is the agile SDLC model to help the company deliver projects with aggressive deadlines using a cheaper approach. References Olorunshola, O. E., & Ogwueleka, F. N. (2021). Review of System Development Life Cycle (SDLC) Models for Effective Application Delivery. In Information and Communication Technology for Competitive Strategies (ICTCS 2020) (pp. 281-289). Springer, Singapore. Shaikh, S., & Abro, S. (2019). Comparison of traditional & agile software development methodology: A short survey. International Journal of Software Engineering and Computer Systems, 5(2), 1-14. 2 SDLC Comparison University of Phoenix CMGT555 1 Phases of Waterfall and Agile SDLCs Waterfall SDLC Requirements: understanding what is to be designed, functions, and purposes System design: Preparing system design after studying requirements specifications. Implementation: writing of the sources as per the requirements Testing: Testing team checks the code for any potential problems. Deployment: the project is released into the markets. Maintenance: this happens after installation. Modifications are made on the system if need be. Agile SDLC Concept: project scope determined by the owner. Inception: the project team is created who also create a mock-up of the user interface and architecture. Iteration: constructions occur here, and the bare functionality of the product is built. Release: Quality assurances team performance test on the product, which is then released Maintenance: software is now fully deployed and made avoidable to end-users. Retirement: replacement of the project if it becomes obsolete. 2 Waterfall and agile Documentation Differences Waterfall documentation adopts a sequential methodology where tasks are handled in a liners process. The tasks are handle in a simple process, one after the other till the end. Agile documentation adopts an iterative methodology that incorporates a collaborative and cyclic process. It provides room for the process to move through a series of cycles throughout its lifetime. Each method can be used depending on the preferences and nature of the project some projects are more iterative while others are sequential. 3 Stakeholder’s expectations The SDLC method to adopt varies depending on the stakeholders expectations. The project team: Expects to have all the time, support, and tools needed to complete the project Management and executive; Expects the project to be completed successfully Expects the project to save on company finances Clients: Expects all the requirements o be executed and followed. The trick to making sure the project runs smoothly is managing all stakeholders expectations by putting them in balance. 4 Pros and Cons Waterfall SDLC Pros Cons No financial Surprises Longer delivery time The outcome is crystal clear. Needs can be difficult to define Time scales are kept.   Testing is made easy. Lacks flexibility Agile SDLC Highly flexible Documentation gets left behind Allows room for better communication Hard to predict The product gets to market faster.   One can get immediate feedback. Hardtop measure progress   Faster to detect and fix issues.   5 Graphic summary 6 WeLoveVideo attributes WeloveVideo loves a better, faster, and cheaper approach to quickly meeting customers demands and increasing team productivity. The company has high regard for transparency to offer clients a chance to be involved throughout their project. The company utilizes very complicated technology with a very skillful team. The company also handles projects with aggressive deadlines, a high degree f novelty, and a higher degree of complexity. Most of the time companys projects are new and designed according to customers specifications. 7 References Olorunshola, O. E., & Ogwueleka, F. N. (2021). Review of System Development Life Cycle (SDLC) Models for Effective Application Delivery. In Information and Communication Technology for Competitive Strategies (ICTCS 2020) (pp. 281-289). Springer, Singapore. Shaikh, S., & Abro, S. (2019). Comparison of traditional & agile software development methodology: A short survey. International Journal of Software Engineering and Computer Systems, 5(2), 1-14.