vault backup: 2023-10-12 15:07:48

01 - Notes/Literature/DevOps in Game dev - GDC 2020.md

@@ -84,7 +84,26 @@ Any devops pipeline is better than no pipeline.
 - Patch notes made from commit messages and issue titles automatically, which remove manual work and defects (forgetting a change)
 - These patch notes can be converted into checklists for the QA to track what they should test and make a feedback accordingly
 
+## [[The second way: amplify feedback loops]]
+Feedback is what allows the team to catch problems, improve processes and build quality
+For QA tests, what to test should be an automated checklist depending on the patch notes. This lets one track which tests have been made, on which platforms and issues should be reported in a way that the problem is reviewed once and then automatically creates new tasks to fix the stuff.
 
+Better feedback faster -> defects seen sooner, less waste
+
+Systems should be made to facilitate good feedback, making it easily available to the dev team.
+
+Some issues can be automatically tracked and created through tools like Sentry.
+
+## [[The third way: continuous learning]]
+Making work visible could help track whatever anyone is doing at anytime which should provide markers to improve where people are spending time on waste.
+
+Bi-weekly meetings lets users only focus on too specific matters. Monthly to quarterly meetings to discuss whole pipeline issues fits well. Questionnaires can help to gather inputs and use this to help improve the processes.
+
+Everyone has the right to experiment -> culture of psychological safety to let people try and learn new things
+
+*The work culture is a result of the structures and processes you use -> people are only as good as the systems they work and develop themselves in.*
+
+Make the culture about learning.
 
 ---
 # References