Page 1 of 10 - Cover Page Submission ID trn:oid:::17268:90661066
Turnitin Report
Agile Meth-1.docx
My Files
My Files
University
Document Details
Submission ID
trn:oid:::17268:90661066 8 Pages
Submission Date 1,492 Words
Apr 10, 2025, 8:56 PM GMT+5:30
9,263 Characters
Download Date
Apr 10, 2025, 8:56 PM GMT+5:30
File Name
Agile Meth-1.docx
File Size
26.4 KB
Page 1 of 10 - Cover Page Submission ID trn:oid:::17268:90661066
Page 2 of 10 - AI Writing Overview Submission ID trn:oid:::17268:90661066
35% detected as AI Caution: Review required.
The percentage indicates the combined amount of likely AI-generated text as It is essential to understand the limitations of AI detection before making decisions
well as likely AI-generated text that was also likely AI-paraphrased. about a student’s work. We encourage you to learn more about Turnitin’s AI detection
capabilities before using the tool.
Detection Groups
1 AI-generated only 24%
Likely AI-generated text from a large-language model.
2 AI-generated text that was AI-paraphrased 11%
Likely AI-generated text that was likely revised using an AI-paraphrase tool
or word spinner.
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
writing that is likely AI generated as AI generated and AI paraphrased or likely AI generated and AI paraphrased writing as only AI generated) 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.
Frequently Asked Questions
How should I interpret Turnitin's AI writing percentage and false positives?
The percentage shown in the AI writing report is the amount of qualifying text within the submission that Turnitin’s AI writing
detection model determines was either likely AI-generated text from a large-language model or likely AI-generated text that was
likely revised using an AI-paraphrase tool or word spinner.
False positives (incorrectly flagging human-written text as AI-generated) are a possibility in AI models.
AI detection scores under 20%, which we do not surface in new reports, have a higher likelihood of false positives. To reduce the
likelihood of misinterpretation, no score or highlights are attributed and are indicated with an asterisk in the report (*%).
The AI writing percentage should not be the sole basis to determine whether misconduct has occurred. The reviewer/instructor
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 accordance with their school's policies.
What does 'qualifying text' mean?
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 likely AI-generated will be
highlighted in cyan in the submission, and likely AI-generated and then likely AI-paraphrased will be highlighted purple.
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.
Page 2 of 10 - AI Writing Overview Submission ID trn:oid:::17268:90661066
Page 3 of 10 - AI Writing Submission Submission ID trn:oid:::17268:90661066
Managing Agile Projects
Reflective Report on Agile Project Management: Smart Air Quality Monitoring System
Student name:
Student ID:
Module name:
Page 3 of 10 - AI Writing Submission Submission ID trn:oid:::17268:90661066
Page 4 of 10 - AI Writing Submission Submission ID trn:oid:::17268:90661066
Table of Contents
Reflective Report on Agile Project Management: Smart Air Quality Monitoring System ... 1
Introduction ..................................................................................................................... 3
1. Description ................................................................................................................... 3
2. Feelings ......................................................................................................................... 4
3. Evaluation .................................................................................................................... 5
4. Analysis ........................................................................................................................ 6
5. Conclusion .................................................................................................................... 6
6. Action Plan ................................................................................................................... 7
2
Page 4 of 10 - AI Writing Submission Submission ID trn:oid:::17268:90661066
Page 5 of 10 - AI Writing Submission Submission ID trn:oid:::17268:90661066
Introduction
The Smart Air Quality Monitoring System project attempted to solve worldwide air pollution
problems through real-time monitoring of CO, CO2, PM2.5, PM10, and temperature and
humidity assessments. The project utilized innovative technology combinations between IoT
WSN and cloud computing to achieve precise air quality measurement results. Agile/Scrum
methodology was selected because it offers continuous improvement cycles during project
development. In this initiative, the Quality Manager's responsibility was to achieve necessary
quality requirements and maintain reliable performance and accurate system functionality.
The reflective analysis adopts Gibbs' Reflection Cycle to examine quality management, Agile
method evaluation of ethical situations, and project learning in our development work. The
reflective analysis will help me evaluate the project's positive and negative aspects, which I
will use to create better solutions for upcoming tasks.
1. Description
The project was structured using the Scrum framework, with the development process
divided into several sprints. The key roles within the team were clearly defined as follows:
Project Manager: Responsible for overall project delivery and managing the
stakeholders.
Start-up Manager: Focused on initial planning, including defining the project's
scope and ensuring team alignment with the goals.
Quality Manager (my role): Ensured that quality standards were defined, tracked,
and maintained throughout the project. I also organized the testing processes and
managed the Quality Plan, which included performance and reliability testing for
hardware components (e.g., sensors), software (e.g., the dashboard and cloud
services), and system integration.
Risk Manager: Managed project risks, developed mitigation strategies, and
monitored potential threats to the project’s success.
Scheduling Manager: Maintained the project schedule, tracked progress, and ensured
deadlines were met.
3
Page 5 of 10 - AI Writing Submission Submission ID trn:oid:::17268:90661066
Page 6 of 10 - AI Writing Submission Submission ID trn:oid:::17268:90661066
The tasks in my position as Quality Manager required upholding project deliverable
compliance for sensor calibration precision and real-time data transmission dependability
alongside system functional performance levels. My developed quality plan outlined the
essential criteria that established sensor calibration testing requirements, precision standards
systems, system combination protocols, and application interface performance standards.
Each sprint required designated individuals to conduct quality assurance examinations and
performance tests.
Our project incorporated Agile principles through iterative development, including
continuous feedback and project flexibility. The product development occurred through
multiple segments called sprints, which focused on providing operable system components.
The team showed the functionality it developed to stakeholders while assessing system
performance after each sprint before receiving adjustments to the project roadmap.
2. Feelings
The project's start brought both enthusiasm and apprehension to me. The real-world challenge
of the project excited the team to use Agile methodology while sharing high motivation for
delivering relevant solutions. I had mixed feelings about the technical aspects, including the
sensor integration into cloud-based systems and ensuring real-time data precision.
The primary responsibility of a Quality Manager role included upholding the purity of sensor
data collection. During the initial stage, I believed the testing system and monitoring devices
would uphold the data integrity. I faced some frustrating situations because sensor calibration
and system integration problems appeared. Through Agile processes, we quickly solved all
obstacles that appeared. A set of retrospective meetings took place after each sprint for team
members to outline challenges and create solutions while planning the next course of action.
I felt pride as the project team successfully worked together and solved their initial system
problems during the concluding project phases. The implemented system developed structure
as it matched all the quality requirements outlined in our Quality Plan. The rapid
development cycle caused worry for me since I needed to maintain comprehensive testing
standards. I maintained a non-stop equilibrium between test requirements and time
constraints for releasing functional product components.
4
Page 6 of 10 - AI Writing Submission Submission ID trn:oid:::17268:90661066
Page 7 of 10 - AI Writing Submission Submission ID trn:oid:::17268:90661066
3. Evaluation
Agile methodology proved its worth as a practical approach toward extending the project.
The team was able to resolve problems continuously because Scrum utilizes an iterative
process. The project achieved substantial success because it used frequent feedback loops as
one of its main strengths. Through sprint reviews, which brought stakeholders together, we
created a system that successfully obtained their requirements at each meeting and adapted
quickly to their feedback. The sensor data quality and dashboards needed constant
enhancement through real-world testing, making these elements particularly important for
perfection.
The project achieved success because of how the team members collaborated. The team
maintained a high performance-driven focus, leading to optimal results because every
member devoted themselves to excellence in addition to daily meetings that fostered project
cohesion. As Quality Manager, I connected with my entire team to observe their component
progress and delivered assistance when required. Quality checks performed as part of the
collaboration process took place at necessary stages so critical problems could be detected
without delay.
The work presented some obstacles along with its accomplishments. Agile offered rapid
adaptation capabilities to project changes, yet it brought certain uncertainties to the project.
The project experienced unexpected growth of scope that resulted in missed deadline dates.
Additional sensor integration required extra calibration testing beyond the initial sprint
timeline because they did not have proper consideration within earlier development stages.
The project's developmental stages slowed down because of this interim stoppage. Our
success in resolving the issue demonstrated how Agile projects face time versus flexibility
dilemmas.
The project experienced scheduling challenges because we did not adhere to strict deadlines,
which caused rapid development pressure during the late stages of development. The
demanding need for testing created a dilemma for me while managing the team's push for
efficiency through each sprint. Several testing phases proceeded at an accelerated pace while
I needed to verify whether our system validation process reached full maturity before the
final deployment.
5
Page 7 of 10 - AI Writing Submission Submission ID trn:oid:::17268:90661066
Page 8 of 10 - AI Writing Submission Submission ID trn:oid:::17268:90661066
4. Analysis
Early quality assurance emerged as the main lesson from this project because of its vital role
in project development. Implementing Agile did not help the project because an insufficient
rigorous testing phase in early sprints resulted in later process delays. The Gibbs' Reflective
Cycle enables experience assessment for improved future practice, so I would enable
enhanced quality assurance inspections during early programming cycles to prevent late
issues. The project should include automatic tests for sensor calibration and data transmission
reliability to detect issues that can harm system performance before it is too late.
We utilized Jira as one of our Agile tools to monitor project development through task
administration and stakeholder communication features. This tool proved essential for
maintaining visibility and responsibility throughout the team operations, and it permitted
everyone to monitor deadline targets and task distribution. The tool stands alone in failing to
guarantee project success because team discipline combined with process commitment
decides outcomes. Jira stands as an excellent Agile tool yet requires team culture
development to promote a focus on quality as the top priority.
Ethical factors had a central role in the project development. The handling of live health data
required strict compliance with data protection laws, including GDPR, because these
regulations safeguarded public health. The project applied encryption methods, which
enabled secure handling and transfer of data. The employment of cheap sensors during
execution posed difficulties related to ethical criteria for data precision and dependability. I
maintained prompt accuracy improvement of sensor data and provided transparent
information about sensor limitations to stakeholders in my position.
5. Conclusion
Implementing Agile/Scrum methodology and the team's dedicated approach allowed the
Smart Air Quality Monitoring System project to fulfill its objectives. My work as a Quality
Manager helped the project succeed by developing a comprehensive quality system that
verified sensor information and tested both cloud infrastructure and graphical display
systems. The Agile model supplied a helpful framework for handling project challenges by
letting the team perform iterative development tasks and request continuous feedback for
system improvements.
6
Page 8 of 10 - AI Writing Submission Submission ID trn:oid:::17268:90661066
Page 9 of 10 - AI Writing Submission Submission ID trn:oid:::17268:90661066
The system requires additional progress in several directions. Improvements to project
planning at the start should have included detailed scope planning and testing durations for
better project outcomes. The flexible aspects of Agile strategy are helpful but need better
annotation of timelines to prevent sacrificing quality for quicker project completion.
6. Action Plan
In future projects, I will implement the following improvements based on the lessons learned:
1. Early Quality Assurance: Incorporate rigorous testing and quality assurance
earlier in the project, particularly in the early sprints, to identify issues before they
affect later stages.
2. Clearer Time Management: Balance the flexibility of Agile with better time
management and a stronger focus on meeting deadlines to avoid unnecessary delays
in testing and integration.
3. Scope Control: Implement stronger scope control mechanisms to prevent
unnecessary feature additions that could delay project completion or affect the quality
of the deliverables.
4. Stakeholder Engagement: Continue to engage stakeholders regularly to ensure
their expectations are managed and the system aligns with their requirements.
By making these adjustments, future projects will benefit from improved quality, faster
delivery, and greater stakeholder satisfaction.
7
Page 9 of 10 - AI Writing Submission Submission ID trn:oid:::17268:90661066
Page 10 of 10 - AI Writing Submission Submission ID trn:oid:::17268:90661066
8
Page 10 of 10 - AI Writing Submission Submission ID trn:oid:::17268:90661066
