Project plan
| Document | Project Plan |
| Author: | Team Issues |
| Version: | 1.1 |
| Date: | 20.02.2023 |
1. Assignment
Our task is to design and develop a website as a tool to gather information on the desired skills of various companies for job seekers of the future.
1.1 background and starting points
This project is a part of the Future Factory IT implementation (ZZPP0920-3038) and is being worked on by Team Issues.
1.2 Goals and tasks
The goal of our project is to design and develop a functional tool that meets the requirements of our customer, Lippa-program. The tool will have a set of features that are needed for the users. For more information on the requirements and features of the tool, visit Requirement Specification.
1.3 Limitations and interfaces
The software is implemented only for desktop use and there is no support for mobile devices.
1.4 Rights and IPR
The rights of the various parties are defined in the project contract.
1.5 terms and definitions
-
Stage = A sequential phase that a project goes through from initiation to completion, including: initiation, planning, execution, monitoring & control, and closing.
-
Sprint = A period of time where a specific set of tasks are completed. In our case one sprint is two weeks.
1.6 Challenges related to the project
As students, many of us may have little to no experience with the kind of project we're undertaking, which means there could be a plethora of hidden challenges that we are yet to encounter.
Given that we only work on the project on Mondays and Tuesdays from 9-16, we have limited time to implement new features and address any challenges that may arise.
2. Project organization
2.1 Organization
2.2 Responsibilities and decision-making process
Project Group
| Name | Responsibility | Company/Community |
|---|---|---|
| Marko Rintamäki | Product owner | JAMK |
| Arttu Hautala | Team leader | Issues |
| Taavi Kalaluka | Backend developer | Issues |
| Jenna Penttilä | DevOps | Issues |
| Lauri Kosonen | Frontend developer/Test Manager | Issues |
| Roope Lappalainen | Frontend developer | Issues |
| Juha Wirlander | SecOps | Issues |
Board Members
| Name | Responsibility | Company/Community |
|---|---|---|
| Karo Saharinen | Vision owner | Lippa-program/JAMK |
| Essi Silvennoinen | Vision owner | Lippa-program/JAMK |
| Hanna Frilander | Vision owner | Lippa-program/JAMK |
Support Group
| Name | Responsibility | Company/Community |
|---|---|---|
| Juho Pekki | Support OPS | JAMK |
| Heli Ciszek | Support SEC | JAMK |
| Veeti Hakala | Support DEV | JAMK |
| Marko Rintamäki | Support TEST/SUS/General | JAMK |
2.3.Project Steps and Financial Objectives
Project's steps, schedule and preliminary cost estimate can be found on the section 3 on this page. Also you can check our progress from roadmap.
2.4.Quality verification
Product owner Marko Rintamäki makes the final approve of the product. See also quality assurance from requirement specification.
2.5.Communication and tracking of project progress
Communication specificiation is defined in communication plan. Our project's progress can be tracked from milestones or roadmap.
2.6.The end of the project
Delivery date is 18.4.2023.
3. Project's temporal Gates
3.1 Partitioning and Phase
3.2 Project preliminary cost estimate
Presenting a cost estimate with a table:
4. Quality assurance
See requirements specification document
4.1 Approval of intermediate and results
Project needs to be approved by Marko Rintamäki the product owner.
4.2 Manage changes
After project is done it is owned by lippa hanke and they can develope it further if they want.
4.3 Documentation
Documents are stored in GitLab.
4.4 Risk management
4.5 Reviewing Policy
Milestone reviews:
E1 Offer 31.02.2023
E2 Status check 14.03.2023
E3 Demo day 04.04.2023
E4 Realese 18.04.2023
4.6 Complementary plans for the project plan
- Project Agreement
- Requirement Specification
- Release Plan
- Master Test Plan
- Communication Plan
- Risk management plan
4.7 Plans for review and updating
Regular project status reviews
Milestone reviews
Risk management reviews
4.8 Project Suspension Criteria
Lack of resources: If the project lacks the necessary resources, such as funding, personnel, or equipment, it may be suspended until the resources become available.
Stakeholder feedback: If stakeholders are not satisfied with the project's progress or outcomes, or if the project is not meeting their expectations, the project may be suspended to address their concerns.
Change in priorities: If there is a change in the organization's priorities or strategic direction, the project may be suspended to realign it with the new priorities.
External factors: If external factors, such as market conditions, legal or regulatory changes, or natural disasters, affect the project's feasibility or success, it may be suspended until the situation improves.
Health and safety concerns: If there are health and safety concerns related to the project or its execution, the project may be suspended until the concerns are addressed.
5. Communication plan
6. The end of the project
6.1 Delivery of the end product, introduction
The project is ends 18.04.2023 when the application is realesed and Lippa hanke reviews it and decides if they want to use it and develope it into an actual application in the future.
6.2 Taxation of the project produced by the project, archiving and retention period
It is recommended that project-related documents and information be retained for a minimum of three to seven years.
6.3 Official termination of the project
The project ends in 18.04.2023 when it is released.
6.4 Termination
Final project meeting 18.04.2023 in Teams channel Issues.
6.5 Project Final Report
The final report of the project will be drawn up by the last management team meeting.