Page 1 of 9 - Cover Page Submission ID trn:oid:::1:2787013480

GF
Principle
Quick Submit

Quick Submit

D2L V2 Testing

Document Details

Submission ID

trn:oid:::1:2787013480 7 Pages

Submission Date 1,441 Words

Dec 17, 2023, 1:53 AM CST

9,494 Characters

Download Date

Dec 17, 2023, 1:55 AM CST

File Name

Principles_of_Project_Management_Assessment_2.docx

File Size

113.7 KB

Page 1 of 9 - Cover Page Submission ID trn:oid:::1:2787013480

 Page 2 of 9 - AI Writing Overview Submission ID trn:oid:::1:2787013480

How much of this submission has been generated by AI?

82%
Caution: Percentage may not indicate academic misconduct. Review required.

It is essential to understand the limitations of AI detection before making decisions

about a student's work. We encourage you to learn more about Turnitin's AI detection
capabilities before using the tool.
of qualifying text in this submission has been determined to be
generated by AI.

Frequently Asked Questions

What does the percentage mean?

The percentage shown in the AI writing detection indicator and in the AI writing report is the amount of qualifying text within the
submission that Turnitin's AI writing detection model determines was generated by AI.

Our testing has found that there is a higher incidence of false positives when the percentage is less than 20. In order to reduce the
likelihood of misinterpretation, the AI indicator will display an asterisk for percentages less than 20 to call attention to the fact that
the score is less reliable.

However, the final decision on whether any misconduct has occurred rests with the reviewer/instructor. They should use the
percentage as a means to start a formative conversation with their student and/or use it to examine the submitted assignment in
greater detail according to their school's policies.

How does Turnitin's indicator address false positives?

Our model only processes qualifying text in the form of long-form writing. Long-form writing means individual sentences contained in paragraphs that make up a
longer piece of written work, such as an essay, a dissertation, or an article, etc. Qualifying text that has been determined to be AI-generated will be highlighted blue
on the submission text.

Non-qualifying text, such as bullet points, annotated bibliographies, etc., will not be processed and can create disparity between the submission highlights and the
percentage shown.

What does 'qualifying text' mean?

Sometimes false positives (incorrectly flagging human-written text as AI-generated), can include lists without a lot of structural variation, text that literally repeats
itself, or text that has been paraphrased without developing new ideas. If our indicator shows a higher amount of AI writing in such text, we advise you to take that
into consideration when looking at the percentage indicated.

In a longer document with a mix of authentic writing and AI generated text, it can be difficult to exactly determine where the AI writing begins and original writing
ends, but our model should give you a reliable guide to start conversations with the submitting student.

Disclaimer
Our AI writing assessment is designed to help educators identify text that might be prepared by a generative AI tool. Our AI writing assessment may not always be accurate (it may misidentify
both human and AI-generated text) so it should not be used as the sole basis for adverse actions against a student. It takes further scrutiny and human judgment in conjunction with an
organization's application of its specific academic policies to determine whether any academic misconduct has occurred.

Page 2 of 9 - AI Writing Overview Submission ID trn:oid:::1:2787013480

 Page 3 of 9 - AI Writing Submission Submission ID trn:oid:::1:2787013480
1

Report on Project Management Methodology Application: The Clementon Company

Dilemma Case Study Analysis.
Subject Code: PROJ6000
Student Name:
Student Number:
Assessment Item: 2
Lecturer:
Date Submitted: 16/12/2023

Page 3 of 9 - AI Writing Submission Submission ID trn:oid:::1:2787013480

 Page 4 of 9 - AI Writing Submission Submission ID trn:oid:::1:2787013480
2

INTRODUCTION
Project Management Body of Knowledge (PMBoK) is like a guidebook or a toolbox for
managing projects effectively. It refers to a collection of best practices, principles, and processes
that project managers use to organize, plan, execute, and close projects successfully (Buehring,
2023). PMBoK ensures that project activities stays on track, within budget, and the intended
goals met. PMBoK was first released in 1987, marking a key moment in project management
and in 1996, the PMI released the first edition of the PMBoK Guide which comprised 176 pages,
featuring nine knowledge areas and 37 processes (Fitsilis, 2008). The latest edition of PMBoK,
the 7th edition, introduces eight performance domains, which represent areas of practice within
the project management field. Additionally, it includes 49 project management processes that
cover various aspects of initiating, planning, executing, monitoring and controlling, and closing a
project (Project Management Institute, 2021).
Agile is a project management methodology focused on flexibility, collaboration, and
continuous improvement. It emphasizes adaptive planning, iterative development, and quick
responses to change. This methodology emerged from the software development domain in
2001, catalysed by the Agile Manifesto penned by software developers seeking a more flexible
approach to project management. Initially crafted to address the challenges of traditional
software development practices. It encompasses various methodologies such as Scrum, designed
to adapt to changing requirements and foster continuous improvement throughout the project
lifecycle (Schwaber, 2004)
SIMILARITIES & DIFFERENCES
In the Clementon Company case study, PMBoK and Agile methodologies bear significant
similarities and differences that impact the project's management dynamics.
Similarities:
Both PMBoK and Agile prioritise aligning project objectives with the company's
strategic goals. PMBoK ensures a structured approach to defining project objectives right from
the initiation phase, mirroring Clementon's need to streamlining and standardizing IT processes
and also maintaining its wide IT infrastructure. Similarly, Agile, with its customer-centric
approach, ensures continuous alignment with evolving customer needs, which would benefit
Clementon in catering to changing market demands (Project Management Institute, 2017).

Page 4 of 9 - AI Writing Submission Submission ID trn:oid:::1:2787013480

 Page 5 of 9 - AI Writing Submission Submission ID trn:oid:::1:2787013480
3

The involvement of stakeholders, including Clementon's leadership, employees, and

external partners, is crucial. PMBoK's focus on identifying and managing stakeholders aligns
with the need to keep Clementon's leadership engaged and informed at each project phase.
Similarly, Agile's emphasis on regular customer feedback corresponds to the importance of
employee and customer engagement in project (Dingsøyr et al., 2012). In the TCC and ICS
collaboration, Agile's emphasis on ongoing stakeholder involvement could facilitate swift
adjustments to digital solutions based on real-time feedback, ensuring alignment with evolving
business needs and customer expectations.
Differences:
PMBoK places significant emphasis on upfront planning and scope definition aiming to
prevent scope creep whereas, Agile's approach is more adaptable, allowing for changes in
requirements even late in development (Nerur & Balijepally, 2007). For TCC and ICS, Agile's
adaptability could be beneficial in rapidly evolving digital initiatives, enabling ICS to adjust to
emerging tech trends. PMBoK's detailed planning however, might offer stability in structuring
larger aspects of the digital transformation where fixed requirements are critical.
A fundamental difference lies in their approach to flexibility and predictability. Agile
thrives in dynamic environments, embracing change and valuing flexibility. On the other hand,
PMBoK while adaptable, emphasizes predictability through detailed planning, suitable for more
static project environments (Williams, 2010). For TCC and ICS, Agile's flexibility can
accommodate the evolving digital landscape, allowing adjustments to digital solutions promptly,
while PMBoK's structured predictability could provide stability in managing certain aspects of
the transformation.
RISK ANALYSIS
In the Clementon Company Dilemma, PMBoK and Agile methodologies offer distinct
approaches to managing project risks, influencing how Clementon tackles uncertainties in its
expansion project.
PMBoK, renowned for its structured processes, emphasizes a comprehensive risk
management framework. It includes risk identification, analysis, response planning, and
continuous monitoring (Project Management Institute, 2021). Conversely, Agile while
acknowledging risks, fosters adaptability by integrating risk management within its iterative

Page 5 of 9 - AI Writing Submission Submission ID trn:oid:::1:2787013480

 Page 6 of 9 - AI Writing Submission Submission ID trn:oid:::1:2787013480
4

cycles. It promotes ongoing risk assessments and adaptations as part of its flexible approach
(Dingsøyr et al., 2012).
In relation to the case study, PMBoK's meticulous risk management aligns with the need
for comprehensive oversight in the TCC’s digital transformation. The engagement between TCC
and ICS in streamlining their digital infrastructure requires a systematic understanding of
potential risks such as technical complexities which are crucial to mitigating threats and
capitalizing on opportunities. PMBoK's structured risk assessment methodologies can offer TCC
and ICS a robust framework to identify risks associated with technology adoption thus ensuring
proactive measures to address them.
The collaborative efforts between TCC and ICS demand agility in risk response, enabling
swift adjustments in digital solutions as new technological trends emerge. Agile's iterative cycles
facilitate ongoing risk assessment and adaptation allowing both entities to respond promptly to
market dynamics or changing business requirements thereby, reducing the risk of potential
disruptions in the digital transformation journey.
By blending elements from both approaches, Clementon can stay responsive to market dynamics
ensuring a balanced risk management strategy that suits the multifaceted challenges due to its
expansion project.
PROJECT CONTEXT
PMBoK and Agile methodologies find application across various project types, yet their
suitability often aligns with different project contexts.
PMBoK, known for its structured approach is well-suited for projects characterized by
stable requirements and clear objectives. Industries like construction, engineering, or regulated
sectors such as healthcare or finance, often leverage PMBoK due to its emphasis on detailed
planning, documentation and adherence to processes (Project Management Institute, 2017).
On the other hand, Agile methodology thrives in dynamic and uncertain environments
where requirements evolve rapidly. It's widely employed in software development, innovation
projects, start-ups, and creative initiatives that demand flexibility, customer-centricity and rapid
adaptation to changing needs (Fitsilis, 2008). Agile's iterative and collaborative nature allows
teams to deliver incremental value quickly and is ideal for projects with evolving or unclear
requirements.

Page 6 of 9 - AI Writing Submission Submission ID trn:oid:::1:2787013480

 Page 7 of 9 - AI Writing Submission Submission ID trn:oid:::1:2787013480
5

Both methodologies cater to different project landscapes, offering tailored approaches to address
specific challenges and demands.
LIFECYCLE IMPLICATIONS
In a project's lifecycle, PMBoK typically follows a sequential approach across its process
groups: initiating, planning, executing, monitoring and controlling, and closing. Each phase
emphasizes detailed planning, documentation and adherence to the predefined project plan
(Project Management Institute, 2017). PMBoK's structured nature ensures a systematic
progression through these phases, focusing on predictability, control and comprehensive project
documentation.
In contrast, Agile embraces an iterative and incremental approach throughout the project
lifecycle. Agile's emphasis lies in shorter cycles or sprints where planning, execution and review
happen continuously. It promotes flexibility, adapting to changing requirements and delivering
value iteratively (Fitsilis, 2008). Agile encourages collaboration, quick response to change and
customer feedback, enabling teams to pivot or adjust direction as needed. The methodology's
flexibility allows it to address uncertainties and evolving project needs across all stages of the
project lifecycle.
APPLICATION
The Clementon Company (TCC) is undergoing a digital transformation, partnering with Iota
Consultancy Services (ICS) to enhance its operational efficiency and customer service by
integrating digital solutions into its services. ICS is assisting TCC in implementing digital
technologies, streamlining operations, and improving customer interactions through digital
platforms.
In this scenario, considering the collaboration between TCC and ICS for digital
transformation, Agile methodology would be more appropriate. This is because, Agile's iterative
nature allows for flexibility and adaptability, essential for a project focused on implementing
digital solutions. Agile's incremental approach enables the quick release of functionalities
aligning with TCC's goal of enhancing customer service and operational efficiency through
digital platforms. Also, Agile's emphasis on collaboration and customer feedback throughout the
development process aligns well with the objective of creating customer-centric digital solutions.
The iterative cycles of Agile enable continuous improvement based on feedback ensuring that
the digital transformation aligns closely with TCC's evolving needs and customer preferences.

Page 7 of 9 - AI Writing Submission Submission ID trn:oid:::1:2787013480

 Page 8 of 9 - AI Writing Submission Submission ID trn:oid:::1:2787013480
6

Given the dynamic nature of digital transformations and the need for rapid adaptations
and enhancements in digital platforms, Agile's iterative, customer-focused approach seems better
suited for TCC's collaboration with ICS in achieving their digital transformation objectives.

Page 8 of 9 - AI Writing Submission Submission ID trn:oid:::1:2787013480

 Page 9 of 9 - AI Writing Submission Submission ID trn:oid:::1:2787013480
7

References
Buehring, S. (2023). Agile vs PMBoK project management.
Dingsøyr, T., Nerur, S., Balijepally, V., et al. (2012). A decade of agile methodologies: Towards
explaining agile software development.
Fitsilis, P. (2008). Comparing PMBoK and Agile Project Management software development
processes.
Nerur, S., & Balijepally, V. (2007). Theoretical reflections on agile development methodologies.
Project Management Institute (2017). A Guide to the Project Management Body of Knowledge:
PMBoK(R) Guide. Sixth Edition. Pennsylvania: Project Management Institute, Inc.
Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge
PMBoK® Guide. Seventh Edition and The Standard for Project Management. ISBN
9781628256666 (Kindle edition).
Schwaber, K. (2004). Agile Project Management with Scrum. Microsoft Press.
Williams, L. (2010). Agile software development methodologies and practices.

Page 9 of 9 - AI Writing Submission Submission ID trn:oid:::1:2787013480