KING’S OWN lNSTi TUTE*
Success io Higher Education
OROUPASSIGNMENTCOVERSMEET
Unil Name: ICTT12 IT Proiect Man aqemenl
Lecturer’s na me: Fadi Kotob
Assign merrl Title. Proiect Manaqe ment for App Development
Declaration
(This declaratior. must he completed by a II sturterfls in the grou p cs the assig nmerrt v Ill not be merked.}
VUe. the undersigned. certify time foIIcra’irtg:
• We haveread and understood fhe SñJO’en*Academ thishauct/ o/’cy
• This assignment is our ovm work ba=•ed on our personal study and or resea rch.
• We have ac ncw1edgecl all melerial and sources used in Ihe preparation of Ihis assignment
incJudi any material gene rated in the course of ouremployment.
• The a ssignment has not previously been subrn itted for assessment in this or any other
unit.
• We h eve not copied in part or in whole or otherwise plsgiartzed the work of otherstudents.
• We have read and unde Bland the criteriB used for assessment.
• The essI›;gnment is within the word and page limits specifie<I in the unit outline.
• The use cf any material in this essign meot dces not inftirge the ‹nteIIectuaI property ‘ oopyrigh
of a Third party.
• ‘”e cJndersfsnJ fat this essigrmenf may Undergo electronic detection for pegia‹ism, arid on
anonymous copy of the ass gr•mens may be retained an the database and used to make
comparisons vrih other assignments in future.
• By compleéng this co wrsleet in full and submitting this assigr ment electronically, we are
bound bythe conditions or the KOI’s StucfentAcacferrzi”c /rfz”acooduor Pb/i” and the declarañon
en this coversheet.
Assignment Receipt
Unit Name: ICT 712Information Technoloqy ProiectManagement Lecturers Name: Fadi Kotob
Assignment Title: Project Management for App Development
1
EXECUTIVE SUMMARY
This report demonstrates project planning for application development through appropriate project
management methodology. The extent purpose of this report is to apply IT project management
concepts in order to develop and manage an application that would help in reducing the spread of
coronavirus using tools and techniques and project management methodologies.
Various journal articles, documents from websites, scholarly articles, library papers and
conference papers has been referenced in order to demonstrate project management methodology
best suited for the COVIDAlert app. The paper contains four different tasks. The first task is related
to PMBOK phases that has been implemented in the development of COVIDAlert app. Project
charter, Work Breakdown Structure(WBS), Gantt Chart, Budget estimation, Risk assessment and
management plan has been set forth in this task. Second task elaborates Agile Project Management
in with reference to this project. Trello, Slack and Sprint was setup for the development of
COVIDAlert. Thirdly, comprehensive comparison was done between PMBOK and Agile Project
management to discuss which of them best suited for project COVIDAlert. Finally, ethical issues
regarding the project was discussed.
Overall, this project provides demonstration of developing an App that would assist in reducing
the spread of Coronavirus, using suitable project management methodology in order to finish
development by 6 month and with maximum budget of $3.4m.
2
TABLE OF CONTENTS
EXECUTIVE SUMMARY ……………………………………………………………………………………………… 1
LIST OF FIGURES ………………………………………………………………………………………………………… 4
LIST OF TABLES………………………………………………………………………………………………………….. 5
CHAPTER 1: INTRODUCTION TO COVIDAlert…………………………………………………………….. 6
1.1. BUSINESS CASE ………………………………………………………………………………………………… 7
CHAPTER 2: PMBOK METHODOLOGY……………………………………………………………………….. 8
2.1. Project Initiating……………………………………………………………………………………………………. 8
2.1.1. Develop Project Charter…………………………………………………………………………………… 8
2.2. Project Planning …………………………………………………………………………………………………. 11
2.2.1. Work breakdown Schedule (WBS)………………………………………………………………….. 11
2.2.2. Gantt Chart…………………………………………………………………………………………………… 13
2.2.3. Budget…………………………………………………………………………………………………………. 16
2.2.4. Risk Assessment and Management Plan…………………………………………………………… 18
2.3. Project Execution ………………………………………………………………………………………………… 18
2.4. Monitoring and Control ……………………………………………………………………………………….. 19
2.5. Project Closing……………………………………………………………………………………………………. 19
CHAPTER 3: AGILE PROJECT MANAGEMENT METHODOLOGY …………………………….. 20
3.1. Introduction to Agile Project Management……………………………………………………………… 20
3.2. Benefits of Agile Project Management…………………………………………………………………… 21
3.3. Agile Framework Implemented in COVIDAlert ……………………………………………………… 21
3.4. Trello…………………………………………………………………………………………………………………. 23
3.5. Slack………………………………………………………………………………………………………………….. 29
3
CHAPTER 4: PMBOK VS. AGILE PROJECT MANAGEMENT(APM)……………………………. 37
CHAPTER 5: ETHICAL ISSUES…………………………………………………………………………………… 39
CHAPTER 6: CONCLUSION ……………………………………………………………………………………….. 40
REFERENCES …………………………………………………………………………………………………………….. 41
4
LIST OF FIGURES
Figure 1: Work Breakdown Schedules (WBS) ………………………………………………………………….. 13
Figure 2: Gantt Chart based on Work Breakdown Schedule (WBS)…………………………………….. 15
Figure 3: Creation of Product Backlog and other cards………………………………………………………. 23
Figure 4: Moving Task to Sprint 1: To Do ……………………………………………………………………….. 24
Figure 5: Task detail during To Do state …………………………………………………………………………. 24
Figure 6: Moving task from Sprint 1:To Do to Sprint 1:In Progress…………………………………….. 25
Figure 7: Task detail during In Progress State…………………………………………………………………. 26
Figure 8: Moving task from Sprint 1:In Progress to Sprint 1:Done………………………………………. 26
Figure 9: Task detail during Done State ………………………………………………………………………….. 27
Figure 10: Moving Task to Sprint 2: To Do ……………………………………………………………………… 28
Figure 11: Moving task from Sprint 2:To Do to Sprint 2: In Progress State………………………….. 28
Figure 12: Moving task from Sprint 2:In Progress to Sprint 2: Done State……………………………. 29
Figure 13: Starting of the Slack communication ……………………………………………………………….. 30
Figure 14: Channel created named documentation…………………………………………………………….. 30
Figure 15: First Weekly Meeting held, and meeting minutes shared to the team……………………. 31
Figure 16: Second Weekly Meeting held, and meeting minutes shared to the team ……………….. 32
Figure 17: Third Weekly Meeting held, and meeting minutes shared to the team ………………….. 33
Figure 18: Fourth Weekly Meeting held, and meeting minutes shared to the team ………………… 34
Figure 19: Project Update and file shared to team……………………………………………………………… 35
Figure 20: Project Update and file shared to team……………………………………………………………… 35
Figure 21: Project update and file shared to the team…………………………………………………………. 36
5
LIST OF TABLES
Table 1: Project Business Case …………………………………………………………………………………………. 7
Table 2: Project Stakeholders and their responsibilities ……………………………………………………… 10
Table 3: Budget Table for Wages ……………………………………………………………………………………. 16
Table 4: Budget Table for Rental Mobile Phones ……………………………………………………………… 16
Table 5: Budget table for Office Expenses ……………………………………………………………………….. 17
Table 6: Final Budget Table …………………………………………………………………………………………… 17
Table 7: Risk Assessment and Management Plan ……………………………………………………………… 18
Table 8: Stakeholder Communication Plan ………………………………………………………………………. 19
Table 9: Steps in Agile Project Management Methodology………………………………………………… 22
6
CHAPTER 1: INTRODUCTION TO COVIDAlert
The coronavirus pandemic has proving to be one of our generation’s hardest challenges. The
disease has influenced crucial facets of daily life, including travel, jobs, cancelled events,
shutdown of education and school, employment, stock markets, and fears of a depression. As of
September 23rd, 2020, there is a total of 31,816,653 coronavirus cases around the world among
which 976,021 have died due to coronavirus pandemic. (Worldmeters, 2020) On 23rd
September,2020, the total cases recorded in Australia was 26,974 among which 859 was total
deaths. (Australian Government Department of Health, 2020)
A successful COVID-19 vaccine that can be efficiently delivered is anxiously awaited by the
world. Before then, the emphasis is on re-energizing organizations to act rather than to respond.
The outbreak in Australia of the COVID-19 pandemic has resulted in a health emergency. The best
way to reduce the transmission of COVID-19 is to avoid near, face-to-face contact with others.
(Centers for Disease Control and Prevention, 2020) This is termed as social distancing also called
physical distancing which can be simply put as keeping a safe distance between yourself and other
people. It can be practiced by maintaining at least 6 feet (2 arm’s length) distance from other
people.
The Australian Government is planning to create a new application that will assist individuals in
minimizing the spread of the coronavirus and undoubtedly strengthen the existing processes of
contact tracking performed by health authorities of the State and Territory (Maddocks, 2020). As
a result, it allows the government to recognize persons in Australia that may have come into touch
with someone who has tested positive for COVID-19, so that the individual can be provided with
effective guidance and treatment for COVID-19.
7
1.1. Business Case
Table 1: Project Business Case
8
CHAPTER 2: PMBOK METHODOLOGY
PMBOK stands for Project Management Body of Knowledge. “It is the entire collection of
processes, best practices, terminologies and guidelines that are accepted as standards within the
project management industry.” (Wrike, 2020) Project Management Institute(PMI) is a not-forprofit organization that oversees the documentation related to PMBOK within the PMBOK guide.
The Project Management Institute (PATHAK, 2020) originally developed these five phases. The
five phases of project management include initiating, planning, executing, monitoring &
controlling , and closing.
2.1. Project Initiating
The project initiating stage of the project life cycle reflects the basic work required for an approved
project. Here, the introduction of the project can be understood through the following elements.
2.1.1. Develop Project Charter
Project objective
The aim of the project is to develop an application in Australia to minimize the spread of the
coronavirus (COVID-19) via giving out official information and advice, displaying current status
within Australia and contact tracing.
Project Scope Statement
1. Deliverables
• Technical documentation (Product & Process)
• UML Diagrams
• Design prototype using wireframe
• Launch screen and App icon for the app
• Database Schemes
• Login functionality for the users
• Home page and Setting page
9
• Symptom checker functionality
• Filling contact form functionality
• Dashboard for admin
• Tested and full-fledged app
• Maintenance and Help Guide
2. Milestones
1) Project management Plan and Technical documentation by November 2nd, 2020
2) Project team formation and assignment of responsibilities by November 6th , 2020
3) Prototype design review by November 24th,2020
4) Design approved by 25th November,2020
5) Database setup by 30th November,2020
6) Runnable and debugged app by December 29th, 2020
7) Testing completed by 19th January 2021
8) Performance review produced by February 22, 2021
9) Project results reviewed and summarized by March 5th,2021
10) Project closed by 7th march, 2021
3. Technical Requirements
1) Internet connections
2) Cloud hosting
3) Cloud Backup Server
4) Workstation for the project team
5) Security System
6) Mobile Devices for testing
Initial project budget allocation
The estimated budget of around $3.4 million, including developer and staff training, will be
covered by the project.
10
Project Stakeholders
Table 2: Project Stakeholders and their responsibilities
11
2.2. Project Planning
This stage is crucial to effective project management and focuses on the creation of a blueprint
that can be implemented by everybody. Usually, this step starts by setting goals.
2.2.1. Work breakdown Schedule (WBS)
The total scope of the project is organized and specified by WBS. A progressively comprehensive
description of the project work is described at each descending step. (Brotherton, Shelly A., et al.,
2008) The WBS is decomposed into work packages. The deliverable orientation of the hierarchy
includes both internal and external deliverables.
The project schedule can be understood through below mentioned figure which is prepared through
MS Project software. It represents project activities, timeline, and their sequence.
12
13
2.2.2. Gantt Chart
Figure 1: Work Breakdown Schedules (WBS)
Simply put, Gantt chart is the visual representation of the tasks scheduled over time. It is widely
used for planning and scheduling projects in project management. It helps to keep track of what
various activities are scheduled and what is its start and end date. Likewise, it shows activities that
are overlapped and how long the whole project last.
With respective to Work Breakdown Structure mentioned in 2.2.1., Gantt chart has been produced.
14
15
Figure 2: Gantt Chart based on Work Breakdown Schedule (WBS)
16
2.2.3. Budget
Budget projects the total cost needed to complete the project over a period of time. The cost defined
in budget plan are estimate rather than actual expense. Actual expense could go over or under the
budget.
Initial project budget allocated for the project COVIDAlert is $3.4 million. Project Budget has
been made for wages, utility and office related expense and rental mobile phones over a period of
6 month(26 weeks).
Table 3: Budget Table for Wages
This budget table is created through MS-Project. Hourly rate of wages is defined for all individual
based on the designation. Standard rate has been set based on average salary being offered by most
of the IT company. (Payscale, 2020)
Table 4: Budget Table for Rental Mobile Phones
17
Budget table has been prepared for rental mobile phone required for testing purposes. The rental
cost per week for above mentioned mobile phones has been referenced from site Rent The Roo.
(Rent The Roo, 2020)
| Item Name | Cost Per Week |
Qty | Duration (6 months) |
Cost | Source |
| Rental lease cost (Rent advance/deposit) |
$1,025.00 | Nil | 26 | $26,650.00 | (Calautti, 2019) |
| Utility connections & bonds (Electricity, gas, water) |
$170.00 | Nil | 26 | $4,420.00 | (OriginEnergy, 2020) |
| Communications (Phone Communication) |
$15.00 | 1 | 26 | $390.00 | (Optus, 2020) |
| Internet connection | $16.25 | Nil | 26 | $422.50 | (Compare BroadBand, 2020) |
| Cloud Hosting | $50.00 | 1 | 26 | $1,300.00 | (Lahn, 2019) |
| Cloud Server Backup | $2.50 | 1 | 26 | $65.00 | (Roos, 2019) |
| Workstations | $1,000.00 | 10 | Nil | $10,000.00 | (Roos, 2019) |
| Security system | $250.00 | Nil | 26 | $6,500.00 | (Roos, 2019) |
| Total cost | $49,747.50 |
Table 5: Budget table for Office Expenses
This budget table display recurring cost for the office related expense including utility such as
internet, electricity, gas and phone line, rental lease, technical requirements such as hosting server,
backup server, workstations for team member and security system. Here, the quantity column is
especially defined to denote the number of required workstation.
Table 6: Final Budget Table
18
This is a final budget table that aggregates all the above-mentioned budget table and calculate the
total estimated cost over a period of 6 month. Total estimated cost is over 1 hundred thousand
dollar.
2.2.4. Risk Assessment and Management Plan
This is a key steps in project management. Risk Assessment help to identify, categorize, prioritize,
and implement risk management methods such as avoidance, retention, mitigate or transfer. Risk
assessment and management plan has been proposed for the project.
| Risk Event | Likeli hood |
Impact | Detection Difficulty |
When | Response | Contingency Plan | Trigger | Who is Responsible |
| Budget Constraint | 4 | 5 | 3 | Entire Project |
Mitigate: Use of Budget management software |
Review projectplans;Re-evaluatethework flow; Deliberate with project sponsor |
Under or over expenses | Project Manager |
| Time Constraint | 2 | 5 | 2 | Continuous | Mitigate: Complete the task within time |
Review projectplans;Re-evaluatethework schedule; Deliberate with project sponsor |
Delay in deliverables or completing milestones |
Project Manager |
| Human Resourse Constraint |
5 | 4 | 2 | Continuous | Mitigate: Work Extra hour | Hire more human resourse | Unavailability of team member; Sick or emergency leave |
Project Director |
| Delay in getting Hardware |
4 | 3 | 5 | Installation | Mitigate: Continuous follow up with vendor |
Search for more trustworthy vendor | Hardware was not delivered in time |
Project Director |
| Cloud Backup Failure | 1 | 3 | 4 | Installation | Mitigate: Select reliable vendor Transfer: Warranty |
Complain and feedback; Order for better service; Migration ofdatatoanotherservice provider |
Backup fail | Developer |
| Equipment malfunction |
1 | 4 | 2 | Continuous | Mitigate: Select reliable vendor Transfer: Warranty |
Order for Replacement | Equipment Fail | Project Manager |
| Interface Problem | 1 | 3 | 2 | Beta release |
Mitigate: Testing the interface design |
Review interface design; resolve the problems | Feedback from beta tester | Designer |
| App crashes | 2 | 5 | 2 | Start-up | Mitigate: Test the prototype | Unpublish the App and resolve the issues | Feedback from users | Project Manager |
| User Backlash | 4 | 3 | 3 | Postinstalla tion |
Mitigate: Prototype demonstration |
Increase staff support | Call from top Mangement | Project Director |
Table 7: Risk Assessment and Management Plan
2.3. Project Execution
At this stage, the project team will start working on the project and stakeholder communication is
carried out as the project progress.
Stakeholder Communication Plan
This communication plan outline about what need to be communicated with whom, by what
method of communication and how often.
19
Table 8: Stakeholder Communication Plan
2.4. Monitoring and Control
In this stage, we measure the project performance and progression against the project plan. Any
areas in the project plan that requires change is identified and changes are initiated.
2.5. Project Closing
A project is formally closed after performing series of important tasks such as delivering product,
releasing resources, review and recognizing team performance and formal termination of
contractors.
20
CHAPTER 3: AGILE PROJECT MANAGEMENT
METHODOLOGY
Agile Project Management(APM) has skyrocketed in popularity. It is being considered as “the”
project management methodology for today’s projects in comparison to traditional project
management methodology. (Špundak, 2014) A survey of development professionals was done in
period of 2015 to 2018 in relation to use of Agile development by software developers. As of early
2018, 91% of respondents highlighted that their organization has adopted an agile development
methodology. (Liu, 2019)
3.1. Introduction to Agile Project Management
Simply put, Agile Project Management(APM) is an iterative approach used by project team to
manage project by breaking it up into various stages incorporating constant collaboration and
continuous improvement at every stage to deliver releases. Constant collaboration is one of the
key aspect of APM where both team members and project stakeholders make fully informed
decisions relating to project progression whereas another key aspect is continuous release of
deliverables throughout the process rather than only at the end.
“The core of Agile Methodology was developed by 17 people in 2001 in written form.” (Wrike,
2020) Four key values and 12 principles was formalized and published as Agile Manifesto. The
key values are stated as:
1. “Individual and team interactions over processes and tools
2. Working software over comprehensive documentation
3. Customer collaboration over contract negotiation
4. Responding to change over following a plan” (Beck, et al., 2001)
21
3.2. Benefits of Agile Project Management
Agile Methodology was originally developed to streamline and improve software development
process to rapidly identify and rework on issues and defects. The benefits of APM are many. 5
significant benefits are listed below:
1. Continuous Customer Interaction
Continuous feedback from the customer throughout the project ensure that the team is on
track, any changes to requirement can be dealt accordingly, customer satisfaction is
maintained as they can review the iterative deliverables.
2. Ability to adapt
Changes can be incorporated with minimal effort thus making the team able to adapt for
any uncertain scope change. The changes can be easily added to the next iteration.
3. Faster Delivery
Instead of thorough planning, the team involves in continuous development while
constantly delivering workable products. Customer will get working version at shorter
intervals.
4. Low Project Risk
Continuous feedback on developing versions of product regularly reduces the risk of
project failing. Breaking down larger project into several iterations will largely scale down
the risk to the overall project.
5. Ongoing innovation
Constant collaboration and continuous improvement lead to innovation and development
of new products and features.
3.3. Agile Framework Implemented in COVIDAlert
There are wide variety of Agile framework. Scrum and Kanban are two powerful Agile framework
in software development. (Howard Lei, 2015)While choosing the framework, three things need to
be considered: identification of appropriate framework, identification of project specific
requirements, adaptation, and implementation of the framework. (Rasnacisa & Berzisaa, 2016)
22
“Scrum is a framework for organizing and managing work.” (Rubin, 2012) It focuses on managing
tasks within team-based development environment and is not suited to highly interrupt-driven
work. “Kanban is not a stand-alone process solution but instead an approach that is overlaid on an
existing process.” (Rubin, 2012) It offers visualization of how work flows on each stage, limit
work in progress and measures and optimize the work flow to make continuous improvements. It
is well suited for interrupt-driven environment.
Scrum framework along with Kanban visualization has been implemented for the project
COVIDAlert. Trello Kanban Board has been used as a collaboration app to keep track of
everything and to build roadmap. Furthermore, Slack has been used as open communication
channel for team collaboration and scrum meetings.
Table 9: Steps in Agile Project Management Methodology
23
3.4. Trello
Trello is a web-based Kanban-Style application that can be used for making lists of lists. It can be
used by all the team members thus ensure collaboration in project management. Real-time updates
allow the team to be on same perspective.
Two Sprints have been planned with a release in this project. User story with acceptance criteria
has been defined along the project roadmap.
Figure 3: Creation of Product Backlog and other cards
At first, a product backlog with user stories was created. The user stories were based on the feature
of the COVIDAlert app.
24
Figure 4: Moving Task to Sprint 1: To Do
In figure 4, the task is moved to Sprint 1 To do status. Here, the task is assigned to team member
along with a due date. Priority is also set to the task and user acceptance criteria are added in each
task of the Sprint 1.
Figure 5: Task detail during To Do state
25
Figure 5 displays the task detail like user description, user acceptance criteria, task priority, due
date and the assignee.
Figure 6: Moving task from Sprint 1:To Do to Sprint 1:In Progress
In figure 6, the task/s are moved and placed to Sprint 1: In Progress state. One or more of the user
acceptance criteria has been performed in this state.
26
Figure 7: Task detail during In Progress State
Figure 7 displays two of the acceptance criteria has been marked as completed.
Figure 8: Moving task from Sprint 1:In Progress to Sprint 1:Done
27
In figure 8, the task/s are moved from Sprint 1: In Progress and placed to Sprint 1: Done state. The
task in this state has been completed.
Figure 9: Task detail during Done State
Figure 9 displays that all of the user acceptance criteria have been marked complete.
28
Figure 10: Moving Task to Sprint 2: To Do
In figure 10, remaining task from product backlog has been moved to Sprint 2: To Do. Similar to
Sprint 1, the task is assigned to team member along with a due date. Priority is also set to the task
and user acceptance criteria are added in each task of the Sprint 2.
Figure 11: Moving task from Sprint 2:To Do to Sprint 2: In Progress State
In figure 11, the task/s are moved and placed to Sprint 2: In Progress state. One or more of the user
acceptance criteria has been performed in this state.
29
Figure 12: Moving task from Sprint 2:In Progress to Sprint 2: Done State
In figure 12, the task/s are moved from Sprint 2: In Progress and placed to Sprint 2: Done state.
The task in this state has been completed. Also, the completed task has been released.
3.5. Slack
Slack is the open communication tool used in this project. It incorporates team communication and
collaboration into one place. Slack has been used in this project for scrum meeting, file sharing
and collaboration in the project.
30
Figure 13: Starting of the Slack communication
Workspace was created and named as CovidAlert. Team member was added, and different
channels were created such as meetingminutes, documentation, covidalert, etc.
Figure 14: Channel created named documentation
Figure 14 displays the channel named documentation, where team members will be sharing
guidelines, references related to the documentation of the project.
31
Figure 15: First Weekly Meeting held, and meeting minutes shared to the team
First weekly meeting invites was sent to the team via Slack. After meeting has been conducted,
the minutes of the meeting was shared to the team.
32
Figure 16: Second Weekly Meeting held, and meeting minutes shared to the team
Second weekly meeting invites was sent to the team via Slack. After meeting has been conducted,
the minutes of the meeting was shared to the team. To share the real time view of the project
33
discussion, Zoom app has been added to the workspace and all the future meeting has been
scheduled in Zoom App.
Figure 17: Third Weekly Meeting held, and meeting minutes shared to the team
34
Third weekly meeting invites was sent to the team via Slack. After meeting has been conducted,
the minutes of the meeting was shared to the team.
Figure 18: Fourth Weekly Meeting held, and meeting minutes shared to the team
Fourth weekly meeting invites was sent to the team via Slack. After meeting has been conducted,
the minutes of the meeting was shared to the team.
35
Figure 19: Project Update and file shared to team
Figure 20: Project Update and file shared to team
36
Figure 21: Project update and file shared to the team
Figure 19 to 20 shows files sharing along with the update regarding project progression to the team
via Slack.
37
CHAPTER 4: PMBOK VS. AGILE PROJECT
MANAGEMENT(APM)
This task highlights the comparison between PMBOK and Agile methodology in relation to
software development that may aid in reducing the spread of the coronavirus. In recent years, Agile
Project Management(APM) has proven to be a new approach for high-risk and time-sensitive
projects as it offers better productivity, higher quality, and more successful decision-making unlike
traditional methodologies such as PMBOK. (Salameh, 2014)
In order to choose and implement a suitable methodology for application development, various
factors such as nature of the project, size, resources have to be considered. (Kashyap, 2018)
PMBOK Methodology is best suited for large scale projects with very low involvement of
customer in overall process. The only involvement of customer is during the initial stages for
requirement collection and design approval. The entire project is planned upfront without any
scope of changing requirements. (Carr, 2017)On the contrary, APM is all about customer
satisfaction and collaboration through early and continuous software delivery. Likewise, APM can
accommodate changing requirements throughout the development phases. (Muslihat, 2018 )
In addition , PMBOK methodology follows linear fashion thus, delivers the final end product after
going through all the process(the initiating process, planning process, executing process,
monitoring, and controlling process, and closing process). Whereas, APM follows iterative fashion
that enables the project team to delivers workable product continuously in every sprint cycle.
(Salameh, 2014) More importantly, it incorporates customer collaboration thus promoting
continuous improvement through feedback.
COVIDAlert app is a proposed solution that can aid to slow the spread of COVID-19. Being one
of the widespread virus which has no vaccination or cure yet, the only best thing is prevention
which can be achieved by adhering to public health guidelines. COVIDAlert helps Australians to
38
stay up to date with official information and health advice, let users fill a questionnaire to check
for any symptom and more importantly facilitate to find people who have been in close or casual
contact with someone with COVID-19. The need to complete this project is of high priority, thus
sticking to APM for the development seems relevant. Then again, considering the nature of this
project, there may be changing requirements as the project progress. Furthermore, this project
requires multi-functional and self-organized team that allows the team to go beyond their usual
competencies. In addition, constant collaboration with customer is also equally important for this
project. To sum up, Agile Methodology is best suited for this project.
39
CHAPTER 5: ETHICAL ISSUES
There are ethical issues specifically relevant to the practice of software application. During
software development, project team undergoes through social process with clients, end users,
discipline of the software application and the organization. Some of the ethical issues related to
this project has been noted down.
In COVIDAlert app, end user needs to register themselves to get started. Specifying their personal
identifier to any application poses a question of being vulnerable to identity theft or data breach.
Moreover, application needs to practice informed consent via the help of Terms of conditions,
Privacy policies, etc. (Gotterbarn, 1991)
Likewise, privacy issue relating to location protection can also arise in software application.
COVIDAlert is used for tracking people who have been close or casual contact with someone with
COVID-19. This feature of COVIDAlert can give rise to concern relating to location disclosure.
“Data protection by design and default” is one of the concept that has been encouraged in software
development. (European Commission, 2018) Through technical and social solutions, data privacy
can be achieved. Protecting data from unauthorized or accidental access or loss is part of technical
solutions. Proper planning and securing collected data help to prevent any data breaches and
privacy violation. Social solutions include building open and confidential acceptance and
understanding among consumers about whether and how their data is being used. Employees have
to devote themselves to compliance with organizations and corporate privacy legislation should
advise them about how to consciously prevent practices that can violate privacy (Lee, 2016).
40
CHAPTER 6: CONCLUSION
In summary, everyone in the world knows one of the most daunting threats of our generation has
proved to be the coronavirus pandemic. To reduce the number of cases rising in Australia, the
government has planned to use software that would assist in this cause. The software needs to have
a features that allows end user to view official information and health advice to help stop the spread
and stay healthy, check their symptom to if they are concerned about themselves and moreover,
track people who may be close or casual contact of someone with Covid-19.
For this project development, two of the project management methodology was thoroughly
discussed and implemented. The report has been divided into four task. Firstly, the project
management has been demonstrated in PMBOK methodology. In this methodology, five steps
have been followed generating project charter, work breakdown structure(WBS), Gantt chart,
budget estimation, risk assessment and management plan, Stakeholder communication plan and
many more. Secondly, Agile Project Management(APM) methodology has been demonstrated.
The project was divided into Sprint, scrum meeting was conducted via Slack, Trello app was used
to build project roadmap and team collaboration. Thirdly, comprehensive comparison between the
two mentioned methodology was performed to discuss which is best suited for the project
COVIDAlert. And finally, ethical issues in relation to this project was discussed.
In short, two of the popular methodology (PMBOK & Agile) was demonstrated along with
discussion of which being the suitable and what ethical issues is prevalent in the project
COVIDAlert.
41
REFERENCES
Academy, T. P., 2020. [Online]
Available at: https://www.pm-primer.com/agile-methodology-and-pmbok/
Australian Government Department of Health, 2020. Coronavirus (COVID-19) current situation
and case numbers. [Online]
Available at: https://www.health.gov.au/news/health-alerts/novel-coronavirus-2019-ncov-healthalert/coronavirus-covid-19-current-situation-and-case-numbers
[Accessed 21 09 2020].
Beck, K. et al., 2001. Manifesto for Agile Software Development. s.l.:s.n.
Bennison, P., 2008. gile and PMBOK® guide project management techniques: closer than you
think. Paper presented at PMI® Global Congress 2008. North America, Denver, CO. Newtown
Square, PA, Project Management Institute..
Berzai, L., 2019. Ethical Problems in Computing, Sydney: CompTia.
Brotherton, Shelly A., Fried, Robert T. & Norman, Eric S., 2008. Applying the work breakdown
structure to the project management lifecycle. North America, Denver, CO. Newtown Square,
Project Management Institute.
Calautti, L., 2019. How much does it cost to rent office space?. [Online] Available
at: https://www.commercialrealestate.com.au/advice/how-much-does-it-cost-to-rent- officespace-57245/
Carr, K., 2017. Agile Project Management Vs. Traditional Project Management. [Online]
Available at: https://www.knowledgehut.com/blog/agile/agile-project-management-vstraditional-project-management
42
Centers for Disease Control and Prevention, 2020. Prevent getting sick. [Online] Available
at: https://www.cdc.gov/coronavirus/2019-ncov/prevent-getting-sick/social- distancing.html
[Accessed 04 09 2020].
Compare BroadBand, 2020. Wifi costs compared. [Online]
Available at: https://www.comparebroadband.com.au/get-wifi-costs.htm
European Commission, 2018. Ethics and data protection. DG Reaserach and Innovation.
Gotterbarn, D., 1991. Ethical considerations in software engineering. s.l., 13th International
Conference on Software Engineering, 1991.
Griffiths, M., 2016. Agile Methods and PMBOK v5 Guide Alignment, s.l.: s.n.
Hand, D. J., 2018. Aspects of Data Ethics in a Changing World:. Big Data, Volume 6, pp. 176-
190.
Howard Lei, F. G. P. K. J. P. O., 2015. A statistical analysis of the effects of Scrum and Kanban
on software. Robotics and Computer-Integrated Manufacturing.
Kashyap, S., 2018. Traditional vs Agile Project Management Method: Which One is Right for Your
Project?. [Online]
Available at: https://www.proofhub.com/articles/traditional-vs-agile-project-management
[Accessed 25 June 2020].
Kashyap, S., 2018. Traditional vs Agile Project Management Method: Which One is Right for Your
Project?. [Online]
Available at: https://www.proofhub.com/articles/traditional-vs-agile-project-management
[Accessed 25 June 2020].
43
Koppensteiner, S. |. U. N., 25th September, 2003 A.D.. Will agile development change the way we
manage software projects? Agile from a PMBOK® Guide perspective. Baltimore, North America,
Project Management Institute.
Lahn, M., 2019. How much does a server cost for app hosting?. [Online] Available
at: https://www.servermania.com/kb/articles/server-cost-for-apps/
Lee, W. W., 2016. An Ethical Approach to Data Privacy Protection. ISACA Journal, p. 9.
Liu, S., 2019. Use of agile development and continuous integration by software devs globally
2015-18. Statista, 11 April.
Maddocks, 2020. THE COVIDSAFE APPLICATION, s.l.: s.n.
Muslihat, D., 2018 . 7 Popular Project Management Methodologies And What They’re Best Suited
For. Zenkit, 9 March .
Optus, 2020. Business phone lines & landline plans. [Online]
Available at: https://www.optus.com.au/business/office-phone/phone-lines
OriginEnergy, 2020. Charges for Electricity and Gas. [Online] Available
at: https://www.originenergy.com.au/business/electricity-and-gas/plans/energy- plans.html
P., F., 2008. Comparing PMBOK and Agile Project Management software development processes.
s.l., Springer, Dordrecht, pp. 378-383.
| PATHAK, R., 2020. 5 Phases | of Project | Management | (PMP). | [Online] Available |
| at: | https://project-management.com/project-management-phases/ | |||
| [Accessed 09 09 2020]. |
| Payscale, Available at: https://www.payscale.com |
2020. | [Online] |
44
Rasnacisa, A. & Berzisaa, S., 2016. Method for Adaptation and Implementation of Agile Project
Management Methodology. ICTE , December.pp. 43-50.
Rent The Roo, 2020. New Smart Phones Rentals!. [Online]
Available at: https://www.renttheroo.com.au/phone-rentals/smart-phones
Roos, A., 2019. IT budgeting: How much should Australian businesses spend?. [Online]
Available at: https://www.empowerit.com.au/blog/it-and-business/it-budgeting/
Rubin, K. S., 2012. Scrum Framework. 2013 ed. s.l.:Pearson.
Salameh, H., 2014. What, When, Why, and How? A Comparison between Agile Project
Management and Traditional Project Management Methods. International Journal of Management
Reviews, 2(5).
Špundak, M., 2014. Mixed Agile/Traditional Project Management Methodology – Reality or
Illusion?. 27th IPMA World Congress, 5 April.
Thomson, A. J. & Schmoldt, D. L., 2001. Ethics in computer software design and development.
Computers and Electronics in Agriculture- Elsevier, Volume 30, pp. 85-102.
Worldmeters, 2020. COVID-19 CORONAVIRUS PANDEMIC. [Online]
Available at: https://www.worldometers.info/coronavirus/#countries
[Accessed 2020 09 02].
Wrike, 2020. What is Agile Methodology in Project Management?. [Online] Available
at: https://www.wrike.com/project-management-guide/faq/what-is-agile-methodology- inproject-management/
| Wrike, 2020. | What | is | PMBOK | in | Project | Management?. | [Online] Available |
| at: | https://www.wrike.com/project-management-guide/faq/what-is-pmbok-in-project | ||||||
| management/ |
45
Individual Contribution
Week 7 Activity Log
| No. | Criteria | Week 7 |
| 1 | Attendance at weekly meeting |
1. 2. 3. 4. |
| 2 | Weekly activity log | Week 7 is the starting of this project. During this week, all the team members attended a meeting for a brief discussion related to the project. • Project leader and project name was finalized. • Workspace in slack was setup and all the members were invited. • Trello board was setup and all the members were invited. • All the team members were assigned to go through the project description. • Also, thorough research of Trello was suggested to all. |
| 3 | Time management | • The brief meeting was held on August 25th , 2020. • All members were required to go through projectdescription before next meeting which was scheduled on 1st of September. |
| 4 | Tasks | • Brief discussion on project held. • Project name finalized: COVIDAlert • Project Leader finalized: • All member was assigned to go through project description and do a thorough research of Trello. |
46
| 5 | Actual contribution to group project |
During this week, project discussion was held, all member was assigned to go through the project description. Research on Trello was done. |
Week 8 Activity Log
| No. | Criteria | Week 8 |
| 1 | Attendance at weekly meeting |
1. 2. 3. 4. |
| 2 | Weekly activity log | In this week, we held our first official meeting. Discussion on PMBOK phases was carried out among team members. Slack was used for the communication. MS-Project was setup for WBS. Task was divided between members : Meeting minutes was shared to the team. |
| 3 | Time management | • The first meeting was held on 1st September. • Thorough research related to task division has to be done by 2nd September. • All the task was completed by 5th September. |
| 4 | Tasks | • Discussion on PMBOK phases was done. • Task division was carried out. • Meeting minutes was shared to the team. • MS-project was setup for WBS. |
| 5 | Actual contribution to group project |
Research was done on Work Breakdown Structure (WBS) and Gantt Chart. MS-Project was setup to generate work breakdown structure. Different feature of MS-Project was learned to carry out the task. |
| Project Schedule, Work Breakdown Structures (WBS) and Gantt Chart |
Rojina |
| Budget Estimation | |
| Risk Assessment and Management Plan |
47
| Then, me and Dipa created a WBS and schedule and finally Gantt chart was generated. |
Week 9 Activity Log
| No. | Criteria | Week 9 |
| 1 | Attendance at weekly meeting |
1. 2. 3. 4. |
| 2 | Weekly activity log | In this week, we held our second meeting. Discussion on Agile Project Management (APM) Methodology was carried out among team members. Slack along with Zoom session was used for meeting. User story and acceptance criteria was noted down. Trello Project roadmap was laid out. Task was divided between members : Meeting minutes was shared to the team. |
| 3 | Time management | • The second meeting was held on 6th September via Zoom session. • User story and acceptance criteria was noted down on 7th September • Product backlog was created on Trello board along with Sprint division and priority was set by 9th September • User acceptance criteria was transferred to Trello board 12th September |
| User criteria |
Story | and | Acceptance | All the member |
| Product Backlog, Sprint division and Priority was set, and member was assigned to task in Sprint |
||||
| User Acceptance was specified for Sprint 1 |
and | |||
| User Acceptance was specified for Sprint 2 |
and |
48
| • Task of sprint 1 and Sprint 2 was assigned to team member by 13th September. |
||
| 4 | Tasks | • Discussion on Agile Project Management (APM) was done. • User story and acceptance criteria was noted down. • Task division was carried out. • Meeting minutes was shared to the team. • Trello project roadmap was laid out along with product backlog, Sprint 1, Sprint 2, and Release • Priority and member were assigned to task • User acceptance was transferred to Sprint task by all the team members individually |
| 5 | Actual contribution to group project |
User story and acceptance criteria was noted down after thorough brainstorming by all the members of the project. Project roadmap was laid out on Trello by creating different card as Product backlog, Sprint 1, Sprint 2, and Release. Sprint 1 and 2 has 3 different status : To do, In progress and Done. After user acceptance criteria was transferred to Trello by all the member , priority and member was assigned to task in Sprint 1 and 2. I transferred the user acceptance criteria of two user story(Set up an account on COVIDAlert and Fill out Contact Information) of Sprint 1 to Trello board. |
Week 10 Activity Log
| No. | Criteria | Week 10 |
| 1 | Attendance at weekly meeting |
1. 2. 3. 4. |
| 2 | Weekly activity log | In this week, we held our third meeting. Discussion on documentation was carried out among team members. Slack along with Zoom session was used for meeting. Task was divided between members for completion of documentation: |
49
| Task 1: PMBOK Methodology | ||
| Task 2 : Agile Project Management(APM) Methodology |
||
| Task 3 : Comparison between PMBOK and APM |
||
| Task 4 : Ethical Issues | ||
| Conclusion and Executive Summary |
||
| Meeting minutes was shared to the team. | ||
| 3 | Time management | • The third meeting was held on 14th September via Zoom session. Meeting minutes was shared to the team. • 50% of the task was completed by 20th September. • Any queries have to be noted down and put up for discussion on slack for the team member for next meeting. |
| 4 | Tasks | • Discussion on documentation was done. • Task division was carried out. • Meeting minutes was shared to the team. • Team did research on the assigned topic and started report. |
| 5 | Actual contribution to group project |
I did some research regarding the Agile project management by going through different journal. I started doing the report for the Agile methodology. For the Trello section, I took the snip from the Trello board for the project. |
Week 11 Activity Log
| No. | Criteria | Week 11 |
| 1 | Attendance at weekly meeting |
1. 2. 3. 4. |
| 2 | Weekly activity log | In this week, we held our fourth and final meeting. Discussion on documentation progress was carried out among team members. Slack |
50
| along with Zoom session was used for meeting. Final refinement and integration were carried out by project leader. Meeting minutes was shared to the team. |
||
| 3 | Time management | • The fourth meeting was held on 21st September via Zoom session. • Meeting minutes was shared to the team. • Remaining 50% of the task was completed by 23rd September. • The report of all the members were integrated in one. • Conclusion and Executive summary were refined. |
| 4 | Tasks | • Discussion on documentation was done. • Task division was carried out. • Meeting minutes was shared to the team. • Team completed the report. • Final refinement , integration and formatting was completed by the project leader. |
| 5 | Actual contribution to group project |
After receiving the complete report of the team, I integrated the document into one. Me and Abhishek worked on conclusion and executive summary. I finished the final review and formatting. |