Skip to content

Project plan (template)
Document Project Plan
Author: Milla Sammallahti
Version: -
Date: 21.2.2025

1. Assignment

1.1 background and starting points

Our team Mighty Ducks mandate is to build a eCommerce service platform. The project will be implemented under the OPF framework. As a service developer and provider of an eCommerce platform based on PrestaShop, our team offers a solution for individuals and businesses looking to sell products online. The customer is any person or company seeking to leverage our platform to establish and manage their online store efficiently.

1.2 Goals and tasks

The goal of the project is to build an e-commerce platform that includes a variety of features. These include, for example, various security fixes and payment integration. More detailed requirements can be found in the requirements specification. The project has a timeframe of three months.

1.3 Limitations and interfaces

The project will focus on the development of the eCommerce platform based on PrestaShop, without modifications to the core PrestaShop functionalities. Maintaining the shop after a project is not one of the goals of the group. In this context, user training and introductory materials are also outside the scope of our project. The software interface will be developed in English only.

1.4 Rights and IPR

The rights of the various parties are defined in the project agreement.

1.5 terms and definitions

Scrum = A scrum is a project management framework commonly used in agile software development.

Sprint = Means a work cycle of a project. In this project, sprints are two weeks long.

Daily scrum = A daily meeting is a time-limited meeting of up to 15 minutes where the team sums up the work done and makes a plan for the day.

Gate = The intermediate stage of a project, where the results of the previous stage are evaluated before moving on to the next stage.

If the project plan lacks a detailed timeline and milestones, it will make it challenging to track progress and ensure timely delivery.

2. Project organization

2.1 Organization

Structure of Project Organization in MindMap form

uml diagram

2.2 Responsibilities and decision-making process

Project Group

Name Description Company/Community Task Responsibilities
Kuisma Kuivanen Team leader Mighty Ducks Leads the project team, ensures progress and maintains the big picture
Jere Koskimäki DEV Mighty Ducks Develops the eCommerce platform, implements features, and fixes bugs
Joona Hirvonen OPS Mighty Ducks Manages deployment, server infrastructure, and system performance
Riku Voutilainen SEC Mighty Ducks Conduct security assessments, identify vulnerabilities and ensure compliance with security policies.
Milla Sammallahti SEC Mighty Ducks Conduct security assessments, identify vulnerabilities and ensure compliance with security policies.
Tomi Isokytö TEST Mighty Ducks Plans and executes testing, identifies bugs, and ensures the platform meets quality standards

The project group consists of team members from Mighty Ducks who will be responsible for various tasks related to the development and testing of the project.

2.3. Project Steps and Financial Objectives

A precise schedule and budget are defined for the project to ensure that the work is carried out within the agreed timeframe and with the available resources. We monitor the schedule and budget so that we can spot any delays or budget overruns immediately. The Roadmap goes through the project steps in more detail.

2.4. Quality verification

  1. Standards: The project will follow widely accepted standards and best practices for software development, security, and user experience.

  2. Approval Procedures: A clear and structured approval process will be implemented to verify and authorize project deliverables. This will involve detailed evaluations and formal approvals from key stakeholders, including the project team and external consultants.

  3. Documentation: Detailed documentation will be created and kept up to date throughout the project to ensure all information is recorded and reflects the latest developments.

  4. Reviews: Regular reviews will be held to evaluate the project's progress and quality at key stages (in Gates). The feedback from these reviews will help identify areas for improvement and ensure that the project continues to meet quality standards.

  5. Risk Management: A risk management plan will be developed during the project and maintained throughout the project. The plan will identify potential risks and outline mitigation strategies. In our Risk management plan, we go through the details and example situations.

2.5. Communication and tracking of project progress

Communication is addressed in the Communication plan.

2.6. The end of the project

The project will be handed over to the customer for full use by 25.4.2025.

Delivery: The completed product will be handed over to the client in accordance with the project's specifications.

Filing: All documentation and records related to the project will be properly organized and stored for future use.

3. Project's temporal Gates

3.1 Partitioning and Phase

GANT using PlantUML

uml diagram

The team is ready for assignment: the Team Leader is selected, the team has chosen a name, and the project working environment (OPF+SITES) is up and running. The home page and status page have been updated, and the assignment is clear.

  • Gate 1 - Plan + offer

The team has introduced itself and defined roles, planned project management and the roadmap, and estimated costs with a feature-specific budget. Requirement specifications and the roadmap are set, an offer has been made to the customer, and key delivery aspects have been clarified, including the feature set and pricing.

  • Gate 2 - Implement + test

Overview of used resources, progress, challenges, and achievements.

  • Gate 3 - Demo

We ensure that the product includes essential functional features. We prepare and review the demo together, making sure to collect feedback. We keep our presentation simple, avoiding technical details, and focus on aligning our implementation with user needs.

  • Gate 4 - Delivery day

We will hold a final seminar to review what we have learned and the results.

3.2 Project preliminary cost estimate

Budget

4. Quality assurance

By following these guidelines, the project team can maintain strong quality assurance practices throughout the project lifecycle to ensure reliable and high-quality product delivery:

  1. Working Methods – Establish clear development processes, coding standards, and testing procedures. Document these practices and ensure the entire team follows them consistently.

  2. Tools and Platforms – GitLab and Open Project Framework serve as platforms for managing test cases, test plans, and results.

  3. Development and Testing Standards – Define coding conventions, testing methodologies, and documentation guidelines to maintain consistency and high-quality outputs throughout the project.

  4. Compliance with Requirements – Identify and integrate client and industry-specific standards into the quality assurance process, ensuring all requirements are met.

  5. Monitoring and Reporting – Set up a framework for tracking project progress and evaluating quality metrics. Regularly analyze performance.

  6. Comprehensive Documentation – Maintain detailed records of all project activities, decisions, and updates. Use GitLab and Open Project Framework as central repositories for structured and up-to-date test documentation.

4.1 Approval of intermediate and results

The chain of approval for intermediate results in the project is as follows:

Development Team: Responsible for producing intermediate results, such as software components or features.

Testing Team: Verifies the quality and functionality of the intermediate results using various testing methodologies, ensuring they meet the required standards and specifications.

Team Leader: The team leader oversees the progress of the project and evaluates the intermediate results. They review the work done by the development and testing teams and ensure it aligns with the project goals and requirements.

Security Team: Ensures that the software is secure by identifying and addressing potential vulnerabilities, applying best security practices, and verifying that the system complies with necessary security standards.

Scrum master / Team Coach: Scrum master review and approve the intermediate results to ensure they meet the expectations and align with the project objectives.

Mentor / Customer: Being the client, reviews and approves the intermediate results from their perspective. They ensure that the deliverables align with their requirements and expectations.

4.2 Manage changes

Performance reviews are held at each Sprint and changes are agreed upon at the beginning or mid-term of the sprints as necessary.

4.3 Documentation

The project is documented in this file. Its various steps are displayed in GitLab and in the progress section.

4.4 Risk management

Identified risk situations and their management are reviewed in the risk management section.

4.5 Reviewing Policy

The product inspection with the customer is organized in stages 1 and 2. The trial use of the production service is organized in stage 3, as is the approval testing with the customer.

4.6 Complementary plans for the project plan

4.7 Plans for review and updating

The project plan will be reviewed and updated at the end of each sprint.

4.8 Project Suspension Criteria

The Right Project Plan also includes the project's suspension criteria.However, these are not used in student projects because projects use a certain number of hours to make a result and the result will be released as it is at the end of the course.However, the project team makes a further development plan that a potential new project continues.

5. Communication and tracking of project progression (communication plan)

5.1 Communication Plan

During the project, Discord will be the main communication tool for the team. More detailed information can be found in the Communication Plan

6. The end of the project

6.1 Delivery of the end product, introduction

The final product of the project should be documented and introduced to the customer, including any necessary installation or commissioning services. If training is required for the customer, a training plan should be developed. Additionally, an installation plan and deployment plan can be included if needed.

6.2 Official termination of the project

According to the agreement, the project will end no later than 25 April, 2025, when the service has been handed over to the customer.

6.3 Termination

A final meeting with the client and the team will be held in stage 4 to hand over the service. A more specific date will be arranged when it is known when the service is ready to be delivered.

6.4 Project Final Report

The project's final report will be prepared during the last management team meeting. This report summarizes the project's objectives, outcomes, challenges, lessons learned, and recommendations for future projects. It serves as a valuable source of information and insights for stakeholders and contributes to organizational knowledge and improvement.