Software Project Management Plan for
“Online LPG Gas Booking System”
1 Introduction
The Software Project Management Plan (SPMP) for the Online LPG Gas Booking System
outlines the strategic framework for the successful development, implementation, and
maintenance of the system. This comprehensive document serves as a guide for project
stakeholders, detailing project objectives, scope, milestones, schedules, resource allocation,
risk management, and quality assurance processes. The SPMP ensures transparency,
effective communication, and adherence to industry standards throughout the entire software
development life cycle, ensuring the timely delivery of a robust, secure, and user-friendly
Online LPG Gas Booking System.
1.1 Project Overview
The Online LPG Gas Booking System is a dynamic web-based application
developed to modernize and streamline the process of Liquefied Petroleum Gas
(LPG) cylinder booking. This project responds to the growing demand for a more
efficient and user-friendly system, catering to both residential and commercial
users. Key features include a secure user authentication system, real-time tracking
of cylinder availability, an intuitive booking interface, seamless payment
integration, and responsive customer support. The project aims to reduce manual
intervention, enhance user experience, and ensure the timely and reliable delivery
of LPG cylinders.
1.2 Project Deliverables
Preliminary Project Plan- 27.05.2023
Requirements Specification- 13.06.2023
Architecture Specification- 04.07.2023
Design - 01.08.2023
Source Code- 01.09.2023 - 14.10.2023
Test Plan- 15.10.2023 -12.11.2023
Final Product Demo- 13.11.2023 - 22.11.2023
1.3 Evolution of this document
As the project progresses, we updated the document accordingly. Updates should
be expected in the following sections:
References - updated as necessary.
Definitions, acronyms, and abbreviations - updated as necessary.
Organizational Structure will be updated as the team leaders are assigned for
each phase.
Technical Process - In this section will be revised appropriately as the
requirements and design decisions become clearer.
1|Page
Schedule – as the project progresses, the schedule will be updated accordingly.
Revision History –
Revision Date Updated By Update Comments
1 01.10.2023 Vishal Kumar First Draft
2 18.11.2023 Vishal Kumar Second Draft/Final Draft
1.4 References
[Link]
[Link]
1.5 Definitions, Acronyms, and Abbreviations
i. DFD -> Data Flow Diagram
ii. CFD -> Context Flow Diagram
iii. ER -> Entity Relationship
iv. IDE -> Integrated Development Environment
v. SRS -> Software Requirement Specification
2 Project Organization
2.1 Process Model
The process used for this project will be a V-model such that each stage of the
model allows us to do testing after completing a phase. Referring to the diagram
below, each phase is tested after completion.
2|Page
2.2 Organizational Structure
Team Members –
1. Vishal Kumar
2. Zakir Hussain
3. Aman Raj
4. Sameer Sharma
5. Hemker Agarwal
6. Kingshuk roy
Name Organization/Position Contact Information
Vishal Kumar ITech Project Manager vishal8112@[Link]
6295122463
Kingshuk roy ITech Business Analyst king61109@[Link]
9327589346
Deliverable Days Team Leader Description
1 Vishal Kumar Project Plan
2 Zakir Hussain Requirements
Specification
3 Aman Raj Analysis
4 Sameer Sharma Architecture
Specification
5 Hemker Agarwal Component/Object
Specification
6 Subham Chandra Source Code
7 Kingshuk roy Test Plan
8 Whole Team Final Deliverable
2.3 Organizational Boundaries and Interfaces
Team leaders throughout each development of the phases will be responsible for
coordinating team meetings, updates, communications, and team deliverables.
2.4 Project Responsibilities
For the most vital responsibilities per phase of each team members, please refer to
segment 2.2. Ultimately the project team is responsible for the successful delivery
3|Page
of the product. The team member tasks per deliverable according to expertise and
the phases are as given below:
1. Project Plan – Vishal Kumar
[Link] Specification – Zakir Hussain
3. Analysis – Aman Raj
4. Architecture Specification – Sameer sharma
[Link]/Object Specification – Hemker Aggarwal
6. Source Code – Subham Chandra
7. Test Plan – Kingshuk roy
8. Final Deliverable – Whole Team
Name Organization/ Role/Responsibilities
Position
Vishal kumar ITech Project • Managing and leading the project team.
Manager • Developing and maintaining a detailed
project plan.
• Monitoring project progress and
performance.
• Managing project evaluation and
dissemination
Zakir Hussain ITech Business • Deadlines and resource requirements.
Analyst • Develop and perform work flow
analysis to find out the difficulties in
reaching goals.
• Provide project cost estimates.
Aman Raj ITech Designer • Propose effective design solutions to
meet project goals.
• Prepare design layouts and sketches
according to company design standards.
• Keeping of records and files.
Sameer Sharma ITech Staff • Documentation of daily activities.
• Making kick-off meeting reports.
• In-charge of materials needed for team
building activities
Hemker Agarwal ITech Staff • Documentation of daily activities.
• Making kick-off meeting reports.
• In-charge of materials needed for team
building activities
Kingshuk roy ITech Staff • Documentation of daily activities.
4|Page
• Making kick-off meeting reports.
• In-charge of materials needed for team
building activities
3 Managerial Process
3.1 Management Objectives and Priorities
Efficient LPG booking, enhanced user experience, robust security, scalable
system, reliable operations, responsive customer support, seamless payment
integration, user feedback-driven improvement, adherence to standards,
comprehensive documentation, continuous performance monitoring, and cost-
effective resource utilization.
Streamlined processes, user satisfaction, data security, scalability, system
reliability, customer support excellence, secure payments, continuous
improvement, regulatory compliance, comprehensive documentation,
performance optimization, and cost-effective operations.
3.2 Assumptions, Dependencies, and Constraints
In this project plan, a number of factors are taken into account. The following list
shows the way milestones on various project phases have been scheduled:
• The team budget of 8 persons x 365 hours = 1825 hours
• The project deadline of November 15th.
• The final presentation is on November 22nd.
• The peer evaluation deadline is on November 22md.
• Other than the weekends, holiday is closed.
NOTE: Due to the deadline of 15th November 2023, running out of time will have
its reflection on the product, and not on the duration of the project. By assigning a
priority to every user requirement, a selection can be made of user requirements
that may be dropped out if time runs out.
3.3 Risk Management
This section mentions about potential risks that could be during project
production. Also, schedules or methods are defined to prevent risks such as
below:
i. Technology risk
ii. Financial risk
iii. People risk
5|Page
iv. Market risk
v. Structural risk
The following are the possible risks to be encountered during the development of
the project and how they can be prevented.
Miscommunication
Prevention: Team members should not hesitate to ask and re‐ask questions
if things are unclear. Team members should have a written copy of the
tasks assigned to them every meeting.
Correction: When it becomes clear that miscommunication is causing
problems, the team members should gather in a meeting to clear things up.
Time shortage
Prevention: Care is taken to plan enough spare time.
Correction: When tasks fail to be finished in time or when they are
finished earlier than planned the project planning is adjusted.
Illness or absence of team members
Prevention: Team members should warn their team leader or the PM
timely before a planned period of absence.
Correction: Work can be taken over quickly by someone else or be
distributed among the team members if a person gets ill.
3.4 Monitoring and Controlling Mechanisms:
The monitoring of progress is done by the PM using the following means:
i. Weekly project status meetings
ii. Shared document repository
iii. Project tracking by MS project plan
iv. Tracking utilizing baselines in MS project
Project Kick-off Meetings
The project group meetings take place within the class room or through
chat. These meetings are meant to inform each other of the progress made
on various tasks and to assign new tasks.
Progress Report
Progress report is done every Friday. This is meant to inform and show the
progress in the development of the project and how things are going.
6|Page
4 Technical Process
4.1 Methods, Tools, and Techniques
The project will be implemented utilizing V-model methodology, and tools such
as Dreamweaver, Microsoft Project, Star UML, Java, MySQL, QTP, and Load
Runner will be utilized. The risks for each category are listed to complete the
project successfully. For each risk, a description, a probability of occurrence, the
associated action and the impact of the risk are given.
4.2 Software Documentation
Documentation such as Project Charter, Business Requirement Document,
Functional Specification document, Cost Benefit Analysis, Technical
Specification document, Detail Design Document, Test Plan, Implementation
Plan, Detailed Project Report, and Benefit Realization document.
4.3 Project Support Functions
All project support documents will be completed in applicable phases.
5 Work Elements, Schedule, and Budget
I. The project is accounted for project resources, technologies and tools required to whole
analysis, implementation, and test of the application.
II. The project lead will be rotated for each phase within 5 team members.
III. The document for all phases will be revised in subsequent phases if applicable.
Budget and Resource Allocation
Salary 1,50,000.00
Office Operations/Supplies/Equipment/Consumables 45,000.00
Miscellaneous 15,000.00
Total Rs. 2,10,000.00
Schedule
7|Page
6 Conclusion
The SPMP for the Online LPG Gas Booking System provides a comprehensive roadmap for the
successful development, implementation, and maintenance of the system. By aligning
management objectives and priorities, the project aims to deliver an efficient, secure, and user-
friendly solution that meets the needs of consumers and stakeholders. The SPMP serves as a
guide for effective project management, ensuring transparency, adherence to standards, and
continuous improvement throughout the software development life cycle. With a focus on
efficiency, user satisfaction, and system reliability, the Online LPG Gas Booking System is
poised to revolutionize LPG distribution processes.
8|Page
