Table of Contents

Introduction..................................................................................................................3
Statement of Work.........................................................................................................4
Work breakdown structure.........................................................................................11
Risk management plan...............................................................................................14
Project Organizational Structure...............................................................................19
Conclusion..................................................................................................................21
References...................................................................................................................22

Section Prepared By:

Introduction Saeed AlKatheeri
Hamad AlMutawa and Shaima
Statement of Work
AlMarzooqi
Work Breakdown Structure Maha Riyad and Hassan AlQadi
Risk Management Plan Shamsa AlMansoori
Project Organizational Structure Asma Alshehhi
Conclusion Saeed AlKatheeri

23 Page 1 of
1. Introduction

The acceleration of the recent Covid-19 pandemic has motivated the shift towards an
enhanced digital world while triggering the process of online shopping among
consumers. The policies of maintaining social distancing norms along with lockdowns
have motivated the buyers to move towards the e-commerce businesses to purchase
all forms of essential commodities. There has been a significant change in the buying
behavior of consumers. The pandemic has created difficulties associated with the
traditional shopping process following certain limitations like social distancing and
restricted number of entry of consumers within the retail stores. People being
quarantined find it more convenient to purchase products online as there are fewer
restrictions. Unlike the traditional shopping method, products are being delivered at
their doorsteps to ensure effective safety measures and they are able to shop at any
hour of the day or night from any location at any given time.

Online marketplaces have allowed many stores to their sell products within a few
minutes online. This has eliminated their overhead costs by removing the expense of
retail outlets and staff to serve consumers. Many businesses are now shifting their
business models to cater to the online segment and UAE MART Supermarket is one
of them. Therefore, MobiApps aims to develop a mobile-based application called
QUICKMART for the supermarket as the company is willing to provide for its
consumers a safer and more comfortable shopping experience. MobiApps will be
highlighting the different aspects of the application development activity including the
scope, technical needs, project schedule, budget, risk management plan, and roles and
responsibilities of the project team members throughout this paper.

2. Statement of Work 
23 Page 2 of
 I. BACKGROUND
MobiApps is specialized software development company that has been
established in 2004, with its headquarter in Abu Dhabi. Our range of services
include retail and e-commerce application solutions and web development
solutions. To meet the rising demand of online shopping and recurring
customer requests, UAE MART supermarket has decided to develop a mobile
application for their customers called QUICKMART. The number of shoppers
has decreased by about 10% at UAE MART supermarket and that is attributed
to the shopper’s reluctance to visit the supermarket due to COVID-19 related
health concerns and precautions. In order to cater to their needs
QUICKMART would enable them to shop from the comfort of their homes
and receive their groceries without any hassle.

II. PURPOSE
UAE MART supermarket is aiming to increase their sales by 20% in the first
year and retain their customers in the long run. Through the development of
QUICKMART, they are aiming to ease the shopper’s purchasing experience
while maintaining health and safety procedures.

III. ABREVIATIONS & DEFINITIONS

a. ABBREVIATIONS

AWS Amazon Web Services

CV Curriculum Vitae

D Effective Contractual Date

KOM Kick-off Meeting

M Period of (30) consecutive calendar days

WEEK Period of (7) consecutive calendar days

WBS Work Breakdown Structure

b. DEFINITIONS

23 Page 3 of
 CUSTOMER UAE MART Supermarket

SUBCONTRACTOR any person or persons, firm, partnership,

corporation or combination thereof to
whom any part of the WORKS has been
subcontracted by MobiApps

PROJECT Developing a Mobile Delivery

Application for a Supermarket:
QUICKMART

WORKS all works, services and obligations to be

carried out by MobiApps under the
agreement, including: works, services
and labour needed for the engineering,
management, testing and handover upon
completion of the PROJECT; performing
warranty and remedial works in relation
to the PROJECT ; and the provision of
all documents required by this agreement
to CUSTOMER

IV. SCOPE OF WORKS

a. GENERAL REQUIREMENTS
MobiApps shall be responsible for designing, engineering, testing and the
deployment of QUICKMART delivery application. MobiApps will also be
responsible of managing all specialist SUB-CONTRACTORs in line with
the CUSTOMER’s approval.

MobiApps shall be responsible for producing, maintaining and updating

throughout the execution of the WORKS the Project Execution Plan.
MobiApps shall be responsible for all necessary management activities for
project execution. This includes but not limited to management, control,
supermarket surveys, design and engineering, subcontracting, testing etc.

MobiApps shall nominate a competent experienced Project Manager who

will be fully dedicated to this PROJECT. The Project Manager will have
authority to act as MobiApps representative and will be responsible for the
management of the PROJECT, coordination, control and PROJECT
performance activities.

23 Page 4 of
MobiApps shall be responsible for all necessary activities for PROJECT
implementation, including:

(i) Project supervision and planning

(ii) Contract administration
(iii) Quality Assurance / Quality Control (QA/QC)
(iv) Cost Control
(v) Conduct Daily / Weekly / Monthly progress meetings
(vi) Issue Project progress reports (Weekly/monthly)
(vii) Project administration and invoicing
(viii) Issuing and distribution of documents and correspondence to
CUSTOMER

MobiApps shall manage, control and coordinate all interfaces associated

with the PROJECT such as coordination with end users and
SUBCONTRACTORS.

MobiApps shall submit to CUSTOMER all required final documentation

upon completion of the WORKS.

b. TECHNICAL REQUIREMENTS
MobiApps shall develop a prototype for the user journey inclusive of a
storyboard and wireframe for CUSTOMER approval. The user journey
blueprint shall detail the application structure, content, and functionality.

MobiApps shall present to CUSTOMER at least three design options along

with the user interface showing different visual design elements such as
graphics and typography.

MobiApps shall be responsible of providing full access of the source code to

CUSTOMER.

MobiApps shall be responsible of the applications back-end and front-end

development.

MobiApps shall be responsible for submitting the application to the required

application platforms and obtaining their approval for deployment.

23 Page 5 of
 MobiApps shall be responsible of testing the application for quality,
performance, reliability, usability, and security and deliver to
CUSTOMER a Quality Assurance report for approval.

MobiApps shall be responsible of Beta testing the application on a

sample of targeted audience before public release.

MobiApps shall be responsible of integrating a payment gateway into the

application, upon CUSTOMER approval. The payment gateway shall enable
secure online transactions for users.

MobiApps shall be SUBCONTRACTING some of the WORKS to Amazon

Web Services in order to incorporate notifications, delivery emails, and cloud
servers.

V. MILESTONES & SCHEDULE

a. GENERAL OVERVIEW

The project is technical in nature due to its reliance on the technical team, they
are responsible for developing the main deliverable which is the application in
itself. MobiApps is proposing to the CUSTOMER to use rolling wave
planning approach to track the project milestones which will “roll out” the
detailed plans and then as the project progresses, periodically reevaluate the
completion dates (Knutson, 1996). This method will allow flexibility for any
changes in the application development life cycle. The total project duration of
8 months, however, will not be reevaluated as per the CUSTOMER’s request.

b. MILESTONES AND DELIVERABLES

Milestone Duration
(Weeks)
1. Project KOM & Requirement Agreement 2
Deliverables: KOM Presentation, Organization Chart inclusive of
CVs
2. Planning Package 2
Deliverables: Level-4 Schedule, Execution Strategy, Quality
Management Plan, Risk Management Plan
3. Technical Feasibility Assessment 1

23 Page 6 of
 Deliverable: Feasibility Report (inclusive of operating systems,
web services, & payment gateways)
4. Prototype Development 2
Deliverable: User Journey
5. Application Design 2
Deliverable: User Interface
6. Application Development 16
Deliverables: Source code, Running code, and Readme file
7. Testing & Platform Approvals 4
Deliverable: QA report
8. Application Deployment and Final Documentation 2
Deliverables: As-built documentation

Table 1.1 – Milestone Durations and Deliverables

c. SCHEDULE

A level-1 schedule has been created to show the major milestones and overall
duration. A level-4 schedule will be developed as part of the planning package
detailing the subcontracted works, and daily planned activities.

Figure 1.1 – QUICKMART GANTT CHART

23 Page 7 of
 d. COMPLETION DATES

The purpose of the Milestones & Completion Dates Schedule is to ensure that
the overall and intermediate PROJECT objectives are met. MobiApps shall
ensure that all milestones and COMPLETION DATES are achieved as
detailed below in Table 1.2.

Milestone Completion Date

1. Project KOM & Requirement Agreement D + 2 Weeks

2. Planning Package D+1M

3. Technical Feasibility Assessment D + 1.5 M

4. Prototype Development D+2M

5. Application Design D + 2.5 M

6. Application Development D + 5.5 M

7. Testing & Platform Approvals D + 6.5 M

8. Application Deployment and Final D+8M

Documentation
Table 1.2 – Completion Dates Schedule

VI. BUDGET

QUICKMART project cost is based on the hourly rate of each job title
multiplied by the duration spent on this project (Average Salary in United
Arab Emirates, 2021).

Title Hourly rate Duration Total cost

(AED) (Hours) (AED)
Project manager 150 1280 192000
Planning engineer 100 160 16000
App Developer 110 480 52800
Database Admin 100 480 48000
QA Analyst 110 200 22000
Graphic Designer 75 200 15000
Testing Officer 110 160 17600
Launching Officer 100 160 16000
Document Controller 55 160 8800

23 Page 8 of
 Table 1.3 – MobiApps Hourly Rates
In our proposal estimation in the slides, we didn’t consider the administrative
cost and planning cost, we only looked at the development cost. So now
considering all the costs in Table 1.3, the PROJECT lumpsum cost would
Total: 388,200.00 AED.

There are also operating costs which will be paid by the CUSTOMER and the
services cof which an be scaled later on if their user base increases. The
CUSTOMER annual external services cost, will be as follows:

Service Monthly Cost Annual Cost

(AED) (AED)
Amazon Cognito 162.50 1950.00
Amazon API Gateway 270.00 3240.00

DynamoDB provisioned 465.40 5584.80

capacity
Amazon Simple Email 209.30 2511.60
Service (SES)
Amazon Simple 80.00 960.00
Notification Service (SNS)
AWS Storage Gateway 77.20 926.40

AWS Support 528.90 6346.8

Payment Gateway (Telr) 200.00 2400.00

Apple store annual fee - 1,101.90

Grand Total 25021.5

23 Page 9 of
 Table 1.4 – CUSTOMER Annual Fees

3. Work breakdown structure

Work breakdown structure, according to PMBOK, is a hierarchal structure of all

deliverables and tasks that need to be accomplished throughout a project. The chart
divides all complex deliverables into smaller tasks that can be handled in a
manageable way. The WBS chart is divided into levels, and accordingly, the upper
levels represent the project's major deliverables and are divided into more outcomes
and deliverables that are more detailed and focused. There are several characteristics
of a WBS that differentiate it from any project breakdown chart. First, the WBS chart
should be hierarchal, dividing all deliverables into smaller deliverables that sum up to
produce the final product. Second, each of the deliverables must have at least two sub-
elements which sum up to produce a major deliverable. Third, the WBS is outcomes
and deliverables focused instead of activities and tasks focused, making it a
breakdown of the final product. Moreover, every element in the WBS must not
overlap with any other deliverables to avoid work duplicates. Due to the benefits of
having a Work Breakdown structure for complex projects, most of the projects
implemented do have a WBS breakdown for all project deliverables. In this project,

23 Page 10 of
we have also implemented it to ensure the final product is delivered successfully, to
make sure all deliverables are known to all members ahead of time, resources are
assigned, deadlines are set, and all members are fully accountable for the work
assigned to them (Cohen, 2021).

23 Page 11 of
 QUICKMART
WBS

Project Application
Engineering
Management Deployment

Supervision & Interface Debugging&

Design Prototyping
Coordination Management Testing

Application
Budget Subcontracting User Journey User Interface Platform
Approval

End-User Source Code

Scheduling Documentation
Reporting Development

Quality End-User
Management Training

Risk
Management

Figure 1.2 – QUICKMART Work Breakdown Structure

As shown in the diagram above, this project is divided into three major work
packages: project management, engineering, and application deployment. The first
work package which is project management includes all necessary items to monitor
and control the project’s progress. It involves developing an approved project
planning package, execution plan, quality plan, and risk management plan such as the
one shown in section 4. The work package also includes management, control and
coordination with all interfaces associated with the PROJECT including the
subcontractors Amazon Web Services and the payment gateway in addition to the
End-user.

The second work package is engineering which involves the design, data
management, prototyping and code development. It shall also involve the application
initial submission into the selected application platform based on the CUSTOMER’s
selection of iOS and/or android platform.

23 Page 12 of
The third work package is the application deployment which shall involve the testing
process, platform approval, documentation and end-user training. The Beta testing of
the software shall be conducted on more than 30 smartphones to ensure that it runs
and works flawlessly on any mobile platform. The application's efficiency and
behavior will be evaluated in a number of scenarios, including poor network
reception, low battery, and insufficient usable memory. It will also be put through
paces of incoming and outgoing SMS and MMS, media player on/off, and incoming
and outgoing calls to ensure the final product is free of flaws. The documentation
shall be handed over to the CUSTOMER as an editable source code in order to enable
the user to modify anything in the future id required. The final subsection of work
package three is the end-user training which will involve training a number of
employees to navigate the application and troubleshoot it in case of any system errors.

23 Page 13 of
4. Risk management plan
A risk management plan is a project manager’s guide to identify the potential risks of
the project, to estimate impacts and probabilities for them and to define the responses
and mitigation strategies to these risks.

In the scope, schedule, cost or quality, risk can be an uncertainty. Identifying those
risks and building a system to optimize positive impacts and to minimize possible
negative impact as a means to create a risk management plan is crucial (MACKAY,
2020).

There are many sources of defining the risks, it could be from previous experience,
brainstorming or from other competitor experience in the same field. In our project
which is designing a new home delivery mobile application for a supermarket, we a
brainstormed with all members of the team to come up with the expected risks for this
project. We ended up with different risks that associated with our project such as
approval of platforms, risk of investing in platform we don't have control over it, risk
of tying our application in a single platform, staff turnover, unplanned scope
variations, underestimating the cost & time and finally the software security risks.

Then we created the risk register form to help us to define the risk, evaluate and
assess the consequence, impact, and probability of each potential risk and to assign
roles and responsibilities to each risk (MACKAY, 2020).

23 Page 14 of
 Risk Management Plan
INTRODUCTION
Information
QuickMart which is a new mobile phone delivery application for a
Project Name
supermarket

MobiApps Company, a software development company that

Project Overview
specializes in mobile phone application design and development.

Project Duration 8 months

Project Manager Eng. Shaima Almarzooqi

DOCUMENT INFORMATION

Information

Document ID MORI-00-01

Document Owner Shamsa Almansoori

Issue Date 19/03/2021

Last Saved Date 27/03/2021

File Name Risk Management Plan

23 Page 15 of
RISK REGISTER

Impact
Probability
Priority (Minor,
Ref. Risk Description (Low, Medium, Moderate, Major Response Plan Assignee
(Rare, Unlikely,
High or Very and Severe)
Possible or Probable)
High)

Build an app
complied with the
Getting the approval standards and
01 Approval of platforms from the application Rare Very high Moderate guidelines for Project Manager
stores. application stores
such as IOS and
Android.

The major risk of mobile

Risk of investing in app growth is your total
platform we don't lack of control over the
Investing in different Software
02 have control over it. platform itself. What Unlikely Low Minor
platforms. Developer
about the owner of the
platform selling or
shutting down?

Risk of choosing single

Risk of tying our platform will limit your
application in a company’s future
Investing in different Software
03 single platform. options. What if your Unlikely Medium Moderate
platforms. Developer
customer wants to
switch to another
platform.

High Major To avoid this risk, Project Manager

04 Staff Turnover Key personnel leave Possible

23 Page 16 of
 the project taking
will increase
critical information with
collaboration and
them that significantly
shared information
delays or derails the
on the team.
project.

As the project
progresses more and we will have
more features that were customer
Unplanned Scope not identified at the involvement in all
05 Possible High Major Project Manager
Variations beginning of the project project stages to
emerge that threaten reduces unplanned
estimates and scope variation.
timelines.

Project costs and lead

Underestimating the Good planning and
time increases because
Cost and Time. studying of all
06 of poor precise Possible High Major Project Manager
aspects of the
assessment and
project.
planned scope.

It is a combination of
efficiency, security and
transaction risk across
the whole system. To do continuous
Software Security integration, testing Technical
07 Possible Very High Severe
Risks This risk will appear at and updating for the Security staff
late stage of the system.
application when
number of active users
increased.

23 Page 17 of
RISK ASSESSMENT MATRIX

(Shuttleworth, 2017)

DOCUMENT APPROVALS
Role Name © Signature Date
Project Sponsor Quick Mart Super Market electronic 28/03/2021

Project Manager Eng. Shaima Almarzooqi electronic 28/03/2021

(MACKAY, 2020)

23 Page 18 of
5. Project Organizational Structure

This section will contain the project’s organizational chart and the roles and
responsibilities for department/individual.
Project organizational structure

Figure 1.3 – MobiApps Organization Chart

23 Page 19 of
Roles and Responsibilities
Table 1.5 – MobiApps Main Departments
Title Roles & Responsibilities
1. CEO - Leads the company.
- Major decision making.
- Decides on the roles of all departments.
2. PMO - Supporting other departments.
3. Human Resources - Staff recruitment.
- Policies updates.
- Staff records.
- Perform benefit analysis.
4. Software - Responsible for the awarded projects design and
Development development.
Department
5. Finance - Company’s cash flow management.
- Financial forecasting.
- Documentation of financial reports.
- Advice the management regarding financial decisions.
6. Marketing - Managing company’s social media.
- Marketing and promoting the company’s products and
services.
- Regular updates on marketing tools.

Table 1.6 – MobiApps Software Development Department:

Title Roles & Responsibilities
Project Manager - Manage the agile project plan with the team and
stakeholders.
- Managing the outcomes and deliverables to meet up the
client’s expectations.
- Technical updates and training.
- Interface management between the higher management,
team members, other departments, and stakeholders.
Senior Planning - Planning project schedule and allocate resources.
Engineer
Technical Lead - Leading the app development and coding process.
- Gather information and database administration.
- Supervise the QA analysis regarding fixing bugs and
errors.
Design Lead - Leading the app interface design that includes visuals,
audio, and icon design.
Software Performance - Responsible for the app testing and launching process
Team where they make sure that is works with all expected
features requested by the client.
- Request necessary updates from the technical team.
Senior Document - Record progress and keeping all members up to date
Controller regarding app design and development processes.
After-Sales - End-user app training.
Representative - App maintenance and after-launching updates.

23 Page 20 of
6. Conclusion

Thus, from the above discussion, it can be inferred that with the occurrence of the

recent pandemic situation there has been an enormous rise in the online shopping

behavior of consumers. People are more inclined to purchase online since this

effectively helps in maintaining social distancing norms while items being delivered

at the doorsteps. Different retail businesses like UAE Mart supermarket are willing to

shift from the traditional Brick and Mortar layout to online platforms to serve the

needs of their consumers while maintaining both safety and ensuring high-end

consumer satisfaction. The development of a mobile-based application called

QUICKMART is initiated for the development and the responsibility for developing

the concerned mobile-based application is assigned to MobiApps. A detailed

development plan is initiated along with the technical requirement and project scope.

The scope includes project supervision, contract administration, quality control, and

cost control. Technical requirements include the development of a prototype, full

access to source code, Beta testing of the application, and the payment integration

within the application. The project milestone is set and the project timeline is set

around 7 months. The total project budget is assumed around 388,200 AED. The

project team includes different members whose roles and responsibilities are already

defined before project initiation. Seven different types of risks are identified

concerning the development of this particular application and are segregated based on

their occurrence, impact, and probability. Different risk mitigation strategies are

developed to manage the risks. The development of this application will ensure the

effective accomplishment of the consumer needs who are focused on online purchase

.during the pandemic situation

23 Page 21 of
Word Count: 3443

7. References
1. Average Salary in United Arab Emirates (2021). Salary Explorer [online].
[Viewed on March 30, 2021]. Available at:
http://www.salaryexplorer.com/salary-survey.php?loc=227&loctype=1
[Accessed March 29, 2021]. 

2. Cohen, E. (2021). What is WBS (Work Breakdown Structure) in Project

Management?. Retrieved 10 April 2021, from
https://www.workamajig.com/blog/guide-to-work-breakdown-structures-wbs

3. Knutson, J. (1996). Rolling wave approach to project management. PMI

[online]. [Viewed on March 29, 2021]. Available at:
https://www.pmi.org/learning/library/rolling-wave-approach-project-
management-10514

4. MACKAY, J. (2020, April 3). "7 Steps to Write a Risk Management Plan For
Your Next Project (With Free Template!)". Retrieved from Planio:
https://plan.io/blog/risk-management

5. SHUTTLEWORTH, M. (2017, April 2). "Risk Matrix Sizing: Does size really
matter?". Retrieved from project-risk-manager: https://www.project-risk-
manager.com/blog/risk-matrix-sizing/

23 Page 22 of
23 Page 23 of