# PL5 - Totally Awesome Genome Coders
------

## Rubrics
|                                     | Sprint 4   |           |                |                       |                |            |
|-------------------------------------|------------|-----------|----------------|-----------------------|----------------|------------|
|                                     | User Story |           |                | Learning From History |                |            |
| Group                               | Definition | Splitting | Responsibility | Estimation            | Prioritisation | Reflection |
| PL5 (Totally Awesome Genome Coders) | 7          | 9         | 8              | 4                     | 9              | 10         |

|                                     | Code Evolution Quality 4 |         |                     |                  |         |          |                        |         |         |                        |             |
|-------------------------------------|--------------------------|---------|---------------------|------------------|---------|----------|------------------------|---------|---------|------------------------|-------------|
|                                     | Architecture             |         |                     | Code Readability |         |          | Continuous Integration |         |         | Pull-based Development |             |
| Group                               | Changes                  | Arch-DD | Code Change Quality | Change           | Quality | Comments | Building               | Testing | Tooling | Branching              | Code Review |
| PL5 (Totally Awesome Genome Coders) | 8                        | 9       | 5                   | 9                | 9       | 10       | 9                      | 6       | 9       | 10                     | 9           |

## Notes
sprint:
-definition: concrete tasks + better specification (give colour to genomes)
-splitting: here and there big difference
-responsibility: a bit shifted for some people

reflection: 
-estimation: not accurate

EAD:
-only HD space @scalability?
-Use design goals in your subsystem choices, why is this a good choice?

EAD-Changes:
-Should split back-end in modules
-Structure of back-end should be better described in EAD

CQ:
-Roughly same as last week
Add feedback for sprint 4
Add feedback for sprint 4
