Project plan
| Document | Project Plan |
| Author: | - |
| Version: | 1.0 |
| Date: | 11.2.2025 |
1. Assignment
1.1 background and starting points
Purpose of this project is to study, test and enhance an existing e-commerce platform, PrestaShop. We work in teams with the help of various mentors and task force member, to practice teamwork in an agile project environment.
1.2 Goals and tasks
Goal of this project is to learn how to work in project teams. We are creating a PrestaShop platform and trying to enhance it our way. Each team chooses their own EPICS to implement and try to learn while doing them.
1.3 Limitations and interfaces
Task is to create a PrestaShop as a service and learn by doing it.
1.6 Challenges related to the project
Strengths include technical expertise in PrestaShop development and Docker container usage, while weaknesses may arise from limited experience in handling large-scale projects. Opportunities include the growing demand for e-commerce solutions, while threats could stem from delays, technical issues, or changing customer needs. Strategic gates, such as planning, development, feedback, and deployment, will help monitor progress and address challenges.
2. Project organization
2.1 Organization
Structure of Project Organization in MindMap form
2.2 Responsibilities and decision-making process
The team leader works with the designated Product Owner to ensure that tasks and priorities are aligned with the project's goals. All decisions are made during daily scrum meetings, sprint planning, and the final sprint review. To close an issue in GitLab, it must have both an assignee and a reviewer, as well as a confirming comment.
Project Group
| Name | Responsibility | Company/Community |
|---|---|---|
Board Members
| Name | Responsibility | Company/Community |
|---|---|---|
Support Group
2.3.Project Steps and Financial Objectives
Task cases, bidding and phasening, intermediate results, schedules and resource plans, budget
2.4.Quality verification
Methods, standards, approval procedures, change management, documentation, reviews, risk management, Other complementary plans
2.5.Communication and tracking of project progress
Getting Started, Workspaces and Communications, Packaging Policy and Connection, Reporting, Reporting and Information, Project Folder
2.6.The end of the project
After the final delivery, the project will be transferred to the customer. All final documentation will be transferred in strict accordance with the project agreement.
3. Project's temporal Gates
3.1 Partitioning and Phase
The progress of the project can be described as a ns.With a Gantt chart.It can be used to show the progress of different phases with a timeline, while showing the critical points associated with different tasks.
GANT using PlantUML
Gate marks the initial setup phase, ensuring teams are formed, roles are assigned, and the project environment is operational. By this point, the team should be ready for the assignment, with a clear understanding of tasks, and a functional OPF environment.
The review checkpoint ensures the team is prepared for implementation by planning, budget, and deliverables. A clear project roadmap, documented requirements, and a well-defined offer outline what the customer will receive and at what cost.
- Project status
- Used resources and progress
- Problems and achievement
Test the mockup with stakeholders, gather feedback, and ensure the demo is well-prepared. Create a clear A4 presentation for a non-technical audience and share project documentation. Focus on user needs, avoiding technical discussions, and align implementation with expectations.
The termination phase includes measures to terminate the project.During the phase, the project team will draw up a project final report and the performance team.During the phase, the project's result for the contractor is considered the last management team meeting in week x and unloading the project organization.The closing phase results in the final report of the project. "
3.2 Project preliminary cost estimate
Presenting a cost estimate with a table:
4. Quality assurance
4.4 Risk management
4.6 Complementary plans for the project plan
This paragraph mentions what complementary plans are available or will be made within the project (e.g., a communication, risk management, testing and deployment plan).
- Project Agreement
- Requirement Specification
- Release Plan
- Master Test Plan
- Communication Plan
- Risk management plan
- Other Documentation