# Hackaton 2022

## Theme
The theme for this edition is ENGAGEMENT. The teams must develop a product that **promotes overall internal company engagement** and deliver until **February 22nd**.

## Do I need to be a B-Fronter to participate?
No. You can be part of any area of BairesDev.

## We developed a scoring system based on 4 categories
| Category | Maximum Score |
| ------- | -------- |
| Completeness | **5.5 points**
| Adoptability | **35 points**
| User Experience | **35 points**
| User Interface Design | **5 points**

## Completeness Score
| Score | Requirement |
|------- | -------- |
| **1 point** | The product must allow the user to engage self to others.
| **2 points** | The product must allow others to engage with the user.
| **3 points** | The product must have a feature of engage reminder.
| **4 points** | The product must have any kind of points/score system.
| **5 points** | The product must have a rewards/achievements/gamification aspect implemented.
| **0.5 point** | BONUS REQUIREMENT | Build an Admin Access (CRUD users, etc…) | 0.5 at the final Completeness score.

## Adoptability Score
Would I use this app again?
| Score | Requirement |
|------ | -------- |
| **1 point** | Never Again
| **2 points** | Once a Month
| **3 points** | Once a Week
| **4 points** | More than once a Week
| **5 points** | Every Day

## User Experience Score
| Score | Requirement |
|------ | -------- |
| **1 point** | Very Hard to Perform.
| **2 points** | Hard to Perform.
| **3 points** | Can be performed with minor difficulties.
| **4 points** | Easy to Perform.
| **5 points** | Very Easy to Perform.

## User Interface Design
Each topic has a 0.5 point value.

| Category | Requirement |
|------ | -------- |
| Visibility of app status | The app should always keep users informed about what is going on.
| Match between app and real world | The app should speak the user’s language, with words, phrases, metaphors and representations familiar to the user. Take into - consideration the BairesDev environment.
| User control and freedom | Supports easy editability. Allow user to override the app.
| Consistency and Standards | Users should not have to wonder whether different colors, design elements, situations, or actions mean the same thing.
| Error Prevention | Prevents a problem from occurring in the first place. Be permissive to various entry formats.
| Recognition rather than recall | Making objects, actions, and options visible. Make navigation visible and make it easy to go back, go to home page and quit.
| Flexibility and efficiency of use | Speed up the interaction for the expert users with accelerator. Experts prefer few screens with a lot of information and a lot of flexibility in the methods, while novice users prefer going through step by step sequences with little information.
| Aesthetic and minimalist design | Dialogues should not contain information that is irrelevant or rarely needed. In other words, present only necessary information for the task, rarely used information should be in secondary screens or windows.
| Manage Errors | Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.
| Help and Documentation | Use prompt and contextual help related the task, allow easy search

## What needs to be delivered at the end of the Hackathon?
- Web or Mobile App and it has to be a user engagement automation tool.
- Users must be able to self login and the tool must immediately start to take actions to engage users, such as connection suggestions, first login tutorials, etc…

## General considerations

_F.M. - 7 hours ago_
- According to the subject and the scoring system, the hackathon seems to focus **more** on **socialization** than engagement.
- Looking for the specific goal of the competition, there are no clear guidelines.
- As far as I can see, the metrics are based on the **interaction between the employees**, considering as true that this boots engagement, right?