Daily Journal

Transcript

1. The benefits of keeping a daily journal in an agile team
2. Everyday every team member uses the last five minutes of the day to write a diary about their day
3. Questions •What have we done?
4. Questions •What do we miss to end this story?
5. Questions •What problems did we uncover?
6. Questions •What did we learn?
7. 4 April - Registration process & Retro Actions Today I worked with @XXX on the card 1234. We fixed the sending of the email when the account was not created. The problem we faced was that the library we were including to send the email was too big and that was hitting the AWS Lambda limit size (250MB). We fixed that by doing a PR (https://github.com) to include only the AWS SDK part that we needed in the library (in this case SNS). We discovered that is not easy to fork a dependency and point to it to a private fork using SBT. More over here https://github.com/JetBrains/intellij- scala/wiki/%5BSBT%5D-How-to-use-provided-libraries-in-run- configurations On the end of the day we also created a retrospective board so we are better able to track and prioritize what actions we still need to do. The general team feeling is that we are not dedicating enough time to do the actions and retro after retro we accumulate more actions.
8. Main Benefits of the Journal Reflect Individually
9. Main Benefits of the Journal Reflect Individually Reflect in team
10. Main Benefits of the Journal Reflect Individually Reflect in team Log
11. Main Benefits of the Journal Reflect Individually Reflect in team Log Knowledge base
12. Main Benefits of the Journal Reflect Individually Reflect in team Log Knowledge base Reduce cognitive load
13. Tools • Wiki • Confluence • Discourse • Google Sites • <anything else>
14. Experiment time! Try to save the last 5 minutes of the day to write a journal entry everyday
15. Thank you!