I start most mornings with my coffee and two (sometimes three) automated summaries waiting in Slack. One tells me what my team did yesterday—tickets moved, PRs opened, potential bottlenecks. The second checks upcoming releases and cross-examines those with our JIRA board, flagging changes stuck in QA or review. The third is a recap of my team’s weekly performance in terms of velocity and defects. By the time I’m at my desk, I have a good idea of where to put my focus and what to follow up on. These automations let me spend more time diving into PRs and resolving risks and less time pulling data to understand where the risks might be.
I start most mornings with my coffee and two (sometimes three) automated summaries waiting in Slack. One tells me what my team did yesterday—tickets moved, PRs opened, potential bottlenecks. The second checks upcoming releases and cross-examines those with our JIRA board, flagging changes stuck in QA or review. The third is a recap of my team’s weekly performance in terms of velocity and defects. By the time I’m at my desk, I have a good idea of where to put my focus and what to follow up on. These automations let me spend more time diving into PRs and resolving risks and less time pulling data to understand where the risks might be.