Meeting Title: PM Team Weekly Planning Sync Date: 2025-09-24 Meeting participants: Justin Breshears, Rico Rejoso, Amber Lin


WEBVTT

1 00:00:55.740 00:00:57.590 Justin Breshears: Howdy, Rico!

2 00:00:58.780 00:01:00.610 Rico Rejoso: Hi, Justine, how are you?

3 00:01:01.140 00:01:02.340 Justin Breshears: Good, man, how are you?

4 00:01:02.700 00:01:03.430 Rico Rejoso: Good.

5 00:01:07.790 00:01:08.930 Justin Breshears: Good deal.

6 00:01:10.890 00:01:12.299 Rico Rejoso: I was submitting the default.

7 00:01:12.870 00:01:17.749 Justin Breshears: Oh, it was good! They’re happy with us, renewing the contract.

8 00:01:18.120 00:01:19.490 Justin Breshears: All good things.

9 00:01:20.380 00:01:21.200 Rico Rejoso: Wonderful.

10 00:01:32.140 00:01:33.360 Amber Lin: Hello!

11 00:01:34.450 00:01:35.560 Justin Breshears: Howdy, Amber.

12 00:01:38.310 00:01:39.070 Amber Lin: I am.

13 00:01:39.780 00:01:47.770 Amber Lin: I am feeling my food coma, but let’s get started. What are the items we want to talk about today?

14 00:01:48.620 00:01:58.529 Justin Breshears: Well, I think y’all had some stuff, because I took up all the time yesterday, so… good sales item, so…

15 00:01:59.520 00:02:06.390 Amber Lin: Alright, let’s… let me share screen. It’s still the same notes from yesterday, so I’ll just be in that doc.

16 00:02:11.590 00:02:14.910 Amber Lin: Did that… Folk.

17 00:02:18.500 00:02:20.139 Amber Lin: Did that one.

18 00:02:24.010 00:02:33.259 Amber Lin: Let’s do these, and then we can do Remo last. How are both of your projects doing after we did the switch?

19 00:02:35.270 00:02:40.240 Rico Rejoso: For sales, right now, I think the pro- one thing is that we’re…

20 00:02:40.770 00:02:44.919 Rico Rejoso: Trying to get more tickets, since we don’t have anything on the backlogs.

21 00:02:45.100 00:02:51.799 Rico Rejoso: Not yet. So we’re depending on the, planning meeting every Monday.

22 00:02:52.750 00:02:55.899 Rico Rejoso: would delay some of the work, so it’s after Monday.

23 00:02:56.160 00:03:00.809 Rico Rejoso: We got Tuesday to plan out, since Justina is working part-time.

24 00:03:00.990 00:03:06.909 Rico Rejoso: And we don’t have enough hours to, you know, yeah, I mean, he works around 8 a.m. ESP.

25 00:03:08.050 00:03:21.860 Rico Rejoso: Or 9 a.m. EST, and it’s just up until 2 p.m, 3 p.m. EST, so not enough time for us to, you know, do a planning session as well by Monday, since we need to wait for the GPM planning by 3PM to 4 p.m. EST.

26 00:03:22.680 00:03:38.700 Rico Rejoso: So I think that’s one thing. But we do have, like, some tickets right now that we’re working based on the previous meeting as well. And right now, we’re, also transferring some tickets that we have from marketing and, content that were previously under linear theme modes.

27 00:03:38.920 00:03:49.240 Rico Rejoso: On AI, we’re doing good. We set up some of the tickets. Right now, we’re focused on grooming some, grooming more of the backlog, since we

28 00:03:49.240 00:03:59.409 Rico Rejoso: I mean, we need to check for the relevant tickets as well, since I think they’re just putting in a lot of tickets, and none were prioritized, so that’s one thing.

29 00:03:59.950 00:04:03.970 Rico Rejoso: Once we clean up the board, I think we can… You know,

30 00:04:05.010 00:04:08.830 Rico Rejoso: make sure that some of the tickets are within the OKRs, and we’re focused on it.

31 00:04:09.000 00:04:10.750 Rico Rejoso: Ending this quarter.

32 00:04:12.420 00:04:14.210 Amber Lin: Great.

33 00:04:15.090 00:04:24.929 Amber Lin: What about time allocations and time caps? How do you allocate points, and do we check the total points each week?

34 00:04:25.510 00:04:26.280 Rico Rejoso: Yes.

35 00:04:26.600 00:04:32.189 Rico Rejoso: St. Louis with sales, I based it on their, I mean, on their working hours, like, for.

36 00:04:32.650 00:04:37.579 Rico Rejoso: Brian, who work across departments from marketing, or from.

37 00:04:37.580 00:04:37.940 Amber Lin: content.

38 00:04:37.940 00:04:56.099 Rico Rejoso: to sales. It’s… we spread it, it’s, like, 2020, but, I try to make it within 15 to 18 points every week, so that he has, like, 2 points, 1 point buffer. But if in case we went overboard, we will be… I mean, I created an SOP for ad hoc.

39 00:04:56.600 00:05:04.149 Rico Rejoso: On how we will do, or, you know, when we encounter ad hoc stuff that is not within our planning or within their bandwidth.

40 00:05:04.430 00:05:12.160 Rico Rejoso: I also presented it to them, and I think we haven’t used it yet, since everything’s within their bandwidth for this week.

41 00:05:12.380 00:05:21.640 Rico Rejoso: But we just came prepared for it. For the AI team, I used the information from the Notion page you shared with me.

42 00:05:21.640 00:05:22.050 Amber Lin: Mason.

43 00:05:22.050 00:05:23.830 Rico Rejoso: We’re meeting with Sam, we’re in…

44 00:05:23.940 00:05:27.800 Rico Rejoso: We set up a gap for each team member, like.

45 00:05:28.000 00:05:33.469 Rico Rejoso: 10 hours, 10 hours, 15 for them, and I just want to make sure we stay within those.

46 00:05:33.940 00:05:40.949 Amber Lin: Okay, yeah, sounds good. Any… knows any… Feedback from you, Justin?

47 00:05:41.050 00:05:43.750 Amber Lin: On how we’re handling the internal teams right now?

48 00:05:44.460 00:05:54.989 Justin Breshears: Yeah, I think that was the big one, was just, like, handling when somebody makes a request to, like, the AI team or whatever, you know, making sure that, you know, there’s bandwidth within the team, and if there’s not, like.

49 00:05:55.210 00:06:04.820 Justin Breshears: you know, having a proper process for qualifying that request and making sure that, you know, it’s something that should prioritize over something else.

50 00:06:05.360 00:06:12.320 Justin Breshears: So… that, I would love to see that SOP that you created over that, but…

51 00:06:12.650 00:06:14.229 Justin Breshears: Oh yeah, there you go. You got it.

52 00:06:14.900 00:06:16.330 Justin Breshears: You just want me to quote up.

53 00:06:17.560 00:06:23.950 Rico Rejoso: Sure, I wasn’t able to use the format that you sent, since I have, like, a format that I use on operations, but I’ll…

54 00:06:24.060 00:06:31.200 Rico Rejoso: Because I made it quick so I can present it to them immediately, so that it’ll form… but I’ll change it after, Ms.

55 00:06:32.270 00:06:33.020 Justin Breshears: All good.

56 00:06:33.840 00:06:46.139 Justin Breshears: Yeah, let me take a look at that, and I can provide any feedback on it, but the main thing is just making sure, like, you treat it like a project, like, with a client, right? But your client is UTAM, basically. So you’re, you know, if you need

57 00:06:46.510 00:06:55.240 Justin Breshears: have a discussion around priority, then yeah, you’re checking with the client, quote-unquote, all the time. So, but I think you’ve got that all figured out, so… good job there.

58 00:06:55.240 00:06:56.750 Rico Rejoso: Thank you.

59 00:06:59.230 00:07:00.220 Amber Lin: Okay.

60 00:07:00.350 00:07:05.339 Amber Lin: And Justin, how is your… your two new teams doing?

61 00:07:05.710 00:07:09.860 Justin Breshears: Good! I have been really working on…

62 00:07:10.380 00:07:17.790 Justin Breshears: the… basically, standards for, like, managing linear a lot with my teams, so…

63 00:07:18.310 00:07:37.739 Justin Breshears: I have found that I don’t think that we’re very diligent in how we’re tracking our work on linear, so I’ve been trying to clean all that up, clean up backlogs, between all three teams, and making sure that, like, every bit of work we’re doing is being tracked there.

64 00:07:37.980 00:07:43.170 Justin Breshears: Because the reason for that is, one, I want, you know, to be able to have, like.

65 00:07:43.350 00:07:56.029 Justin Breshears: an accurate list of work that we’re doing for clients, for sure, but I also want to create a status report template that can be automated. That’s one of the things that I’ll probably run by the AI team.

66 00:07:56.030 00:08:04.440 Justin Breshears: Of how we can do that, and we need, like, you know, accurate linear data, probably, to pull from… for that status report eventually.

67 00:08:04.910 00:08:19.389 Justin Breshears: So, I’ve been really big on, like, making sure everything’s tracked, you know, making sure we have capacity planned, and holding people to deadlines and prioritizing the right work. So, it’s been going well.

68 00:08:19.390 00:08:30.509 Justin Breshears: we just had a really good conversation with Default. That has nothing to do with anything that I’ve done, but they wanna… they wanna renew their contract, so, we have a new contract for…

69 00:08:30.560 00:08:34.220 Justin Breshears: It’s gonna get finalized through the end of the year, so that’s good.

70 00:08:35.200 00:08:35.919 Amber Lin: Okay.

71 00:08:36.470 00:08:37.260 Justin Breshears: Awesome.

72 00:08:38.859 00:08:40.350 Justin Breshears: I think we’re… Interlude?

73 00:08:41.549 00:08:51.359 Justin Breshears: Interlude is one where, like, yeah, we just needed to really clean up how we were managing that one, but for all intents and purposes, it’s… it’s going well.

74 00:08:51.710 00:08:52.390 Amber Lin: Okay.

75 00:08:54.070 00:09:07.189 Amber Lin: Since you mentioned the status report template for the AI team, I do want to go over the third item I mentioned briefly yesterday of what the AI team has built for us, and what needs our review or improvement.

76 00:09:07.330 00:09:08.490 Justin Breshears: Yeah, let’s take a look at it.

77 00:09:08.490 00:09:17.689 Amber Lin: Yeah, so I separated it out by the source, so there’s stuff in Linear, stuff in Slack, and in the platform. So…

78 00:09:17.800 00:09:28.989 Amber Lin: I think starting at linear, that one, I think, is… I think it’s updated needs and needs review, so to change the previous estimates.

79 00:09:29.240 00:09:33.689 Justin Breshears: Oh, that’s the historical, like, changing the… the story pointing to…

80 00:09:33.690 00:09:34.100 Amber Lin: for the U.

81 00:09:34.100 00:09:35.160 Justin Breshears: with our new… okay, yeah.

82 00:09:35.500 00:09:44.549 Amber Lin: Yeah, and they also made, once upon a time, they made a grooming agent, so I think it’s still only available in the AI team, but if you

83 00:09:44.590 00:10:01.420 Amber Lin: type in grooming, then they, based on our ticket standards, gives feedback. However, the ticket standards that they use are not updated, so we need to give them updated linear ticket evaluations, not only the standards, but also how to grade a ticket, so…

84 00:10:02.730 00:10:04.469 Rico Rejoso: Did we do the grooming? I’m sorry.

85 00:10:06.120 00:10:08.519 Rico Rejoso: How do you use the grooming agents on Linda?

86 00:10:09.730 00:10:14.129 Amber Lin: I think it’s still only available in the AI team.

87 00:10:14.960 00:10:21.949 Amber Lin: But… let me… let me see… So… let me…

88 00:10:22.890 00:10:25.340 Amber Lin: Let’s see if it pops up here.

89 00:10:28.300 00:10:29.569 Amber Lin: This one.

90 00:10:31.540 00:10:32.760 Amber Lin: Oh, sorry.

91 00:10:40.990 00:10:43.040 Amber Lin: Oh, this is new, I see.

92 00:10:43.220 00:10:51.699 Amber Lin: Back into here, say, if it’s… Let me try.

93 00:10:59.910 00:11:02.440 Amber Lin: Oh well, I guess we’ll have to ask them.

94 00:11:03.020 00:11:04.690 Amber Lin: Okay, but it is possible.

95 00:11:04.690 00:11:05.269 Rico Rejoso: That’d be helpful.

96 00:11:05.270 00:11:15.630 Amber Lin: used it in the past, but, it will be helpful, especially if they make this bulk grooming, and then we can get, like, a valuation of that.

97 00:11:15.820 00:11:20.169 Amber Lin: And then in Slack, what we have right now is…

98 00:11:21.570 00:11:35.999 Amber Lin: And Justin, that’s similar to the status report template you were talking about. We already, we made these… they send it in the project management every Friday, so they send…

99 00:11:36.170 00:11:55.049 Amber Lin: something like this. So this is an overview of just the tickets, of how many things were completed, and then they have a email summary, which currently uses a template I gave them a few months, like, two months ago. Key wins, projects, their progress, what’s left.

100 00:11:55.190 00:11:58.539 Amber Lin: Next sprint, velocity, risk. And…

101 00:11:58.540 00:11:59.570 Justin Breshears: I love this.

102 00:11:59.570 00:12:06.069 Amber Lin: And if you could, left some review on what templates, we can use.

103 00:12:06.330 00:12:23.460 Amber Lin: And this is sent every Friday, and definitely… not only the tickets summary here can be improved, also the email here can be improved. For example, we don’t need ticket titles in the update, but I will… I would like to have some reviews there.

104 00:12:24.520 00:12:26.200 Justin Breshears: Absolutely. Yeah, that’s great.

105 00:12:26.200 00:12:27.410 Amber Lin: That’s, let me.

106 00:12:27.410 00:12:37.979 Justin Breshears: And, like, we probably need to tweak, like, the one for Insomnia Cookies, because that way we send out the… yeah, we send out the updates on Thursdays for that one, so that would be great.

107 00:12:38.950 00:12:40.339 Justin Breshears: We can tweak that.

108 00:12:41.980 00:12:43.000 Amber Lin: Alright.

109 00:12:44.080 00:12:45.370 Justin Breshears: And have it look at, like.

110 00:12:45.370 00:12:47.110 Amber Lin: Like, the previous…

111 00:12:47.110 00:12:51.180 Justin Breshears: Friday, all the way to… You know, Thursday.

112 00:12:52.410 00:13:06.269 Amber Lin: Yeah, and then another thing is that there are meeting quality score ratings. So I think by now, you’ve probably seen the meeting summaries that it sends after each meeting. So, for example, this.

113 00:13:06.270 00:13:17.700 Amber Lin: There’s a summary of what’s discussed here, which we can also update this template, and I think on the bottom, which I have not used, at the bottom, there’s a meeting summary score.

114 00:13:17.700 00:13:21.880 Amber Lin: who… how do we do… I just want to say…

115 00:13:21.880 00:13:25.489 Justin Breshears: Which I don’t love. I don’t do it.

116 00:13:25.490 00:13:38.529 Amber Lin: And if we can… if we should remove it, if we should turn it into weekly as an over… overall view based on all of the meetings, we can talk about what we want to do there.

117 00:13:38.530 00:13:49.689 Justin Breshears: I don’t think it’s super useful, because, like, today, we were laughing about my stand-up, for Insomnia. We started off the stand-up, like, kind of just chit-chatting, right?

118 00:13:49.690 00:13:59.349 Justin Breshears: And the AI, like, dinged us and was, like, off-topic, you know, for… for the meeting, like, at the beginning, and I’m like, okay, but…

119 00:13:59.700 00:14:00.490 Justin Breshears: like…

120 00:14:01.160 00:14:09.959 Justin Breshears: being human and having some conversations that aren’t necessarily, like, work-related is, like, totally okay and something we should be doing, right? So…

121 00:14:09.960 00:14:10.369 Amber Lin: And that…

122 00:14:10.370 00:14:10.720 Justin Breshears: I agree.

123 00:14:10.720 00:14:30.409 Amber Lin: We can also score. If you want to improve the scoring standards, that’s something we can do. I think it’s mostly targeting, okay, did everybody participate? Did we have an agenda? Do we have follow-ups? And did we confirm with the client on what we heard? I think those are important.

124 00:14:30.410 00:14:46.429 Justin Breshears: Yeah, I think that since we have it, it’s a great thing to just keep. Like, I wouldn’t just, like, delete it, right? I don’t know how much more effort I would put into, like, developing it, than where it is right now, just because I don’t find it, like, super helpful, but…

125 00:14:47.040 00:14:52.909 Justin Breshears: I’m also not the end-all, be-all on that. What is everybody else’s thoughts?

126 00:14:53.910 00:14:58.600 Amber Lin: I don’t use it, so… I have not looked at it at all.

127 00:14:59.360 00:15:00.269 Justin Breshears: Oh, there you go.

128 00:15:00.410 00:15:01.240 Rico Rejoso: Yeah.

129 00:15:01.240 00:15:19.399 Amber Lin: we aren’t looking at it, I bet you nobody is. But it’s more of should we be, and what is something we can take away from that, even as a weekly review of how we conduct meetings overall? Like, is there something that should be improved on? Maybe that’s the value there, I don’t know.

130 00:15:19.400 00:15:32.329 Justin Breshears: Why don’t we start there, then? I like that, where let’s see if we can look at it from a more aggregate view than just, like, meeting by meeting. Let’s see if we can, like, look at it from a weekly basis, and then see, you know, where we’re lacking. I do like that.

131 00:15:34.750 00:15:48.500 Amber Lin: Alright, and then on the platform, there’s a meeting summary that I remember, Rico, you were sending for default, so it was the key conclusions, and then action items…

132 00:15:48.820 00:16:01.939 Amber Lin: So there’s… if we can have… I’m asking the team if they can put that summary into our platforms for… so for each meeting, we can generate a summary, or we can just update it in…

133 00:16:02.370 00:16:10.130 Amber Lin: In here… And then…

134 00:16:10.270 00:16:19.720 Amber Lin: They also wanted our feedback on how the linear tickets are generated in the platform per meeting, so this… this function.

135 00:16:19.720 00:16:33.790 Amber Lin: I also don’t use it, because it’s not very accurate or helpful, but you can take these tickets and directly create them, and they will show up in linear. So that is a possibility that we can use.

136 00:16:33.990 00:16:42.999 Amber Lin: Also, there’s another item that creates linear tickets. So, for example, here we can… Create the different…

137 00:16:43.810 00:16:48.430 Amber Lin: You can edit it, and then you can publish it to the linear board.

138 00:16:48.840 00:16:55.920 Amber Lin: And then additionally, there’s this other one that bulk create tickets from…

139 00:16:56.300 00:17:01.030 Amber Lin: From, say, a Notion doc or multiple transcripts.

140 00:17:01.720 00:17:05.339 Amber Lin: So that’s something that they would also like to have reviews on.

141 00:17:10.230 00:17:16.540 Amber Lin: I think that one’s done. The meeting namings, I remember you mentioned that to them.

142 00:17:17.510 00:17:33.219 Amber Lin: Okay… Oh, one last question of, do you guys use this… client hub chat, so…

143 00:17:33.440 00:17:41.749 Amber Lin: Say, for instance, under, let’s say under insomnia, where all the insomnia

144 00:17:41.920 00:17:46.190 Amber Lin: meetings live. Have you guys chatted with this agent?

145 00:17:46.610 00:17:47.410 Justin Breshears: Yes.

146 00:17:47.640 00:17:51.259 Amber Lin: Okay, sounds good. I have not, so that’s something I need to do.

147 00:17:51.520 00:17:54.689 Justin Breshears: I mean, I’ve used it to ask for, like, meeting summaries and things.

148 00:17:55.360 00:18:03.129 Amber Lin: Oh, I think it’s… it’s different in terms of that there’s a chat you can have directly with

149 00:18:03.790 00:18:15.530 Amber Lin: a singular meeting, or you can have it with the client hub, which means all of our past meetings, and I do think it also has access to other…

150 00:18:15.920 00:18:21.880 Amber Lin: So let’s say generate client report. Okay, I guess they have… issues.

151 00:18:22.270 00:18:25.029 Amber Lin: I’ll try for ABC…

152 00:18:27.680 00:18:43.360 Amber Lin: So they have access to maybe the repo as well, so they… this would have more context if we need broader, higher… higher… higher level updates, such as, oh, the wins so far on what we have been working on.

153 00:18:44.630 00:18:54.590 Amber Lin: And I would say that… I would say that this is… Half accurate.

154 00:18:55.320 00:18:58.979 Justin Breshears: I would say… Based on my just-now…

155 00:19:00.290 00:19:03.460 Justin Breshears: Using it, is not accurate.

156 00:19:03.460 00:19:03.890 Amber Lin: Huh.

157 00:19:03.890 00:19:12.010 Justin Breshears: I’m on the default one, and I said, give me a summary of the work we’ve done for this client, and it started talking about ABC.

158 00:19:12.470 00:19:14.000 Amber Lin: Mmm, no.

159 00:19:14.190 00:19:20.289 Amber Lin: Yeah, okay, I’ll let them know. It is not accurate on ABC either. Alright, so that’s that.

160 00:19:20.910 00:19:29.899 Amber Lin: Looked at it, and then Awash sent me the ticket tagging…

161 00:19:31.330 00:19:35.680 Amber Lin: Thing that he wanted us to review…

162 00:19:36.110 00:19:39.989 Amber Lin: Oh, also, what about what Robert sent? About this?

163 00:19:40.610 00:19:41.870 Amber Lin: Any thoughts?

164 00:19:42.180 00:19:45.260 Justin Breshears: I haven’t gotten a chance to look at it yet, but I want to.

165 00:19:45.370 00:19:46.410 Amber Lin: I’ll just put it at the.

166 00:19:46.410 00:19:58.710 Justin Breshears: Definitely, yeah, something that we can take a look at and incorporate into our processes, but, like, we’re already kind of tackling a lot of that. But yeah, if that’s something, like, if we find something in there that we like, we can definitely steal it.

167 00:20:06.250 00:20:06.920 Amber Lin: Okay.

168 00:20:07.250 00:20:17.220 Amber Lin: And then scrolling up to… Way sh… Where is his comment?

169 00:20:20.160 00:20:21.120 Amber Lin: What?

170 00:20:40.840 00:20:46.549 Amber Lin: Where did I add you in the things that we need to… oh, here, this one.

171 00:20:47.830 00:20:49.559 Justin Breshears: I was gonna say, don’t ask me, I have…

172 00:20:50.850 00:20:54.940 Justin Breshears: Realize that I’m gonna have about 14 million slacks a day, so…

173 00:20:54.940 00:20:55.870 Amber Lin: Yeah.

174 00:20:56.090 00:21:02.050 Amber Lin: This one, so, these are…

175 00:21:02.460 00:21:08.489 Amber Lin: Essentially, in linear, we have these labels that we can add to things.

176 00:21:08.650 00:21:27.590 Amber Lin: And I currently, I only… for my projects, I only have one tag that I use commonly, it’s just needs grooming. But for, say, for data work, there could also be spike ticket, modeling ticket, strategy ticket, viz, visualization ticket.

177 00:21:28.120 00:21:36.350 Amber Lin: And for product analytics, Which she hasn’t filled in yet. But for AI, for instance, there’s… .

178 00:21:37.900 00:21:42.010 Justin Breshears: What is the purpose of these labels?

179 00:21:42.010 00:21:52.799 Amber Lin: We need to have a clear understanding of, one, what type of tasks we’re getting overall, and also for a clear visual

180 00:21:53.120 00:21:59.579 Amber Lin: idea of, okay, this is a AE ticket, and okay, yeah, I’ll go to Devilate.

181 00:22:01.680 00:22:04.650 Amber Lin: So just clear categories.

182 00:22:05.080 00:22:05.810 Justin Breshears: Okay.

183 00:22:06.040 00:22:07.730 Amber Lin: What are your thoughts on it?

184 00:22:08.090 00:22:10.940 Justin Breshears: I mean, it’s gonna require us to be buttoned up.

185 00:22:11.270 00:22:20.850 Justin Breshears: Yeah, it’ll be required us to be buttoned up on, like, how we create tickets, because it’s only helpful as long as the data is actually accurate, right? So if…

186 00:22:21.040 00:22:24.850 Justin Breshears: People are creating tickets and not using these labels, then we can’t really…

187 00:22:25.080 00:22:28.899 Justin Breshears: trust the data. So, I… I hesitate on…

188 00:22:29.690 00:22:35.200 Justin Breshears: Requiring something like that, where it’s very dependent on everybody doing it well every time.

189 00:22:35.200 00:22:49.240 Amber Lin: So there should be a recommendation, and we could say every grooming, we… because we run on one week sprint, so every week we do a grooming, and then maybe we can add in some labels at grooming, instead of.

190 00:22:49.240 00:22:56.670 Justin Breshears: So, one question I have is, can we make… Like, fields requirements in linear?

191 00:22:56.720 00:22:58.129 Amber Lin: I don’t think so.

192 00:22:59.070 00:23:09.509 Justin Breshears: Because that would be really helpful to make all the fields that we need to have requirements. Because then I would trust it, because then you can’t create a ticket without these labels, right?

193 00:23:09.510 00:23:10.220 Amber Lin: Huh.

194 00:23:11.220 00:23:14.360 Justin Breshears: So, maybe we need to do some research on that.

195 00:23:15.840 00:23:19.319 Amber Lin: Gee… nope, not that,

196 00:23:25.090 00:23:28.900 Amber Lin: The only required field is project name. Project name.

197 00:23:33.030 00:23:34.050 Amber Lin: Yeah.

198 00:23:37.750 00:23:39.060 Amber Lin: Can’t do that.

199 00:23:41.340 00:23:42.280 Amber Lin: Okay.

200 00:23:42.380 00:23:43.790 Amber Lin: So, what…

201 00:23:43.790 00:23:46.830 Justin Breshears: Back to where you just were, in that Google search.

202 00:23:47.040 00:23:51.210 Amber Lin: Field requirements.

203 00:23:55.710 00:24:00.869 Justin Breshears: Scroll down… Can we, yeah, click on that Reddit link.

204 00:24:06.160 00:24:10.300 Amber Lin: Hmm… -

205 00:24:14.960 00:24:16.320 Justin Breshears: I guess you need to, like.

206 00:24:17.010 00:24:20.400 Justin Breshears: Shoehorn it with a third party, that’s not ideal.

207 00:24:20.770 00:24:22.030 Amber Lin: Yeah.

208 00:24:22.030 00:24:22.780 Justin Breshears: Okay.

209 00:24:24.250 00:24:27.510 Amber Lin: I mean, we… Cush…

210 00:24:27.950 00:24:34.890 Amber Lin: tell them that we’ll try to add labels. I don’t… what do you think is the… I agree…

211 00:24:34.890 00:24:36.610 Justin Breshears: It’s just, like, what’s the benefit.

212 00:24:36.610 00:24:37.769 Amber Lin: I’m seeing for the…

213 00:24:37.770 00:24:55.089 Justin Breshears: amount… yeah, what’s the benefit for the amount of effort that we’re asking people to do? Like, I know individual tickets… Yeah, individual tickets, it’s not a lot of effort, but, like, we are requiring, like, for the data to be useful, we’re requiring everybody to be buttoned up on that, and so, like, what is the overall benefit that we’re seeing

214 00:24:55.460 00:24:57.230 Justin Breshears: Of doing that, you know?

215 00:24:58.880 00:25:00.199 Justin Breshears: I guess that’s my question.

216 00:25:00.380 00:25:14.630 Amber Lin: Yeah, so let’s… let’s write a wish… Push back on… What is the benefits… Versus…

217 00:25:22.570 00:25:23.380 Justin Breshears: Aha!

218 00:25:23.570 00:25:24.760 Justin Breshears: I found it.

219 00:25:25.460 00:25:26.230 Amber Lin: Huh.

220 00:25:27.340 00:25:29.290 Amber Lin: What is it? You want to share a screen?

221 00:25:29.310 00:25:31.410 Justin Breshears: Yeah.

222 00:25:31.410 00:25:32.160 Amber Lin: Cheer.

223 00:25:39.590 00:25:42.910 Justin Breshears: All you gotta do is… Install this.

224 00:25:43.880 00:25:44.595 Amber Lin: Oh…

225 00:25:46.170 00:25:54.030 Amber Lin: Oh, I think Uten will be very interested in this. I’m just concerned for security reasons, but I don’t think it’ll be that big of an issue, but…

226 00:25:54.030 00:26:01.389 Justin Breshears: Well, let’s… well, yeah, let’s have somebody who has that mindset to… to vet it before we require it, but…

227 00:26:01.390 00:26:01.850 Amber Lin: Let me…

228 00:26:01.850 00:26:07.499 Justin Breshears: I mean, it’s on the Linear website, so I would imagine that it’s, like, vetted by Linear.

229 00:26:11.140 00:26:15.009 Justin Breshears: Good call out. Okay, let me send this link.

230 00:26:16.180 00:26:16.820 Amber Lin: Yeah.

231 00:26:18.090 00:26:21.700 Justin Breshears: our channel… There you go.

232 00:26:23.820 00:26:28.129 Justin Breshears: Yeah, take that, run with it, see if that’s an option.

233 00:26:28.420 00:26:34.460 Justin Breshears: Because I like that for, like, all the minimum requirements, right? Like, we want to have… you know.

234 00:26:35.640 00:26:40.459 Justin Breshears: due date, priority, like, assignee, like, all of those, I think, should be required.

235 00:26:40.460 00:26:43.300 Amber Lin: Right now, make our lives easier down the line.

236 00:26:43.420 00:26:44.020 Justin Breshears: Yeah.

237 00:26:44.020 00:27:02.460 Amber Lin: Okay, last thing on the agenda is Remo’s start. I did write the things that I will be doing, namely project management plan, which includes a lot of the fields on how we’re going to manage this project, resources, stakeholders, and then the sprint schedule.

238 00:27:03.240 00:27:13.449 Amber Lin: Other than that, I have a… we have a meeting with the clients tomorrow. I just have not gotten time to do the Remo stuff yet.

239 00:27:15.110 00:27:24.169 Justin Breshears: That’s alright. I would just ask, can you just document everything that you do, step by step, and then we can review, like, the kickoff process, because we really need to, like…

240 00:27:24.340 00:27:29.720 Justin Breshears: review that as a team and make sure that we, you know, are doing what we need to there.

241 00:27:29.760 00:27:44.660 Justin Breshears: because that’s kind of the next step, like, I’m seeing the STD process come together now, okay, now the next step would be, like, project initiation, right? Let’s really do a deep dive there, and then the actual, like, kickoff of the client. Because, like, in Remo’s case, like, you have a pretty set…

242 00:27:44.820 00:27:49.129 Justin Breshears: scope and deliverables. This’ll be a really good one to test, like.

243 00:27:49.280 00:27:56.449 Justin Breshears: okay, like, we kick off with the client, we do some discovery, we build out a backlog, and then we, like, go to it, you know, get it done.

244 00:27:56.920 00:28:02.949 Justin Breshears: Better than all these, like, ad hoc ones. Like, default’s hard because it’s, like, so random. Insomnia’s hard, it’s so random, you know?

245 00:28:03.080 00:28:07.760 Justin Breshears: I want to really use Remo as a guinea pig, because it’s actually, like, kind of defined, you know?

246 00:28:11.380 00:28:14.679 Justin Breshears: So yeah, just document everything you’re doing, and then we’ll review.

247 00:28:15.720 00:28:16.970 Amber Lin: Gosh, okay.

248 00:28:20.720 00:28:26.419 Amber Lin: Right, I’m just adding owners to the action items from this meeting, and that should be all.

249 00:28:27.210 00:28:28.050 Justin Breshears: Awesome.

250 00:28:28.050 00:28:29.450 Amber Lin: Alright, thanks everyone.

251 00:28:29.450 00:28:31.890 Justin Breshears: I kind of told y’all I appreciate y’all.

252 00:28:32.360 00:28:33.990 Justin Breshears: Thanks for all the work that you do.

253 00:28:35.160 00:28:38.129 Amber Lin: Well, thank you for being on the team. I’ll see you tomorrow.

254 00:28:38.520 00:28:39.530 Rico Rejoso: Thank you so much, As.

255 00:28:39.530 00:28:41.030 Amber Lin: Thanks. Bye.