Coming from an e-commerce background at Flipkart, I’ve seen how fast-paced and unpredictable digital projects can be. Now, as I undergo Business Analyst (BA) training at COEPD, one thing is becoming very clear—Agile methodology is no longer optional, it's the norm. And within Agile teams, the role of a BA is more important than most people think. Earlier, I used to believe that Business Analysts were just responsible for writing requirement documents. But after being exposed to Agile concepts during my training, I now understand that the BA is the bridge that keeps the product vision, customer needs, and technical execution all connected. In Agile, we don’t do heavy documentation at the start. Instead, we work in short spirnts of development, usually of 2 to 4 weeks long. This means a BA has to be involved continuously, not just at the beginning of the project. In my experience at Flipkart, especially while working with cross-functional teams on categories like furniture and medical supplies, I saw how difficult it can be to align tech, design, and business. There were many times when feature rollouts got delayed or misunderstood simply because of miscommunication. Now, when I look back with a BA’s lens, I realize this is exactly where a Business Analyst working in Agile can make a difference. As a BA in Agile, the first major task is to play the role of a Product Owner. The PO defines the high-level business goals, converts those into actionable user stories, backed by proper acceptance criteria. For example, if the goal is to reduce customer returns in the furniture category, a PO would break that down—maybe suggesting changes to product descriptions, delivery slot features, or customer review mechanisms. They make the “what” clear to developers and explain the “why” behind every feature. Another important area is backlog refinement. Agile doesn’t work well if stories in the backlog are vague or unclear. The BA works with the team to make sure each item is well-defined, prioritized, and understood by everyone. During sprint planning, they clarify doubts, provide business context, and ensure that the tech team is building the right thing—not just building fast. In daily stand-ups and sprint reviews, the BA plays the role of a communicator. During my time in category management, I often had to mediate between logistics teams, product designers, and marketing heads. That experience helps me now visualize how BAs act as facilitators in Agile—keeping everyone informed and aligned, while also gathering feedback for future sprints. One key takeaway from my COEPD training is that Agile doesn’t mean no documentation—it means smart documentation. BAs still create user stories, flowcharts, and wireframes—but only what’s needed to keep the team moving. Tools like JIRA, Confluence, etc, are essential for this. I’ve also started exploring these tools hands-on, and it’s interesting how they simplify work management when used effectively. Another skill I’ve had to develop is comfort with changing priorities. In a traditional setup, once requirements were frozen, they rarely changed. But in the Agile, the changes are expected and are welcomed. At Flipkart, I remember how fast campaign strategies changed based on customer behavior. That agility is now reflected in how BAs must adapt quickly—whether it’s updating a user story or changing the sprint scope based on stakeholder feedback. From my point of view, the Business Analyst in Agile is like the glue holding everything together. Developers build the product, testers ensure quality, and product owners set direction—but it’s the BA who keeps everyone aligned and ensures that what’s being delivered actually solves the business problem. The ability to connect business with technology is what makes this role so valuable. To conclude, my understanding of a BA’s role in Agile has completely changed over the past few months. It’s not just about writing requirements—it’s about facilitating collaboration, driving clarity, and helping the team deliver real value in every sprint. As I move forward in my BA career, especially with my Flipkart experience as a foundation, I’m excited to contribute more in Agile environments where speed, clarity, and adaptability truly matter.