CIS 604 Discussion 2

docx

School

Park University *

*We aren’t endorsed by this school

Course

604

Subject

Information Systems

Date

Oct 30, 2023

Type

docx

Pages

Uploaded by ChefIceHamster

Many software companies exist in the modern world. Each company uses unique methodologies for project development. Project Managers could deviate from the pre-determined methodology during the requirements-gathering process, but a change order may be required. Below, I will describe the six most common methodologies and how their implementation methods relate and differ. The difference between Agile and Waterfall: The Agile methodology is operations based: The five operations are started, planned, implemented, evaluated, and close. These operations are addressed by the agile methodology in iterative cycles, which helps in reverting to the planning processing instead of an inefficient design. Moreover, this aids in providing flexibility, enabling the project team to react positively to change (Baker, 2022). Waterfall - dissimilar to agile methodology, the waterfall methodology is a linear technique, i.e., the next step will only be initiated once the first step finishes. Following are the five main steps of the Waterfall approach: scoping, designing, launching, evaluation, and closing. Although the steps of both methodologies are similar, the Waterfall is more rigid than agile, and hence it is more qualified to be used in predictable projects with direct objectives. Both Waterfall and agile are methodologies used for project development, and both are used for software development and have distinct phases in the operational process. Agile works on big or larger projects due to its collaborative nature and flexibility. Waterfall works efficiently on smaller or medium projects because it can be easily simplified, works on the requirements, and helps deliver a project quickly. Each methodology has unique characteristics that make it suitable for a specific project. CPM and CCPM: CPM and CCPM focus on project scheduling and differ in processes and operations. The CPM method involves the start and finish pass analysis through a schedule of a network path, and the CCPM method modifies the schedule to manage the time. This jobs series is known as the critical path. If any of these critical jobs are postponed, the entire project will be at elevated risk of being delayed. Once the critical path is identified, the project team will be allowed to distinguish the earliest time the project can be completed and identify the recent start time (Nerur et al., 2005). CPM focuses on project scheduling and considers the number of activities of the project. Similarly, CCPM focuses on time buffers and helps to manage limited resources. CCPM - like CMP, the Critical Chain Project Management approach distinguishes the time and sequence in which the jobs of the project will be completed. The difference between the two methodologies is that CCPM focuses on the project's resources, unlike CMP, which focuses on project completion time (Scheiner, 2023). SCRUM and SIGMA: Scrum will focus on managing the projects in a short sprint by project values and requirements, whereas Six Sigma approaches the project in a minor way on an existing process. The Scrum method uses the Agile framework and Six Sigma. Both methods view projects in a sprint and are good at process improvement and solving problems between teams and clients. Each method has a standard workflow to solve problems from different standpoints. A combination of both on a single project will serve the project well (Eby, 2017). Six Sigma is used to correct or improve the

processes or products when three fail to fulfill the performance criteria and requirements (Nitansh, 2022). In scrum methodology, defined product backlogs are increased into tasks. After that, these tasks are prepared via sprints of 1-4 weeks. The project team produces a deliverable product increase when one sprint is finished. I prefer the agile methodology. The reason for choosing this methodology is that this method does not bind a person to follow any specific steps in a specific order. The main advantage of the agile method is that we can add new features, and by discussing with the clients, the changes can be modified, and the cost of the method is also low (Code, 2022). It saves time, as there is no need to wait for the entire cycle to be addressed and correct any issues. Furthermore, agile uses in-person collaboration between team members during the daily scrum meetings. These conversations and sharing of considerations can bring novel thoughts to knowledge. For any project development, teamwork and discussion would play vital for successful output. Reference: Baker, R. (2022, August 2). Scrum vs. Kanban vs. Agile vs. Waterfall – a side-by-side comparison . Task. https://www.ntaskmanager.com/blog/scrum-vs-kanban-vs-agile-vs- waterfall/#:~:text=Scrum%20is%20focused%20on%20completing,Agile%20emphasizes %20adaptable%2C%20concurrent%20processes Eby, K. (2017, February 12). What is the difference? Agile vs. Scrum vs. Waterfall vs. Kanban . Smartsheet. https://www.smartsheet.com/agile-vs-scrum-vs-waterfall-vs-kanban Nerur, S., Mahapatra, R., & Mangalaraj, G. (2005). Challenges of migrating to agile methodologies. Communications of the ACM , 48 (5), 72–78. https://doi.org/https://eds.s.ebscohost.com/eds/pdfviewer/pdfviewer?vid=1&sid=2899e5ff- 253a-4c50-9b21-cfb4efd50cdb%40redis Nitansh. (2022, July 9). agile, Scrum, Waterfall, and More – top project management methodologies and how they are different . Flow. https://www.getflow.com/blog/agile- scrum-waterfall-and-more-top-project-management-methodologies-and-how-theyre- different Scheiner, M. (2023, June 8). Project management methodologies comparison (11 pm methods). CRM.org. https://crm.org/news/project-management-methodologies

Response to Professor's comment: The primary difference between agile vs. waterfall is that the waterfall approach values planning, while the agile approach values adaptability and involvement. Unlike waterfall approaches, where there is a distinct testing phase, agile methods insist on testing through every project phase. Agile breaks the project into individual deliverables instead of creating a timeline for one big software development project. These ‘time-boxed’ phases are called ‘sprints and last just a few weeks. Once each sprint is completed, the feedback from the previous stage is used to plan the next one.

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version