![]() Some companies even create a #retrospectives channel to reduce clutter in other channels.īesides searching through the broadcast channels, you can find everyone’s answers in your Geekbot dashboard, alongside details like report streaks and participation rates. This can be any channel you want - #general if the retrospective concerns everyone, #dev if it’s specific to the development team’s sprints, and so on. Once participants answer their retrospective questions, their answers get posted to a channel of your choosing. This is especially useful if your remote team is distributed across different timezones, as it ensures all teammates receive their retrospective questions at an appropriate time. Plus, Geekbot can also take into account each participant’s timezone. Once every month (e.g., on the first Monday of each new month to recap the previous one and prioritize tasks for the next sprint).Every two weeks (e.g., on Friday afternoon to recap the previous two weeks before logging off).That’s why Geekbot allows you to select any schedule for your sprint review, including: Scheduleĭifferent teams conduct their retrospective at different frequencies. To choose who gets the retrospective questions, simply type in their name.īecause Geekbot integrates with your Slack or Microsoft Teams account, your teammates’ profiles will appear automatically once you start typing. This ability to customize questions lets you easily create different types of retrospective templates, as you’ll see later. “What’s the most important thing you learned from the last sprint?” to understand what outcomes team members value.“On a scale of 1 to 10, how do you feel after this sprint?” to get a better understanding of each participant’s emotional state. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |