Académique Documents
Professionnel Documents
Culture Documents
Ardhya Pratiwi Setiowati MSc in Business Development Grenoble Graduate School of Business
areas that are needed to manage projects throughout their process for any industry, so the company can build and apply the best practices. The second one is that it defines the required tools, techniques, inputs and outputs of each process. The limitations of PMBOK are it is too complex for a small project and the application of PMBOK requires adaptation to the area industry, project size, time and budget. PMBOK is a great approach to teach the knowledge in project management, however it doesnt provide an affective guidance to carry a project. There are several strengths of Scrum. The first one is that it offers a structured framework without bureaucracy. It gives freedom to team members to speak their minds, as a result the miscommunication is lessened and mistakes are reduced. The second strength is that Scrum emphasizes ongoing assessment throughout a project, it gives flexibility to adapt to business realities that are highly dynamic. The third strength is that it also emphasizes on output rather than input, that helps the team to focus on the bigger picture. However Scrum also has several limitations. The first one is it expects every member in the team to be a smart, experienced and high-motivated people. In reality, not every team can be experienced, skilled and high-achieving enough to be a self-organized and efficient team. So applying Scrum framework would be sufficient only for highly functional organization. The second one is the requirement of enormous freedom in individual and team throughout the process. It would be difficult for traditional companies that underline strong controls over their employees. This requirement also has another drawback, it can cause the teams to be insufficiently controlled. The last limitation is inadequately support a large company or large project. As a highly participative style of framework, the efficiency of the process is affected by the number of the team members. This drawback extends to project size because generally the bigger the project, the larger the teams. Prince2 is a process-driven approach, it defines when and what things that the project team and project manager should do. It offers a clear and fixed path to do a project. In the other hand, PMBOK is a knowledge-driven approach, it describes how to do those things. It stands as a reference that offers standard guidelines to all project managers. While Scrum is significantly different from the other two approaches, it offers a framework that is responsive and people-oriented as a base of completing a project. These three approaches also have different controls or checkpoints. Prince2 has multi level controls carried out to improve reporting and tracking at various levels. Whereas, PMBOK left all the controls to the project managers decision. And Scrums checkpoint are the daily Scrum meeting and sprint review, where all the team members, ScrumMaster and Product Owner review the performance of the team and maybe revise the objectives. Fortunately, projects may use Prince2 and PMBOK at the same time because two of these approaches are complement each other. Prince2 missing several keys of project management areas, such as; procurement, contract administration and cost control. PMBOK offers a practical guidance to prepare, interpret and use good quality plans to control a project. Bibliography http://en.wikipedia.org/wiki/Project_management http://www.12manage.com/methods_pmi_pmbok.html http://www.brighthub.com/office/project-management/articles/2042.aspx http://www.pmforum.org/library/papers/2002/Prince2vsGuide3.pdf http://www.scribd.com/doc/10319690/Limitations-of-Agile-Software-Development