# Retro 17.03.2021

* 👏 The app is in the production and earns money
* 👏 The test and the produciton environment are using the same tech stack
* 😟 Rapid AG and concert flows get less attention than PCR flow
* 😟😟 Switching pace is too slow
* 😟😟 Master branch has not been releasable all times (think about feature toggle and feature branches to improve it still)
* 👏 Error logging has been improving a lot - allows us to react to problems and understand them better
* The team has been growing
* 😟 Some of the problems do not get attention, because something else is in progress and sometimes it is expected that someone else is solving them
* 😟 It is not always clear which stories need design review (add Design review in Pivotal)
* 👏👏 Communication between us and the customer is lot better now
* 😟 Stories are done formally - whoever takes the story should take responsibility from the beginning to the end - from analyzing whether the story makes sense till checking if the feature actually works after a deployment etc. (Share ideas, doubts with team members)
* 😟 Superman Kirill - rewriting existing/ready functionality (new members sometimes does not know the background, something did not work as expected)
* 😟 Rush and pressure from the customer is sometimes pushing us to fix things quickly and not to complete our work properly (quick fixes for high priority issues are OK, but then we have to take time to really fix these issues)
* 👏 The person who makes the demo is rotating well
* 👏 Clear message was sent to the team that we should not work in weekends and after business hours (It does not mean that we hide ourselves)

## Keep

- [x] document design decisions *(Ilja)*
- [ ] prepare for reviews (make it interesting for others) *(everybody)*
- [x] try new tech/features *(everybody)*
- [x] add smoke tests to ensure that the main functionality still works after a release (rnd1 project in AWS) *(Ilja)*

## Try

- [x] keep changes small and switch pairs frequently (1-2-3 days) *(Tõnis, everybody)*

## Notes

* Kirill ig going to organize the next retro
* Tõnis is keeping eye on pair switching (maximum time of working together is 1 week)

----

# [Notes](https://hackmd.io/@aivar/retro-17-02-2021) from the previous retro

## Keep

- [x] use “master releasebale” mindset *(everybody)*
- [ ] keep changes small and switch pairs frequently (1-2-3 days) *(everybody)*
- [ ] document design decisions *(Ilja)*
- [ ] prepare for reviews (make it interesting for others) *(everybody)*
- [x] rotate who is making a demo *(everybody)*
- [x] Slack communication - check time to time and react if necessary *(everybody)*
- [x] keep iteration meetings focused *(everybody)*

## Try
- [ ] find a way to simplify and make realeasing more reliable *(Kirill)*
- [x] try new tech/features *(everybody)*
- [x] add smoke tests to ensure that the main functionality still works after a release *(Ilja)*
- [x] keep calm! *(everybody)*