# PL2 - Pantzerfaust
## Sprint
| Group                               | Sprint Management |           |                |                       |                |            |
|-------------------------------------|-------------------|-----------|----------------|-----------------------|----------------|------------|
|                                     | user story        |           |                | learning from history |                |            |
|                                     | definition        | splitting | responsibility | estimation            | prioritisation | reflection |
| PL2 (Pantzerfaust)                  | 10                | 10        | 10             | 7                     | 6              | 8          |

## Code Evolution
| Group                               | Code Evolution Quality |         |                     |                  |         |          |                        |         |         |                        |             |
|-------------------------------------|------------------------|---------|---------------------|------------------|---------|----------|------------------------|---------|---------|------------------------|-------------|
|                                     | architecture           |         |                     | code readability |         |          | continuous integration |         |         | pull-based development |             |
|                                     | changes                | arch-dd | code change quality | change           | quality | comments | building               | testing | tooling | branching              | code review |
| PL2 (Pantzerfaust)                  | 5                      | 5       | 9                   | 10               | 10      | 8        | 10                     | 10      | 5       | 10                     | 10          |

## Notes
Sprint
Definition: 10

Splitting: 10

Responsibility: 10

Reflection
Reflection: 8
-The "adjustment for next sprint plan" is actually a reaction to Wouters illness.
-Some notes don't explain much (e.g. problem 1 and 2 combined to this not being finished)

Estimation: 7

Priority: 6
-Tasks both done partly while they had different priorities. Priorities should also be followed up.
-I recall that in the customer meeting was stressed on the usability; I don't see that in your tasks. 

Architecture
Changes: 5
Document: 5
-No new version, same feedback as last week
-Feedback should be implemented

CQ: 9
-Unused classes should be deleted

Readability
Formatting: 10
Naming: 10
Commenting: 8
-Some classes not commented

CI
Building: 10
Testing: 10

Tooling: 5
-Still loads of tooling errors
-Should be fixed per PR

PBD
Branching: 10
Code Review: 10


## Announcements
We will not have the regular SE Meeting next Friday because of the Serial Meetings we will have with Bacchelli. You will need to prepare a 10-15 minute demo and sell your product. 
 
Besides that please fill in this survey for your feedback on me [here.](https://docs.google.com/forms/d/1eprgikpJsNbVj6x0CDLeKqxsdnkfd1P9k9Qdn8kkqr8/viewform#start=openform) 

Add feedback for sprint 5
Add feedback for sprint 5
