Mar 15, 2026 Enterprise Brain Scrum - Transcript 00:00:00 Satyasri Prabhakar Mantripragada: There's some Yeshwanth Reddy Yerraguntla: Hi, good morning. It's 8:00. Hi, Manisha Gundapuneedi: Hi Professor. Yeshwanth Reddy Yerraguntla: Manisha. Manisha Gundapuneedi: Good morning. Good evening. Yeshwanth Reddy Yerraguntla: Good morning. Satyasri Prabhakar Mantripragada: Good morning. Yeshwanth Reddy Yerraguntla: Hey, make 8:30. Okay. Manisha Gundapuneedi: radiator as in English. Yeshwanth Reddy Yerraguntla: 7:30 Manisha Gundapuneedi: 8:30. Okay. 7:30. Yeshwanth Reddy Yerraguntla: Okay. And there is only one concern which is if the meeting extends so people will not be have will they'll not have the time to get ready. Satyasri Prabhakar Mantripragada: Both Manisha and Rajak will represent you in the scrum. Yeshwanth Reddy Yerraguntla: Mhm. Satyasri Prabhakar Mantripragada: They'll have to take internal scrums for the squads technical challenges they'll bring that Yeshwanth Reddy Yerraguntla: Okay. Satyasri Prabhakar Mantripragada: to you and you will give them the directions. But in case they have somebody needs some concern that the squad lead will need your help they can join in. It's open for everyone but it's not mandatory for everyone except for the square leads and practice 00:01:41 Yeshwanth Reddy Yerraguntla: Okay. Satyasri Prabhakar Mantripragada: set. Yeshwanth Reddy Yerraguntla: Okay. Satyasri Prabhakar Mantripragada: active on the actual task. Yeshwanth Reddy Yerraguntla: Got it. Yeah. I mean that makes sense also that uh we can have everyone optional in the call. Um, so Satyasri Prabhakar Mantripragada: Maybe every day end of the day uh square leads can take a scrum with their team members on what happened what was wrong with the previous plan previous day work and then the next day morning they can bring it up to you to get the direction and uh they can forward Yeshwanth Reddy Yerraguntla: yeah, Satyasri Prabhakar Mantripragada: it. Yeshwanth Reddy Yerraguntla: I mean I don't want this uh this waiting time of next day morning like if something is off ideally some there has to be some way to get it resolved as soon as possible. One advantage Diwami has right now at least this one team has right now Satyasri Prabhakar Mantripragada: Yeah. Yeshwanth Reddy Yerraguntla: is in one way it's a disadvantage but in one way it's an advantage that we are living in two different time zones which means in principle 00:03:00 Satyasri Prabhakar Mantripragada: 24 by7. Yeshwanth Reddy Yerraguntla: uh some the wami can work 24 hours of the day this I observed with the last week's demos that I was giving some things to Ganesh or Raja they were able to handle it then they will give back to me this there is a there is this company called Ninja in America Satyasri Prabhakar Mantripragada: Yeah. Yeshwanth Reddy Yerraguntla: uh like one of their success story is that they have two research uh research locations one in America one in China so apparently their speed is really double that of rest of the uh competitors Yeah. So we have to not rely on this. Uh we wait for rashant to come and then we'll resolve somehow if you can if you can summarize surface that information to me. I should be in a position to uh I'm not saying it should be done or ideally it should be done. We just don't know the right procedure or process. But you have to strive towards Satyasri Prabhakar Mantripragada: as uh every day if they 00:04:12 Yeshwanth Reddy Yerraguntla: that. Satyasri Prabhakar Mantripragada: can um post their updates in the space somewhere and or their own space, it pulls up the summary via an agent. So that can be a quick reference for you to look at and that also enforces team to post their daily status updates in Yeshwanth Reddy Yerraguntla: Correct. Satyasri Prabhakar Mantripragada: the channel off that was missing. Yeshwanth Reddy Yerraguntla: True. Satyasri Prabhakar Mantripragada: So we can reinstitute that. Yeshwanth Reddy Yerraguntla: Agree. I agree with that. Any other general point? I have I worked yesterday and today mainly today to um I was reorganizing most of our work. Um right. So mainly um I created a GitHub uh scaffolding in um enterprise brain repo where it should like every time we start something it should have the context of what we are trying to do. So um we will have more and more skills uh uh coming up but essentially our agent should know what is enterprise brain before it even tries to attempt uh coding. So that is the purpose of this github and uh anyway it's present in this u uh a enterprise brain uh repo. 00:05:50 Yeshwanth Reddy Yerraguntla: I added it in chanaka/alpha folder just now I added a meeting sprint sync skill also what that means what that does is it will um like every day at the end of our uh meeting Google itself is sending one uh mail saying that this meeting happened and for our this current uh half an hour meeting also every day I auto uh set up auto recording so It will automatically start recording even if one person joins and all the 10 whatever 12 people will get that email that so and so thing happened. Uh honey ideally if we can simply uh what do you call copy that meeting transcription right and put it in the documents. Currently it is phase two. So phase 2/ conversations folder this skill should be in a position to understand okay this is the update currently and it should first of all create a minutes of meeting in the same folder what that will do is it will immediately uh once that is created uh if someone pushes it it will immediately uh show should show up in the phase 2 uh minutes of meeting. 00:07:17 Yeshwanth Reddy Yerraguntla: Secondly, that skill is also trying to update what is the status of the current sprint like who is doing what, what are their blockers, all those things. Um, I hope we can try to use this mainly to keep ourselves in synchron uh that sync uh state. Secondly, I'm also like because this is enterprise brain, lot of um things should happen automatically in enterprise brain. So how to deal with snapshots, how to update information, how to manage skills for enterprise brain. I'm saying the whole system of how enterprise brain itself should work. uh we will we'll start to have some kind of learnings from this activity like when you start creating skills the act of how to create skill how to update skills the act of updating snapshots all these things will directly translate into how good enterprise brain itself will work in in other words what I'm trying to say is if we can learn proper skills and proper for snapshots in enter this repo that will give us enough learnings to build enterprise brain itself uh like the product itself. 00:08:40 Yeshwanth Reddy Yerraguntla: So I hope everyone can take start taking advantage of these things and you can add more and more skills and um you know start learning and implementing more advanced concepts. Finally what I want to uh talk about is I went through so that one of the skill that I created is called as Jira access right. So this skill directly I sort of made it understand how to uh access our Jira repo itself based on certain things like Jira token and all those things certain secrets but once that is present because I gave that it was able sprint uh uh directly from co-pilot and give me what is expected in the sprint right So um I was able to create a summary of current sprint. Not that I'm saying we'll we'll discuss the sprint from here. Ideally our sprint should uh be discussed only from the Jira board. Right? So backlog we have active sprint. So I'm starting the sprint unless Palash is there and he will say don't can we start this or he didn't join 00:10:07 Vara Kumar Jagarapu: Uh maybe yeah sure maybe how much capacity we have Yeshwanth Reddy Yerraguntla: okay I'm not Vara Kumar Jagarapu: planned uh based on the Yeshwanth Reddy Yerraguntla: sure Rajar and Mahisha you can answer that. Rajashekar G: by 12 hours. Yeshwanth Reddy Yerraguntla: Mhm. Rajashekar G: But uh Vara Kumar Jagarapu: okay uh I will um maybe uh in few hours uh session Rajashekar G: still Vara Kumar Jagarapu: we'll start on it but I just want to Because yeah because because like one started right Yeshwanth Reddy Yerraguntla: Okay, I'll not touch it then. Vara Kumar Jagarapu: so I think adjustments may Yeshwanth Reddy Yerraguntla: Fine. Fine. I didn't touch it. That's why you can get started. Maybe tomorrow that sprint started. Vara Kumar Jagarapu: No today we will start maybe after taking I will discuss with Rashag and Manisha and then start a couple of Yeshwanth Reddy Yerraguntla: Okay. Yeah. The the next thing is uh I think it has pulled the entire backlog. But ideally for every ticket um yeah this is taking to the ticket directly. 00:11:10 Yeshwanth Reddy Yerraguntla: But if I search for 379 there is a LLD document also. that I just created. It's a dummy document with whatever was my understanding of the project. Right? Based on all the discussions we have been having since two weeks, I asked a agent to come up with a summary of what is being expected for that one life cycle. So all those tickets are present in the same uh AI enterprise brain in LLD's folder. So one ticket has one diagram. I don't know uh maybe some tickets are too basic to have a diagram so we can skip them but the point is uh if we have to do have these communications right um uh u that let's say Abilash has so and so ticket is working on like whatever needs to happen in that ticket in the form of low-level designs all those diagrams there is a dedicated page in enterprise his brain now uh in the form of LLDS. So I'm I'm asking everyone to mainly just start at this point understand what your task is update this document uh to the fullest extent get your approval from either Manisha or Rajar or myself only then you should get started. 00:12:42 Manisha Gundapuneedi: Now just a small question sorry. Um these tasks are same as whatever we have broken down in the Jira or Yeshwanth Reddy Yerraguntla: Yeah. Yeah. Manisha Gundapuneedi: U. Yeshwanth Reddy Yerraguntla: Yeah. The the ticket number is also there. No. Manisha Gundapuneedi: Okay. Yeshwanth Reddy Yerraguntla: So the description everything it directly came from Jira because again I say because of the Jira skill in a few moments there will be a minutes of meeting skill like that. Manisha Gundapuneedi: f*** Yeshwanth Reddy Yerraguntla: We'll have to keep updating with all the things that you know we think are useful Manisha Gundapuneedi: you. Yeshwanth Reddy Yerraguntla: because a 10 member team is a large team. So we have to be really on top of our um automation and everything to uh keep everything up to date for not only for ourselves but also mainly for uh co-pilot because when I start saying just start implementing DB117 all the diagram should be properly there only then it will know okay I have to go and do this kind of a thing. 00:13:46 Yeshwanth Reddy Yerraguntla: So yeah, this is what I wanted to uh Satyasri Prabhakar Mantripragada: For example, what I was suggesting is everybody before you pick up the task uh they should have the clarity on what is expected of the task or story to a level that Yeshwanth Reddy Yerraguntla: correct. Satyasri Prabhakar Mantripragada: exactly what is the technical things that you need to take care of what are the functional things that you need to take care of and there's no scope creep if there is a scope creep or something else has to be done in different uh stories or different task better split them at the start of it. For example, open user access something where it mentions Yeshwanth Reddy Yerraguntla: Yeah. Satyasri Prabhakar Mantripragada: that whoever user has logged in and if they have access to a certain resource uh it should give them the requested information. Yeshwanth Reddy Yerraguntla: Yeah. Satyasri Prabhakar Mantripragada: So that is a that's a high level statement functional statement that we can give but for somebody who is implementing it you should know which resources are you targeting otherwise the story will never be complete. 00:14:51 Satyasri Prabhakar Mantripragada: So that we need to further break it down or give acceptance criteria that this story is only with respect to say this. This story is respect to only uh some other uh resource. So then we can call it it is done. Otherwise somebody can always open a bug saying that okay that resource I have tested this resource I have tested within the scope of it because it is abstract as of now. Yeshwanth Reddy Yerraguntla: H. Satyasri Prabhakar Mantripragada: So we cannot defend or if we if it's impossible we can resources 1 2 3 are part of this Yeshwanth Reddy Yerraguntla: So if I have to summarize it properly, you're saying this document should clearly contain what are the inscope uh tasks and out of scope tasks and the testing criteria Satyasri Prabhakar Mantripragada: huh correct that is the that's what We call it Yeshwanth Reddy Yerraguntla: also is Manisha Gundapuneedi: resources also. I guess Yeshwanth Reddy Yerraguntla: is Satyasri Prabhakar Mantripragada: as when we call we calling it as acceptance criteria when do you say it is done kind of a checklist item that you go cross check against okay is it done done okay now 00:16:00 Yeshwanth Reddy Yerraguntla: Yeah. Satyasri Prabhakar Mantripragada: this story is complete so that basically in Jira we need to have that criteria and obviously this data from Jira so it will obviously Yeshwanth Reddy Yerraguntla: Okay. Yeah. Uh true. Like if we can do both ways. If uh if we are happy with the acceptance criteria here, we can simply say copilot use this and update my Jira. Or if someone is updating Jira, we can always say copilot Jira or something is updated come and put it here. I know it's a duplication of information but mainly this the purpose of this diagram is Jira cannot contain super depth details like for the example this diagram we can't have it in Jira right. Satyasri Prabhakar Mantripragada: We can reference we can Yeshwanth Reddy Yerraguntla: So huh in Jira you can always yeah point this Satyasri Prabhakar Mantripragada: have Yeshwanth Reddy Yerraguntla: uh URL say this is where it is correct basically confluence used to that whatever Atlassian has both confluence and Jira ideally that's how you would connect those two things but I don't think we are using confluence right it's another paid this that so we'll use this 00:17:19 Satyasri Prabhakar Mantripragada: We're not Yeshwanth Reddy Yerraguntla: Okay. Satyasri Prabhakar Mantripragada: not Yeshwanth Reddy Yerraguntla: Any and this is far more better than Confluence in my opinion because like my wife uses Confluence and the number of features Viasa has is far more than that portal. It will make integrations easy but I think uh we have more control here. So so let's try to do it this way. uh mainly action items for everyone is this is the current sprint. You can always check the current sprint. It will point you to this guy. Um I based on assign already things are there. So you can just do Ctrl+ F and see how which ones to prioritize which ones to not prioritize and update the documentation. See this is mainly for documentation. This is the place where you'll update your task status. So keep these two in mind. I have two tasks on my plate. So from tomorrow I will also uh start reporting here only and while I report something here I'll show this uh documentation saying this is how it works. 00:18:32 Yeshwanth Reddy Yerraguntla: Um is that is that good enough? Rajashekar G: And so the team is now has to start with like their own stories and uh they need to come up with the breakdown again and they need to Yeshwanth Reddy Yerraguntla: Main correct mainly low-level diagrams of how they have to Rajashekar G: R&D. Yeshwanth Reddy Yerraguntla: approach the problem the acceptance criteria in scope out of scope and testing Rajashekar G: Yeah. Yeshwanth Reddy Yerraguntla: criteria. Rajashekar G: So but here like what I'm suggesting is we need to have a deadline for this like by today end of the day like that. Yeshwanth Reddy Yerraguntla: We have to time block it. Rajashekar G: So why because yeah so Yeshwanth Reddy Yerraguntla: I will say uh 16 hours is more than enough. Rajashekar G: team will continuously doing the R&D and it will eat up Yeshwanth Reddy Yerraguntla: Correct. Correct. Correct. Rajashekar G: more. Yeshwanth Reddy Yerraguntla: Yeah. 16 hours is more than enough. Probably in that case. Rajashekar G: Yeah. Yeshwanth Reddy Yerraguntla: Let me also create LLD and get up ro right. 00:19:26 Yeshwanth Reddy Yerraguntla: So I believe everyone has that. Rajashekar G: Yes. Yeshwanth Reddy Yerraguntla: So here if I come here basically my uh oh wait why is this unassigned? Rajashekar G: Subtask we haven't assigned like subtasks like people themselves they can Yeshwanth Reddy Yerraguntla: Okay, got it. Rajashekar G: assign Yeshwanth Reddy Yerraguntla: So I assigning it to me. Uh due date I have to put it as um today Rajashekar G: tomorrow 7 Yeshwanth Reddy Yerraguntla: I have 8 hours. Tomorrow I have 8 hours. So I'm saying t for me it is Tuesday. Uh time sorry in that case it is this only. Yeah, start date. There is no time blocking. Rajashekar G: original Yeshwanth Reddy Yerraguntla: Okay. Rajashekar G: student, Yeshwanth Reddy Yerraguntla: Uh 16 hours. Okay, that's it, right? Rajashekar G: right? Yeshwanth Reddy Yerraguntla: Or should I also add story points story? Rajashekar G: No, only right. Yeshwanth Reddy Yerraguntla: This Yeah, it's a research task. You're Rajashekar G: Team has to log their hours like what like what they have done by the end of the day. 00:20:24 Yeshwanth Reddy Yerraguntla: right. Rajashekar G: Like whenever they are logging of their task they need to log the time and put what has done by that Yeshwanth Reddy Yerraguntla: H so I have context propagation life cycle and Rajashekar G: day. Yeshwanth Reddy Yerraguntla: I have adop question answer life cycle. Um both of them need 16 16 hours on I can't have deadline as 16th March for this guy. Rajashekar G: Hey Yeshwanth Reddy Yerraguntla: Um maybe I'll not really talk about deadline. I'll simply say 2 days. If this is 16th March, the deadline is um 1 day, 2day, 3 day, 4 days. Okay, done. Right. So yeah, I will work mainly on these two uh guys for the next uh I will 4 days is an overestimate. I am very confident. But yeah, this is what I will work on. Anything else I am missing? Rajashekar G: till here clear or not and uh one thing is while they are picking up that particular story they need to come up with LLD as well as the subtask list also like whatever we have put there is all the subtask That's where like we did the R&D and we put them team has to clearly know like what are the subtask they need they need 00:22:15 Yeshwanth Reddy Yerraguntla: Yeah, Rajashekar G: to accomplish and in which subtask what needs to be done. Yeshwanth Reddy Yerraguntla: correct. Rajashekar G: Everyone has to be clear with that particular part. Yeshwanth Reddy Yerraguntla: Yeah. Yeah. Rajashekar G: Yeah. Yeshwanth Reddy Yerraguntla: I mean by based on the deadline subtask should be done, LLD should be done, uh acceptance criteria should be done, testing criteria should be done for that one Rajashekar G: Yes. Yeshwanth Reddy Yerraguntla: story. Rajashekar G: Guys, are we clear or do you have any other questions? You need more clarity or somewhat please ask here itself so that we will be on same page everyone. Abhilash Adunuri: Yeah, understood. If there are anything uh the notical alarm said, we'll try. is still having that same Yeshwanth Reddy Yerraguntla: Yeah. 60 to 70% or at least 40% of information you'll directly get from here only. If you are still confused access um approach who is this um Rajar Manisha or V yeah but I'll always be like uh listening in enterprise brain uh chat space so anybody has any question just at the rate and uh start whatever your question is this This is not accessible because I think I deleted this guy. 00:24:04 Yeshwanth Reddy Yerraguntla: Uh yeah, I think I renamed it. Yeah. Rajashekar G: And now one more thing uh to come up with this LLDS and research items right they need to clone Chan a repository and they need to check Yeshwanth Reddy Yerraguntla: Huh? Rajashekar G: out Chanica alpha and everyone has to write the points in that MD Yeshwanth Reddy Yerraguntla: Correct. Rajashekar G: MD file. Yeshwanth Reddy Yerraguntla: Right. Right. Yeah. Write all your points in that MD file. Rajashekar G: today. Yeshwanth Reddy Yerraguntla: like I will say Rajakhar, Prabhakar, Vanisha whenever they are coming to you with uh this is what I have done. Ideally you should sit uh and on this web page and see what is being explained. Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: Of course when you have points to tell they will always have the VS code repo, right? So they'll update their MD document there itself. Rajashekar G: Okay. And every we need to publish this here or like if they push will directly come up here. Sometimes we are uh it is not 00:25:21 Yeshwanth Reddy Yerraguntla: Uh what this uh Vasa Rajashekar G: accessible. Yeshwanth Reddy Yerraguntla: fold Rajashekar G: Yes. Yeshwanth Reddy Yerraguntla: repo Rajashekar G: Sometimes it is saying like server unreachable. Sometimes it is getting down. Some PS are coming. Yeshwanth Reddy Yerraguntla: if that is happening then we should connect with NISH and get a stable deployment. Yeah, Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: but if you push it to do/main uh uh whatever or branch, it will automatically show up here. Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: And there should be some link from ticket to here. Uh if that is possible maybe we Rajashekar G: It is there. Yeshwanth Reddy Yerraguntla: So that is already there. Vara Kumar Jagarapu: can Yeshwanth Reddy Yerraguntla: That is what this Jira skill uh if I open skills Jira access. So if you're really talking about any Jira ticket that you want it updated here or vice Vara Kumar Jagarapu: Mhm. Yeshwanth Reddy Yerraguntla: versa copilot can now directly do that as long as you maintain the env folder there is this env file where you put your Jira token that is enough now it will write the necessary code and uh get all the information on the fly that is how it was able to create the um ticket uh these things. 00:26:40 Yeshwanth Reddy Yerraguntla: So if I click on this guy, it will take me to 378 Vara Kumar Jagarapu: Yeah. Yeah. I I'm talking about in a different way. Yeshwanth Reddy Yerraguntla: the opposite, Vara Kumar Jagarapu: Yeah. Yeshwanth Reddy Yerraguntla: right? Vara Kumar Jagarapu: Opposite from Jerard to here. Yeshwanth Reddy Yerraguntla: That manually we can do it. Vara Kumar Jagarapu: uh see uh what I'm thinking is like Yeshwanth Reddy Yerraguntla: Yeah. Vara Kumar Jagarapu: say if someone uh generally will consider Jira task as uh source of truth right if you go there so description and everything like if you write you'll get some context but main context will be residing in the deployed place right uh we we are at same place yeah but ticket should have that URL or something So Yeshwanth Reddy Yerraguntla: H. Vara Kumar Jagarapu: that I mean if you can add it in description or or in the comments somehow the ticket will be having the complete information. Uh that is what intent is. Yeshwanth Reddy Yerraguntla: Oh, good. Vara Kumar Jagarapu: Yeah. Yeshwanth Reddy Yerraguntla: makes Vara Kumar Jagarapu: Yeah. 00:27:38 Vara Kumar Jagarapu: We'll see. Yeshwanth Reddy Yerraguntla: sense Vara Kumar Jagarapu: Uh maybe how we can do that. But yeah. Yeshwanth Reddy Yerraguntla: like I think it can directly work right now. So if I try to say I'm Yeshwant and u please go through all my tickets and um update the markdown file URL in Jira description and update the Jira ticket in um Jira itself. Vara Kumar Jagarapu: Oh, Yeshwanth Reddy Yerraguntla: This level it should already work. Let me see. Oh, by the way, we have to give this thing right that like it has to connect to Yasada. Uh I'll just change the prompt and we'll try again. But yeah, we'll do it like at least tomorrow when I am showing my this thing um that URL will be there. So everyone else can also do the same. Rajashekar G: Okay. And do we need to have any setup to link this like any Jira token need to be placed in our ENVS or something like that? 00:28:54 Yeshwanth Reddy Yerraguntla: Everyone, everyone needs to create general settings. There is a way to do that. Yeah. Yeah, you can create a fresh token here. Create it and put it in that env. Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: So, env.example already. You need these three basically. Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: When you're clicking on this Rajashekar G: Just a second. Yeshwanth Reddy Yerraguntla: guy, We done after this call. Rajashekar G: Okay. So now shall we take the individual updates like what has been done and everything need to be in a concluded place what has done in the last week right. So shall we take that information from now? Hello Vara Kumar Jagarapu: There are uh the schedule time is like 8:30 to 9 right I think like if there any blockers or something maybe we can discuss and see time then we Yeshwanth Reddy Yerraguntla: Yeah. Yeah. We'll focus only on blockers in this Vara Kumar Jagarapu: can Yeshwanth Reddy Yerraguntla: school. Rajashekar G: Okay. 00:31:35 Rajashekar G: And one more point like Manisha's team will be jumping into the projects if Tata Steel or something comes up. So platform people will be only my squad Yeshwanth Reddy Yerraguntla: Yeah, once it comes up, Rajashekar G: once. Yeshwanth Reddy Yerraguntla: we'll do we'll try to Rajashekar G: Yeah. Got it. Yeshwanth Reddy Yerraguntla: adjust. Rajashekar G: You guys please Yeshwanth Reddy Yerraguntla: No blockers. Rajashekar G: talk Yeshwanth Reddy Yerraguntla: Sure. Abhilash Adunuri: While creating the LLDS we can find. So we put the Yeshwanth Reddy Yerraguntla: Sure. Sorry. Am I um I think Rajashekar G: and Satyasri Prabhakar Mantripragada: What are the expectations at the platform level? Rajashekar G: Initially brief what is they'll come up with the questions right now we have a notebook so people will directly ask the questions there and get the clarities if still they have the questions they need to discuss internally Yes. Satyasri Prabhakar Mantripragada: This is regarding architecture overview. Rajashekar G: Yes. Enter architecture and what needs to be done in everything. Satyasri Prabhakar Mantripragada: Okay. Rajashekar G: Right now we 00:33:01 Satyasri Prabhakar Mantripragada: Did you also mention unit test coverage and test testing within the storage by Rajashekar G: are Satyasri Prabhakar Mantripragada: themselves? Rajashekar G: yes for uh for my squap for everyone like Ganesh and everything everyone were busy with something else. Satyasri Prabhakar Mantripragada: So I will just reiterate uh in case somebody's not clear or it was very abstract that everyone that is assigned to a story or a task uh it is your duty to complete the testing also and you need to document what test cases have you done so far and publish the report when you say it is done. Similarly, when you say a research topic is assigned to you and you are claiming that it is done, you should also produce the necessary evidences like whatever the documentation. So all this has to happen when you say it is done. It is not that on the done day you have submitted it to H1 for review but on the done day it is already reviewed and posted somewhere else. So that is when we call it as done. 00:34:05 Satyasri Prabhakar Mantripragada: So please plan your deliveries accordingly and once the story is closed we cannot reopen it. We don't want to reopen it basically. We can reopen always but we don't want to reopen. It means that any story that we picked up we have full clarity on what needs to be accomplished and if it is said as done it is done done forever. If there is anything that is missing that will come in a new story and obviously one practice that you could also do is that any anything that you have developed and you see there is a gap you should log a bug against your story generally the practice that I have seen here is that you go and fix it and then silently you check in the code but there is no trace of why you have made a change so any change that is pushed to the code should have a Jira ticket reference. Let us start that practice. So we are more transparent in why we are doing what we are doing and that also helps other teams to know okay this is the reason something has got changed. 00:35:22 Satyasri Prabhakar Mantripragada: Uh is that here? Abhilash Adunuri: Yes. Vara Kumar Jagarapu: Uh yes, I think uh I mean I I'll speak to once I'm there and I will be there Satyasri Prabhakar Mantripragada: Sure. Vara Kumar Jagarapu: in some time. Satyasri Prabhakar Mantripragada: Sure. Vara Kumar Jagarapu: Yeah. Satyasri Prabhakar Mantripragada: I I want your help uh in establishing this process in Jira. Vara Kumar Jagarapu: Yeah. Sure. Satyasri Prabhakar Mantripragada: You cannot take in anything without a zero because it cannot be Vara Kumar Jagarapu: Yeah. Yeah. Satyasri Prabhakar Mantripragada: a Vara Kumar Jagarapu: I Yeah, I understood. I just want to uh like understand your perspective of I mean where uh testing life cycle Satyasri Prabhakar Mantripragada: Yeah. Vara Kumar Jagarapu: ending. So that uh there should be some person uh who should uh take this kind of testing ownership and so yeah maybe we can discuss once there. Satyasri Prabhakar Mantripragada: Huh. Vara Kumar Jagarapu: Yeah. So that Satyasri Prabhakar Mantripragada: Okay. I think I give a high level input here itself. Vara Kumar Jagarapu: like Satyasri Prabhakar Mantripragada: So uh the squad model right the reason why we have developed a squad model is that the squad team itself is self-sufficient. 00:36:23 Satyasri Prabhakar Mantripragada: Okay they everybody is responsible for both development and QA roles as much as Vara Kumar Jagarapu: Yeah. Satyasri Prabhakar Mantripragada: possible. So if somebody does not have enough development work so I've asked Manisha and Raja to consider them as own within that sprint. So one resource may have say random work demo request ad hoc request to the address in which case it is not necessary that every day they have a demo request or an adop request once in a while it may come. So while that comes what they have to do is consider the stories of all the Rajashekar G: Big Satyasri Prabhakar Mantripragada: resources and then start validating those or write test scenarios on how do you want to test it. You may that we can decide on how we want to test it. But that guy plays the roles of the guy or girl plays the roles of role of a key resource. Vara Kumar Jagarapu: H. Satyasri Prabhakar Mantripragada: Also, Vara Kumar Jagarapu: Yes. Satyasri Prabhakar Mantripragada: Nav has suggested that they may add one or two resources to each of these squads to complement that. 00:37:26 Satyasri Prabhakar Mantripragada: But it need not be or it necessarily not be a QA typical Q. Vara Kumar Jagarapu: Yeah. Yeah. uh yeah I'm not expecting there should be a complete QS specific role but yeah like someone from team itself uh uh like assign that tag so that I mean that tag will might be changed uh every sprint might be but we need to come Satyasri Prabhakar Mantripragada: Yeah. Vara Kumar Jagarapu: up with some uh I mean practice so that like uh Satyasri Prabhakar Mantripragada: Good. Vara Kumar Jagarapu: like for that particular sprint someone will be answerable for that particular testing and Yeah. So mostly it should be directed from acceptance criteria only. Yeah. That's it. Yeah. I just have few questions over there. I will talk to you only. Satyasri Prabhakar Mantripragada: Yeah. Sure. Vara Kumar Jagarapu: We can take it from this is exactly what in my mind as Yeah. Satyasri Prabhakar Mantripragada: Sure. Yeah. Vara Kumar Jagarapu: Share only. Thank you. 00:38:19 Satyasri Prabhakar Mantripragada: And one more thing that I wanted to convey to Ganesh particularly is that Gia and PMA wanted to share their appreciations to uh Ganesh uh for the weekend the Friday work. I don't know Ganesh if you have gone to uh your friend's marriage but this has paid off that they were really appreciating you for staying back late and then supporting them with whatever is needed the last minute rush and all. Thank you. Ganesh Danuri: Thanks and thanks for you also. Yeshwanth Reddy Yerraguntla: Yeah, UI was really good. It was was so good. Satyasri Prabhakar Mantripragada: And those that were not part that were not available in the all hands right um you please understand that we are contributing to a very very good platform at the enterprise scale. So every contribution that you are making is going to make an impact on uh some or other industry as a whole. If you are taking manufacturing or anything this is a general kind of a platform. So we should be promoting whatever we are doing. 00:39:29 Satyasri Prabhakar Mantripragada: It's not just one specific client this time we are targeting but a group of clients which are going to leverage uh the enterprise dream. And one more thanks to Pawan. Uh we got we got this quickly shown we have quickly shown the uh basic governor of Gmail to goalu and nav Friday late evening while Ganesh is working on the other side on the UI improvement and they said okay and we may be rolling it out to few members in the leadership team now and thanks to Paw as well. Rajashekar G: Okay sir. Pan hasn't joined here. Satyasri Prabhakar Mantripragada: uh but these are some good things that have Rajashekar G: Yeah. Satyasri Prabhakar Mantripragada: happened. So we'll start using the uh Gmail integration that is we'll see how it comes out and then we'll have feedback and he also has certain action items uh to look into sync up with him get those action items add them to the backlog or take that whatever you can call it and prioritize the strength Rajashekar G: sync up with Pan, right? 00:40:41 Rajashekar G: Yeah. Got it. Got Satyasri Prabhakar Mantripragada: there one is the arbback implementation some Rajashekar G: it. Satyasri Prabhakar Mantripragada: I and then implement that within enterprise and there are few more Rajashekar G: Sorry. Can you can you please repeat sir or Satyasri Prabhakar Mantripragada: points in in we have Rajashekar G: backup? Satyasri Prabhakar Mantripragada: implemented arbback. So there is some admin kind of a control wherein they can map they can Rajashekar G: Okay. Satyasri Prabhakar Mantripragada: add users to roles and roles will have permissions. So you can grant one or more roles to an individual. the cumulative uh sum of all the roles will be granted to the user and that controls the privileges that the user may have. So instead of reworking on arbback for enterprise brain they suggested we better pick up Rajashekar G: Oh, Satyasri Prabhakar Mantripragada: that uh arbback implementation from directly into enterprise bra Vara Kumar Jagarapu: Now recent I think like I already spoke to someone about this not only that one the user module also Rajashekar G: okay. 00:41:44 Vara Kumar Jagarapu: if there is common like how the I mean other teams are implementing right so we thought of like checking with them uh so similarly like we can I mean no need Satyasri Prabhakar Mantripragada: Yeah, Vara Kumar Jagarapu: to do rework again or inventing again yeah whatever it may be not only this one like when Satyasri Prabhakar Mantripragada: got it. Yeah. Vara Kumar Jagarapu: you are coming up with some uh common thing in our repo so how others are doing like we just need to catch up with them and try to get practices on top of it like we see if we can use that modules uh something directly here. So recently like we did some NFRS in manager right. So for example the consents management system right or tempted management system. So like that like there are some packages already there. So if there any requirement like that we need to modify a little bit maybe we can raise to them or we can do directly uh as there are already present most of them are already present at the wi labs ownership itself. 00:42:42 Vara Kumar Jagarapu: Yeah, that's it. Satyasri Prabhakar Mantripragada: Yeah, that's what Narin was suggesting that have common modules created whichever were already done have been some somewhere in other projects. Let us reuse them as much as possible. And when you are developing something new, uh yeah fine. So that's all from my side. Rajashekar G: Your audio was cut in the Satyasri Prabhakar Mantripragada: Okay. Rajashekar G: middle. Satyasri Prabhakar Mantripragada: What I was saying is u anything that you are developing your objective should be that it will be reused by somebody else. So create it in such a way that it can be brought back to common library and be reused by some other product. Rajashekar G: Okay. Satyasri Prabhakar Mantripragada: Yeah, that's also my Yeshwanth Reddy Yerraguntla: Finally um so I'll leave it to Rajaka and Manisha to have their squad level scrums then from today onwards tomorrow Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: onwards um who all will be compulsory um I am not like suggesting anything like that even prair uh palash I don't know who all should join, who all should not join but definitely I'll be joining and uh any blockers on the previous day I'll I'll be available even though I'm saying that ideally when you have blockers try to get them resolved in the chat itself. 00:44:37 Yeshwanth Reddy Yerraguntla: Yeah. Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: See if Palash can join every day because this is scrum right. So every day how much we are moving we should know. Satyasri Prabhakar Mantripragada: I have asked Halas to join that is he was also sent the invite so he should be joining but I'll remind him today to take care of Yeshwanth Reddy Yerraguntla: Okay sir. Yeah that's all. Fine then. Bye. Rajashekar G: Yeah. Manisha Gundapuneedi: At Rajashekar G: Bye. Satyasri Prabhakar Mantripragada: That's Manisha Gundapuneedi: least somebody can get started on that unifier. Satyasri Prabhakar Mantripragada: how long. Manisha Gundapuneedi: fine. We are almost sure. Rajashekar G: Oh my god. Satyasri Prabhakar Mantripragada: Well, so anything that anything that that is independent you should identify and then start independent is Manisha Gundapuneedi: Sir Satyasri Prabhakar Mantripragada: only Hello. Hello. Hello. Manisha Gundapuneedi: PH dependenc NC data sources. I come up with chicken. Satyasri Prabhakar Mantripragada: That's what I suggesting like what I was suggesting is do you have any dependency on building a Ped no dependency 00:46:38 Rajashekar G: Everyone. Manisha Gundapuneedi: depend should be able to I agent should be able to uh already have data I mean knowledge about our industry it should be able to Learn chat interface escalations. It should be able to identify and send emails. Last demo of dashboard. Okay. I mean, so Satyasri Prabhakar Mantripragada: Okay. Manisha Gundapuneedi: The 16 Satyasri Prabhakar Mantripragada: So we'll proceed on that only Manisha Gundapuneedi: data Rajashekar G: So what I'm suggesting if we could prepare Manisha Gundapuneedi: Ara. Rajashekar G: so whatever is there like questions and answers life cycle is nothing but chart interface like interface answers Manisha Gundapuneedi: Oh no. Rajashekar G: interface alert life cycle and understanding escalations. Manisha Gundapuneedi: explations. Rajashekar G: this part come up with like any source escalation Manisha Gundapuneedi: Oh no. Rajashekar G: understand what is okay Manisha Gundapuneedi: So basically Rajashekar G: data connections. Oh no. Manisha Gundapuneedi: and so easy. Rajashekar G: This is like simulator. That is what that is. Manisha Gundapuneedi: I don't Rajashekar G: Friday. 00:50:16 Manisha Gundapuneedi: know. I don't know. Rajashekar G: Okay. Next, context propagation life cycle and question answer achil and knowledge base. So knowledge info and snapshot major focus user infoc Manisha Gundapuneedi: Indeed, Rajashekar G: So nextert only back Manisha Gundapuneedi: I did chase. Rajashekar G: WhatsApp only that particular module Manisha Gundapuneedi: I'm going to Uh Rajashekar G: WhatsApp. Manisha Gundapuneedi: separate Rajashekar G: This is like escalation of Manisha Gundapuneedi: taskh Rajashekar G: understanding. Manisha Gundapuneedi: discuss Rajashekar G: So, so Manisha Gundapuneedi: I don't Rajashekar G: best. Manisha Gundapuneedi: status. Rajashekar G: So, Manisha Gundapuneedi: Sorry. No Rajashekar G: You know, Manisha Gundapuneedi: way. Rajashekar G: chest 920 1020 1020 10:30. Manisha Gundapuneedi: Foreign speech. Foreign speech. Foreign speech. Rajashekar G: Okay. Done. Wherever Satyasri Prabhakar Mantripragada: I would suggest pooling Rajashekar G: it Manisha Gundapuneedi: Hey there sir. Satyasri Prabhakar Mantripragada: people. Manisha Gundapuneedi: Okay Satyasri Prabhakar Mantripragada: You play the role of technical lead project management. Manisha Gundapuneedi: sir. Satyasri Prabhakar Mantripragada: He should be able to handle that and he should have a clear picture on where things are 00:53:21 Manisha Gundapuneedi: Okay sir. Satyasri Prabhakar Mantripragada: going. We are done. Manisha Gundapuneedi: S. Satyasri Prabhakar Mantripragada: Then you execution team me from a timeline aspect. Manisha Gundapuneedi: Okay. Okay, sir. Satyasri Prabhakar Mantripragada: You should figure it Manisha Gundapuneedi: Okay Satyasri Prabhakar Mantripragada: out. Rajashekar G: Okay. Manisha Gundapuneedi: sir. Rajashekar G: Mickey Satyasri Prabhakar Mantripragada: Okay. Rajashekar G: board. Manisha Gundapuneedi: I mean Rajashekar G: Oh, no. Yeah. Got it. Manisha Gundapuneedi: Thursday, Rajashekar G: Okay, Manisha Gundapuneedi: Friday. Rajashekar G: right. Got it. Okay. Manisha Gundapuneedi: Foreign speech. Foreign speech. Foreign speech. Rajashekar G: Okay. Pific whatever is doing here Manisha Gundapuneedi: Maxford. Rajashekar G: will be the new one and training on that part is the new one but remaining interface alerting mechanism Manisha Gundapuneedi: I'm Rajashekar G: If that is the case, Manisha Gundapuneedi: dead. Rajashekar G: what needs to be done? And every time like Manisha Gundapuneedi: is Rajashekar G: generation Manisha Gundapuneedi: okay. Rajashekar G: Yeah. Manisha Gundapuneedi: Sorry. Rajashekar G: Okay. Manisha Gundapuneedi: Okay. Satyasri Prabhakar Mantripragada: Mhm. Manisha Gundapuneedi: Uh 00:57:06 Satyasri Prabhakar Mantripragada: I also suggest to set up some process Manisha Gundapuneedi: um Satyasri Prabhakar Mantripragada: daily. Manisha Gundapuneedi: I don't want Satyasri Prabhakar Mantripragada: I want him to be accountable. Manisha Gundapuneedi: Active Satyasri Prabhakar Mantripragada: kind of see how we can take it forward. Rajashekar G: Okay. Satyasri Prabhakar Mantripragada: Yeah. And maybe work towards next sprint. Rajashekar G: Got it. Got it. Satyasri Prabhakar Mantripragada: Good. Figure Rajashekar G: Sure. And Satyasri Prabhakar Mantripragada: out. Manisha Gundapuneedi: Pro last week. Are they? Rajashekar G: Yeah. Satyasri Prabhakar Mantripragada: Then you can get started on next Manisha Gundapuneedi: Oh, Satyasri Prabhakar Mantripragada: week. Rajashekar G: Sure. Manisha Gundapuneedi: heat. Satyasri Prabhakar Mantripragada: When we have it Manisha Gundapuneedi: Sure Satyasri Prabhakar Mantripragada: task Manisha Gundapuneedi: sir. Sir Satyasri Prabhakar Mantripragada: then you can get started on it. Rajashekar G: Sure. Manisha Gundapuneedi: in platform Satyasri Prabhakar Mantripragada: How many Manisha Gundapuneedi: I wanted to help with research on platform. So Satyasri Prabhakar Mantripragada: printable? Manisha Gundapuneedi: research I want to be part of Satyasri Prabhakar Mantripragada: Hey Manisha Gundapuneedi: it. Rajashekar G: Yeah. Satyasri Prabhakar Mantripragada: sir. Manisha Gundapuneedi: platform Satyasri Prabhakar Mantripragada: Yeah. Sure. Manisha Gundapuneedi: indirect. Transcription ended after 01:00:29 This editable transcript was computer generated and might contain errors. People can also change the text after it was created.