Submitted by: Yasmin Khaled Abdel Maksoud

Hend Osama Ahmed

Submitted To: Prof. Atef Ghalwash
 Driving (Ride sharing) Mobile Application Project
Project Management

To start with, there are many requirements needed while conducting a project of “driving
mobile application” like “Uber”, “Careem”, “Didi”, “In drive” and to be able to compete with
them not only in an efficient way but also an effective way.
Project Details:
 The Project scope will only be specific and directed to be an application for ride
sharing. There for the scope of this project will be “Ride-Sharing Mobile
Application”.

 The project target audience will be mainly: Practical people who are found in many
markets’ segmentation. Therefore, the project will be focus on demographic,
psychographic, and behavioural segmentation. As the practical people can be
found through varies genders, income levels, age groups, and diverse educational
backgrounds. They are also in the psychographic segmentation as they are having
traits like time-conscious, goal-oriented, and value-focused individuals; they are
always giving priorities to the cost effectiveness, convenience, and functionality in
their choices. In addition, they also can be allocated in the behavioural segmentations
as they are having specific behaviours such as reading the review of the products
before buying, comparing prices, and look for solutions that are efficient and reliable
enough.

 The target audience for the project “the practical people” shows the importance of
having Time efficiency, Cost effectiveness, efficient Customer Support with clear
communication, high level of data privacy and flexibility in the options delivered to
them.

 Project Requirements can be as follows:

 First Requirement: User Registration and Authentication

It is related to the user’s registration through the usage of their personal email, phone number,
or social media accounts with an implementation of a user authentication system for a secure
user access and this will be conducted by having password encryption.
 Second Requirement: Simple & Intuitive User Interface
It is related to the implementation of a user0friendly interface design having both a clean and
straightforward navigation by providing priority to let the user have an ease of use and
efficiency while accessing the application’s key features.
 Third Requirement: Quick Ride Request
As mentioned before that the practical people, as being the project’s target audience, are
focusing on practicality. Therefore, the application must provide the users the ability to
request their rides with minimal effort with no pointless steps by implementing a simplified
process for the ride request with options of “pre-set pickup” & “drop-off”.
 Fourth Requirement: Fast Matching & Dispatch
By implementing an efficient algorithm, the matching between the users and available drivers
will be much easier with a focus on reducing the waiting times with the driver availability
optimization.
 Fifth Requirement: Cost Transparency
Provide the needed details such as a clear and upfront pricing information with estimated
fares based on both the distance and time and all of those will be appeared to users before
confirming the request of the ride.
 Sixth Requirement: Flexible Payment Options
Not only a transparent pricing, but also allows the many payment methods like cash, digital
and credit cards with providing the users the freedom in choosing their preferred method of
payment for accessibility.
 Seventh Requirement: Reliable and Safe Drivers
To provide a safe service, background checks with drivers’ verification process will be
needed in addition to the comprehensive raring systems for the drivers including reviews
from prior passengers to guarantee the required reliability.
 Eight Requirement: Real-time Updates
The focus here is informing the users always by their driver arrival, ride status, and any
changes in their requested trop with timely updates and notifications.
 Ninth Requirement: Offline Access
Providing the users with the offline mode will let them able to have access to the application
necessary features such as examining their previous rides or contact information.
 Tenth Requirement: Minimalistic Advertising
Focusing on creating a user experience with no distraction by many advertisements to let
them have a focused experience.
 Eleventh Requirement: Efficient Customer Support
Providing the users with the chat option in the app to be a quick channel to resolve problems
in addition to the normal channel which is the email to address the users’ common concerns
and queries.
 Twelfth Requirement: Privacy and Data Protection
For data security, the implementation of robust security measures is needed by informing the
users with the privacy policy for their consent to collect data and process them.
A work breakdown structure (WBS) for a ride-sharing mobile application project, along
with estimated durations for each task:
1. Project Initiation (2 weeks)
1.1 Define project scope and objectives (3 days)
1.2 Identify stakeholders and gather requirements (4 days)
1.3 Conduct market research and competitor analysis (5 days)
1.4 Develop project charter and obtain approvals (3 days)
2. Requirement planning (2 weeks)
2.1 Functional Requirements (5 days)
2.2 Technical Requirements (5 days)
2.3 Requirement Review & Approval (3 days)
2.4 Statement of work (2 days)
3. Design Phase (4 weeks)
3.1 User interface (UI) design (7 days)
3.2 Database design and architecture (10 days)
3.3 Backend system design (14 days)
3.4 Integration design with payment gateways (7 days)
4. Development Phase (12 weeks)
4.1 User registration and authentication (14 days)
4.2 Ride request and matching algorithm development (21 days)
4.3 Driver management system development (28 days)
4.4 Payment system integration (14 days)
4.5 User feedback and rating system (14 days)
4.6 Testing and bug fixing (21 days)
5. Deployment and Launch (2 weeks)
5.1 App deployment to app stores (5 days)
5.2 Server setup and configuration (7 days)
5.3 User acceptance testing (UAT) and final bug fixing (10 days)
6. Marketing and Promotion (4 weeks)
6.1 Marketing strategy development (7 days)
6.2 App promotion and advertising campaign (21 days)
6.3 User acquisition and growth hacking techniques (14 days)
7. Post-Launch Support and Maintenance (ongoing)
7.1 Monitoring and performance optimization (continuous)
7.2 Bug fixing and updates (as required)
7.3 User support and feedback management (continuous)