Discussion on PMBOK and Agile Model-Free-Samples-Myassignmenthelp

Question: Discuss about the Contrast between PMBOK and Agile Method of Software Development. Answer: Introduction This report is all about contrast between PMBOK and Agile model of software development. Agile model is generally the best model for management of different project. In earlier days waterfall model of software development was considered best for managing various project (Allen, 2012). There are generally three subdivision of agile model that are Extreme programming (EX), feature driven development (FDD). XP stands for Extreme programming which was developed in 1990 is a type of agile model developed at an organization called Chrysler corporation. FDD acronym of feature driven development is an upgrading software development which consist of five steps that are upgradation of overall model, making a list of specific features, make a plan for different areas, having a set of features, creating features (Balaji Murugaiyan, 2012). Scrum is a technique used for developing various products and it is developed by having a proper observation on different teams. This method follows project w ork through a series of iteration or loop which is known as sprints. PMBOK stands for Project Management Body of Knowledge helps in putting various ideas for proper management of a project (Burke, 2013). A proper contrast between agile model and PMBOK method of software development has been achieved. Use of PMBOK and agile model has been proper achieved. Discussion Project methods PMBOK: Project Management Body of knowledge can be acronym as PMBOK is the summation of different knowledge or ideas with in project management. Project management is nothing but the use ideas, skills, techniques and skill of different activities for satisfying the requirement of the project. It can be easily achieved by using a series of steps ranging from the phase of initiation to closure. Manager of the project is the only person responsible for having satisfying the goals of the project (Ghosh et al.,2012). PMBOK mainly focuses on different methods of management of project which generally have various discipline of management. In general, executive or manager of a project has to considered three factors that are cost, scope and time. Quality of a project mainly depends on the above mentioned three factors. In words project management can be stated as a method in organizational way for proper managing of projects. PMBOK model has various areas like communication management, integ ration management, time management, human resource management, scope management and risk management at last. Agile project management: This method is considered to be best method for managing different projects. It is the latest method of project strategy which is used for managing different software development (Ghosh et al., 2012). In earlier days waterfall was used for managing different model of software development. This method generally focuses on following facts like interaction among individual using process and tools. This method focuses on working software rather than making or creating proper documents for it. There are generally three methods in agile model of software development that are Extreme programming (XP), Scrum, Feature Driven Development (FDD). Extreme programming Extreme programming can be abbreviated as XP which has generally four values that are communication, simplicity, feedback and lastly courage (Kerzner, 2013). It has some more number of practices like planning, small release, metaphor, simple and easy design, programming in pair, collection of ownership, getting on-site customer. Planning: The main aim is to define the next output as soon as it is possible by the help of various business and technical abilities. Small release: The system should be designed in such a way that it has quick and easy release by making short cycle. Metaphor: All development takes place by a simple story behind the working principle of the system. Simple design: Simple solution or methods are generally preferred and complexity must be removed as far as possible. Programming in pair: All programmers work in pair for better upgradation of software. Collection ownership: This method provides freedom to developers to change any code at any instant of time. On-site customer: A customer representative should be made available to the team members of the team for a full time duration to team members of the project. Scrum Scrum method was developed by after making observation on high performance teams at different companies. Scrum is kind of agile software development in process range from a series of iteration ranging in long month loops or iteration known as sprints (Larson Gray, 2013). At the beginning phase of the project it is generally made into a list known as product backlog. Scrum has mainly three phases that are program, game and lastly post game. Program phase consist of planning phase which consist of new released which is currently based on product backlog which help in estimation of cost and various schedules. Architecture development emphasizes on developed of proper architecture which helps in development and providing high level of designing (Mahalakshmi Sundararajan, 2013). Game consist of new sprints which is produce at the new release of the product. Post program is the last or closing phase which help in final documentation of project which focuses in executive at the site of acceptance and final release of the product. Feature Driven Development Feature driven program or FDD is an upgraded model of software development process and it has mainly five steps development of overall model, creating a list of features, planning of different subject area, proper designing of various set of features and lastly it is built by many features. In the first phase that is development of overall model, an analysis of the objective or aim of the system and its current environment is done (O'Sheedy Sankaran, 2013). The ultimate goal is to track the requirements and make an initial UML diagram of class which generally describes the parameters of various problems. In the second phase that is list of features, the team of developers will check the list of features which is required for decomposing the functionality (Popli Chauhan, 2013). Generally, a feature needs two weeks of time for proper development. In some cases, it is seen that this particular step is broken down into smaller step. In the third phase, development plan of project is produced and planning involves proper planning of project which is subdivided into grouping of set of features and different areas of subject. In the fourth step proper designing of set of features is achieved and ultimate goal is to produce proper designing of each set of features (Richter, 2015). Design model includes proper diagrams of UML sequences. In the fifth phase that is built by feature consist of package consist package and after that developing codes from it and after that making unit test form it. Package or batch of feature is also known as Chief Programmer Work Package (CPWP). Contrast methods PMBOK emphasizes on upgrading the following things like upgradation of plan of project management, proper statement of scope of project management and verification of different project work. On the contrary agile model of software development focuses on getting approval from different bodies of management for getting funds at the planning phase and development tool for various management during the planning stage of the project (Schwalbe, 2012). With respect to scope management of project, PMBOK focuses on different definition, scope planning and goals for creating work breakdown structure. With respect to time management of project, PMBOK has many activities like defining phases, resource calculation, calculation of project duration, and proper control and development. On the other hand, Agile model of software development has proper techniques for upgradation of software and helps in estimation of delivery dates and regular or monthly basis loops or iteration. In respect to cost ma nagement, PMBOK model helps in control, estimation and budget of various projects on the contrary agile model helps in having a proper knowledge or idea about the cost involved in the project. On the contrary agile model helps in accumulation of knowledge or idea about the various involved in the planning stage of the project. With respect to quality management factor, PMBOK model helps in controlling of project, quality planning and assurance on the contrary agile model helps in estimation of helps in adjustment, distribution and review of various products (Schwalbe, 2015). In respect to risk management, PMBOK model has proper planning and identification of risk on the contrary, proper planning and controlling of it on the contrary agile model makes review of risk at various meeting which are held by the organization. Applicability PMBOK: PMBOK relate to the idea or fact that can be used by different firms for proper management of various projects (Snyder, 2017). Three key benefits that can be achieved by the use of PMBOK are use of various process for management of various projects, proper guide to various methods of management of project and aims for providing proper documents. It helps different firms in maintaining standard of projects which are implemented by many managers or executive. It helps in easier technique or method of performing different function of a project. It helps in documentation of individual step or part which is being used in the project (Snyder, 2014). It will ultimately help in improving the outputs of a project. The main of benefit of using PMBOK is that it is not limited for use in different parts of a firm. Agile Model: In this model the needs of the given project can vary as the requirement of the project and in many cases it is seen that the needs or requirement of the project are not clear. This method of software development is used when the size of the project is small and a team with small number of members is required for managing the project (Stackpole, 2013). Agile model is created in such a way that it can satisfy the requirement and it is designed in such a way that it is flexible. In this method the developers should have good idea or knowledge about the given project. Occurrence of risk is more and it can have adverse effect on the given project. In this method continuous interaction between customer and software developer is required and most part of the attention is paid or given to the designing of the product. If the customers need any modification in the product, then it can be directly achieved at the end time or release time of the product. Changes are acceptable in the upcoming pages of the development of any software. On the contrary the given model of software development has many issues like it has less Conclusion In the above discussion it can be clearly stated that project management model is considered to be proper for management of various project. There are three well known sub model in agile model of software development that are FDD or feature driven development, XP or Extreme programming and lastly scrum. All the three models have been described in details. In the year of 1990, XP model of software development came into action form a project from well-known organization that is Chrysler corporation. Scrum model of software development is used for upgrading or developing various product in a new and better way and the project is developed by chain of iteration or loops which are generally known as sprint. Feature driven development can be acronym as FDD which is a kind of incremental or upgraded software which generally comprises of five steps like building list of features, upgradation of overall model, proper designing of list of features, and proper planning of list of features. A pr oper contrast between PMBOK and agile model of software development has been done in brief. Various application of PMBOK and agile model has been done. References Allen, M. (2012).Leaving ADDIE for SAM: An agile model for developing the best learning experiences. American Society for Training and Development. Balaji, S., Murugaiyan, M. S. (2012). Waterfall vs. V-Model vs. Agile: A comparative study on SDLC.International Journal of Information Technology and Business Management,2(1), 26-30. Burke, R. (2013). Project management: planning and control techniques.New Jersey, USA. Ghosh, S., Forrest, D., DiNetta, T., Wolfe, B., Lambert, D. C. (2012). Enhance PMBOK by Comparing it with P2M, ICB, PRINCE2, APM and Scrum Project Management Standards.PM World Today,14(1), 1-77. Ghosh, S., Forrest, D., DiNetta, T., Wolfe, B., Lambert, D. C. (2012). Enhance PMBOK by Comparing it with P2M, ICB, PRINCE2, APM and Scrum Project Management Standards.PM World Today,14(1), 1-77. Kerzner, H. (2013).Project management: a systems approach to planning, scheduling, and controlling. John Wiley Sons. Larson, E. W., Gray, C. (2013).Project Management: The Managerial Process with MS Project. McGraw-Hill. Mahalakshmi, M., Sundararajan, M. (2013). Traditional SDLC Vs Scrum MethodologyA Comparative Study.International Journal of Emerging Technology and Advanced Engineering,3(6), 192-196. O'Sheedy, D., Sankaran, S. (2013). Agile Project Management for IT Projects in SMEs: A Framework of Success Factors.International Technology Management Review. Popli, R., Chauhan, N. (2013). A mapping model for transforming traditional software development methods to agile methodology.International Journal of Software Engineering Applications,4(4), 53. Richter, W. (2015, April). PMBOK vs. agile methods: How cultural change can become transparent. InSoftware Testing, Verification and Validation Workshops (ICSTW), 2015 IEEE Eighth International Conference on(pp. 1-2). IEEE. Schwalbe, K. (2012, September). Managing a Project Using an Agile Approach and the PMBOK Guide. InISECON conference, New Orleans, LA. Schwalbe, K. (2015).Information technology project management. Cengage Learning. Snyder, C. (2017).A project manager's book of forms: A companion to the PMBOK guide. John Wiley Sons. Snyder, C. S. (2014). A Guide to the Project Management Body of Knowledge: PMBOK () Guide. Project Management Institute. Stackpole, C. S. (2013).A User's Manual to the PMBOK Guide. John Wiley Sons