project management
samira121
PROJ6000 Assessment 2B Sample Completed Assignment
There are a variety of standards available globally to guide the management of projects. Though
these standards vary, they are all unified by a common goal, to increase project success rate. On this
basis, many efforts have been made to bring the standards together in to a single body of
knowledge. However these attempts have been largely unsuccessful due to the vast area of
expertise in project management. A single standard simply cannot be versatile enough to cover the
requirement. Therefore, maintaining a variety of recognized standards should be seen as a strength
of the discipline (Global Alliance for Project Professional, 2018). Though there is a shared goal, each
standard offers a framework to the PM that focuses on different competencies. Ghosh, et al. (2012),
summarise as follows;
“PMBOK emphasizes on repeatable processes, ICB stresses on technical, contextual and emotional
competences, Scrum brings customer collaboration, quick turnaround time, PRINCE2 focuses on
product of the project in a controlled environment, P2M devises innovation and alignment with
project portfolio and finally APM focusses on design and technology management, business case and
interpersonal skills.”
(Ghosh, Forrest, DiNetta, Wolfe, & Lambert, 2012)
Being that projects are increasingly conducted without geographic borders and can span many
different countries, the selection of standard is increasingly complex. However whilst global projects
can add complexity this should not be the defining reason for selecting one standard over another.
In fact, the advantage of having recognised global standards is that they surpass language and policy
by presenting a common framework. Rather, the selection of which standard to adopt should be
based specific nature of the project in question and the most relevant for that purpose.
For example, PMBOK and PRINCE2, are a very process orientated methodologies that divide projects
in to multiple stages. They leaves nothing to chance and are great frameworks for running large
scale, predictable projects. These are both very popular in IT infrastructure projects. Scrum
methodology on the other hand, is far lighter approach. It was designed for and is a popular choice
for software development projects, ultising a small team meeting regularly to discuss priorities and
milestones which can move daily. (Aston, 2017)
In 2003 Global Alliance for the Project Professionals was established with the vision to become “the
independent reference benchmark for alignment and transportability of standards and qualifications
for leadership and management of projects, programs and portfolios.” They have developed a useful
tool for comparing project standards to aid in the PM selection.
Comparison of PM Standards and Assessments Tool available at;
https://globalpmstandards.org/tools/comparison-of-global-standards/
(Global Alliance for Project Professional, 2018)
References
Aston, B. (2017, March 2). 9 Project Management Methodologies Made Simple. Retrieved from
thedigitalprojectmanager: https://thedigitalprojectmanager.com/project-management-
methodologies-made-simple/
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, 4(9), 1-77.
Global Alliance for Project Professional. (2018). About Us. Retrieved from Global Alliance for Project
Professional: https://globalpmstandards.org/about-us/