Project Plan
Version <1.2>
| Date | Version | Description | Author |
|---|---|---|---|
| 15/01/2026 | 1.0 | Simple placeholders changed | Adrian |
| 27/01/2026 | 1.1 | Most of document are done. Only needs attachments | Adrian |
| 05/02/2026 | 1.2 | Final Draft | Cathrine, Roar and Robin |
1.Goals and terms.
1.1. Introduction.
1.2 Problem Description and Expected Outcomes.
1.3 Terms.
-
Organization.
-
Follow-up and quality assurance.
3.1. Quality Assurance.
3.2. Reporting.
- Attachments – Process documentation.
4.1. Collaboration Agreement.
4.2. Project Timeline and Activity Structure.
4.3. Meeting Summon.
4.4 Meeting Minutes.
4.5 Timesheets w/ Status Report.
In the light of recent events, destruction and misery are evident throughout the world. Wars conflicts and disasters run amok and common folk quenched beneath their feet. For the people to get the aid that they deserve, organizations and project work to keep them safe and alive. But most organizations lack funding, that is where we come in.
In collaboration with Innsamlingskontrollen (IK), we (Team 6) have been tasked by a computer consulting company to plan and develop a software application. Said application will allow consumers to track and donate money to multiple organizations/projects/charities across the globe. Organizations and projects shown to users are legitimate and trustworthy organizations listed on the non-profit foundation Innsamlingskontrollen. To further improve the user experience, we have been also tasked to develop unique features and functionalities. These features will be developed through user feedback and user testing. The name of this project is Help Me Help (HmH) Application.
Technical requirements
- The application should be a Java desktop application.
- Use of Scene builders is allowed.
-
Application data should be persisted into a relational database.
-
Any usage of AI tools should be justified and documented both in source code (with comments) and in report. Specifically, it must be described which AI tools are used, what they are used for, and why.
-
All students should you NTNU´s GitHub instance (https://git.ntnu.no) for source code and project management.
Other Prerequisites:
- The project should be carried out in 3 iterations/sprints:
- First iteration: Vision document, Collaboration Agreement, Project manual and an early prototype using wireframes should be done. As well as User testing of the prototype, use-case diagram and domain model.
- Second Iteration: A relatively error-free MVP (Minimum Viable Product) Java should be done. As well as user testing, first version of requirements documentation and WIKI
- Final Iteration: Finalizing the application and all other documentation and attachments.
-
Each team member is expected to contribute minimum 80 hours to the project.
-
In the milestone plan, you will find deadlines for compulsory deliveries in different iterations.
-
To ensure the quality of the application the team must continuously undertake unit testing.
-
To ensure high usability and good user experience the application must relate to Don Norman’s principles of interaction design
-
To evaluate the user, experience the team must carry out usability tests after the first and second iteration (wireframe and MVP)
-
Universal Design – the application must be designed according to WCAG 2 principle 1 – Perceivable
-
Each team should incorporate sustainability practices into system development
| Members | Role(s) | Details |
|---|---|---|
| Roar Andre FagerKind | Software Quality Responsible | Ensure product quality by following standards. |
| Cathrine Kristiansen | Archive and Document Responsible | Overall responsible for all relevant documents. |
| Adrian Paul Limpiado Balunen | Scrum Leader | Ensure a clean working enviroment and efficient execution of backlog items and tasks. |
| ROBIN STRAND PRESTMO | Product Owner | Ensure clear communication of product goals and ordering backlog items. |
| MEENAKSHI JAYACHANDRAN | Software Quality Responsible | Ensure product quality by following standards. |
In the scrum-board we have a dedicated section for review and feedback. All issues and tasks will go systematically through this section during a scrum and will always be a subject to review. Depending on the team, the issue will go back to the progress column or will be considered done.
In addition, we have a dedicated role for quality assurance. Following the collaboration agreement, the role of Software Quality Responsible ensures product quality by following be given standard. That role is in Roar Andre Fagerkind.
These projects assistants require a weekly meeting that acts as a status report, and one established meeting at the end of each referred process iteration. Each meeting will require an official meeting summons and documented meeting minutes.
In accordance with the collaboration agreement the team will arrange a meeting among the team members every other week. These meetings will resemble weekly scrum meetings and will focus on status reports from each member and bring up important topics if necessary.
This team’s Collaboration Agreement can be found on our team GitHub. Directly accessible on the GitHub Wiki page and downloadable in the GitHub repository. Follow this link to our GitHub.
Version <1.1>
| Date | Version | Description | Author |
|---|---|---|---|
| date | 1.0 | Meeting summons created. | name |
| date | 1.1 | Meeting minutes | name |
Time/location: Date, Time, Place
The following persons are called for: Names
Case no. 01 Opening meeting
Case no. 02 Status Sprint 1
Case no. 03 Wireframe/Figma status
Case no. 04 Ending Remarks/Questioning
Please contact me if you are unable to attend the meeting.
Regards
Name Place, Date
Minutes from project meeting in project team X
Time/location: Date, Time, Place
Present: Name
Absent: Name
Moderator: Name
Case no. 01 Opening meeting
Case no. 02 Status Sprint 1
Case no. 03 Wireframe/Figma status
Case no. 04 Ending Remarks/Questioning
Place, Date
Name
