1) The two SDLC methods I would consider are: Waterfall and Agile The waterfall methodology is a sequential design process. Completion of one phase (Requirements, Design, Implementation, Verification and Maintenance) leads to the next phase. In the waterfall methodology, once a client signs off a project, changes are not allowed. Therefore, extensive planning and documentation is necessary at the beginning of the project in order to avoid errors which may lead to rework at the end of the process. It is very expensive when changes are made at any phase of the project. The waterfall methodology keeps every team member at alert and attentive during the process in order to avoid or reduce error. The waterfall methodology is very useful when users really know what they wanted with a well-documented requirement. On the other hand, Agile software development methodology became popular as a result of the disadvantages of the waterfall and spiral methodologies. Agile method is based on iterative and incremental development where requirements and solutions are gathered through interaction between the team members and users. It makes it easy to know who is accountable for what. Agile method involves users/clients from the beginning to the end, thereby, needed changes are made as the development progresses. Extensive documentation may not be required because of its flexibility that allows changes to be made to requirement at any point in time, but this might lead to a different product. The quality delivered on the long run is high and delivery is faster. Team members’ and customers’ feedback gives room for improvement on the products throughout the process. Comment: 2) The two SDLC Methodologies chosen are: Scrum VS Kanaban To compare, these two methodologies allow members of the team to conduct multiple projects at a time. Both of these lean on Agile methodology very closing. "Agile software development is based on an incremental, iterative approach. Instead of in-depth planning at the beginning of the project, Agile methodologies are open to changing requirements over time and encourages constant feedback from the end users." ("What's the Difference? Agile vs Scrum vs Waterfall vs Kanaban ," 2017). Both of these also use pull scheduling which means that it the scheduling for any major activities is divided by periods which can identify what can be improved on. All teams on both Kanaban and Scrum must me cross functional. To contrast while Scrum and Kanaban are both properties they have differences. Scrum requires you to have specific roles where as Kanaban does not. Scrum also has limits to the work in progress where as Kanaban has WIP for each workflow that is being presented. The scrum board is reset constantly after each sprint where as when working with Kanaban it is continously used.("What's the Difference? Agile vs Scrum vs Waterfall vs Kanaban ," 2017). What's the Difference? Agile vs Scrum vs Waterfall vs Kanban . (2017). https://www.smartsheet.com/agile-vs-scrum-vs-waterfall-vs-kanban Comment: 3) The two SDLC methods I would consider are: Waterfall and Agile The waterfall methodology is a sequential design process. Completion of one phase (Requirements, Design, Implementation, Verification and Maintenance) leads to the next phase. In the waterfall methodology, once a client signs off a project, changes are not allowed. Therefore, extensive planning and documentation is necessary at the beginning of the project in order to avoid errors which may lead to rework at the end of the process. It is very expensive when changes are made at any phase of the project. The waterfall methodology keeps every team member at alert and attentive during the process in order to avoid or reduce error. The waterfall methodology is very useful when users really know what they wanted with a well-documented requirement. On the other hand, Agile software development methodology became popular as a result of the disadvantages of the waterfall and spiral methodologies. Agile method is based on iterative and incremental development where requirements and solutions are gathered through interaction between the team members and users. It makes it easy to know who is accountable for what. Agile method involves users/clients from the beginning to the end, thereby, needed changes are made as the development progresses. Extensive documentation may not be required because of its flexibility that allows changes to be made to requirement at any point in time, but this might lead to a different product. The quality delivered on the long run is high and delivery is faster. Team members’ and customers’ feedback gives room for improvement on the products throughout the process. Comment:
Purchase answer to see full attachment