# Minutes of Meeting - Enterprise Brain Scrum **Date:** March 15, 2026 **Duration:** ~60 minutes **Source transcript:** [20260315.txt](20260315.txt) **Attendees:** Yeshwanth Reddy Yerraguntla, Satyasri Prabhakar Mantripragada, Manisha Gundapuneedi, Rajashekar G, Vara Kumar Jagarapu, Abhilash Adunuri, Ganesh Danuri ## Act I - 00:00 to 00:03, reset the cadence before the sprint picks up speed The meeting opened by reworking the scrum operating model rather than discussing features. Satyasri proposed moving the daily scrum to 8:30 AM and shrinking attendance to squad leads and practice leads, with squad leads handling the internal updates for their own people. The intent was to stop burning the whole team on a synchronous call when a smaller layer could absorb routine status. Yeshwanth pushed back on any process that simply deferred blockers until the next morning. The team is spread across time zones, so in his view the product should behave like a 24/7 delivery machine instead of a once-a-day queue. He wanted a path for immediate unblock even if the daily scrum itself becomes lighter. > *"I don't want this waiting time of next day morning."* > — Yeshwanth Reddy Yerraguntla _(~00:02:30)_ The group converged on a compromise: daily status should still exist, but squad leads can represent the rest of the team, and the asynchronous layer should carry the detail. That keeps the live meeting short while preserving the ability to react when something is truly stuck. ## Act II - 00:03 to 00:10, build the tooling first, then let the team use it Yeshwanth then walked through the support work he had been building in the repo. The enterprise-brain repository now has scaffolding so agents and copilot can understand the platform before writing code, and the new `meeting-sprint-sync` workflow turns meeting transcripts into MOMs and sprint status artifacts. He also showed that Jira access is now part of the workflow, which means the team can pull sprint context from Jira instead of trying to reconstruct it from memory. > *"I was able to create a summary of current sprint."* > — Yeshwanth Reddy Yerraguntla _(~00:09:30)_ The important shift was that LLDs are no longer optional brainstorming notes. Every sprint ticket needs a document with scope, architecture, acceptance criteria, and test criteria before implementation begins. Yeshwanth set the expectation that this is how junior engineers should learn the system: do the reading, write the LLD, then come back with a buildable story. ## Act III - 00:10 to 00:23, lock the task shape before opening implementation Rajashekar pushed back on letting the exercise drift into open-ended research, and Yeshwanth agreed to cap the preparation window at 16 hours. Abhilash confirmed that questions would surface while writing, and Yeshwanth explicitly told the team that most of the context should be reachable through the repo, the squad leads, or the enterprise-brain chat itself. That same segment is where the group corrected the ticketing logic: one exploration ticket should fan out into the lower-level work rather than skipping directly to implementation. The benefit of that discipline is that the team can split the work cleanly enough to move on. Once the exploration notes are solid, the sub-tasks can be created with real boundaries and no one has to guess where the design ends and the build begins. ## Act IV - 00:23 to 00:32, reconnect Jira, docs, and ownership Vara raised the link between the ticket system and the design docs: Jira should point at the relevant LLD page so the ticket remains the source of truth while the deep context lives in markdown. Yeshwanth agreed and said he would demonstrate the pattern on his own tickets so the rest of the group could follow it. > *"Jira task is source of truth."* > — Vara Kumar Jagarapu _(~00:27:00)_ From there the meeting hardened into process standards. Definition of done means done-done, not a draft waiting for review. Every code push needs a Jira reference. Testing is not a side activity but an explicit ownership area for the sprint, with the squad model deciding who carries QA for what. ## Act V - 00:32 to 01:00, reuse existing modules, then close with the operating contract Satyasri also reinforced that the team should reuse working modules from other products whenever possible, especially RBAC and shared account-management building blocks. The message was simple: do not rebuild something that already exists in another product line unless the reuse path is impossible. The recognition segment mattered too. Ganesh was thanked for staying back to finish a UI change, and Pawan's Gmail integration got called out as a promising demo thread that could be shown upward. Rajashekar also flagged that Manisha's team may be redirected into Tata Steel, which means the squad allocation can shift as the broader account plan shifts. By the end, the scrum had become less about a single sprint and more about a delivery contract: from the next day, the team would run scrum at 8:30 AM, squad leads would carry the internal updates, blockers would surface in chat first, and the LLD would be the first place to look before anyone touched code. ## Todos Complete the LLD document for each assigned ticket with scope boundaries, architecture diagrams, acceptance criteria, and testing criteria.
All developers EOD Mar 16 (+16 hrs) Set up the Jira personal API token and place it in the `environments/` env file so the workflow can read sprint context directly.
All team members Mar 16 Link each LLD/docs page URL into the corresponding Jira ticket description.
All developers Mar 16 Start the new sprint formally after the capacity discussion is complete.
Vara Kumar / Rajashekar / Manisha Mar 15 Work on the context propagation life cycle LLD and implementation path.
Yeshwanth Mar 19 Work on the Q&A life cycle LLD and implementation path.
Yeshwanth Mar 19 Align on QA ownership and sprint testing rotation with Vara and Satyasri.
Satyasri / Vara Kumar Mar 16 Sync with Pawan on the Gmail integration demo and capture follow-up action items in the backlog.
Rajashekar Mar 16 Reuse the existing RBAC implementation from the other product instead of rebuilding it in Enterprise Brain.
Rajashekar / Platform Squad Current sprint Enforce the Jira-ticket reference rule for all code commits going forward.
All developers Immediate Remind Palash to join the daily scrum.
Satyasri Mar 16 Post daily status updates in a shared space so the team can consume them asynchronously.
All team members Daily, starting Mar 16 Investigate and fix the intermittent Vasa/docs deployment downtime with Nitish.
Rajashekar This week