Project plan
| Document | Project Plan |
| Author: | Ilmo Pitkänen |
| Version: | 1.0 |
| Date: | 23.2.2024 |
1. Assignment
1.1 background and starting points
The goal of the project is to develop further the already existing application Tukko. Tukko is a traffic visualizer which has been developed for Combitech Oy. The project team's plan is to select and add new features given by the product owner.
Currently Tukko is a functional service, but the product owner sees that it needs more features, some of which will be implemented by this team.
1.2 Goals and tasks
This document aims to provide a thorough description of the projects' goals, tasks, resources and phases. The main goal of this project is to further enhance Tukko.
The final result will be adding several new features to Tukko, which will improve the user experience and useability of Tukko. intermediate results will include a few smaller features.
Groups involved with the project will include the Future 16 project team, Combitech Oy and the Jyväskylä University of Applied Sciences.
The project will include the following phases.
- Planning
- Designing
- Implementation
- Testing
- Release
1.3 Limitations and interfaces
The project will include a few limitations which are listed below.
Tukko technical limitations: Tukko is based on certain programming languages, software and hardware on which this project will build on. Naturally this will limit some options that can be used to improve the application.
Team knowledge: The Future 16 team consists of students, which means that the project team doesn't have a large knowledge base to start on. This leaves some features outside of the capabilities of the team.
Time: The project has a set time limit that affects the phases of the project. This also affects the time that can be used to study needed programming languages or software.
1.4 Rights and IPR
The rights related to the project are governed by the project agreement. Any separate agreements will be added to this project plan.
1.5 terms and definitions
This section presents the definitions, terms and abbreviations in the project plan. It is important that all parties understand these terms.
1.6 Challenges related to the project
Strenghts: The project team has all its six members present and it is being supported by the peer coaches and mentors.
Weaknesses: The team consists of students, which means that there are no experienced members in it.
Opportunities: Tukko in itself is an already functional software and any new added features will improve customer interest in it.
Threats: Inexperience could lead to the team encountering debilitating challenges that may severely affect to progress of the project.
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 |
|---|---|---|
| Ilmo Pitkänen | Team leading | JAMK |
| Pyry Anttila | Security | JAMK |
| Stefano Confalone | Development | JAMK |
| Samir Benjenna | Operations | JAMK |
| Juhani Jussila | Testing | JAMK |
The project team performs the tasks set by the Management Team for the project within the scope of the available resources.
Board Members
| Name | Responsibility | Company/Community |
|---|---|---|
| Reima Parviainen | Product owner | Combitech Oy |
| Marko Rintamäki | Project Guidance | JAMK |
2.3.Project Steps and Financial Objectives
The project will follow the predefined schedule and cost estimation.
2.4.Quality verification
The project will follow the agile development method. The project team has also created a communication- and risk management plan and also has documented the wanted features.
2.5.Communication and tracking of project progress
Project communication can be found in the communication plan
Gitlab will be used for storage and file management.
OPF framework will be used for documentation such as this.
2.6.The end of the project
At the end of the project the results will be delivered to the client. The team will also write a final report on the project. Project results will also be showcased in the end seminar.
3. Project's temporal Gates
3.1 Partitioning and Phase
GANT using PlantUML
-
Setup Teams and OPF
-
Team roles selected
-
Offer ready for customer
-
Project plan and Requirement Specification Ready.
- Planned features initially implemented.
- Have a demoable sample ready.
- Product has been finished and has been given to the client.
3.2 Project preliminary cost estimate
Presenting a cost estimate with a table:
4. Quality assurance
For quality assurance the project follows several practices.
-
Documentation: The project team maintains documentation on the project and uses the Open Project Framework for document management.
-
Risk Management: Currently risks are being monitored in the Risk Management Plan
-
Communication: The team has listed its communications in the Communication Plan
-
Version Management: Gitlab is used for the handling of version management. Gitlab is also used for handling some of the schedule planning.
-
Testing: The developed solutions will be tested by team members so that planned features will maintain desirable quality.
4.1 Approval of intermediate and results
The following will be used for result approval
-
Team approval: Team members will superficially review if the produced result is up to standard.
-
Test approval: Testers will test the results through several strategies to see if they are functional and working properly.
-
Team lead approval: Team lead will check that the result is inline with the project's documentation and definitions.
4.2 Manage changes
Change management is handled by identifying the changes, communicating about them to the team and implementing.
4.3 Documentation
Documents of the project are stored in Gitlab in the Open Project Framework.
4.4 Risk management
4.5 Complementary plans for the project plan
This paragraph mentions what complementary plans are available or will be made within the project
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 Future 16 project. With clear and consistent communication, it is ensured the passage of information and influence the implementation of the project quality objectives.
6. The end of the project
6.1 Delivery of the end product, introduction
The final result will be documented and then introduced to the customer. If needed the product will be installed for the customer.
6.2 Official termination of the project
The project ends on 26.4.2024 when the project contract expires. Ideally this will be the date when the project results will be handed to the customer.
6.3 Termination
For the termination of the project a final meeting can be held.
6.4 Project Final Report
The final report of the project will be drawn up by the last management team meeting. This document will detail the challenges and outcomes of the project and what the team learned while making it.