1.The methodology is about how the project managers are able to employ for the design, planning, implementation and setting the achievement for the better project objectives. The adaptive project framework is based on the time and cost which is considered to be constant for the project scope with maximised business value. (Alliance, 2016). The project managers work on delivering the projects and setting principles, themes, frameworks and processes that are sets to provide a stack with PMBOK or XP. This includes the delivering of the projects which includes the proper working collaboration and responding to the changeover following a plan. The set of values are defined with the principles to follow the process that needs to be applied to a particular object. Through this, there is also a major possibility to work on the individuals and the interactions over processes and tools so that there is an easy methodology setup.

2.Agile Methodology: This is based on the project management, where there is a need of handling adequate delivery of the process with improved framework that has been put to practice. The goal of the same is to improve the communication, teamwork and the development speed. (Sharma et al., 2017). Through this, there is a possibility to handle the sprints, scrums and the backlogs which are set with the ongoing framework development and maintaining the complex products. The approach is based on defining and setting the roles, to meet the tools in effective manner. The incremental forms of the delivery are found to be valuable with the easy shipping functionality. Agile is considered to be the technology which is for the setup for the self-management of the teams and for delivering and defining the goals that would be to create the health tension which would advocate for the small and the cross-functional team of people upto 9 in number. The collection is for the user stories defined under the product ownership.

Waterfall methodology: This is based on handling the SDLC where there is a proper project management approach to work on planning and handling the agile approach as well. The planning is based on charging and working over the plans which adhere to the requirements and delivering the project. The requirements need to be defined with the plans adapted through the necessary changes. (Ghafoor et al., 2017). The designing, implementation, testing and the maintenance is possible through this, where the approach mainly reflects about the scope to handle and revise the concepts related to the testing stage.

3.The agile technology is based on advocating with the cross-functional team where there is a need to handle the development with the team report. It works with the development and improvement in the progress of the team. (Campbell et al., 2016). The technology is facilitated mainly by enabling and leading the demos and the reviews with proper and best working. The optimisation and improvement is designed through the software development where there are other agile artefacts that could be leveraged and set in the creative agency world. The standards for the development project include the agile methods where there is a possibility to work in fixed budgets with providing heavy constraints.

Waterfall is considered as one of the project where the requirements are fixed in a well-documented and clear manner. The technology is understood with the project that is short with no additional value which is gained from going agile. The approach of the project is to handle the details under a particular budget, with timeline and scope. The tasks and the testing stages are examined with the forms that include the changes that are designed in the concept stages.

References

Alliance, S. (2016). What is Scrum? An Agile Framework for Completing Complex Projects-Scrum Alliance. Scrum Alliance. Available at: https://www. scrumalliance. org.

Campbell, J., Kurkovsky, S., Liew, C. W., & Tafliovich, A. (2016, February). Scrum and agile methods in software engineering courses. In Proceedings of the 47th ACM Technical Symposium on Computing Science Education (pp. 319-320). ACM.

Ghafoor, F., Shah, I. A., & Rashid, N. (2017). Issues in Adopting Agile Methodologies in Global and Local Software Development: A Systematic Literature Review Protocol with Preliminary Results. International Journal of Computer Applications, 160(7).

Sharma, A., & Bali, M. (2017). Comparative Study on Software Development Methods: Agile vs Scrum