Current Status
Gitlab Board and issues
Status of sprint 06 Date 19.04.2024
What has been achieved
- We have shown our Demo
- Colors have been altered
- Testing for visual changes are carried
Do we have a problems/challenges?
- Time constraints, HTTPS in a bit complicated, may need to create whole file structure again
Next steps
- Finalizing our product
- Project end report & individual learning diaries
- Adding some features if possible
- Making changes to product based on feedback
Status of sprint 05 Date 05.04.2024
What has been achieved
- Pipeline works both back and front
- FEA507 is tested and confirmed working as planned
- Testing for visual changes are carried
Do we have a problems/challenges?
- Time constraints are still the main challenge
Next steps
- Implementation and testing continues
- Started working on demo day page
- Pipeline needs more work (different stages etc.)
Status of sprint 04 Date 22.03.2024
What has been achieved
- HTTPS is configured on the server side almost completly, still runs in the wrong port.
- Git <-> server automatisation is on the way, front works as planned but backend has still some difficulties.
- Logos have been changed to repesent Kaizen and JAMK instead of previous creators.
- Adjustments for dark mode were implemented
Do we have a problems/challenges?
- Time constraints have been the main challenge
Next steps
- Implementation continues
Status of sprint 03 Date 08.03.2024
What has been achieved
- Updated RoadMap
- Updated Master Test Plan
- Team members have done familiarization regarding selected features.
Do we have a problems/challenges?
- This sprint was a shorter one because of winter break.
- There has been a lot of conversation how to start implementation and what is the smartest way to handle different code versions.
Next steps
- Implementation
Status of sprint 02 Date 23.02.2024
What has been achieved
- Documents are in order to be presented.
- Members have studied and read through the materials needed to work on the project.
- Planning for future tasks has been done.
Do we have a problems/challenges?
- Workload has increased, but the team's spririts are high. We are eager to get to work.
Next steps
- We are preparing to start working on the project. Team is taking a small one week break before starting.
Status of sprint 01 Date 09.02.2024
What has been achieved
- Tukko has successfully deployed to the CSC server using Docker.
- The team logo is finished, and work on the team site building continues.
- There has been a discussion about the features that the team is planning to incorporate.
- Members have studied appropriate materials about the project.
Do we have a problems/challenges?
- Still figuring out how to share workload (especially documentation) evenly among the team; some tasks are easier to hand out than others.
- Deploying Tukko was surprisingly difficult and took way more time than actually needed.
Next steps - For the next sprint, the main focus is completing Project, Communication, and Risk Management Plans, Requirement Specification, Offer, Feature RoadMap, and Team Pages.
Status of sprint 00 Date 26.01.2024
What has been achieved
- Team has achieved cohesion and member roles have been selected.
- cPouta work environment has been set up for team use.
- Pages setup work has been started.
- Members have studied appropriate materials about the project.
Do we have a problems/challenges?
- Workload seems to be minimal at the moment, members are eager to continue working.
Next steps
- Main focus for next sprint is the preparation for the customer interview.