# Project plan


Document	Project Plan
Author:	Juho Eräjärvi
Version:	1.0
Date:	2.2.2024

1. Assignment

1.1 background and starting points

This project is a part of Future Factory IT course in Jyväskylä university of applied sciences. Our project team consists of six JAMK students and all have different roles in this project. Project scheduling is done in two week sprints and progress is kept track with Gitlab issue board.

The objective of the project is to develop an existing application called Tukko. Tukko is a traffic visualizer which WIMMALab team IoTitude has been developed for Combitech Oy. Tukko utilizes public traffic APIs, particularly Digitraffic. Tukko is already functional, but in this project we aim to add the features that the product owner wants. As a team, our job is to add new features to Tukko and finish the project on time.

The following sections of this project plan will give an accurate overview of the information for the whole project.

1.2 Goals and tasks

The main objective is to add new and improve existing features to the Tukko that will enhance features and improve the user experience and useability. We want to make the project a success by responding to the expectations of stakeholders. We were offered a large list of features, from which we select the ones we want to add to Tukko.

The project includes our team called GUI Guerillas, along with Reima Parviainen (Product Owner), Sini Karvonen from Combitech (Scrum Master), Jarmo Luostarinen from Combitech (Scrum Master), and Marko Rintamäki from JAMK (Coach).

Our team had to choose what features we wanted in the application. We considered the choices from a user perspective. The application must satisfy the user's eye, but it must also be technically functional.

Here is a list of planned features:

Improve dark mode colors
Search location by name
Change branding to team and JAMK branding
Export Data to csv
Export history
Enforce secure coding practises
Control access to the server
Regular updates to the feature stack
Manual Testing
Maintainable Documentation

The project includes different phases. Phases are:

Phase 0: Starting
Phase 1: Planning and design
Phase 2: Implementation and testing
Phase 3: Demo day
Phase 4: Delivery of solution

1.3 Limitations and interfaces

In this section, we will go through the limitations and interfaces.

Limitations

1. Technical limitations: The programme uses a wide range of different technologies, so many of them may be new to us. For example, Tukko is built in a certain programming language and software so this might be a slight limitation.

2. Time Constraints: The project has a time limit, so work and learning must be planned accordingly.

3. Communication Constraints: Lack of communication can lead to misunderstandings in software development.

Interfaces

1. API Communication: Tukko will interface with the Digitraffic API to retrieve real-time traffic data. A connection issues with the API can lead to problems in project. Team members have to understand how API works.

1.4 Rights and IPR

The rights and intellectual property rights related to the project are governed by the project agreement. Unless specifically addressed in a separate agreement, the rights associated with the project will be in accordance with the terms specified in the project plan.

1.5 terms and definitions

This section presents the definitions, terms, and abbreviations used in the project plan to ensure clear communication and avoid misunderstandings. It is important that all parties involved in the project understand these terms.

Strengths: Team members are motivated and ready to work to accomplish our goal. Some may be more skilled in certain areas, so when there is some problem, everyone helps each other. Also being supported by coaches and mentors.

Weaknesses: The team consists only of students, so there is not much experience yet.

Opportunities: External support is good and varied, so help should be available in problem situations. Tukko is also already functional, so the features will make it even more versatile and functional.

Threats: Incorrect team communication can lead to problems. However, with good communication and cooperation, these problems should not appear.

2. Project organization

2.1 Organization

Structure of Project Organization in MindMap form

2.2 Responsibilities and decision-making process

Project Group

Name	Responsibility	Company/Community
Julius Siukola	Team leading	Jamk
Juho Eräjärvi	Operations	Jamk
Arttu Hiekkanen	Developer	Jamk
Vili Rautiainen	Security	Jamk
Tomi Jokinen	Testing	Jamk
Aleksandr Baranov	Generalist	Jamk

Board Members

Name	Responsibility	Company/Community
Reima Parviainen	Product owner	IoTitude
Marko Rintamäki	Project coach	Jamk
Sini Karvonen	Scrum Master	Combitech Oy
Jarmo Luostarinen	Scrum Master	Combitech Oy

Support Group

Team members has multiple support channels to get guidance. We have multiple discord channels, where you can get help from coaches and mentors if you need it.

2.3.Project Steps and Financial Objectives

The project advances via a sequence of clearly outlined stages, structured within Sprints. Each Sprint focuses on particular task scenarios, indicating significant checkpoints and efficiently distributing resources and timeframes. Financial goals for the project are projected during Sprint planning, ensuring alignment with resource demands and project necessities.

2.4.Quality verification

Within this segment, we delve into the realm of quality assurance within the project, a pivotal component for its success. This encompasses various critical areas aimed at guaranteeing the quality of project deliverables. To bolster this, we've devised a comprehensive risk management plan to identify and evaluate potential project risks. Additionally, our communication plan delineates the channels and methods through which communication transpires within the team and amongst diverse stakeholders, ensuring transparency and efficacy throughout the project's evolution.

2.5.Communication and tracking of project progress

Regarding communication and monitoring project advancement:

Communication: The main communication platforms for team members and associates will be Discord and Teams.
Documentation: GitLab's OPF repository will serve as the hub for reporting, documentation, and version control, residing in its dedicated repository.
Workspaces: Specific workspaces on Discord and Teams will be established to accommodate different project segments.
Information Storage: Vital project particulars will be disseminated and stored within the GitLab repository.

2.6.The end of the project

At the end of the project, the finished product is delivered to the customer. Any project document will be stored for future use. A final report on the project will also be produced.

3. Project's temporal Gates

3.1 Partitioning and Phase

The project schedule is presented with Gantt-chart.

GANT using PlantUML

The next step is each step, the time resources and results they require in briefly.The steps and their tasks are described in more detail in the phase plans.The ongoing phase of the current stage should be known precisely who is doing and how much work to perform this step.Later phases work estimates can be made at an early stage at a rough level, which is then refined to a detailed level of the project.This happens at the end of each phase to be designed in more detail the next step.

Note: The following are the startup and ending steps.Of all the phases of the project, their duration and workloads, the so-called Gantt chart (attached), which also shows the interdependencies between the steps and the main easses (e.g., the management team meeting date of the management team).

Milestone - Gate 0

Setup Teams and OPF
Redesigned our website
Generated team logo
Assigned team roles

Milestone - Gate 1

Familiarize about Tukko
Got the Assignment from product owner.
Setting up development and production environment.
At the end of gate 1, the team will have offer ready to customer, finished cost estimation, project plan and requirement specification.

Milestone - Gate 2

Design and implementation of the service. Testing of the planned features.
Clear and varied documentation of progress.
Project status check.

Milestone - Gate 3

Workable demo should be ready.

Milestone - Gate 4

Acceptance testing and fixing all the possible problems.
Product has been finished and has been delivered to the client.
final report of the project.

3.2 Project preliminary cost estimate

Presenting a cost estimate with a table:

4. Quality assurance

To guarantee the quality of the project, we set high criteria for the work and the tools.

Communication: Communication must work in this project. You can read about it in Communication plan
Documentation: The project team maintains documentation on the project and uses the Open Project Framework for document management.
Risk management: Risks are being monitored in the Risk management plan
Testing: By testing, we guarantee that the quality is certainly excellent and we can be sure that the product will work for the customer.

4.1 Approval of intermediate and results

Feature creation is shared between team members. The tester tests the functionality of the features and possibly informs of the improvements. The whole team goes through the project with the team leader to see if the product is ready to be handed over to the product owner.

4.2 Manage changes

The team needs to identify and then communicate about any changes.

4.3 Documentation

Documents related to this project will be stored in Open project framework. All team members have access to it and be able to edit documents. Documents show the author but changes have also been made with team.

4.4 Risk management

Information on risk management can be found in:

Risk management plan

4.5 Reviewing Policy

The "Reviewing Policy" section outlines the procedures and guidelines the GUI Guerillas team follows to ensure the quality and integrity of their project work. It emphasizes the importance of regular reviews and assessments throughout the project's lifecycle, focusing on code quality, project documentation, and overall progress. This policy ensures that all project outputs meet the predefined standards and requirements, facilitating continuous improvement and adherence to best practices.

4.6 Complementary plans for the project plan

4.7 Plans for review and updating

At the beginning of each sprint we will go through plans. This process ensures the project stays on track.

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

5.1 Communication Plan

The communication plan details the methods and frequency of interactions among the project team, stakeholders, and external entities. It outlines the platforms and tools to be used for communication, ensuring that all parties remain informed and engaged throughout the project lifecycle. For more detailed information: Communication plan

6. The end of the project

6.1 Delivery of the end product, introduction

In 22.4.2024 the final result will be documented and then introduced to the customer. Including any necessary installation service.

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

Project related documents will be stored by our team. We also hand over the documents to the customer, who can decide how they are stored.

6.3 Official termination of the project

The project ends on 22.4.2024 when the project contract expires.

6.4 Termination

Final project meeting will be held 22.04.2024 in a Teams meeting.

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. It summarizes the project's outcomes, achievements, and lessons learned. It might include details on project performance, objectives met, challenges faced, and recommendations for future projects.