Methodology in Project Management-Free-Samples-Myassignmenthelp.com

Questions: 1.Define what a Methodology is and the role it serves in Project Management. 2.Choose two Methodologies from this list to Compare and Contrast. 3.Discuss about the Processes relate to the Project Life Cycle (PLC). Answers: 1.The project methodology is based on handling the planning, execution, controlling and working on the team to achieve the goals with meeting the specific changes and the criteria. The project is based on producing the unique product along with services defined approach with the time constrains. The management needs to work on the project documentation with development process based on scope, time and the budget. The project management gets enhanced with the use of methodology as there are proper planning, designing, monitoring and then controlling all the engineering projects with the agile project management which focus on the adaptability to change the situations with consistent feedback from the clients. (Mayo et al., 2016). The chain for the project management is also for the defined resources, with the planning based on coordinating and working over the limited standards to execute the project 2.The waterfall project management is to handle the things with the concepts and the quality, where there is a defined assurance and the project completion. There is a need to maintain and work on the plans till there are no alterations needed. This methodology focus on the planning and then predict all the important processes. (Arthur et al., 2017). The agile project management has been to handle the different situations with the consistent feedback where the clients come with particular feedback for the members. The idea is about handling the clients and the management with proper production, that results in the change of the requirements with shift in the team assignments as well. The ideal process is for the new and similar smaller projects that are related to the accelerated development patterns. 3.The waterfall is related to the gathering of the documents, with proper approach and defined schedules, designing, code and the unit tests. (Vijaysarathy et al., 2016). This brings a change in the performance of the user acceptance testing, along with fixing the issues, with delivering the finished products as well. The representation is about how to review and approve the customer designing before it begins, where the waterfall works with the developments and the customers who agree on what needs to be delivered. Along with this, there is a proper designing and the planning, progress is measured with the scope to work. The development in the team with the involvement of the work is set with the active phase and the documentation is through coding. (Brinker et al., 2016). The exceptions are related to the reviews, status meetings and the presence of the customers. The designing is completed with the development where the approach is about handling the multiple software components. The agile methodology is for the team based approach with the focus on the rapid devoir and the application. The time boxed advantage is set into phases were the sprints are in defined duration to work and set the deliverables in a planned manner. For the project lifecycle, the customer has a very frequent way to handle the opportunities to work on what the decisions need to be set and how the customer is able to bring the strong sense of ownership with working on the project teams as well. The development is focused with the frequent directions that comes from the side of customer. The higher degree of the customer involvement with the project requirements where the development is dedicated to the project on the time boxed delivery and the reprioritization. There are items which are then allocated in a set timeframe. The additional prints are found to be handling the project costs with the involvement of the customer in a overall time and cost. The Agile development leads to the met hod of refactoring with the scope that includes the initial architecture and the designing. the system can easily hold the reduction with the quality that is pronounced on the large scale. (Larson et al., 2016). References Arthur, J. D., Dabney, J. B. (2017, April). Applying standard independent verification and validation (IVV) techniques within an Agile framework: Is there a compatibility issue?. InSystems Conference (SysCon), 2017 Annual IEEE International(pp. 1-5). IEEE. Brinker, K. R., Marcolina, R. C. (2016, November). A LESSON IN CONFLICT MITIGATION: INTEGRATING DIVERGENT DESIGN PHILOSOPHIES. InInternational Telemetering Conference Proceedings. International Foundation for Telemetering. Larson, D., Chang, V. (2016). A review and future direction of agile, business intelligence, analytics and data science.International Journal of Information Management,36(5), 700-710. Mayo, D. B., Johnson, T. C. (2016). Software Systems Engineering and Rapid Development Methods. Vijayasarathy, L. R., Butler, C. W. (2016). Choice of software development methodologies: Do organizational, project, and team characteristics matter?.IEEE Software,33(5), 86-94.