1. what they're working today,
2. what features they're going to code today, and
3. what features and what activities they did the day before, and
4. if they have any blockers. | | | Set up internal meetings | Set up internal meeting | | | Updating user stories | keep those stories updated as in if the development team has commented that design files are not updated and the designer has not responded, your responsibilities would be to follow up with the designers to confirm whether the design files attached have been updated or not. | | | Shadowing cross-functional teams

• to report back to Shreya & Polina
• answer questions from the cross-functional teams | To shadow cross-functional teams to ensure:
• product team has all the related knowledge to make the right decisions.

Now, these right decisions are the user stories, how the feature will function, basically. So it will happen that design team will have their own meetings amongst the designers to figure out the different screen flows Research team will have their own meeting to understand the insights that they derive from different user interviews.

Research team will also be responsible for conducting user interviews. Development team will have their internal meetings.

So your responsibilities as a team liaison would be to shadow these meetings and collect insights as critical for taking the calls from me and Polina in understanding the feature workings and if in any case there are any blockers and you feel that yes this is something that is critical and that might risk the scope of work in the future then you need to come back to us and inform us that during the call that some of the design the design team was confused into taking the call into this. | | | Prepare meeting minutes

Only for Strategy Team | To prepare meeting of minutes and share them during the strategy team catch up call. Any one of you can take up that responsibility before the call and you inform that on the agenda that who will be responsible for taking minutes of meeting. And during that call, just be responsible and write down all the notes, any action it is on any team member should be clear.

And once that is done, just respond back. This is the gist of what you have to do. And especially for cross-functional meetings, whenever you are available, try to summarize the call in such a way that is actionable for us.

And if at all, there are no actionable in the meeting, then it is just for your information that you attended that call. And what you understood in that call, what was going on in that call, because some of the cross function calls will be different, especially with design development and research. | | | Keep strategy Notion page clean | Once or twice a week | | | Conduct Sprint retrospective | Sprint retrospective is done at the end of the sprint just to engage all of the team members that were a part of that particular development sprint. And that is generally a reflective session where we understand where we did well, what could have been done better, and what we can change in the future. So this is a general sprint retro meeting. | |