The paper "Agile Project Management Framework" is an outstanding example of management coursework. The achievements of much software are being hindered by the nature of software architecture. Some of the various qualities attributes which include security, maintainability, and performance can only be enhanced through the improvement of the software architect (Hussain, Slany & Holzinger 2012). There are several methods that have been developed by scholars to support software architecture analysis. It should be noted that these architecture have several commonalities among them. Some of the commonalities include artifacts, activities, and stakeholders involved in the project.
Since among all the methods, there is no clear cut on which of them is the best, it is very important to have an objective approach in choosing the method. In order to address this issue, a more comprehensive approach needs to be taken, in comparing the agile project and PRINCE2. We are going to use the two project management framework, that is; Agile project management Prince2 project management The agile project management framework Agile development refers to a group of methods that challenges the traditional linear based approach to the development of software (Turk, France & Rumpe 2014).
Though it is a software development approach, the method can be incorporated into the lifecycle of information technology project management (Ambler 2012). Scrum is one of the lightweight process frameworks to be used in this discussion. This framework is commonly applied in conjunction with agile methods. It can be used as a lightweight framework to help in the execution phase of the project(Turk, France & Rumpe, 2014). It usually works well on projects that include the application of software development.
One of the merits of using this framework is that it works quicker and adapts quickly to changing designs. It works in modules which are called sprint where team members have a specific time period to work on the suggested functionality with a more solidified set of requests. In this framework, sprints are normally supplemented by daily and weekly status meetings (Ambler, 2012).
Ambler, S. 2012 Agile database techniques: Effective strategies for the agile software developer. John Wiley & Sons.
Bentley, C. 2015 The PRINCE2 Practitioner: From Practitioner to Professional. Routledge.
Burns, J., & Sangster, A. 2012 This project is big enough for both of us!-Managing documentation projects using Scrum and PRINCE2. Communicator-the Journal of the Institute ofScientific and Technical Communicators, 36.
Da Silva, T. S., Martin, A., Maurer, F., & Silveira, M. 2011 User-Centered Design and Agile Methods: A Systematic Review. In AGILE (pp. 77-86).
Dodd, S., & Wang, Y. 2012 Prince2 And Entrepreneurship: Risk Taking & Risk Management In Two Micro-Sized Restaurants.
Ghosh, S., Forrest, D., DiNetta, T., Wolfe, B., & Lambert, D. 2012 Enhance PMBOK® by Comparing it with P2M, ICB, PRINCE2, APM and Scrum Project Management Standards. PM World Today, 14(1), 1-77.
Haq, A. N., & Boddu, V. 2015 Analysis of agile supply chain enablers for Indian food processing industries using analytical hierarchy process.International Journal of Manufacturing Technology and Management, 29(1), 30-47.
Has, A., & Bode, V. 2015 Analysis of agile supply chain enablers for Indian food processing industries using analytical hierarchy process. International Journal of Manufacturing Technology and Management, 29(1), 30-47.
Hinde, D. 2012 PRINCE2 Study Guide. John wiley & sons.
Hussain, Z., Slany, W., & Holzinger, A. 2012 Agile Software Developement Methods and Usability/User Centred Design: Prespectives from an Online Survey. Journal of Systems and Software, 54, 86-88.
Murray, A. 2011 PRINCE2® in one thousand words. United Kingdom: The Stationery Office.
Saad, S., Abdullah, I., Asma, O., Muhammad Saad, K., & Abdul Qadir, A. 2013 PRINCE2 Methodology: An Innovative Way of Project Management.
Tomanek, M., & Juricek, J. 2015 Project Risk Management Model Based on PRINCE2 and Scrum Frameworks. International Journal of Software Engineering & Applications, 6(1), 81.
Turk, D., France, R., & Rumpe, B. 2014 Assumptions underlying agile software development processes. arXiv preprint arXiv:1409.6610.
Turk, D., France, R., & Rumpe, B. 2014 Limitations of agile software processes. arXiv preprint arXiv:1409.6600.
Williams, L. 2012 What agile teams think of agile principles. Communications of the ACM, 55(4), 71-76.