...
- Specifying roles for each team member during a meeting: timekeeper, notekeeper, etc
- Timeboxing time spent on each ticket during grooming (calling rabbit hole if we spend more than 5 min on a ticket)
- List questions for Mary Jo product owner or other stakeholder to answer during grooming
- Review epics/features before grooming day, in preparation for grooming
- Organize grooming page before grooming (each team member is responsible for adding tickets)
- During the grooming session: Keeping notes of questions and new tickets on the grooming page or on the requirements page
- Timezone considerations: Agree on the earliest and latest times we want to allow for meetings to be scheduled. Please add the times in your timezone that are acceptable. We'll try and agree on guidelines here.
- Chongsun: No earlier than 8am PT (Pacific Time), no later than 11pm PT
- Nikodem: No later than 11am PT
- Lukasz: No later than 9am PT
- Sam: No earlier than 6am PT, no later than 6pm PT
...
- Keep our meeting agreements - timebox, agenda, leadermeetings are on time (Does this mean must that meetings start on time?), notekeeper
- Meetings start on time
- Meeting agenda created before a meeting, and then everyone agrees and adds agenda items to it
- Other ideas?
...
- Owner of feature to follow up on questions and tickets
- Getting review and feedback from outside our team early and often
- if If we have spike tickets we should complete them as soon as possible be because they may block other tickets
- Be more confident about feature implementation - gather more details, ask questions and so on
- quicker Try to research and find tickets that requires require more time to implement - like split in the requisition service
- Other ideas?
...
- We've improved communication in the team, but we should keep working on it. (How do we want to improve on this?)
- more More discussion outside meetings (either on Slack or JIRA) so we can utilize them more effectively
- Other ideas?
...