Project plan


Document	Project Plan
Author:	Erika Korhonen
Version:	1.0
Date:	4.2.2025

1. Assignment

1.1 background and starting points

The task assigned to Team Blue Frog Software is to develop and deploy a functional webstore with robust security features and minimal bugs. The platform will be hosted in the cloud, and the designated storefront framework for this assignment is PrestaShop.

1.2 Goals and tasks

This document outlines the objectives, structure, resources, phases, and tasks required to successfully complete the PrestaShop webstore project. Each phase is detailed separately to ensure a clear progression toward the final goal.

The main objective of this project is to design, develop, and deploy a secure and fully functional webstore using PrestaShop on CSC's cPouta cloud platform.

Build and configure a webstore using PrestaShop.
Develop features that enhance the shopping experience for both vendors and customers.
Identify and address existing bugs and security vulnerabilities while implementing both visible and backend enhancements.
Ensure a secure and reliable webstore environment for both sellers and buyers.
Enable vendors to efficiently manage inventory and customers to securely track their purchases.

1.3 Limitations and interfaces

Cloud Service Availability
- Since the webstore will be hosted on CSC's cPouta cloud service, any service disruptions on their end are beyond our control. To mitigate potential downtime, implementing a backup service on an alternative server could be considered for redundancy.
Technological Constraints
- As the assignment mandates the use of PrestaShop, the project must work within its inherent limitations, which are currently unknown.
Resource Limitations
- Constraints related to hardware, software, and available team members will impact the project's overall scope and execution.
Time Constraints
- With a fixed project timeline and overlapping coursework, effective prioritization and scaling of features will be necessary. The team's experience and technical proficiency will influence the scope of deliverables.

1.4 Rights and IPR

"The rights of the various parties are defined in the project agreement."Unless a separate agreement has been told about the rights of the job, they must express, for example, in this project plan.

1.5 terms and definitions

This section presents the definitions, terms and abbreviations in the project plan.For example, in different projects, there may be "inspection" and "reviewing" to be different meaning and this can cause misunderstandings.Sometimes it may be in place to agree on different names to the group's inspections (own internal, customer, in the course of the course).Abbreviations should be opened to the original language and add a brief description in Finnish.For example, Case = Computer Aided Software Engineering, Computer Assisted System Work.

Consider the project's Gates and will be drawn up in support of a SWOT description that looks at the entire project and its operating environment.

2. Project organization

2.1 Organization

Who belongs to the project organization?Does the project group / team have other operators? Project Group Instruments and Client Representatives.The organizational chart is presented in the appendix or in the description below.

Structure of Project Organization in MindMap form

2.2 Responsibilities and decision-making process

This includes the responsibilities of all project organizations (eg management team, project manager, secretary, group,> supervisors) and the decision-making process (eg, the project manager prepares and presents the management team to decide ...)

Project Group

Project team details

Name	Responsibility	Company/Community
Erika	Team Lead	Team Blue Frog Software
Niko	Security	Team Blue Frog Software
Daniel	Developer	Team Blue Frog Software
Kushagra	Developer	Team Blue Frog Software
Nora	Testing	Team Blue Frog Software

Board Members

Name	Responsibility	Company/Community
Marko Rintamäki	Scrum Master	Jamk
Hanh Nguyen	Product Owner	Task Force
Erika	Team Lead	Team Blue Frog Software

Support Group

The task of the support group is to provide a project group for a content guidance to complete the task.The passage should> introduce the project's other stakeholders (customer, external consultants, etc.).The> persons involved in the customer must mention at least the name, contacts, work description and the role in the project.

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

Delivery, Commissioning, Maintenance, Taxation of Project Materials, Filing, Final Report, Project Official Decision

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

3.2 Project preliminary cost estimate

Presenting a cost estimate with a table:

4. Quality assurance

Working methods, instruments, instructions and standards applicable in the project This section lists all the methods, tools and standards to be used in version numbers. Often the commissioner has a method of complying with the project team. The client can also determine the appellants to be followed. Otherwise, the project team will tailor the model approved by the IT Institute's template for themselves and approved by the client. The course sets certain requirements for project monitoring tools and reporting that should be taken into account. However, the course does not forced a certain way to use tools, so there is a need to make a plan for this. The basics of information and version management of the project must be clarified so that all project stakeholders know the location of the latest versions of the documents. From the project plan and all other key documents of the project will become several versions that need to be added to the history history to monitor the development of the project afterwards. If a single device or software rises to the critical position of the project's implementation, it is good to designate this person who knows the person who knows. From the device or software group best. Here's a list of things that you should design and document:##

4.1 Approval of intermediate and results

This will record the approval procedure, which is agreed on the project.

4.2 Manage changes

Describe a change management procedure for project practices or changes related to the project's results.

4.3 Documentation

Bookmark where documents are saved / archived how they are shared and who is responsible for different documents.

4.4 Risk management

Listing the risks, evaluate their severity and probability and to think about thinking about how the most serious / most likely risks could be prevented in advance.It would also be good to be a plan for how to work if the risk is implemented. Books the risks to the project below and maintain them as needed.For each risk, a unique identifier is given, for example, RIS007, as this will facilitate their treatment in different situations.

Risk management table

4.5 Reviewing Policy

Lishes and provisionally scheduled on the project's performance review on the basis of the drawn up implementation plan.The list of reviews is presented, the preliminary time, the issues, participants and practices for the delivery of the reviewing material (what, when, how).

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).

4.7 Plans for review and updating

The project plan will be reacted to deviations and environmental changes, so it is updated during the project.To this point, the dates are recorded in which the date of updating the plan at least must be checked.

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

The purpose of the communication plan is to define the communication methods and channels used in the X project. With clear and consistent communication, it is ensured> the passage of information and influence the implementation of the project quality objectives. The plan can be drawn up as part of the project plan or can be referred to as one of the [subpages] (../10 project management / communication plan.md) List the workspaces and communication tools agreed on the project, a return policy and communication, reporting, and information.

6. The end of the project

6.1 Delivery of the end product, introduction

The final product of the project should also be documented at a sensible level. As part of the final product may be the introduction to the customer and possibly installation or commissioning service. If the role of education for the project is considerable (for example, software users have not been involved in the project and do not know how the system works) will include a plan to attach a plan to the customer's training. In addition, if necessary, the project plan also includes an installation plan and a deployment plan.

6.2 Taxation of the project produced by the project, archiving and retention period

"The disadvantaged part of the document group documentation is stored in the X system" With the assistant, you may be able to agree on which documents can be left to the next projects. Typically, different plans and final report are in the most appropriate part of such documents.

6.3 Official termination of the project

It is important to define when or how to end the project.The project's decision may be a certain date, a particular product ready-made, a certain amount of work hours, a certain consumed sum of money when the customer takes the product, the warranty period has expired or when the customer accepts the product.

"The project ends in p.k.vvvv, when the project contract expires."

6.4 Termination

Generally, the projects will be decided on a joint closure seminar.Participants and time are recorded.

In Finland project team can arrange Sauna-event :)

6.5 Project Final Report

The final report of the project will be drawn up by the last management team meeting.