Developer Meeting May 2022

[SimonHeybrock]

Retrospective

Start/stop

• Need to control time spent on reacting to questions and request.
  • Do we need to time-box "user support"? Or dedicate specific times of the day/week?
    • Avoid long user-support chats on Slack -> move to dedicated support calls, limit time spent on this on, e.g., a monthly basis.
    • Raise question higher up: Do we need dedicated position for user support?
  • Slightly delay answering questions, since in many cases users will find the answer themselves (e.g., in docs). Frequently interrupted work from Slack messages. How can this be done in practice?
    • Disable many/most notifications.
    • Check emails/slack in intervals, not continuously.
    • Disable Github emails, use notification view (e.g., a couple times per day).
• Long standing pull request. Either close or merge.
• Analysis paralysis in some cases. Need to either come to a conclusion or stop putting time (without new input/requirements)?
• Standups should be kept brief, move long discussions to dedicated meetings.
• Standups: Instead of "I did this and will do that" -> "I am stuck/blocked with/by, I solved A by B, ...".
• More pair programming.

Continue

• Develop skills and expertise together, don't just work through list of issues. Training and advancement as a team exercise works well.