 Jordan Mosselson |
 Matthew Hubbard |
 Max Day |
 Jaiyesh Pillay |
 Tashil Koseelan |
Primary Sources
- Saskia Singh, “Briconomy”, 2025. [Online]. Available: Canva Project
- Scrum Alliance, “Definition of Ready vs. Definition of Done”, 2025. Read Here
- N. Nazruden, ClickUp-MCP-server, GitHub Repository. View
- GitHub, GitHub-MCP-server, Repository. View
- R. Gong, Office-Word-MCP-Server, GitHub Repository. View
- Atlassian (2023). Definition of Done (DoD) Explained for Agile Teams. View
- Scrum.org (2017). Walking Through a Definition of Ready. View
- D. Bailey (2015). What is Definition of Ready? Agile Alliance. View
- ResearchGate (2022). On the Benefits and Problems Related to Using Definition of Done – A Survey Study. View
Additional Sources
- Investopedia: Property Management (2024)
- Perforce Software: Non-Functional Requirements (2024)
- V. Britto: The Authentication Strategies (2024)
- Qmantic: RBAC and RLS (2024)
- DataGuard: Cyber Risk Mitigation Strategies (2024)
- P. Kirvan: Change Management Strategy (2023)
- Prosci: Kotter’s Change Management Theory (2024)
- M. Tanner: Enterprise Software Architecture Patterns (2025)
- GeeksforGeeks: Software Architecture Patterns
- Refactoring Guru: Strategy Pattern
We, the undersigned, hereby declare that the work submitted in this project is our own, completed collaboratively as a group. All sources of information, ideas, and assistance have been acknowledged and referenced appropriately. This project has not been submitted previously, in whole, for any assessment at this or any other institution. We affirm that we have each contributed meaningfully to the completion of the project and accept joint responsibility for the authenticity and integrity of the work presented.
| Jaiyesh Pillay | ST10292436 | ST10292436@vcconnect.edu.za | | Tashil Koseelan | ST10339603 | ST10339603@vcconnect.edu.za | | Jordan Mosselson | ST10270629 | ST10270629@vcconnect.edu.za | | Matthew Hubbard | ST10301544 | ST10301544@vcconnect.edu.za | | Max Day | ST10322238 | ST10322238@vcconnect.edu.za |
- Scrum Agile Board (Original): View Board
- Scrum Agile Board (Updated): View Board
- ClickUp Roadmap: View Roadmap
- ClickUp Sprint: View Sprint
| GitHub Repository | Briconomy on GitHub | | Code Quality (SonarQube) | SonarQube Report | | Security Report (Snyk) | View Report |
The team cooperated very well throughout the duration of this project. From beginning to end, there were no disagreements, issues, or fights with the team members. Every member contributed equally, showing commitment, responsibility, and respect for ideas and input from one another. We all worked incredibly hard, working countless hours to fine-tune and polish the material to achieve a top-grade product. The team communication was productive and fluid, allowing us to be on the same platform all along. Every team member was highly proactive in completing tasks, assisting wherever possible, and ensuring deadlines were met without hassle. The flow of work was smooth, and task allocation was evenly distributed, resulting in an even workload. In general, the group environment was extremely positive with no grievances or issues regarding anyone's contribution or dedication. Everyone had a crucial part to play in satisfying our overall objectives, and the cooperation exhibited can be termed seamless and collaborative. This project exactly portrayed the essence of teamwork since everyone collaborated very energetically and harmoniously to deliver the final product.
*Document spell-checked with Grammarly | Tables designed in Figma | Logo created in Canva*