# Sprint 184 13/5/20-2/6/20 Che Platform Team

## Capacity

* Sergii: 14
* Lukáš: 14
* Michal: 13
* Maksym: 14

## Plan
### Finalize from the previous sprint
* Prepare demo about available persistent volume strategies https://github.com/eclipse/che/issues/16788 3sp

### CRW related: CRW with wildcard-free SSL certificate [#CRW-832](https://issues.redhat.com/browse/CRW-832)
* Single-host for OpenShift - POC for nginx https://github.com/eclipse/che/issues/16883 3 sps
* Single-host for OpenShift - Hot-reload the gateway using in-container controller https://github.com/eclipse/che/issues/16887 5sp
* Single-host for OpenShift - Traefik testable POCs https://github.com/eclipse/che/issues/16888 5sp
* Single-host for OpenShift - Performance tests https://github.com/eclipse/che/issues/16889 8sp

### Support maven configuration injection in workspaces [#16832](https://github.com/eclipse/che/issues/16832)

* User should be able to set/retrieve secrets/configmap and see them mounted and/or as env variables https://github.com/eclipse/che/issues/14680 8sp
* I would like to specify my maven settings once for all my maven workspaces https://github.com/eclipse/che/issues/16857 5sp

### User Devfiles [#16875](https://github.com/eclipse/che/issues/16875)
* Adapt persistent factories to Devfile concept https://github.com/eclipse/che/issues/16897 8sp

## Metrics

| | Planned | Result |
| --- | --: | --: |
| **Budget SP** | 45 |24|
## Retrospective Comments
* [Better granularity] Try to separate large task on several smaller. In this sprint https://github.com/eclipse/che/issues/14680
was defined as two things: secrets mounting + ability to override in devfile some of the parameters. Unfortunately, we were not able
to deliver it in time because in the middle of implementation we have to switch to an unplanned task.

* Do not take more than two big features in parallel. Historically we noticed that the team has better performance and results
when we are taking only two features in sprint + bugfixes + unplanned + reviews. In this sprint, we took 3 big feature tasks
and were not able to properly deliver them.

* Devs and scrum master each day should estimate the risks or blockers that may happen and lead not to deliver feature on time. Ideally, this topic should be raised as earlier as possible.