Meeting Title: Team Retro and Planning Sync Date: 2025-08-08 Meeting participants: Awaish Kumar, Vashdev Heerani, Amber Lin, Annie Yu, Robert Tseng, Henry Zhao, Demilade Agboola
WEBVTT
1 00:00:17.820 ⇒ 00:00:18.890 Amber Lin: Hello!
2 00:00:19.120 ⇒ 00:00:21.629 Amber Lin: I will keep this at
3 00:00:21.870 ⇒ 00:00:29.390 Amber Lin: 20 to 20 to 30 min, and any tickets or stuff I need to check in. I’ll do it, Async.
4 00:00:30.361 ⇒ 00:00:36.660 Amber Lin: So let me pull up a whiteboard.
5 00:00:38.850 ⇒ 00:00:40.829 Amber Lin: So he just
6 00:00:45.620 ⇒ 00:00:48.530 Amber Lin: alright. I’m gonna make a new one
7 00:00:57.080 ⇒ 00:00:59.600 Amber Lin: today is August 8.th
8 00:01:00.790 ⇒ 00:01:06.420 Amber Lin: All right. I’m going to add a template retro.
9 00:01:18.550 ⇒ 00:01:24.149 Amber Lin: Okay, so I’ll set a quick timer, and then
10 00:01:25.450 ⇒ 00:01:32.079 Amber Lin: we can write. Put stickies in all these different
11 00:01:32.250 ⇒ 00:01:41.610 Amber Lin: sections, and then we’ll talk in about 5 min or so oops.
12 00:02:04.530 ⇒ 00:02:07.919 Henry Zhao: Sorry. This is my 1st retro. We just do it directly on here, right.
13 00:02:08.259 ⇒ 00:02:15.638 Amber Lin: Yeah, just put any stickies you want on the left sidebar. There’s you can also press N to add sticky notes.
14 00:02:16.209 ⇒ 00:02:22.349 Amber Lin: and then you can put anything that you’re thinking about in there.
15 00:03:54.609 ⇒ 00:03:58.619 Amber Lin: Oh, I don’t see anyone writing on the board yet.
16 00:03:58.729 ⇒ 00:04:02.689 Amber Lin: except for me. Are you guys on the same board as me?
17 00:04:11.720 ⇒ 00:04:12.280 Awaish Kumar: Yep.
18 00:04:15.530 ⇒ 00:04:16.649 Amber Lin: Oh.
19 00:04:20.480 ⇒ 00:04:21.170 Amber Lin: oh.
20 00:04:25.190 ⇒ 00:04:28.069 Amber Lin: Vashtav, do you know how to add stickies here.
21 00:04:35.530 ⇒ 00:04:36.900 Vashdev Heerani: And Nope.
22 00:04:37.670 ⇒ 00:04:53.220 Amber Lin: Yeah. So on the left hand side you’ll see a white bar right? And then there is a square icon that’s sticky, says sticky note. If you click on it, you’ll create a new sticky note, and then you can type in there. You can also type in the empty stickies on the
23 00:04:53.580 ⇒ 00:04:57.420 Amber Lin: on the board as well. I’ll add a few new ones.
24 00:05:03.000 ⇒ 00:05:03.989 Vashdev Heerani: Okay, got it?
25 00:05:05.650 ⇒ 00:05:06.890 Amber Lin: Hi devotee.
26 00:05:08.220 ⇒ 00:05:09.090 Demilade Agboola: Hello!
27 00:07:28.000 ⇒ 00:07:31.750 Amber Lin: Does everyone need one more minute, or are we good?
28 00:07:34.360 ⇒ 00:07:35.040 Amber Lin: Oh.
29 00:09:33.920 ⇒ 00:09:34.890 Amber Lin: okay.
30 00:09:36.048 ⇒ 00:09:57.180 Amber Lin: let’s get started. Now, I just want everyone to take a minute or 2 to read. Everyone else stickies, and if you agree, you can click on it and add a emoji. Add a reaction to say if you agree, and then we’ll we’ll start talking in about a minute or so.
31 00:11:27.020 ⇒ 00:11:30.969 Amber Lin: Okay, has everyone got a chance to read everything?
32 00:11:34.120 ⇒ 00:11:34.950 Amber Lin: Alright?
33 00:11:35.130 ⇒ 00:11:50.320 Amber Lin: I I hear a few themes, but I want to hear it from everybody just to know, just so that we can know every what everyone thinks. I think. Let’s start.
34 00:11:51.150 ⇒ 00:11:55.619 Amber Lin: Oh, Annie, what do you think?
35 00:11:55.720 ⇒ 00:11:58.010 Amber Lin: Just an overview of your thoughts?
36 00:12:00.588 ⇒ 00:12:02.740 Annie Yu: Can I go next? I’m gonna organize my.
37 00:12:03.620 ⇒ 00:12:06.490 Amber Lin: Okay. Sure. Donna, do you want to go first? st
38 00:12:13.250 ⇒ 00:12:19.860 Demilade Agboola: From my perspective. The things I feel like went well, were we’re able to.
39 00:12:21.660 ⇒ 00:12:24.800 Demilade Agboola: We’re able to track things much better.
40 00:12:25.522 ⇒ 00:12:31.150 Demilade Agboola: Just kind of have an idea of everything that’s happening. Even ad hoc tasks.
41 00:12:31.988 ⇒ 00:12:35.519 Demilade Agboola: We’re also able to get across
42 00:12:36.460 ⇒ 00:12:44.260 Demilade Agboola: stuff to join out this week. He seemed, at least from the conversation I saw he seemed quite pleased about that.
43 00:12:45.586 ⇒ 00:12:52.929 Demilade Agboola: Things that need improvement. I will say that
44 00:12:53.560 ⇒ 00:12:59.680 Demilade Agboola: setting projects like the Cox project kind of dragged for a bit or is dragging for a bit.
45 00:13:04.150 ⇒ 00:13:18.627 Demilade Agboola: And I would also say that, like certain things like the time, allocation for certain projects don’t necessarily always match the time that actually ends up being required for the tickets.
46 00:13:21.870 ⇒ 00:13:23.020 Demilade Agboola: Yeah.
47 00:13:23.500 ⇒ 00:13:23.880 Amber Lin: Okay.
48 00:13:23.880 ⇒ 00:13:26.489 Demilade Agboola: Yeah, I’ve got 2 main things. I’ll say, pop up.
49 00:13:27.120 ⇒ 00:13:27.800 Amber Lin: Okay.
50 00:13:27.900 ⇒ 00:13:34.260 Amber Lin: So estimates versus it’s just not match.
51 00:13:38.740 ⇒ 00:13:47.399 Amber Lin: Okay? Let’s go around. And then let’s talk about how we can solve that
52 00:13:47.927 ⇒ 00:13:50.489 Amber Lin: which do you want to go?
53 00:13:54.800 ⇒ 00:14:00.589 Awaish Kumar: Yeah, like, some of like one of the things that definitely mentioned like that.
54 00:14:01.670 ⇒ 00:14:04.530 Awaish Kumar: Some projects like kept dragging on.
55 00:14:04.940 ⇒ 00:14:10.170 Awaish Kumar: Because maybe we did have, we could have done post autumn audio
56 00:14:10.380 ⇒ 00:14:15.820 Awaish Kumar: to to have to better define the the.
57 00:14:16.130 ⇒ 00:14:18.820 Awaish Kumar: the root causes and the solutions.
58 00:14:19.020 ⇒ 00:14:24.770 Awaish Kumar: and then the time, estimations for projects so like sometimes we
59 00:14:25.420 ⇒ 00:14:31.280 Awaish Kumar: estimate or comment without better spiking. But how much
60 00:14:31.750 ⇒ 00:14:39.000 Awaish Kumar: time is going to be needed, or even if we have enough capabilities to do that phenomenon.
61 00:14:43.430 ⇒ 00:14:47.280 Amber Lin: Okay, so sounds like on that that we should
62 00:14:48.240 ⇒ 00:15:00.840 Amber Lin: should require spikes, before we assign estimates, do you it’s.
63 00:15:04.740 ⇒ 00:15:10.399 Amber Lin: but on that sometimes the spikes are not done on time, and so
64 00:15:11.158 ⇒ 00:15:18.160 Amber Lin: how can we make sure that if we do the spike it doesn’t affect like our overall progress?
65 00:15:18.350 ⇒ 00:15:24.739 Amber Lin: I do think it should be time boxed, but I sometimes I also don’t back. When people do a spike.
66 00:15:27.220 ⇒ 00:15:34.499 Awaish Kumar: Yeah, spike is could not be more than a day like, it’s just few hours, 2, 3 h, or at Max. It’s like
67 00:15:34.820 ⇒ 00:15:37.560 Awaish Kumar: we can take a day right? Not not more than that.
68 00:15:41.470 ⇒ 00:15:44.150 Awaish Kumar: ideally. 2, 3 h. And yeah.
69 00:15:48.890 ⇒ 00:15:52.524 Amber Lin: Okay, that’s 1 thing that’s good.
70 00:15:54.130 ⇒ 00:16:01.749 Amber Lin: I want to talk about projects dragging in the end, and then communication with clients. Let’s go around first.st
71 00:16:04.110 ⇒ 00:16:05.999 Amber Lin: Yeah. Okay, Annie, what do you think.
72 00:16:06.886 ⇒ 00:16:19.950 Annie Yu: I think I do. Wanna echo the time estimation versus actual and I have probably 2 points here. One is the ad hoc, so ad hoc
73 00:16:20.100 ⇒ 00:16:25.929 Annie Yu: are like usually unpredictable, but they do take time, and they might thank you.
74 00:16:26.750 ⇒ 00:16:29.519 Annie Yu: Cost delayed on some other
75 00:16:29.800 ⇒ 00:16:37.169 Annie Yu: planned projects. I’m not sure I don’t know the best solution. But I’m thinking maybe we should
76 00:16:37.590 ⇒ 00:16:39.499 Annie Yu: plan some buffer time
77 00:16:39.760 ⇒ 00:16:45.180 Annie Yu: when we do our location for ad hocs, because it looks like there’s always gonna be ad hocs.
78 00:16:45.440 ⇒ 00:17:10.499 Annie Yu: And one other thing is also this is also under the same theme, like estimation and actual like, for example, for the Cox thing. The data, the invoice data we got from them were actually in Pdf, and when they provided the Excel files they are actually not like the organized Csv that we
79 00:17:10.609 ⇒ 00:17:12.929 Annie Yu: would expect to see. So
80 00:17:13.099 ⇒ 00:17:19.640 Annie Yu: so those Excel files are basically useless. And so from there I had to do like
81 00:17:20.310 ⇒ 00:17:29.130 Annie Yu: write a script to scrape the Pdf into Csv. And there’s it takes a lot of back and forth with AI, because
82 00:17:29.250 ⇒ 00:17:38.270 Annie Yu: it’s just such a in such a messy format, so that caused a lot of delays as well. And so from those things.
83 00:17:40.160 ⇒ 00:17:43.030 Annie Yu: It ended up taking a lot of time, but
84 00:17:43.330 ⇒ 00:17:47.299 Annie Yu: not the things that were listed in the ticket. But just
85 00:17:47.470 ⇒ 00:17:51.099 Annie Yu: I realized, okay, we do have to take an extra step.
86 00:17:52.022 ⇒ 00:17:53.470 Amber Lin: To finish this task.
87 00:17:54.680 ⇒ 00:17:57.260 Annie Yu: So maybe there there should be, I guess.
88 00:17:57.410 ⇒ 00:18:07.480 Annie Yu: Yeah, there should be better communication on my part as well on that on that part. But this is one thing that that may cause like difference
89 00:18:07.640 ⇒ 00:18:10.240 Annie Yu: between estimation and actual.
90 00:18:11.160 ⇒ 00:18:36.340 Amber Lin: So that so I hear 2 things. So 1st is when we plan during planning we should have buffer zones for ad hoc tasks. And also we should also have some buffers when we plan for the original tickets that we put in the cycle because they might get pushed if we get ad hoc urgent tasks, so we should have we should communicate the deadlines on those
91 00:18:36.667 ⇒ 00:18:51.070 Amber Lin: with a little bit buffer zone. And also, I think this is something we should establish with the clients is the turnaround time. Expectations is usually right. Right now we communicate it for each ticket, but maybe we should have at least of
92 00:18:51.090 ⇒ 00:19:00.999 Amber Lin: 24 h at the bare minimum, 48 h, even, maybe even for the smaller task. So that’s something that we can decide on and communicate.
93 00:19:02.800 ⇒ 00:19:10.900 Annie Yu: Yeah, sure. And yeah, I think one other thing is the priority prioritization cause.
94 00:19:11.980 ⇒ 00:19:22.879 Annie Yu: Because there are all different. Like requests, requests coming in, and sometimes I personally don’t know which one to prioritize, and I
95 00:19:23.590 ⇒ 00:19:36.220 Annie Yu: would love a better direction on that. And just yeah, a balance between, like making sure our time is protected and aligned with planned allocation, but also like tackling the.
96 00:19:36.800 ⇒ 00:19:37.920 Annie Yu: Requests.
97 00:19:38.440 ⇒ 00:19:46.839 Amber Lin: Yeah, totally. So I just remembered for the ad hoc stuff that also, when you spike on the ad hoc tasks, we should.
98 00:19:47.650 ⇒ 00:19:50.392 Amber Lin: Similarly, I’m gonna write it here.
99 00:19:52.820 ⇒ 00:20:02.930 Amber Lin: or ad hoc. Once we spike, we should tell clients 1, 2, 8 facts.
100 00:20:03.320 ⇒ 00:20:07.340 Amber Lin: So and then for priorities.
101 00:20:09.170 ⇒ 00:20:23.053 Amber Lin: I think what enables that is one that we know all the stuff that a person is doing. And then we can say, Okay, these belong to that project. How do we prioritize this?
102 00:20:23.870 ⇒ 00:20:33.259 Amber Lin: so have clear tickets and then ask, and I go? Probably.
103 00:20:35.010 ⇒ 00:20:43.700 Amber Lin: Yeah, on that. How do we best prioritize? Who do we ask, or the.
104 00:20:43.700 ⇒ 00:20:50.190 Annie Yu: I I thought, that’s something that I’m not sure now.
105 00:20:50.840 ⇒ 00:21:03.319 Amber Lin: Yeah, I think I know, for whatever’s already planned in cycle. I think it gets confusing when there’s ad hoc tasks that come in, and I don’t know how it compares to our original rank of priorities.
106 00:21:03.320 ⇒ 00:21:09.439 Annie Yu: Yeah, that makes sense like the josh. The Josh’s dashboard. Right? That that just came up this week.
107 00:21:10.230 ⇒ 00:21:10.700 Annie Yu: Yeah.
108 00:21:10.830 ⇒ 00:21:13.519 Annie Yu: If we should prioritize that over Jonah.
109 00:21:15.292 ⇒ 00:21:18.950 Amber Lin: I think maybe when it comes in
110 00:21:19.714 ⇒ 00:21:30.400 Amber Lin: when ad hoc tests come, come in ask them to compare to the original
111 00:21:30.830 ⇒ 00:21:43.480 Amber Lin: tasks, so say if Josh has a request, and then we’ll just tell Josh, hey, we’re working on something for Jonah. Do you want it first? st And then, and then he can say.
112 00:21:43.930 ⇒ 00:21:51.870 Amber Lin: Oh! And then he can say, Oh, I want this. I want this first, st or you can do whatever you have to for Jonah first.st So okay.
113 00:21:52.430 ⇒ 00:21:56.140 Amber Lin: I’ll ask. So we’ll ask when the ad hoc tasks come in.
114 00:21:57.953 ⇒ 00:21:59.440 Amber Lin: Anything else?
115 00:22:02.680 ⇒ 00:22:05.360 Amber Lin: Okay, Henry, do you want to go.
116 00:22:09.478 ⇒ 00:22:12.559 Henry Zhao: Yeah, I have no, not much more to add. But
117 00:22:12.840 ⇒ 00:22:18.410 Henry Zhao: regarding north beam, I think it’s kind of the same thing of just catching up
118 00:22:18.600 ⇒ 00:22:21.619 Henry Zhao: more quickly, and maybe pushing Andrew a little bit more.
119 00:22:22.500 ⇒ 00:22:25.449 Henry Zhao: But one thing that’s do is take more ownership of that.
120 00:22:26.270 ⇒ 00:22:28.940 Henry Zhao: and so that should be improved. Moving forward.
121 00:22:30.660 ⇒ 00:22:31.400 Amber Lin: Okay.
122 00:22:31.840 ⇒ 00:22:33.020 Henry Zhao: Then communication.
123 00:22:33.340 ⇒ 00:22:34.440 Henry Zhao: Go ahead.
124 00:22:35.020 ⇒ 00:22:35.850 Amber Lin: Yeah. Go ahead.
125 00:22:36.400 ⇒ 00:22:38.350 Henry Zhao: And then I agree with all the prioritization stuff.
126 00:22:38.560 ⇒ 00:22:40.650 Henry Zhao: I think I put similar post-its
127 00:22:40.760 ⇒ 00:22:44.490 Henry Zhao: and the communication with clients. I just put that
128 00:22:45.250 ⇒ 00:22:50.610 Henry Zhao: like when Josh is there, we should have more energy and collaboration just forward.
129 00:22:51.760 ⇒ 00:22:53.619 Henry Zhao: I don’t wanna say.
130 00:22:53.620 ⇒ 00:22:54.640 Amber Lin: Let’s do that.
131 00:22:54.760 ⇒ 00:23:02.000 Amber Lin: How do we? How do we have energy in a morning stand-up, or in late night? Stand up for people.
132 00:23:02.928 ⇒ 00:23:04.870 Henry Zhao: Just being mindful of it
133 00:23:06.800 ⇒ 00:23:09.000 Henry Zhao: and then over time, I think we’ll we’ll get better at that.
134 00:23:11.710 ⇒ 00:23:19.180 Henry Zhao: Because that that came to me because of Robert’s feedback. So once I got Robert’s feedback now, like when I see Josh in the meeting. I just try to
135 00:23:19.440 ⇒ 00:23:21.190 Henry Zhao: be like a little bit more
136 00:23:22.252 ⇒ 00:23:26.339 Henry Zhao: connected to the stand up and like I don’t multitask. I try to just
137 00:23:27.050 ⇒ 00:23:29.269 Henry Zhao: make sure things sound like they’re going well.
138 00:23:30.190 ⇒ 00:23:51.040 Amber Lin: I see. I think something that will make that easier is that I changed the meeting link so that the clients will be there on Monday and Wednesday. So that for the other stand ups we can just do it internally. So we don’t have to be aware every single day. But maybe just for those 2 days just to be aware when they’re there.
139 00:23:51.850 ⇒ 00:23:54.279 Henry Zhao: Yeah. And I think it’s also team collaboration. Where.
140 00:23:54.410 ⇒ 00:24:02.980 Henry Zhao: like, I think maybe some of his feelings on that were like when we when somebody asked a question like, maybe Amber, you asked like, who’s responsible for something? And nobody knew how to respond.
141 00:24:03.110 ⇒ 00:24:06.520 Henry Zhao: So that like comes across as low energy. Probably so I think
142 00:24:07.400 ⇒ 00:24:11.229 Henry Zhao: us helping each other out to fill in those awkward silences.
143 00:24:11.540 ⇒ 00:24:21.110 Amber Lin: I see. So it it’s coming off as know what we are doing, or have a solution to
144 00:24:21.870 ⇒ 00:24:27.579 Amber Lin: figuring that out displaying ownership.
145 00:24:27.760 ⇒ 00:24:28.300 Amber Lin: Yep.
146 00:24:28.300 ⇒ 00:24:32.720 Henry Zhao: So I think, when upper things that also comes as a consequence.
147 00:24:34.130 ⇒ 00:24:34.660 Amber Lin: Sorry.
148 00:24:35.310 ⇒ 00:24:41.189 Henry Zhao: Like, I think, as we figure out some of the other things up top like in this. Yeah, those also come naturally.
149 00:24:41.840 ⇒ 00:24:48.490 Amber Lin: Okay. Sounds good. So, Robert. Any points.
150 00:24:50.620 ⇒ 00:24:52.090 Amber Lin: Is Robert still here?
151 00:24:52.490 ⇒ 00:24:52.880 Henry Zhao: Well, thank you.
152 00:24:52.880 ⇒ 00:25:05.351 Amber Lin: Robert’s not here. So I also hear better aligning. I think one last point on communication is when deadlines are going to be missed
153 00:25:05.970 ⇒ 00:25:20.559 Amber Lin: or estimates change. I don’t think we communicate that that. Well, a lot of the times it’s clients ask a second time, and we’re like, Oh, sorry. That’s gonna take more time.
154 00:25:20.700 ⇒ 00:25:27.479 Henry Zhao: Like, should we just change the deadline on the task? Should we write a message? Should we use the slack channel like
155 00:25:27.820 ⇒ 00:25:33.620 Henry Zhao: if we know something is going to miss a deadline. How should we be communicating it? I think it’d be nice if we could establish a norm
156 00:25:33.810 ⇒ 00:25:38.000 Henry Zhao: and also communicate that norm of this is how we’re going to be communicating delays.
157 00:25:42.656 ⇒ 00:25:47.500 Amber Lin: We can’t. I think linear is internal, so they don’t get to see it.
158 00:25:47.620 ⇒ 00:26:07.760 Amber Lin: It sounds like slack is the best way. So right. Now, when I create tickets, I try to put the slack thread that it originally came from. So we can update them in that slack thread. And worst case, we’ll just tag them to say, Hey, this was a request. This is the deadline. Now.
159 00:26:07.930 ⇒ 00:26:08.999 Henry Zhao: Yeah, that’s really nice.
160 00:26:09.680 ⇒ 00:26:13.859 Amber Lin: Okay, update in slack. Right?
161 00:26:16.960 ⇒ 00:26:22.699 Amber Lin: It’s not update tag sake order.
162 00:26:26.260 ⇒ 00:26:33.000 Amber Lin: I think an issue with that is that sometimes we don’t have deadlines on the tickets, and so we don’t really know when it’s missed.
163 00:26:33.470 ⇒ 00:26:38.239 Amber Lin: because when I create it, I hear from the stakeholder. Oh, they kind of want it by the end of week.
164 00:26:38.350 ⇒ 00:26:48.339 Amber Lin: and I think we need to communicate before it becomes the end of week. Right? So if it’s due Friday and we can’t get it on Friday. We can’t tell them on Friday.
165 00:26:52.440 ⇒ 00:27:01.690 Amber Lin: How many days prior should we communicate that? Should we communicate like 3 days early a day early? What’s the timeline for that.
166 00:27:05.208 ⇒ 00:27:34.200 Demilade Agboola: I think we should be able to one, either, when we’re scoping, be able to push back on whatever timeline is being given. But if been able to, we’re in decision where we already have the timeline and we’re already trying to work towards it. But there is a delay. I think it’s important to be able to red flag it. And just I don’t know if we have calls that we don’t necessarily want to say that on. Maybe the calls Josh is on. If it’s a thing of
167 00:27:35.404 ⇒ 00:27:48.460 Demilade Agboola: being able to either write it in the ticket, or just being able to just say, Hey, this is potentially at risk of missing whatever deadline. And we state, whatever the reasons are.
168 00:27:48.460 ⇒ 00:28:18.430 Amber Lin: Okay, yeah, sounds. So it sounds like the 1st check is during scoping. Is the expectation. Reasonable? Second check is if we get another ad hoc task assigned to the same person. And then we should check if the deadline, and then maybe 3 days before, if we’re not completing it, we should tell them. And then one day, before we should tell them just how I know it’s a lot of checks, so I think we’ll it’ll just come up as like, oh, I can’t! I can’t do that ticket. I just have something else.
169 00:28:18.660 ⇒ 00:28:27.469 Amber Lin: So we’ll do that. I think one last thing is project dragging.
170 00:28:27.640 ⇒ 00:28:39.279 Amber Lin: How do we deal with that? It’s been a problem. I mean, it’s a common problem that occurs across all clients. I just want to see how this team wants to address that problem.
171 00:28:48.118 ⇒ 00:28:55.120 Awaish Kumar: I have like kind of suggestion. Any project look like foot
172 00:28:55.820 ⇒ 00:29:03.369 Awaish Kumar: like I wouldn’t say project, because there are some projects where we finish the task, and then new tasks come up, and we
173 00:29:03.770 ⇒ 00:29:06.239 Awaish Kumar: and incrementally work on them.
174 00:29:06.380 ⇒ 00:29:22.389 Awaish Kumar: But like for the I would say, for for some tickets hang on, for example, any task, or
175 00:29:23.711 ⇒ 00:29:27.229 Awaish Kumar: kind of something like calls project, which, for for example.
176 00:29:27.410 ⇒ 00:29:30.619 Awaish Kumar: which gets dragged more like for for, like
177 00:29:32.068 ⇒ 00:29:34.930 Awaish Kumar: more than one spend like 2 weeks.
178 00:29:35.090 ⇒ 00:29:37.006 Awaish Kumar: Then we should have an
179 00:29:37.590 ⇒ 00:29:42.749 Awaish Kumar: like kind of a personal auto meeting when we set the direction.
180 00:29:43.140 ⇒ 00:29:49.940 Awaish Kumar: So assess what we have done, and then, like kind of scope it again.
181 00:29:52.710 ⇒ 00:30:03.879 Awaish Kumar: So like, we see what was done. What is the context, what new knowledge we have, and based on that scope it again, and set new deadlines and everything.
182 00:30:07.840 ⇒ 00:30:12.430 Awaish Kumar: So that way, like we are, we are, we will be clearly defining the direction of the project.
183 00:30:12.640 ⇒ 00:30:15.280 Awaish Kumar: So it’s not just going on directionless.
184 00:30:21.890 ⇒ 00:30:44.199 Amber Lin: Yeah. And I think on that end, I do agree. A big problem is that the projects weren’t scoped that clearly from the start. A lot of them just came up. It was one ticket, and then it grew to a few tickets, and there was never a clearly scoped project per se, I feel like that’s what the case was for. For cogs, and I do want to improve that. And I think
185 00:30:44.200 ⇒ 00:30:56.489 Amber Lin: now that we see these projects, dragging as a good chance for us to rescope them and just see what are we really trying to accomplish? And then for any blockers or any risks, we should
186 00:30:56.680 ⇒ 00:31:12.209 Amber Lin: single them out so that I can help you guys chase after them earlier. I can involve. We can involve Josh to help get people to give us the information, as I think, for those blockers. As long as we are proactive enough.
187 00:31:12.706 ⇒ 00:31:23.909 Amber Lin: One, we might get it done, and 2. The client can’t really blame us if we already reached out. We’ve done all that we need to do like. It’s not on us. If we’re really blocked, and we’ve done everything we need.
188 00:31:27.427 ⇒ 00:31:37.890 Amber Lin: Any thoughts on there, I know, like this, this dragging has happened to everybody. So I just want to hear what your thoughts are where you think the solution is.
189 00:31:46.210 ⇒ 00:31:51.019 Henry Zhao: I think personally on my end, I feel like I’m still sort of on a ramp up phase or an onboarding phase.
190 00:31:51.020 ⇒ 00:31:51.530 Amber Lin: Yeah.
191 00:31:51.530 ⇒ 00:31:54.329 Henry Zhao: So I think pretty soon I should be able to
192 00:31:54.510 ⇒ 00:31:57.179 Henry Zhao: drag less, at least on things on my end.
193 00:31:57.600 ⇒ 00:31:59.950 Henry Zhao: and hopefully also have more bandwidth to help
194 00:32:00.400 ⇒ 00:32:03.270 Henry Zhao: team if there’s things dragging out that need help. Yeah.
195 00:32:05.890 ⇒ 00:32:10.370 Henry Zhao: But I felt I felt like a lot of my stuff got delayed because I’ve been still trying to catch up and.
196 00:32:10.370 ⇒ 00:32:11.000 Amber Lin: Right.
197 00:32:11.000 ⇒ 00:32:12.839 Amber Lin: Understand how things work with Eden and stuff like that.
198 00:32:13.320 ⇒ 00:32:14.580 Amber Lin: Yeah, Gotcha.
199 00:32:15.020 ⇒ 00:32:21.910 Amber Lin: Oh, any thoughts demode on Annie Vashav. Any thoughts there.
200 00:32:27.800 ⇒ 00:32:29.850 Demilade Agboola: Not not much from my end.
201 00:32:31.410 ⇒ 00:32:32.080 Amber Lin: Okay.
202 00:32:35.000 ⇒ 00:32:41.090 Amber Lin: Oh, Vasha, what do you think about this 1st sprint with us? How do you feel.
203 00:32:57.580 ⇒ 00:33:01.200 Amber Lin: Vasha? If you’re talking, you’re muted, I can’t hear you.
204 00:33:06.430 ⇒ 00:33:07.300 Amber Lin: Okay.
205 00:33:08.600 ⇒ 00:33:16.739 Amber Lin: maybe we have lost him. Anyways, I think this is a good stand up. I think we have a few takeaway takeaways. We can implement and
206 00:33:17.310 ⇒ 00:33:23.970 Amber Lin: I’ll take note of this and see we what we can change, and hope. I hope that next week will be even better.
207 00:33:27.780 ⇒ 00:33:28.410 Amber Lin: Alright.
208 00:33:28.410 ⇒ 00:33:29.750 Awaish Kumar: Okay. Great.
209 00:33:29.750 ⇒ 00:33:31.340 Amber Lin: Thanks. Everyone.
210 00:33:31.560 ⇒ 00:33:32.380 Awaish Kumar: Thank you.
211 00:33:32.600 ⇒ 00:33:33.239 Demilade Agboola: Thank you.