Project plan
| Document | Project Plan |
| Author: | Kaizen |
| Version: | 1.0 |
| Date: | 23.2.2024 |
1. Assignment
1.1 background and starting points
The aim of this project is to create and add new wanted features for Tukko's traffic visualizer. Our team is focusing on Tukko's infrastructure & user interface. This will make Tukko more visually pleasing and easier to use. These additions are, for example: Location search, changes to coloring & a way to add feedback. We will also add a secure https connection and a way to sign in and out from Tukko.
Our objective in implementing these features is to enhance Tukko, thereby improving its traffic visualizer functionality as a robust traffic analyzer and tool.
In the upcoming sections of this project plan, we'll delve into a comprehensive outline of our project's direction, goals, schedule, and distribution of resources.
1.2 Goals and tasks
This document offers a detailed breakdown of the goals, tasks, phases, resources, and organizational setup for Tukko. Each step and stage will be individually described, providing a thorough understanding of the project's scope and developmental journey.
The primary aims of this project are to augment the Tukko service with additional features, enhancing its user-friendliness and ease of operation. Furthermore, we strive to bolster the security of the service by implementing secure coding practices.
1.3 Limitations and interfaces
In this section, we'll outline the constraints and boundaries that the project will encounter throughout its development phase, along with the interfaces that will be utilized.
Limitations:
-
Time Constraints - This project has a pre fabricated timeframe. As a team, we'll follow this as best as we can, but every single team member has other tasks to do also.
-
Technological Constraints - The project is bound by technological limitations. These include programming languages, frameworks employed for development and compatibility of web-based technologies.
-
Resource Limitations - A lack of resources may slow down or, in the worst-case scenario, halt work on the project.
Tukko: Traffic Visualizer will be the main interface we'll be using during this project.
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 to ensure clear commication and acoid misunderstantings. It's crucial for Combitech Oy, Reima Parviainen, and Kaizen to share a mutual comprehension of these terms.
1.6 Challenges related to the project
-
Streghts - Team Kaizen has great motivation for learning and making this project. Our team's collaboration functions exceptionally well and dynamically.
-
Weaknesses - If the project does not stay on schedule, it will be hard to implement all of the presented features that the team planned to add. Also if the documentation of the project is scarce, it will be hard to keep up whats done and what isn't. When the time comes to make the final report, it will not be easy if there is no documentation of this project.
-
Threats - If we as a gruop are not prepared if something unexpeted happens, in the worst case scenario, our whole progress of this project can make a full stop.
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 |
|---|---|---|
| Marko Rintamäki | Coach/Scrum Master | JAMK |
| Ville Ojanperä | Team Leader | Kaizen |
| Leevi Markkanen | General | Kaizen |
| Juuso Laurikainen | Developer | Kaizen |
| Juuso Leppänen | Tester | Kaizen |
| Joonas Saukonoja | Security | Kaizen |
| Sonja Wesa | Operations | Kaizen |
The project team performs the tasks set by the Management Team for the project within the scope of the available resources. During the project, the roles of the master and the secretary of the group circulate within the group so that each member of the group works once in either role.
Board Members
The board members consists of Reima Parviainen and other members from Combitech Oy.
| Name | Responsibility | Company/Community |
|---|---|---|
| Board member | Project management | Reima Parviainen |
| Board member | adding the presented features | Kaizen |
| Board member | Project management | Combitech Oy |
| Board member | Projcet management | Combitech Oy |
Support Group
The support group members consists of Reima Parviainen and other members from Combitech Oy. These will be our mentors for the duration of this course.
| Name | Responsibility | Company/Community |
|---|---|---|
| Karri Päivärinta | Support SEC | JAMK |
| Marika Matalamäki | Support OPS | JAMK |
| Alena Galysheva | Support TEST | JAMK |
| Justus Hänninen | SUpport DEV | JAMK |
2.3.Project Steps and Financial Objectives
Project will follow predefined cost estimation and schedule.
2.4.Quality verification
We will monitor our progress throughout this project making cycle. We will ensure that we can stay on schedule as best as we can. Our team uses secure coding practices to make Tukko's Traffic visualzer more secure to use. Team will write documents of their progress as often as possible, so more recent made progress will be documented clearly. Cooperation with other students and mentors is vital so we can all learn from this given opportunity.
2.5.Communication and tracking of project progress
Daily Scrum meeting are held during Monday and Friday mornings on Teams. Other meetings outside of the official Teams channel will be held on Discord.
Documentation will be updated in this GitLab Repository.
Communicatin between team members and mentors will be held in Discord. Otherwise we will use email's as a way to communicate.
2.6.The end of the project
- The product will be given to the client at the end of the course.
- The team will write a final report regarding the project with all project related documents arhhived in the GitLab repository.
3. Project's temporal Gates
3.1 Partitioning and Phase
Milestone - Gate 0
- Getting to know every team member
- Setting up the OPF
Milestone - Gate 1
- Offer should be ready for the customer.
- Project plan, Communication plan, Risk management plan & Requirement Specification plans should be ready.
Milestone - Gate 2
- During sprints 3 & 4 the team will be desining, implementing and testing chosen features.
- Documentation of the projcet progress will continue.
Milestone - Gate 3
- We are making sure that features FEA102 & FEA516 are ready at the end of sprint 6.
- If some features could not be made during sprint 4, team will also finish those features during sprint 5 & 6.
- Workable demo should be ready. Team will do testing to the project to make sure it works flawlessly.
Milestone - Gate 4
- The product is ready to be released.
3.2 Project preliminary cost estimate
Presenting a cost estimate with a table:
Total cost estimation with VAT included:
4. Quality assurance
4.1 Approval of intermediate and results
Features will be made with atleast two team member making them. Testers will test test the product and inform of any needed improvements. Once the whole team is approving that the projcet is done and ready, the projcet needs to be approved by the project owner.
4.2 Manage changes
By identifying and communicating can we as a team handle changes regarding this project.
4.3 Documentation
Documents relating to the project will be stored in the GitLab repository in the Open Project Framework. All team members have access to it.
4.4 Risk management
Risk management details listed below.
4.5 Reviewing Policy
- Project team takes features from from the list given by the stakeholders
- Team members will present their planned ideas using mockups form.
- If given feedback from the stakeholders, team will plan newly requested changes to the project.
4.6 Complementary plans for the project plan
4.7 Plans for review and updating
As a team we will go through our current progress and make needed tweaks and adjustments if needed. We will also talk about everyones general mood and progress.
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
Our team's communication plan can be found here: Communication Plan
6. The end of the project
6.1 Delivery of the end product, introduction
Final result and it's documents will be presented to the customer. We will present a PowerPoint presentation if needed.
6.2 Taxation of the project produced by the project, archiving and retention period
Project related documents, if needed, will be handed to Combitech. None of the team members are committed to retaind any files regarding the project.
6.3 Official termination of the project
The project ends in 22.04.2024, when the project contract expires and project is released.
6.4 Termination
Final project meeting will be held 22.04.2024 in a Teams meeting.
- In Finland project team can possibly arrange an Sauna-event
6.5 Project Final Report
The final report of the project will be drawn up by the last management team meeting.