Final Project

Life cycle for the implementation of e-platform

development

Group Members:

1. Dilawar Ali 70075373

2. Rashid Ali 70075434
3. Hamza Arif 70071652
4. Arfa Asghar 70075486
5. M.Aftab 70071501
Submitted to:

Professor Muhammad Faisal

Course name:

Fundamentals of project management

The university of Lahore

 ACKNOWLEDGEMENT

In the name of God, who is the kind and merciful.

We would like to thank our parents, relatives and friends who
really kept backing us up in all the times, both financially and
morally. We would like to express my gratitude and appreciation
to all those who gave us the possibility to complete this report. A
special thanks to our semester resource person, Professor
M.Faisal, whose help, stimulating suggestions and encouragement
helped us in writing this report.

Any omission in this brief acknowledgement does not mean lack

of gratitude to others.

Thanking You,

Table of Contents………………………………………………………………………
1- Project Initiation………………………………………………………………..
1.1. Project Charter…………………………………………………………………………………………
1.2. Appoint the Project Team……………………………………………………………………..
1.3. Stakeholders…………………………………………………………………………….
1.4. Set up the Project Office……………………………………………………………………….
1.5. Perform Phase Review…………………………………………………………………………..
2- Project Planning…………………………………………………………………
2.1. Create a Project Plan………………………………………………………………………………
2.2. Create a Scope Plan
2.3. Create a Resource Plan………………………………………………………………………….
2.4. Create a Cost Plan………………………………………………………………………………….
2.5. Create a Schedule Plan……………………………………………………………
2.6. Create a Quality Plan…………………………………………………………………………….
2.7. Create a Risk Plan………………………………………………………………………………….
2.8. Create a Communications Plan…………………………………………………………
2.9. Create a Procurement Plan…………………………………………………………………
2.10. Perform Phase Review…………………………………………………………………………
3- Project execution and Controlling………………………………………..
3.1. Build Deliverables……………………………………………………………………
3.2. Monitor and Control………………………………………………………………..
3.3. Perform Schedule Management……………………………………………………………
3.4. Perform Cost Management………………………………………………………………...
3.5. Perform Quality Management……………………………………………………………
3.6. Perform Risk Management………………………………………………………………..
3.7. Perform Procurement Management………………………………………….....
3.8. Perform Communications Management………………………………………
4- Project Closing………………………………………………………………..
4.1. Perform Project Closure……………………………………………………………………
4.2. Review Project Completion……………………………………………………………..
5- Conclusion……………………………………………………………………….
Introduction:

The establishment of a mobile application for a multinational company that any

employees, customer or user of the company can use to access company's
information, not only that but users will be able to buy and sell their stocks of the
company. If they're interested in buying or purchasing from the company, they can
use the app to do that, it will have exclusive discounts and deals only through their
application. It is a new initiative by the company to expand itself through IT, to
provide better information to their customers and everyone is able to access it with
ease, Coronavirus pandemic gave a big blow to the industries that weren't on the
internet and now everyone is bringing their business to Internet. We've been
assigned to develop this application for them and monitor is closely.

After looking at the project in details, following are components of project life cycle;
Project Definition.
Defines goals, objectives and critical success factors for the project.
Project Initiation.
Every activity needed to set up the project before actual work starts.
Project Planning.
Detailed plan that how the work will be carried out including time, cost and
resources allocation.
Project Execution.
Doing the work to deliver the product, service and desired outcome.
Project Monitoring and Control.
Ensure that project stays on track and taking corrective actions to ensure it does.
Project Closure.
Formal acceptance of deliverables and disbanding all elements that were required
to run the project.
Objective:

The aim of this project is to discuss the life cycle models implemented. The life
cycle process is to be used to expand the company's portfolio online, available to
everyone with just a tap, on their mobile phones. Through this we'll study and learn
project management of application development project.

1- Project Initiation:

Project Initiation began when the company developed a need of a better online
platform for their customers and people interested in their company, they
thought of a mobile application.

1.1. Project Charter:

A document was issued by the project initiator/ sponsor that formally authorized
the existence of a project, and provided the project manager with the authority to
apply organizational resources to project activities. Including what the objectives
are, how it will be carried out, and who the stakeholders are. It is a crucial
ingredient in planning out the project because it is used throughout the project
lifecycle.
1.2. Appoint the Project Team

Initiation ended after the appointment of a project manager. The project manager
was delegated with authority and direction necessary to start planning.

Project Team

Project team is also made for this project and these were;
● Project Manager
Mr. Dilawar Ali
● Team Leader
Mr. Hamza Arif Butt
● Main Team Members
1. Dilawar Ali
2. Rashid Ali
3. Hamza Arif Butt
4. Arfa Asghar
5. Muhammad Aftab

Stakeholders:

Stakeholders register:

Stakeholders Role Involvement Priority Impact

name

Astral Customer High Main Positive

adhesives

Mr. Dilawar Ali Project Very high Main Very positive

manager

Stakeholders management strategy:

It is used to communicate the project progress to the stakeholders, it includes all

the threats, progress and tweaks of the project
1.4. Project office

We've allocated an office to this team only so they can work and communicate
easily with each other and be more productive.

1.5. Perform Phase Review

A progress monitoring and review system was introduced to establish the end of
one and start of another phase of life cycle.

2- Project Plan:

The complete project plan was thought out from designing phase to operations to
testing it and then delivering it. Each aspect of project was discussed and looked on
very thoughtfully and carefully to minimize the problems and risks. Following
factors were mentioned and looked upon thoroughly:
● Design phase
● Gather requirements.
○ User, hardware and software requirements
● Perform analysis.
● Develop the design in its various iterations:
○ High-level design
○ Detailed design
● Hand over the design to application programmers.
● Code and test application.
● Perform user tests.

User tests application for functionality and usability.

● Perform system tests.

○ Perform integration test (test application with other programs to verify
that all programs continue to function as expected).
○ Perform performance (volume) test using production data.
● Go into production–hand off to operations.
● Ensure that all documentation is in place (user training, operation
procedures).
● Maintenance phase--ongoing day-to-day changes and enhancements to
application.
Application development life cycle

Design phase
Development Phase

Testing Phase

Production Phase
Total duration 6 months

Start time 1/1/2021

End time 1/6/2021

2.1. Create a scope plan:

Application for Android, I Phone and Website for Windows is required, any specific
language to make these apps aren't required.

2.2. Create a resource plan:

Roles, Responsibilities, and Authority of project team

Roles Authorities Responsibilities

Dilawar Ali (Project Had the authority to do Monitor the whole work
manager) change in project and guide the team about
management plan. any difficulty. Also make
sure that all the tasks
performed are within
budget

Hamza Arif Butt (Team Leading the team Showed all results to the
manager) project manager and
solved issues between
team members.

Rashid Ali (Quality Check the quality of apps Report to the team
manager) and report bugs if found. manager about quality
related issues

2.3. Create a Schedule plan:

Schedule is planned om the bases of total duration agreed upon

Phases Duration

Design phase 15 days

Developing 30 days

Testing 15 days

Production 60 days

2.3. Create a cost plan:

Cost of the project is decided on the features demanded and given.

Features Cost ($)

Push notifications 100

Search options 1000

Flexibility (android, iPhone, website) 5000

Security 10,000

Updates 1000

User feedback 600

Customization 1000

Social Integration 1000

Other tweeks 10300

Total 20,000

20,000$ is only for features and other tweaks that came up at last time. The actual
cost for the project will be from 60,000$ to 70,000$ estimated.
There's 40,000$ for the fully simple developed app without these features.
2.4. Create a quality plan:

Quality of the application will be checked by the quality assurance team, any bugs
will be reported to the team, before the project is done and sent to the customer or
before holding a meeting with stakeholders teaching them how to use the new
application, the quality will the checked and the app will be tested many times in
each area.

Quality improvement approach

To improve the quality of the project’s processes many steps were used like:

Weekly meetings will be called between the project manager and project team so
that difficulties which might affect the project were removed.

Reports on cost performance were issued weekly to analyse the cost regarding
quality
Control Charts and Scatter plot were made to analyze project, team members and
schedule performance

2.5. Create a Risk plan:

Risk register

The risk register contained information on threats and opportunities that might
impact the project.

Risk Statement Impact Probability Risk

response

Computers Systems does Cost, schedule 20% Have extra

failure not work computers in
the office

Team member Losing team Time, scope 30% Should have

falling sick member extra men
ready if
needed

Natural Earthquake, Cost, Scope, 10% Contengency

disasters flood etc Time plan
Load Shedding No electricity Cost, Schedule 25% Buy a
to use generator
computers

Stakeholders Change of Quality, Time, 15% Taking notice

requirements Cost of requirement
or progress is and work on
not according them
to their
expectation

2.6. Create a communication plan:

Communication was done mainly through emails and online meetings, to help
manage this whole operation, we have a modern help desk system using PHP
CodeIgniter. This allowed quicker delivery by assigning two senior PHP developers
to the project.

Communication within the project team

The project team communicated with the team leader through face to face meeting.
The team leader interacted with the Project Manager through meetings,
presentations and emails telling him about the current situation of the project. The
Project Manager brought in notice the cost and schedule performance to the CEO.

2.7. Create Procurement management:

There is no such procurement required in this project, the softwares on which the
apps are programmed are one time payment for yearly and some are just one time
payment forever use.

Technologies:

● Kotlin using Android Studio 3.4.1

● Swift using Xcode
● PHP (7.2), CodeIgniter Framework(3.1)
3- Project execution and controlling:

Plan was executed as planned, without too much problems. It was executed just as
we had expected and planned for, the control over the project was extraordinarily
good and everything was kept under comtrol from start to finish.

3.1. Build Deliverables

Each area of the project had its separate semi-finished deliverable which was the
input for the succeeding section. However, the last area had the final finished
products i.e. App for Android, iPhone and Website.

3.2. Monitor and Control.

The project was monitored and controlled by the team leader and quality assurance
team. Team leader kept the whole development processes under control and
monitores all the steps, all steps being done correctly then it was handed to quality
assurance team. It was well monitored and controlled process which left no holes in
it.

3.3. Perform Time Management

All the activities of the project were sequenced conforming to the process
requirement and resources allocation.

3.4. Perform Cost Management

Cost management was done extraordinary, there were many irrelevant and extra
codes and problems which only increased the cost but the team performed those
tasks with easiest ways and methods, reducing the cost of using expensive
software’s and methods to manage the cost.

3.5. Perform change Management

There were changes made in planned procedures due to many problems, all those
changes in performances were recorded.
3.6. Perform quality Management

Quality was managed with care, the quality assurance team kept checking quality
of every feature over and over again until it was running smoothly without any
bugs and lag.

3.7. Perform Risk Management

Before the start of the project risk assessment was done and risk register
maintained. All the measures to counter the negative risks and enhance the positive
risks were taken and exercised,

3.8. Perform Procurement Management

There were no material procured, except the softwares that were utilised to compile
the codes and develop the apps on, it was all mentioned and noted.

3.9. Perform Communications Management

A management information system (MIS) department was established to record the

information and its distribution to the concerned stakeholders.

4- Project Closing:

The project was closed after the product was delivered and it was accepted by the
customer and they approved of it, all the payment was made at the end.

Everything was recorded into the achieves and what we learned as a team and as a
company during this project.

4.1. Review Project Completion.

After the completion of commissioning of the project the end report was reviewed
by the stakeholders and the project was declared done.
Conclusion:

By this project we can conclude that the project life cycle is very important in order
to properly execute and complete a project. No matter how small or big the project
is, if planned correctly and executed accordingly, it becomes easy to complete it
without any hesitance.
If the project stages weren't divided into stages like
● Design
● Development
● Testing
● Production
Then the project wouldn't have been so easy and smooth, there would have been
so many complications and problems without the guidance, surely there were ladt
minute problems and changes made but they only improved the planning phase for
the next project. All the data was recorded, about every single stage.