Grading
How your grade is computed, and a simulator to play with
The grade is a team grade multiplied by an individual factor. The project's ambition can raise or lower the team grade by up to 20 %.
Final grade
7.30
Pass
NEquip = (0.6·Artif + 0.2·GestProj + 0.2·Present) × Ambició = 7.30
NEquip and Nfinal are capped at 10. Competences: A above 8.4; B from 7 to 8.4; C from 5 to 6.9; D below 5.
How much each Fag weighs
| Item | Fag-1, Fag-2 | Fag-3, Fag-4 | Fag-5 |
|---|---|---|---|
| Artif | 10 % | 15 % | 75 % |
| GestProj | 30 % | 30 % | 40 % |
| Present | 40 % | 20 % | 40 % |
The final software weighs a lot (75 % of the artefacts at Fag-5), but management and presentations are spread over the whole course: do not leave everything for the end.
Three assessment points
- Inception (week 4). The first sprint delivery serves as practice.
- Mid-course development (week 11).
- Final delivery, once the course is over.
You get feedback on every delivery. The scope is closed at the end of the course, but its value is estimated along the way.
Functional volume
Typical cross-cutting aspects
Tick the ones your app will have. Not all apply to every topic, and you can add others (an AI component, for example).
| Criterion | Satisfactory | Optimal |
|---|---|---|
| Geolocation | No map | With a map |
| Social networks | Login | Something more |
| Chat | Instant | With history |
| Gamification | Ratings | Trophies or similar |
| Real stakeholders | By how many, the quality of their feedback and when it is asked for | |
| Refutation | Notifications | Blocking accounts |
| Calendar | Internal to the system | Synced (e.g. Google) |
| Admin web app | Depending on its functionality | |
| Multilingual | Architecture ready | Full implementation |