Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/chimera-hackathon-team/chimera-hackathon-preparation
Welcome to the Chimera team repository! Here you will find the work and resources we use to prepare for hackathons.
https://github.com/chimera-hackathon-team/chimera-hackathon-preparation
artificial-intelligence backend data-science database frontend machine-learning web-scraping
Last synced: 22 days ago
JSON representation
Welcome to the Chimera team repository! Here you will find the work and resources we use to prepare for hackathons.
- Host: GitHub
- URL: https://github.com/chimera-hackathon-team/chimera-hackathon-preparation
- Owner: Chimera-Hackathon-Team
- Created: 2024-11-17T15:56:26.000Z (about 2 months ago)
- Default Branch: main
- Last Pushed: 2024-11-24T22:48:12.000Z (about 2 months ago)
- Last Synced: 2024-12-18T14:20:05.071Z (22 days ago)
- Topics: artificial-intelligence, backend, data-science, database, frontend, machine-learning, web-scraping
- Language: Python
- Homepage:
- Size: 46.7 MB
- Stars: 3
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# T-mobile-Hackathon-2024
![chimera_logo](https://github.com/user-attachments/assets/a12f05ad-2fc6-4382-891f-d103b6df36d1)
**Name Team:** `Chimera`.
[Replit Workspace](https://replit.com/join/mafnornexg-dmytro-varich).
[Canva Presentation](https://www.canva.com/design/DAGWwGYgXnI/4x_2s_kDGZGT8e9IxIRUrQ/edit?utm_content=DAGWwGYgXnI&utm_campaign=designshare&utm_medium=link2&utm_source=sharebutton).
[Figma](https://www.figma.com/design/cnubVCDshnbVBriQsz6WBJ/T-mobile_Hackathon_2024?t=CEaLtgpMMKNW3q78-1).
## Scrum Stages for the Hackathon
| **Stage** | **Description** | **Expected Outcome** |
|-----------------------------|---------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|
| **1. Sprint Planning** | Discuss the idea, define the project goal, key processes, features, and tasks. Assign roles and responsibilities to team members. | Roles are clearly defined, the Minimum Viable Product (MVP) is identified, and a task list (Product Backlog) is created. |
| **2. Sprint** | Break tasks into smaller subtasks and implement the core functionality. Set deadlines. | Each participant has a specific task with a clear deadline. |
| **3. Meeting** | Discuss:
- What has been done?
- What is planned?
- What obstacles exist? | Updated plan is formed, tasks are redistributed, and new deadlines are set. |
| **4. Sprint** | Execute tasks while meeting deadlines. Regularly synchronize and document results. | Working prototypes, completed modules, or interfaces are delivered. |
| **5. Testing** | Validate the results: check for bugs, functionality, and performance. | Errors are detected and fixed; the product operates stably. |
| **6. Product Demonstration** | Prepare a presentation and project report. Showcase results: interfaces, working code, charts. | Feedback is received; the final product or presentation is ready for the jury. |
| **7. Retrospective** | After the hackathon, discuss:
- What worked well?
- What can be improved? | Lessons learned and actionable insights for future projects. |