- Duration: 70 min
- Platform: zoom
- Source: Read.ai 01JFJKJ2MNBV8Z5G24X84R83QQ (https://app.read.ai/analytics/meetings/01JFJKJ2MNBV8Z5G24X84R83QQ)
Transcript
[Rafael Bruno]: Hey, guys. Hey, what’s going on? [UNKNOWN_SPEAKER]: What’s up, Ben? Hey, guys. OK. [Michael Houck]: So Ruzvon will not be joining us for this. I think this meeting, just us, at least for now. He’s also heads down some Scraper stuff. So this is our first one of these. Basically, it’s pretty normal for engineering teams to do this. We haven’t done it, but I think now is the right time for us to start doing it because we’ve sort of made it through multi-month sprint of moving the database, fixing the bugs, and sort of moving back to forward-facing, user-facing feature work. So it makes sense for us to sort of transition to this more traditional model where we do this meeting at the end of every sprint. So sprint ends Sunday, and new sprint starts on Monday. We have our normal weekly planning and check-in meeting on Monday. Ever done one of these like sprint retros and explicit sprint planning meetings where we look at the scope of what’s going to be included in the next sprint, what we want to deliver, and what tasks will get us to being able to deliver that and making sure that everyone has a full workload but isn’t overworked sort of going into that next sprint. So we’re going to start doing these every two weeks. Rafael is going to lead the meeting, so I’m just going to kind of be here hanging out answering questions and really two parts of it. So the first part is sort of looking at our current sprint that we’re finishing up, identifying, you know, what went right, what didn’t go right. And also, of the things that are not completed, what do we think we’re going to be able to complete? And then the second half of the meeting, we’ll be moving on looking at next sprint and being like, okay, we know here’s what we want to accomplish. Do we have the right tasks in the sprint to be able to accomplish that, and are they kind of scoped and prioritized correctly? So I’ll turn it over to Rafael, and he can get us started on the first part of that. [UNKNOWN_SPEAKER]: Let me share my screen here. Can you guys see? Yeah. Okay. [Rafael Bruno]: So here we have the tasks for the current sprint. One thing that we can see is that, not looking here, but looking here, we accomplished basically 70% of what we have planned. I believe that looking at the history that we have here, this is like, a medium result, we have done better in the past, but we also have done worse. So it’s kind of like in the middle. Also looking here above the desks. How this is like one question, can I see like the projects that those tasks are related because just looking here, that I can see like this is from referrals, this is from campaigns, this is from groups, but there are a lot of other tasks here that are not related with a project. So I’m not really sure how to group to understand what we’ve accomplished on the sprint. [Michael Houck]: Yeah, so a lot of the tasks in this sprint were not related to a specific project. They were just kind of a lot of the Scraper stuff was just finishing up, you know, unrelated Scraper things. And there were also a lot of random tasks that got moved into this sprint. Uh, one thing I would say, if you want to group it is to click on the little kind of like, I don’t know, like book icon in the top right corner. [UNKNOWN_SPEAKER]: Top right. Uh, what icon? [Mehul Jariwala]: What? [UNKNOWN_SPEAKER]: What? [Rafael Bruno]: Did you said something Sid? [UNKNOWN_SPEAKER]: I don’t think so. [Rafael Bruno]: You said to click. How have you said to click on the top right icon? Yeah, I don’t know. I don’t know what it is. It’s that one right there. Yeah, so if you go down now and you see you can look at this by person by label by priority. I see here. Yeah. Of the projects, the projects. So basically, project related things. We had the content queue and the campaigns, I think that seed and mail who are working on that. We other had other tests regarding referrals. It was a test test the referrals flow end-to-end that I finished and something related with groups that I think that Sid also finished. So I think that this sprint could be categorized by something that we were finishing referrals and groups, basically, and starting other tasks regarding the projects of the campaigns and the content queue. Now, I’m not sure if I pass the word to everyone so everyone could set something that they’ve accomplished. Do you think this would be positive, Hauk? Yeah, I think that’s fine. [Michael Houck]: If anyone wants to call out things that kind of block them from getting things done, so we can dig into those. And also anything that they want to flag that went well, happy to talk about that too. [Rafael Bruno]: I have two topics here that I would like to discuss on this part of the meeting. One is everything that we think that we did right. Like, oh, this time I tried to do this thing and I think it worked. So I think we should repeat that for the next sprints. And the other thing is what you guys think that we need to improve. Like, oh, this is not good. Like it’s example. It’s taking too much to read someone, or sometimes I get blocked and it takes like one or two days to get unblocked. But just to put the topics of things that we should discuss. [Michael Houck]: Yeah, anyone, Sid, Mehul, or Rafael, if you want to kick it off, any of you guys, feel free. [Rafael Bruno]: Okay, so the first topic of what I accomplished that it’s positive, flow, we, we had that in the past, but it was hard to see to track stuff because we are moving from the v2, v1 to v2. So I think that accomplishing that it will create a good value to to the project. And once you put it in production. So this is one thing that I think I think it was good. How about you, Mehul? [Mehul Jariwala]: Yeah, I guess for my side, I would say it’s good that the referral project was good, group project was here and there. We were missing something, but I guess that also we finished it with a really quick manner. But just one thing to like, so whenever you implemented the backend API, or when you change something on backend API, right? So my recommendation would be like, if it is good, like if you can just like have the details of information, like which field will be mapped to which UI part of it, because I might not need to know about [UNKNOWN_SPEAKER]: that. [Rafael Bruno]: Take some notes here. [UNKNOWN_SPEAKER]: Yeah. [Mehul Jariwala]: I mean, so when you, when you’re designing the API, right. So maybe there are the few missing piece of information, uh, which was there. Uh, I mean, it’s happened to me a lot. Then, uh, I mean, uh, UI was have something and then API was, uh, I mean, those parameter was missing. So, I mean, if it is good, like, I mean, just, just the feedback, we are already doing good tests, just if we can improve this, that that really help us for me to like indicate it really quickly. I mean if you need before creating the API if you need any help I will be available like we can discuss it because those are the parameter that needed from the windows are the field that needed from the front end in order to show to the UI. [Rafael Bruno]: Okay so this is the topic that you think we need to improve. Is there anything else that you also think that we should improve? [Mehul Jariwala]: No, that is the only thing. I guess one more thing was, I’m not sure like maybe that will be time consuming. We definitely need to have code reviewer, but maybe we can take a look at sometime later. I just wanted to bring the point. Or we can use any of the GitHub tools that provide auto code reviewer part of it. Like system could really take a look at that. Yeah, that’s only two things. [Rafael Bruno]: How about things that we’ve, we’ve done right? Do you think there is something that we should be repeating on the next cycles? [UNKNOWN_SPEAKER]: I guess. [Mehul Jariwala]: No, I guess it’s good. Like, if we if we repeat the same thing, like, generally, what happened, like Rafael, you send me the sensor of it, like those are the this will be the new API that I have created. And this is a payload that that we that we have. So if we can repeat those, the when, when you’re creating the introducing new API, that that will help to work faster. Okay, because sometimes sometimes what happened, let’s say if your days and and you send something to me, my day started, so I started working on it. And then if I need some question here and then then I need to wait until like you wake up. Just wanted to highlight on that. If you provide the details of information, that will be helpful. [UNKNOWN_SPEAKER]: That’s it. [Rafael Bruno]: One moment. Okay, how about you Sid? What do you think we’ve done right? And what do you think we need to improve? [sid]: Yeah, I think in the last couple of sprints, when it comes to launching, I think we have done a good job in getting on like in our team spirit, we have done a good job in making sure that we deliver on the on the date, of course, we have missed it by one day today here and there. But at least we have shown our participation and getting like pushing ourselves and making sure that we at least try our best to deliver. So that is one good thing, which I’ve often seen those don’t. I mean, other other people other days, they are usually not proactive, but it’s good that we have all the three of us are proactive. So that is one good thing. And I believe we should keep doing that in the in the future sprints also in the coming months. [UNKNOWN_SPEAKER]: So that is one thing. Yeah. [Rafael Bruno]: How about the things that you think we should improve? [sid]: For in terms of improving, I think we can have a code reviewer. But I think there are so many tools out there, like you can have an AI code reviewer, which auto which automatically comments on our PRS. So the one level of review will be will be addressed by AI. And that will, to some extent, eliminate immediate need of reviewing the code that can be so that can at least solve a problem to some extent. [Rafael Bruno]: That is one way I think we should should do it in the coming in the coming months. Okay. How about something that you achieved? Would you like to tell us about that? [sid]: Yeah, sure. So recently, even the completion of inner circle. Although it was delayed, but yes, we finished it. So that was a good achievement. I’m looking forward to launching it. I know there’s some issues with the engagements thing. But as soon as it’s done, I like I’m excited to see that feature in production. And secondly, I’ve started with content queue. So I set some internal goals to myself and by Sunday this I’m I mean, by end of this weekend, I will be able to finish most of it. [Michael Houck]: So whatever I’ve planned, I’m on track to accomplish those goals for the content queue. [sid]: Wow, Sid, that’s awesome about content queue. [UNKNOWN_SPEAKER]: Nice progress there. Yeah, thank you. [Rafael Bruno]: Oh, one thing, since we have Ben here, I think Ben could give us a good perspective of the user side. So Ben, do you think you have something to contribute? What do you think we did right and what do you think we did wrong regarding how we interact with users? Yeah. [Ben Ornstein]: I think part of it that can be improved is on my side because, and I’ll start with that because, and this This is what I’m going to stress to Raina as well as she takes over a lot of the responsibilities here over time. If something is pressing for whatever reason, I could make it very clear that this is something that needs to be prioritized. Yes, anything with users should likely be pretty high prioritization, but there are certain cases where it does need to be done now. And when that is the case, I will make sure and I will make sure Raina knows as well that when there’s a situation like that that comes up, when I’m messaging the channel or maybe one of you individually, if it is pressing, I will make sure to say that it is because there are certain cases where that comes up. That’s really thing that I think can be improved. I think all of you have been really great when it comes to picking up tasks and quickly looking into something when it’s sent over to you. So yeah, great job and thank you for responding so quickly. It’s always very much appreciated. [Michael Houck]: Ben, one idea that I had that you could do there is when you or Rina send those messages in the CX channel, if you have like a, you know, you have a line in that message, like a separate line, that’s like, you know, either something like priority, high, medium, low, or like a need resolution by today, tomorrow, this week, something like that, whichever one you guys think works best. I think that’ll make it really clear to the team if something is like urgent. [UNKNOWN_SPEAKER]: Cool. [Rafael Bruno]: Yeah. It would help. [Ben Ornstein]: Uh, Ben, like an emoji or something, maybe like a red versus a yellow, uh, could that be quicker or, or should it be more detailed than that? I don’t think it matters too much. [Michael Houck]: Whatever you guys want to do. What’s this, some system that between all you guys, you agree to is really all we need. [sid]: Yeah. I think if you put the first message, if you just put important and a red, red label, something like that, just for first line, then because that would, that would be helpful because when we get a notification, that’s the first line usually is, is shown in the notification, not the entire message. If you put it at the last, that might like, that might be overlooked at least from the notification. So you, if you put it at the top, then it will catch our eyes. [Ben Ornstein]: Yep. Good call. Okay. I’ll, I’ll start with that. I’ll do like a, like an alert emoji or something with important and we’ll, we’ll yeah. Good idea. I’ll start with that on the ones that are pressing. And then for the ones that are not, I won’t put anything, just so it’s like, this is a customer reaching out, but it’s not unbelievably important to do this this second kind of thing. [Rafael Bruno]: That’s, yeah, good idea, Sid. And still looking at the user site, what do you think that they’re mostly complaining that you think we need to improve on the product. Yeah, by far it’s onboarding. [Ben Ornstein]: If we could make the onboarding not only a clean experience where they’re not having bugs, but if it’s a delightful onboarding experience. I think it’s like the same thing when you meet someone for the first time. First impressions are everything, right? If they see a product for the first time and they’re having a delightful user experience, they’re going to be so happy. With us, even if they do hit a snag and hit some kind of bug. If it’s still a delightful UX and UI, I think that will solve a lot. [Michael Houck]: Yeah, I think we should set a goal to have like an explicit numerical around like percentage of new users who have a clean onboarding experience and with no issues that they reach out to us about. Because I think right now, if we were to track that number, I think it would be like 50% or more. That’s really bad. I think we need to get that to like, you know, like 2%. So I don’t know what the right way to, you know, keep track of that is maybe Ben, if you want to have Rena keep track of it, feel free, but I think setting a goal around that and focusing on [UNKNOWN_SPEAKER]: that is going to be important. [Ben Ornstein]: Yeah. And then, I mean, most of the questions that are, are that people reach out about it’s in the onboarding, whether they’re having bugs signing in, or they no longer have access to the account. And I don’t know the technical issues on the back end. I can just see what users are saying. And then the second most thing that isn’t really a product thing, maybe this is something how we can work on in PLG and SEO. Potentially, is it’s just the questions that are already in the help center, but it’s like, how much should I spend? What’s an average, you know, what’s an average budget? How quickly? I don’t know. There’s a lot of questions just about like how much they should spend. I don’t know if there’s something we could integrate in the product itself, like little pop-ups or, but yeah, that’s outside of product issues. That’s the biggest questions. Those are the biggest type of questions that are asked. [Michael Houck]: Yeah, I think those are something that we can solve maybe by building a little welcome tour into the intercom bot. I have an example that I saw the other day that I really liked. [Rafael Bruno]: You and I, Ben, can work on that. Cool. Sounds good. I think that I’m not sure if the validation message that we have right now in the frontend solves that issue. I’m not sure if that validation is still on dev or in production. It doesn’t solve. Yeah, this is unrelated. [Michael Houck]: This is just something that Ben and I needed to do in intercom to welcome people. Because, I mean, you guys got to think about it. People aren’t used to spending money to promote their tweets or their LinkedIn posts this way. So they have no benchmark, no frame of reference of what’s normal. And so if we say, here’s the limit, that’s still not going to tell them what’s normal. So what we need to do is just have a little welcome experience for them in intercom that just says, hey, here’s how to use the product. And that’s it. So there’s no work on you guys here for that. [Rafael Bruno]: That’s just something that I need to spend some time on. OK. How about you, Hauk? What is your point of view of things that are doing right and things that you think we should improve? [Michael Houck]: Yeah, I mean, I’ve been pretty pleased really over the past, I guess like five or six weeks, I guess like five weeks. I think our velocity has improved. Obviously bugs have gone down because we’re far away from the v2 launch now. I’m nervous about bugs in the next release that we’ll do next sprint. So we’ll have to see what we can do to mitigate that. But I’m nervous that that could derail our timeline for some other stuff. But overall, I feel pretty good about how we’ve been moving. I think you guys have been communicating well. We’ve been sort of digging into some tricky issues around the scraper really effectively. Obviously, we haven’t every part of it yet, but we’ve really broken down the problem and fixed what we can so far. So I think across the board, I’ve been pretty happy. I guess if I were going to say something that we should improve, I guess one thing that comes to mind is just like staying on top of like what’s the status of things in Linear and what tasks are being completed and things like that. I feel like I need to be pretty proactive with you guys a lot of the time to be like, hey, has this been completed or what’s the status of this? And then it ends up being that it is completed. And so I don’t have the bandwidth to be in the weeds every single minute of every day with you guys on every single issue. And so it’s important to me that the Linear board is kept up to because then I can just quickly look at it and be like, OK, here’s the status of things. [Rafael Bruno]: So I would say that we’ve gotten a little bit better about that, but I would still say that we’re not quite there. Got it. About the retrospective, I think that’s it. Hauke, do you think we should discuss anything else about this part of the meeting? [Michael Houck]: No, let’s move on to the next sprint. Oh, wait, sorry. One thing first. Can you scroll up, Rafael? So we should go through these and make sure that these are on track to be completed before the end of this sprint. [Rafael Bruno]: That’s the last thing we should do. OK. So first, talking about me, I have two tasks here, three tasks here. Is in review. I just need to talk with Mehul to test about the new flow that we want of users that cancelled being on the basic tier. After I talk with Mehul and test it, I can mark it as done. The second thing here is to fix the issue with max budget per amplifier. Also, I just need to test it. My intention was to test it yesterday, but we had a bug in the frontend, which I believe Mehul fixed. So just testing, marker solved. And I have this other task here, which is an improvement on edge cases of the scraper. This I’m still working on, and I will finish this today. So after I finish this, all of those tasks will be done. How about you, Mehul? You also have two tasks. One is in review, and the other is in progress. Could you please tell us about those tasks? [Mehul Jariwala]: Yeah, so first I’ll tell about the in review. So in review that you create user reactivation flow, I just need to test, uh, test, uh, free account user. I guess that is already working, but I’ll just cross through it and then check like whether we are seeing the correct alert warning when user is logged into it. Uh, and, uh, one more thing I have confusion on that, like, uh, we are, are we allowing user to share the broadcast even they, they, they are on the free tire. [Michael Houck]: So if a user is on. Free tier, they’re able to share broadcasts to their inner circle, but they’re not able to spend money in the creator network. [UNKNOWN_SPEAKER]: Oh, okay. [Mehul Jariwala]: Sure. Okay. That’s something I need to add. Probably. Yeah. I’ll fix those because that was in review because I was having the confusion on that. I’ll, I’ll just work on it and I’ll finish the, the interview before the sprint and probably before Monday I’ll work on the weekend. So that is one thing in progress when, uh, Uh, I guess that I’m almost done. I just need to cross check because I was working on the bug that you have given me. So that, that will be maybe that also will fix before. Um, uh, I mean, that will be review, uh, on, on, I’ll, I’ll send over to Hong for the review on that. Okay. I’ll be available to take a look at it on Sunday. [Michael Houck]: Yeah. Yeah. I’ll send it on weekend. [Mehul Jariwala]: So I’ll fix all the bug and then I’ll, I’ll send you to the, for a review and and I’ll mark that as a close. [Rafael Bruno]: So I’m on track of both of the issue. Great. OK. How about this second task here, Mehul? [Mehul Jariwala]: Yeah, yeah. Create amplifier. [UNKNOWN_SPEAKER]: Oh, we were talking about that. [Rafael Bruno]: I thought that we were still talking about the other one. [UNKNOWN_SPEAKER]: Yeah. [Rafael Bruno]: No. No, I was talking about this one. Create amplifier view. [Michael Houck]: Yeah. How about you, Sid? [Rafael Bruno]: You have four tasks in progress. Yeah, so those are related to content queue, and they’re going good. [sid]: I’ve completed one, which is for the API part of capturing the request, and I’m on other ones for the Megastone, Megafone Studios, I mean, ghostwriting interest, and a few like database schema. So yeah, I’m on track. They’re going pretty good. I don’t have any blockers. And yeah, I will be able to finish it. Most like I think 1109 and 1106 will be finished by Sunday itself. [Rafael Bruno]: How about 108? Can I move that to the next sprint? I mean that by Monday it will be completed. [sid]: I need some time on that because the sequences I’m doing 1106 and 1109 and post that 1108. So I started with it but I like I’ve written some code and then we’ll be doing the like I need some other some dependence see on other tickets. I’m doing that. [Rafael Bruno]: And later I’ll switch to this one. So I’ll move this to the next cycle. [Michael Houck]: Yeah, sounds fine. [Rafael Bruno]: Sounds fine. Rizwan is not here, but he has two tasks. [Michael Houck]: Can you check in with him later, Rafael, just to get the status? [Rafael Bruno]: I’ll check with him. Um, okay. Uh, so, uh, by Sunday we should come, uh, everyone agrees that we should complete all of those tasks, right? Yep. On track. [UNKNOWN_SPEAKER]: Okay. [Michael Houck]: This is if we complete everything, this is going to be one of our best, uh, sprints ever in terms of completing, uh, like amount of stuff. [Rafael Bruno]: Really, really nice work guys. Yeah. [UNKNOWN_SPEAKER]: Thanks. [sid]: Let’s make it. Yeah, let’s make it fair. [Michael Houck]: Okay, Rafael, do you want to change on to the next sprint then? [Rafael Bruno]: Okay, moving to the next sprint. One thing that… Oh, I thought that… Moving to the next sprint. One thing that we will have as the objective for the next sprint, we have like two major objectives. We want to release some stuff and we want to make a good progress on other stuff that should be in development. So for the next sprint, we want to release inner circle, release referrals and release the basic tier. And at the same time, we want to complete continue to develop campaigns, the content queue, and work on the scraper issue. So we have those three objectives for the next sprint. And two and three are those six objectives for the next sprint. And three of them are related with releasing stuff. Before we start to go over, to go with the task One thing that I think we should discuss is how to improve the way that we release things so we won’t have the amount of bugs that we are used to have after we release. Because the best experience that we had is that when we release some stuff, we have for like two or three weeks, huge amount of users complaining about some stuff at Intercom. So what do you guys think that we can do to improve the quality of our work? I thought about two things. One is to write a checklist of all the tests that we need to release some stuff. Let’s say, for example, that we want to release Inner Circle, so we need to write the tests like, oh, I want to create a user with a basic tier. And he needs to have his inner circle. And we want to test all the characteristics of the inner circle of that user. I want to do the same thing for the starter tier and the pro tier. I think that if we write the tests. And we have for example, how review what we wrote, we could identify earlier, some bad paths that we are not testing. And that could lead to bugs appearing on introduction. What do you guys think? [UNKNOWN_SPEAKER]: Yeah, that’s a good point. [sid]: I feel that would also add value. And in addition, we can also gather edge cases from others in the team. For example, if you’re building in a circle to fail, then even like others in the team, I may have not been or even there is one or how can you know, think can can give the edge cases that we may that we may that the developer may have forgotten to address. So that way, also, it could help. And secondly, is that I I feel that everyone like me in the team should test it thoroughly on on their environment. Like usually only the developer tested but others in the team like if we have about five people, then it would at least help us to fix it to identify and fix at least five bugs if there are if there are if the end user is facing I’m sure others in the team would also face it. So we can Yeah, I and solid. Yeah, one moment. [Rafael Bruno]: I also think that we should do that. That’s funny because this was the second topic here on my list that we should have more than one person testing the same thing because it’s easy when you’re like, when you develop some stuff, it’s difficult for you to, see the bad spots of what you developed. So a fresh eye testing stuff could easily identify things that you missed. And when we have more than one person testing, it could improve the way that we find issues because sometimes a person will test a flow going in one direction and in the other time the other person could test the same flow, but doing something different that could lead to a different result. So I think it’s also a good idea to have more than one person testing the same feature. [UNKNOWN_SPEAKER]: Any more ideas? [Rafael Bruno]: Behru, do you have an idea? [Mehul Jariwala]: Yeah, just one thing from my side, right? I guess from front end side also, So we need to have the story to write a test cases. Why? Because it’s really important when time scores the reason behind it. I was talking about the unit test cases where if something changed, we get to know by feeling of the unit test cases. So we were right when, when we are building a some model, at least we can test a few functionality so that we can something like, like the minor bug will catch on to the test cases part as well. I know like you guys are writing in for a backend, but I haven’t tried it on frontend. [Rafael Bruno]: So that’s something I feel like maybe if we can improve that, it will be helpful. Yeah, I wrote some unit tests in the backend. And one thing that I saw that really helped me was Cursor because you can take your code And you can create like a new tab there where you can ask Ursur to look at your code and write the unit tests. [Mehul Jariwala]: And that really helps to write things fast. Correct. So that is obvious. Ben, how do you… Oh, go ahead, Mehul, sorry. Yeah, maybe we do have… That will become so overhead for the startup, but it would be like playwright test cases where the Cypress or playwright where it will check the end-to-end flow of the feature, not the unit part of it. But maybe that will be too early to add up, but at least we can add up the unit test cases for now. [Rafael Bruno]: Yeah, unit tests, we can do that faster. Yeah. But about using Cypress, for the ones that don’t know, Cypress is a test tool. And it’s usually used to do end-to-end tests. That is up with how to decide if we should use our time to work with Cypress because although it’s a good tool that will help us to have those tests automated, it’s also time-consuming. So how should we decide if we should use or not our time to do that? [Michael Houck]: Yeah, I think it’s a good idea and I’d like to do it. I think let’s do it after… I don’t think let’s do it for this release. [Rafael Bruno]: Okay, I’ll put it. [UNKNOWN_SPEAKER]: How about you, Ben? [Rafael Bruno]: How can do you have any ideas of how we can improve the quality of what we we are delivering to the users? [Ben Ornstein]: Yeah, I mean, end-to-end testing, if there’s any free tools that don’t expose the code, again, I’m not unbelievably technical. So I don’t know how helpful I’m going to be on this one. But any tools that we can use to be able to identify bugs that maybe missed, that would be great. That saves time, obviously. That’s hopefully free or extremely close to being free. I think the things you guys identified make sense as next steps. [Michael Houck]: Let’s input that. And with more robust testing for this release, we’ll see how it goes. And then we’ll have Cypress for the next one. We’ll see how that goes. And if we need more adjustments after that, we’ll continue making them. [Rafael Bruno]: So now looking at the tasks, first talking about our first objective, which is releasing inner circle. I don’t see other tasks here. Sid, since you were the one responsible to developing most of this feature, do you think we need to add some task here to that is related with releasing in the circle. So yeah, there are two. [sid]: I mean, the one is testing ticket that you may create. Otherwise, I know that’s on me. So I will let you do it. Second one is to populate in a circle for for past users before the release. [Rafael Bruno]: One moment. [sid]: So We need a task to populate inner circle. Yeah, so this I will be doing just the name of the project. [Michael Houck]: The inner circle project was the very, very tiny MVP version we did back in the spring. The project should be, I think it should be groups MVP. [Rafael Bruno]: Yeah, that’s it. How about this? It’s extra small. [UNKNOWN_SPEAKER]: Okay. [sid]: I just need to run it. I have it already. How, what should I add here? [Rafael Bruno]: I’m pretty sure. Data. I think so. Yeah. [Michael Houck]: I mean, generally the way I like to do it is have one that’s like at least one for like what part of the product does it touch? So it would be like groups. And then at least one for like, what type of task is it? So is it a feature? Is it an improvement? Is it a data task? [UNKNOWN_SPEAKER]: Is it a bug? [Rafael Bruno]: I like to at least one of those. Okay. So populate inner circle for all users. Yep. Any other tests? [sid]: Uh, for inner circle, that’s it. That’s the, I mean, that’s the only one. [Michael Houck]: Should we, um, uh, have a task around testing? [UNKNOWN_SPEAKER]: Testing. [sid]: Yes. I think we had one, but it was Mark that’s done, but yes, you can create one. That’s fine. [Rafael Bruno]: Put it as medium because I don’t know how long it should take. Assign that to me. [UNKNOWN_SPEAKER]: OK. OK. [Rafael Bruno]: How about in the front end? Do you think there is something to do regarding in the circle, Mehul? [UNKNOWN_SPEAKER]: Not really. [sid]: Yeah, not really. [Rafael Bruno]: So both of you agree that we don’t have any more tasks, right? Yeah, just once we have the test data, probably we can cross verify. [Mehul Jariwala]: And then if we need it, then only otherwise. Currently, I don’t see any. Be required, but probably once we have testing everything then, if in case if needed, but for now we don’t need it. [UNKNOWN_SPEAKER]: Okay. About referrals. [Rafael Bruno]: I’ll also create another task here. And test end-to-end just to make sure that everything’s OK. About the frontend, Mehul, is everything OK in the frontend? [UNKNOWN_SPEAKER]: OK. [Rafael Bruno]: Yeah, I think that for referrals is also that. About releasing the basic tier, I need to add one task here. Oh. You project should I put this task, Hauk? [Michael Houck]: You can leave it as a no project task. [UNKNOWN_SPEAKER]: There wasn’t a project for free tier, I don’t think. [Rafael Bruno]: So I just need to change the data of inactive users to be of basic tier. So for now on, every time that someone cancels, cancels a subscription, we will not turn that user inactive. But what we will make is that we will still make the user status active, the caster status active, but we will change the accounts. So the accounts will no longer be either on the pro or starter tier, but they will be on the free tier. And that should also impact on the frontend because the frontend should be ready to only allow that user to access free tier stuff. Rafael, are there two parts here? [Michael Houck]: There’s one part. [UNKNOWN_SPEAKER]: Yeah. [Rafael Bruno]: One part is to change this and the other part is to test if everything is OK. [Michael Houck]: No, I mean, is there one part where we need to update the data for the existing inactive folks. And that is their second part for updating the code so that when future people downgrade, they go to basic tier instead of inactive. Oh, yeah. [UNKNOWN_SPEAKER]: This is already done in development. It’s not in production. [Rafael Bruno]: Great. Cool. Changing active users’ data back to basic tier. I will add another task. [UNKNOWN_SPEAKER]: for testing. [Rafael Bruno]: And I will assign that because it’s mostly related with front ends. [UNKNOWN_SPEAKER]: Dashboard. [Rafael Bruno]: And probably onboarding too. So we have those four tasks that are related with the things that we want to deliver at the end of the sprint. Does anyone want to change the size of the task? Like if someone thinks, oh, this should not be M because we need to do further testing, and it should probably be larger. Does anyone want to do that? To talk. I think I should change this to large, because we most likely will find errors, like logical errors or some bugs during testing. And we will need time to fix that. So those two tasks here, so we should be large. Anyone would like to add something? Okay, moving on. Those are the four tasks related with releasing. Now about the things that we should develop on that sprint. We have something related with solving the scraper issue, let me check something here. [UNKNOWN_SPEAKER]: RISC-I has two tasks here. [Rafael Bruno]: I think we should add, I think you told me that we already had a task for that, but I’m not finding it here, at least when I’m looking at Resonance tasks. [Michael Houck]: Yeah, we have 1096 and we have, what’s the other one? 1096 and 1130. They’re both in the sprint. [Rafael Bruno]: One’s assigned to me. Oh, okay. I think that 1096 is related with inner circle. But we need a task to solve the current issue that we have with the scraper. Should I create that right now? [Michael Houck]: Explain to me what the task would be. [Rafael Bruno]: It’s the current issue that we have that Rizwan is working. Oh, I’m not sure if he’s already working on that right now. [UNKNOWN_SPEAKER]: Oh, yeah, he’s working on that. [Rafael Bruno]: Add two Twitter bots and two machines for posting engagements. Yeah, he’s working on that. So we don’t need to add to the next sprint. [Michael Houck]: Yeah, if he doesn’t finish that this week, it’ll just automatically get moved to the next sprint. [Rafael Bruno]: OK. Going back here, so about the other objective that we have to solve this Quaker issue. This is taken care of about the content queue. Sid, would you please tell us a little bit more about the task? Let me just filter this for you. [UNKNOWN_SPEAKER]: Yeah, sure. [sid]: So the three-part thread, one is that let’s say you want to create a post on LinkedIn. So before you create a post, you write your draft. And you send it across for review or rather upgrading the words like the language right and you can pay a certain amount let’s say there are four types you can pay a certain amount choose one of those options and pay for it so let’s say you are writing a hundred characters post but you you like you’re not writer you don’t understand much about that so you can just pay let’s say fifty dollars and hire a writer who would do that job of right using right words, right vocabulary for your post. And so that’s how you request to upgrade. And the writer on the other side will have 72 hours to understand your requirements and what you want to improve in the post. And then they will give a improved version and that user will be able to see that all through the dashboard itself. So that is first part, first and second part, actually, first part is your request. The second part is where the writer delivers the request. And the third part is let’s say you like you like the service, you feel it’s worth the money, then you can apply, you can submit, you can show your interest in the ghostwriting service. And that’s how I mean, then you can fill out form, give your basic details and then like then you can have a call with Hawk and then he’ll like he’ll take it ahead from there. So that’s the entire content queue thing. The idea behind this is that not everyone is able to like not everyone is willing to give 3000 in first shot. So this is a preview of what they would be getting in the service. So let’s say instead like roughly you are hesitating to pay 3000, right? You don’t know what, you will be getting. So maybe you can just pay $50 initially and see what kind of what what like what you will be getting how how good we are. And then if you’re satisfied, you can like subscribe for that course writing service. Yeah, that’s the whole that’s the whole idea behind it. [Rafael Bruno]: Okay, let me just check something here about your current tasks, create API for updating the delivered content, requests for revisions, APIs, create an API to fetch. Do you think we need to add any more tasks here so you can finish the content queue? [sid]: Everything is created on the backend side, of course, for frontend we do need to, but just just one shed like because you are so just sharing that we still I mean, we will be creating a standalone page for writers, which is not included here. But I’m assuming that will be taken care of front end when Mehul creates a ticket. So back end on the back end side, we just need an API that is addressed here. There’s a ticket for that already. So everything on the back end side has been taken care of [Michael Houck]: And we want front-end work for content queue this sprint. [sid]: That’ll be next sprint. [Rafael Bruno]: Yeah, yeah, next. Are the sizes of the tasks right? Like, did you include, when you put the sizes here, did you include the time that you will take to test all the flows of those tasks? [Michael Houck]: Rafael, we probably won’t do testing yet because the front end won’t be done. So we’ll probably save that until until next sprint when we want to release. So for testing, I meant on the back end, like testing everything before integrating with the with the front end. Right. Okay. [sid]: Yeah, it has been taken care of Okay, so that’s how you see most like, few of like one is large, few of them are medium. When when that I’m doing it, it’s a medium ticket, doing the testing, the developer testing. [Rafael Bruno]: OK. So for the content queue, is that? Now, looking at my rules, we have some stuff here for campaigns, campaigns, and content queue. How you said that this standalone page would be for the next sprint, right? [Michael Houck]: Yeah, I think I’d rather have mobile focus on campaigns next sprint and also assisting with the release. We can save the content you work, you can move both of those to next sprint and we move in some more campaigns tasks instead. [Rafael Bruno]: Okay, moving that to… Next screen. Here for campaigns, Mehul has two tasks, add campaigns to main dashboards tab, and create mobile versions of campaigns tab. Mehul, I think you already finished a lot of tasks regarding campaigns. Do you think that there is anything else that you need to add here? [Mehul Jariwala]: No, I guess this is good. I haven’t created a subtask of it. I’m not sure why it’s not visible here, but I have created the subtasks of the campaign. It’s because we’re looking at the sprint view. [Michael Houck]: Rafael, if you click on projects on the left side, No, the other one. And then if you click on, oh wow, you used the weird view. Click on display, up right corner, and change it to a board. [Rafael Bruno]: Oh, okay. Yeah, now click. Campaigns and then click on issues in the top. [UNKNOWN_SPEAKER]: Yeah. [Michael Houck]: Yeah. This is the correct. [Mehul Jariwala]: So all the sub tags for the, because we have the model that that’s needs to be created and which has a lot of functionality into it. So I have breakdown into the multiple part of the of it. [Rafael Bruno]: So, yeah, here. So those are the tasks that you created, right? That’s correct. Okay, so I will add them to the next strings. [UNKNOWN_SPEAKER]: Yeah, good. [Mehul Jariwala]: I guess there is a way you can select multiple and move it once. I’m not sure. Yeah. [Rafael Bruno]: Otherwise, otherwise you have to press five times. [Michael Houck]: Yeah. If you click on the checkboxes on the hand side, just hover over the left hand side. [Rafael Bruno]: Left? No, that one. Oh, here. I found it. It’s because I can only find that if I hover the mouse here. [Mehul Jariwala]: Okay, technical, technical people struggling to do. [Rafael Bruno]: Yeah. [Mehul Jariwala]: Okay, you have to select the upper one as well. [Rafael Bruno]: Select what? [Mehul Jariwala]: The, the Yeah. [UNKNOWN_SPEAKER]: Okay. Okay. [Rafael Bruno]: And I guess I should find something at the bottom. Oh, yeah. [Michael Houck]: or add cycle, yeah, that works too. And then I’m gonna go through and add tags and stuff to this and priorities, but you guys should add sizes. That’s the one thing that I’m not gonna know. So please feel free to go through and do that. It doesn’t need to be right this minute, because we’re already at time. So I do want to make progress and move on to the next thing. Rafael, I’d also like you to add the backend tasks this project here today so that we can have a reference. [Rafael Bruno]: I’ll create those today. Go ahead. No, that was it. [Michael Houck]: We can move on and go back to the next cycle and look at what’s next. My hypothesis is that, Mehul, this is going to take up the majority of the sprint for you. Along with helping with testing and the release? [Rafael Bruno]: Yeah, it is quite a lot too, yeah. So, Mehul will work on adjusting the sizes of those tasks. And if you think that you should include any other task here, I think we need to include one task regarding the integration with the back end. I don’t think I saw something like this here. [Mehul Jariwala]: Yeah, it’s not there. [UNKNOWN_SPEAKER]: Yeah. [UNKNOWN_SPEAKER]: So this is done. [Rafael Bruno]: Besides that, I just need to add the tasks of The backend, I’ll do that today. And we still have some other tasks here. I think that those tasks are related with stuff from the disk prints that we were not able to finish. I think that the Hulk. We’ll probably move those out of the sprint if he finds that it should be better. One thing that I think we should worry is about allocating a capacity of the sprint to solve bugs. Because we will probably have bugs appearing when the sprint is happening. And so we can know that we need time to allocate for those bugs. I’m not sure how to, to work with those capacities here, how, but I think that a good value would be something between like 10 and 20% of the sprint to work on bugs. That’s like a huge number. But just to to be sure that we will have time and that we’ll be prepared to deliver stuff in time, knowing that we will spend time on bugs. [Michael Houck]: Yeah, I think that if all the tests that you added are medium size, like they’re scheduled right now, there’s a couple that are extra small and one that’s large. But if all those are medium size, there’s no way that we’re going to finish all those in one sprint. So we’re going to need to pay and move the other ones to the following sprint, which is fine. But if I look at the current sprint, like right now, you have 43 points in this sprint, which is like two sprints. So yeah, please feel free to break those up and move some of them to the following sprint. That’s totally fine. When I look at workload for Sid and respond to even when I count the ones that we haven’t assigned to anybody yet, I think we’re OK. Like if I assigned all the ones that are not assigned to anybody to Rafael, then Rafael you’d be at 23, which is I think a little lower than you normally finish up at. And said you you’re at 16 right now, so you probably have some bandwidth on top of that too. So I actually think they were in a pretty good place to have some bugs as long as we basically Sloane McCool into two people. [UNKNOWN_SPEAKER]: OK. [Rafael Bruno]: Does anyone want to add something like a comment, wants to add another task or a point that we should observe during this sprint? [UNKNOWN_SPEAKER]: No. OK. [Rafael Bruno]: So I think that’s it. Would you like to say something or? [Michael Houck]: Yeah, I mean, I think this went well. I hope you guys thought this was a good use of time, because I definitely do. And let’s try it again next sprint and see how it goes. But yeah, just let me know, Mehul, when you break up yours into the two sprints. And then, Rafael, you let me know when you add the backend tasks for campaigns. I’ll take a look at those. And we’ll go from there. [UNKNOWN_SPEAKER]: Okay. Cool. [Rafael Bruno]: Okay. So that’s it. Have a nice evening or night because I don’t know where is the time zone of everyone, but everyone has a nice day.