Mar 25, 2026 Enterprise Brain Scrum - Transcript 00:00:00 Rajashekar G: Hi Vara Kumar Jagarapu: Yes, Rajashekar G: everyone. Yeshwanth Reddy Yerraguntla: Hi Raj. Hi. Hi Manisha. Vara Kumar Jagarapu: I think we have another sync up in 10 minutes. Uh yeah, I think like Rash is not there, Yeshwanth Reddy Yerraguntla: HRX. Vara Kumar Jagarapu: right? Rajashekar G: 9:00. Okay. Vara Kumar Jagarapu: Yeah. So at the top level, right? So uh I mean there are a few things like we thought of discussing with you uh me you pra so I think shall we use this call for that or otherwise uh can we go into fast details yes we Yeshwanth Reddy Yerraguntla: Yeah, we can do later also. Vara Kumar Jagarapu: can Yeshwanth Reddy Yerraguntla: Only thing is I have called till 11:00 Indian time. Vara Kumar Jagarapu: okay Yeah, Yeshwanth Reddy Yerraguntla: After that I'll be available. Vara Kumar Jagarapu: maybe then we can sync once again. Uh maybe meanwhile like if some dependencies are there for the team maybe Rashakar you can point out those things and get clarified team will 00:03:47 Rajashekar G: Okay. And now regarding uh the previous agenda, right? So I'll just put Yeshwanth Reddy Yerraguntla: Mhm. Rajashekar G: Yeah. So actually on the previous day we had a discussion with Navin Varu and uh Yeshwanth Reddy Yerraguntla: H, Rajashekar G: later on like uh what he said is the prioritization needs to change accordingly to provided Tata still first Yeshwanth Reddy Yerraguntla: right? But do we have the data? Rajashekar G: data said like and you guys did the analysis part and So how we need to take it further the Yeshwanth Reddy Yerraguntla: Mhm. Rajashekar G: clarity cover. Satyasri Prabhakar Mantripragada: So for now data analysis we did not find what we are looking Yeshwanth Reddy Yerraguntla: Okay. Satyasri Prabhakar Mantripragada: for but Rajashekar G: Okay. Satyasri Prabhakar Mantripragada: still that we realized and we asked them for further data that may come up today or Rajashekar G: Okay. Satyasri Prabhakar Mantripragada: tomorrow Rajashekar G: Okay. So Satyasri Prabhakar Mantripragada: we'll switch to Tatast Rajashekar G: okay sir. Satyasri Prabhakar Mantripragada: Still Rajashekar G: So prayer that uh I'll share my screen. Satyasri Prabhakar Mantripragada: Rajan Manisha. 00:05:51 Satyasri Prabhakar Mantripragada: Meanwhile, can you ensure that all the tasks and stories planned in sprint this sprint are completed? Rajashekar G: Sure sir. Satyasri Prabhakar Mantripragada: A few things are in review. Rajashekar G: Mhm. Satyasri Prabhakar Mantripragada: Uh please close them so that we get a grip of what the how the project looks like. Rajashekar G: Sure sir. So yesana regarding like another point the status of current working system we have explained to Navin sir. Yeshwanth Reddy Yerraguntla: Mhm. Rajashekar G: So we are mainly focusing on this arg snapshot schemas Yeshwanth Reddy Yerraguntla: Right. Rajashekar G: and real time and user awareness like multi these three like three agent orchestration will be set up. Yeshwanth Reddy Yerraguntla: Okay. Rajashekar G: So actually so we are in a good shape with this like what Abash has shown me Abash is providing me the database tables and everything by today or tomorrow this communication part we need to ensure Yeshwanth Reddy Yerraguntla: Okay. Rajashekar G: like Yeshwanth Reddy Yerraguntla: User agent also I'm almost done. Rajashekar G: yeah how it Yeshwanth Reddy Yerraguntla: Um Rajashekar G: needs to how we need to pro proceed with the code and clarity under that is one part and once that is done what NA said Gmail is the not prioritized one Gmail data source we can dep prioritize Gmail we can think like a custom database a custom database is the first data source we need to integrate for 00:07:14 Yeshwanth Reddy Yerraguntla: Okay. Rajashekar G: that if Tata steel comes up we will be hooking up the Tata steel data if Tata steal is not there we will be working with the cautilia. Cautilia as a custom data source. Yeshwanth Reddy Yerraguntla: Okay. Rajashekar G: Uh you you are aware of cautilia. Yeshwanth Reddy Yerraguntla: Some Rajashekar G: Uh so cautilia will be the custom data source and whatever can be done in Yeshwanth Reddy Yerraguntla: work. Rajashekar G: the data source agent we need to prioritize and complete that uh as a custom data source first. Yeshwanth Reddy Yerraguntla: Okay. Rajashekar G: So once the communication part is done uh so that we will be jump and hook that uh data source part into it and uh see what can be possible. Yeshwanth Reddy Yerraguntla: I'll give the KT tomorrow then you can set up a call Rajashekar G: Okay. And uh Yeshwanth Reddy Yerraguntla: uh all communication channels how they are working Rajashekar G: okay, Yeshwanth Reddy Yerraguntla: uh I will give except for the user user uh sorry what is that the topmost agent right uh UI agent except for Rajashekar G: you agent. 00:08:22 Yeshwanth Reddy Yerraguntla: that the other two are done with along with mark Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: data for data agents also right Rajashekar G: Okay. Yeshwanth Reddy Yerraguntla: so we can have that discussion tomorrow custom data Rajashekar G: Okay. So that Yeshwanth Reddy Yerraguntla: source uh cautilia you can you can actually get started then because you already have control Rajashekar G: is Yeshwanth Reddy Yerraguntla: of all of the trades Rajashekar G: uh we can start but that will be like previous enterpint version right now whatever we are doing multi- aent orchestration and all that should be our major agenda. So the platform should strengthen with multi-agent orchestration and this cautilia commands it as a data source agent. Yeshwanth Reddy Yerraguntla: Got it. Rajashekar G: Then if this is working well in future if something comes up like uh what I can say data steel data is figured out and how it is there that Tata steel data data completely will act as a another data source data. Yeshwanth Reddy Yerraguntla: We are on the same Rajashekar G: Yes. Yeshwanth Reddy Yerraguntla: page. Rajashekar G: So right now I can see one more challenge is the UI uh UI also need to be planned. 00:09:30 Yeshwanth Reddy Yerraguntla: Yes. Rajashekar G: On Monday the design team will come up with the UI data frame UI frames. Yeshwanth Reddy Yerraguntla: Okay. Rajashekar G: So right now uh Ganesh is working on the uh experience center. whatever he's working on is uh uh like uh in react he's building a react package and also an agent package so that agent will understand and do all the drill down calculies and some pre-plant pictures on the react dashboard and Anita is working on the uh chart interface conversion into react application Yeshwanth Reddy Yerraguntla: Um, Rajashekar G: converter right now enterprise brain we are using pyog Yeshwanth Reddy Yerraguntla: okay. Rajashekar G: library there uh she's working on a react uh entire react code to convert the entire chart interface into react version. Yeshwanth Reddy Yerraguntla: How far is it Rajashekar G: Uh yesterday she has shown me something like the screen is done chart screen. Yeshwanth Reddy Yerraguntla: done? Rajashekar G: I need to sync up with her and get the clarity more. Yeshwanth Reddy Yerraguntla: Okay. Rajashekar G: For that we need to make changes in the back end also like uh right now the back end API calls and everything we did some changes in the a enterprise previous repository. 00:10:47 Rajashekar G: Right now whatever you are new uh approach like a new KT and all once that is done we need to see how this will be linked with that react application. Yeshwanth Reddy Yerraguntla: Okay. Rajashekar G: Yeah. Yeshwanth Reddy Yerraguntla: Yeah. Rajashekar G: So this is the enter status and one more thing praas we have deployed that demo.goomy.com only uh in which there are three connectors those can be handled with the flags in the environment variables. So right now three are enabled mean test each each individual RPC test that's uh working as expected. Satyasri Prabhakar Mantripragada: Okay. Rajashekar G: head office then we will give that to pre-sales team and down the demo.domi.com Satyasri Prabhakar Mantripragada: Sure. Sure. Rajashekar G: and uh the Gmail Gmail rolling out also we are in progress and yesterday we have deployed the back end to sync but there is one issue we came up with while syncing the data pan is looking into it once done I'll update you today so yes the rolling out of Satyasri Prabhakar Mantripragada: Okay. Rajashekar G: Gmail source to the management team also we are working on 00:12:00 Yeshwanth Reddy Yerraguntla: H. Yes. Satyasri Prabhakar Mantripragada: Uh Rajar uh you know that the deadline for Gmail integration is this Friday. You cannot go beyond. Rajashekar G: Yes. Yes sir. Satyasri Prabhakar Mantripragada: Even if an issue comes, Rajashekar G: Yes. Satyasri Prabhakar Mantripragada: we are dropping it off. Rajashekar G: Yes sir. Yes. Yeshwanth Reddy Yerraguntla: What? What is dropping Satyasri Prabhakar Mantripragada: So there is a lot of work done on Gmail integration this month but we are not able to put it to Yeshwanth Reddy Yerraguntla: off? Rajashekar G: Actually Satyasri Prabhakar Mantripragada: production. So one resource is continuously being occupied with anal analyzing one or the other issue on that rather we put a put a stop through it and then move the resource to some other useful feature for the enterprise brain actual platform because whoever customer is coming they won't be asking for a Gmail Yeshwanth Reddy Yerraguntla: Got it. Satyasri Prabhakar Mantripragada: integration or an outlook integration at this moment. So rather we spend that time and resource for something that is useful for the future vision. 00:12:52 Yeshwanth Reddy Yerraguntla: Got it. Rajashekar G: Yeah. So this was the agenda we wanted to discuss with you previously. So team breakdown for JHRX aka you are clear that team breakdown like right now Anita and Ganesh is working on the UI part. Satyasri Prabhakar Mantripragada: Now, why do we need the H1 for the team Rajashekar G: Uh, Satyasri Prabhakar Mantripragada: breakdown? Rajashekar G: not needed, sir. Like previous Manisha Gundapuneedi: Fore Rajashekar G: Okay. GHX works going to be start by today. Okay. Manisha Gundapuneedi: speech. Rajashekar G: Okay. And one more part like major part the dui usage actually right now we are not using the d in our brain system so basically why I said him like and one more thing that she's taking lot of time like mult multiple questions different but right now whatever we are building is completely different and why you are not Yeshwanth Reddy Yerraguntla: All right. Rajashekar G: enforcing the team stronger Yeshwanth Reddy Yerraguntla: Yeah. It is taking a lot of time to give answers, sir. Rajashekar G: I'll check what he said is feedback if you can correct it and uh 00:14:51 Yeshwanth Reddy Yerraguntla: Yeah, ideally you should improve the Manisha Gundapuneedi: Basic Rajashekar G: Correct. Manisha Gundapuneedi: feedback. Yeshwanth Reddy Yerraguntla: correct fixture. Rajashekar G: can right now system like uh we don't have a proper product spec B brd we don't have Yeshwanth Reddy Yerraguntla: Are we going to Rajashekar G: that Yeshwanth Reddy Yerraguntla: actually Rajashekar G: that's too much of if not like why we did all this We would have created a BRD and uh break down this entire thing using Yeshwanth Reddy Yerraguntla: Whatever we did to put it in du and generate br is not too much of an Rajashekar G: DKA. Yeshwanth Reddy Yerraguntla: effort. The discussions are needed to understand where we align. Du will give its own BRD with the limited data. Right. Rajashekar G: And I'm stuck with like right now if the action for how we can take it forward. Satyasri Prabhakar Mantripragada: range uh ask him if he can reverse engineer from this diagram. See ideally as you said is the ideal situation where you should have a BRD or a product spec and you get into this 00:16:29 Rajashekar G: Yes. Satyasri Prabhakar Mantripragada: level but because we are we have started with something that is not certain like Rajashekar G: All Satyasri Prabhakar Mantripragada: we have been evolving the features. So at that point of time with that dynamism we cannot come up with a product spec. Rajashekar G: right. Satyasri Prabhakar Mantripragada: If that was the case, we would not have even have come this far in the product development, right? We were still maybe in in the finalizing the product spec itself by now. So now that we have some clarity on the overall application and the goal of the application, we can probably give this this diagram to D or some a agent or some tool and reverse engineer to get the product specs at the overall product spec level and the feature level specs. So that should help you get started. Rajashekar G: Okay. Satyasri Prabhakar Mantripragada: Let Rajashekar G: Come on. Yeshwanth Reddy Yerraguntla: retrospective. Satyasri Prabhakar Mantripragada: us Yeshwanth Reddy Yerraguntla: Anyway, we did hard work Satyasri Prabhakar Mantripragada: future enhancements. We'll take it in version two. 00:17:36 Yeshwanth Reddy Yerraguntla: and du is not just sorry Satyasri Prabhakar Mantripragada: Sorry. Continuation. Yeshwanth Reddy Yerraguntla: and du is not just brd. After BRD you have P product requirement based on product requirement you have task breakdown you have LLD all those things whatever is not pending right whatever is sorry pending right now uh you can continue using D to generate those sorry elaborate Satyasri Prabhakar Mantripragada: Yeah, I was just suggesting have this as the version one of it. This is our first milestone that we have committed to. Over a period of time as we grow our thoughts evolve and this yeah this architecture will also evolve but that will not be considered in the current scope otherwise it will be a scope creep unnecessarily. So whatever is as on today whatever is available for us that we we promise to Yeshwanth Reddy Yerraguntla: Yeah. Satyasri Prabhakar Mantripragada: deliver. If it takes two months it takes two months and we deliver that. But however we are open to make enhancements to this architecture diagram and functionality that will come in subsequent 00:18:48 Rajashekar G: Got Satyasri Prabhakar Mantripragada: versions. Rajashekar G: it. Satyasri Prabhakar Mantripragada: Hope I'm making sense there. Rajashekar G: Yes sir. We need to do the reverse engineering first and whatever is pending those are V1 and PES. like uh BRD, PRD and then we Satyasri Prabhakar Mantripragada: Yes. Yes. Rajashekar G: will Satyasri Prabhakar Mantripragada: You'll start working on that branch. Rajashekar G: Okay. Satyasri Prabhakar Mantripragada: So all your deliverables will be against whatever is in your your current branch say V1.0 PRD will be this architecture diagram and Rajashekar G: H Satyasri Prabhakar Mantripragada: its related PRD and all your deliverables will be mapped against Chaneka 1.0 zero. Meanwhile, the product uh owner will continue to work on evolving this uh enterprise Rajashekar G: sure. Satyasri Prabhakar Mantripragada: brain new features adjuster, new capabilities adjuster that will be in Chaneka 2.0. Rajashekar G: Okay. Satyasri Prabhakar Mantripragada: Okay. Until you are done with it, we'll not pick that Rajashekar G: Okay. Satyasri Prabhakar Mantripragada: up. Vara Kumar Jagarapu: One minute. Are the other meeting I think like um needs to be Yeshwanth Reddy Yerraguntla: Okay. Vara Kumar Jagarapu: started. We can connect. Okay. Transcription ended after 00:20:39 This editable transcript was computer generated and might contain errors. People can also change the text after it was created.