Scribd
Upload
482 views

Project Initiation-Kumaranath Fernando: Current Problem Statement

This document outlines the initiation of a project to develop a mobile application called "Rendezvous" that helps groups of people collectively choose the best restaurant based on budget and category and make reservations. The key objectives are to ease the process of selecting restaurants and making reservations, generate revenue through premium versions and ads, and gain market share within 6 months. The project assumptions include dedicated team members and compatibility with existing mobile infrastructure. Constraints include legal processes and limited time/funding. Preliminary requirements include creating user profiles, inviting friends, selecting restaurants by budget/category, and making reservations. A schedule is provided outlining tasks from idea generation through maintenance. Potential risks include requirements changes, low productivity, inadequate planning, resource mismanagement,

Uploaded by

k2k02
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
482 views

Project Initiation-Kumaranath Fernando: Current Problem Statement

This document outlines the initiation of a project to develop a mobile application called "Rendezvous" that helps groups of people collectively choose the best restaurant based on budget and category and make reservations. The key objectives are to ease the process of selecting restaurants and making reservations, generate revenue through premium versions and ads, and gain market share within 6 months. The project assumptions include dedicated team members and compatibility with existing mobile infrastructure. Constraints include legal processes and limited time/funding. Preliminary requirements include creating user profiles, inviting friends, selecting restaurants by budget/category, and making reservations. A schedule is provided outlining tasks from idea generation through maintenance. Potential risks include requirements changes, low productivity, inadequate planning, resource mismanagement,

Uploaded by

k2k02
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

Project Initiation-

Kumaranath Fernando

1.1 Introduction
Current problem statement
Although quite a number of restaurant reviewing apps at large,
yet many people faced numerous difficulties in opting the best
restaurant for the right price.
The situations becomes even worse when the need arises to
organize a meet up among a group of individuals .Since each
individual has different personal preferences and affordabilities.
Thus, ways of selecting the best restaurant based on a budget
and a category, making reservations at times of convenience
were not addressed.

Solution
Rendezvous a mobile application, which picks up restaurants
and makes reservation at convenient times for the user.
An ideal scenario is when an individual wants to hang out with a
group of colleagues he/she could simply
Send invites to desired persons.
Choose a budget everyone could afford using the chat
feature.
Pick out the best reviewed restaurant in town based on its
category (be it Italian, German, Japanese, Indian or whatever
restaurant it could be).
Reserve restaurant at youre your own convenience
Get loyalty discounts from restaurants .
A comprehensive solution for groups of individuals to collectively
decide, reserve the best restaurant at times of convenience.

1.2 Project Objectives


To ease the inconveniences of selecting restaurants and
making reservations with the introduction of new features to
suggest the best restaurants based on its category and its
budget.
To generate revenue by the sale of premium versions and
hosting in-app advertisements.
To capture market share by creating a good company
reputation among the mobile community within the first six
months of the applications first release.

To ensure customer satisfaction by capitalizing on providing


better in-app user experience.

1.3 Project Assumptions & Constraints


1.3.1 Assumptions
Project members will be honest and dedicated, work with
optimum potential throughout the projects lifecycle and will
be fully aware of their respective roles.
Failure to identify changes to draft deliverables within the
time specified in the project timeline will result in project
delays.
Project team members will adhere to the Communications
Plan.

The introduced mobile solution be viable to support the


existing mobile infrastructure (i.e. hardware compatibility of
existing devices).
The users will possess necessary skills to operate and make
the maximum benefit the out of the introduced solution
All project participants will abide by the guidelines which are
governed by the module leader of the group project.

1.3.2 Constraints
Legal proceedings to be followed in order to reach
agreements/endorsements with actual restaurants.
Limited time frame to master new technologies and
successfully complete the project.
Unforeseen turn of events and unexpected mishappenings
/accidents to any team member.
Project funding sources are limited.

1.4 Preliminary Project Requirements


The system will provide users with the ability to create
and maintain a login account and profile online.
The system will provide users with the ability to send
invites to friends on social media, and form a friend circle.
The system will provide users with the ability to decide on
their budget.

The system will provide users with the ability to select the
best reviewed restaurant based upon the budget and its
category.
The system will provide users to make reservations with
the listed restaurants.
The system will provide the ability to host in app
advertisement for third parties.

1.5 Schedule Estimate

Task Name

Duration

Start

Finish

Brain Storming the Idea


and getting domain
expert Idea
Scope Definition

20 days

1/10/2015

20/10/2015

2 days

23/10/2015

25/10/2015

Feasiblility,Suitabilty,Ac
cessibility
Background Research

3 days

23/10/2015

26/10/2015

6 days

24/10/2015

30/10/2015

Gathering Requirements 8 days

24/10/2015

01/11/2015

Requirement
Classifications
Project proposal

3 days

02/11/2015

05/11/2015

4 days

06/11/2015

10/11/2015

Design

10 days

11/11/2015

21/11/2015

Implementation

70 days

22/11/2015

30/02/2015

Testing

70 days

22/11/2015

02/02/2015

Prototype

4 days

02/03/2015

06/03/2015

Final Project report

6 days

07/03/2015

13/03/2015

Final presentation

1day

14/03/2015

15/03/2015

Marketing

Continues

15/03/2015

n/a

Development
(First release version
1.0)
Maintenance

Continues

21/03/2015

n/a

Continues

21/03/2015

n/a

1.7 Potential Risks


Requirements inflation :

As project progresses, more and more features that were not


identified at the beginning of the project emerge that threaten
estimates and timelines.
Poor productivity:
Lower team productivity at often at initial stages of the project
may result in the failing to meet the required deadlines.
Inadequate planning:
Failure to understand the requirements and planning
accordingly will likely cause lots of gray areas during project
lifecycle and would end in a failure.
Mismanagement of resources:
Making correct assessments of available resources are
essential before the inception of the project. Failing to do so,
may lead to wrong assumptions and ambiguity.
Internal Conflicts among team members
Team spirit is vital, to keep the project alive, when
misunderstandings do occur they need to be proper dealt with.
Failing to do so, will distort the unity and harmony among the
members making work miserable.

You might also like