Kalindi Chhabra
Career spanning over 16 years, Kalindi is an experienced professional in areas of business analysis, strategy, and consulting. She specialises in Financial Services, predominantly Insurance. Kalindi is currently acting as a Business Analysis Chapter Lead in QBE Insurance leading a team of Business Analysts for our Small and Medium-Term Enterprises and Commercial customers.
Kalindi is passionate about Business Analysis as a profession and takes pride her ability to navigate unknown and complex situations.
As a Lead, Kalindi strives to develop the BA chapter and continuously bring innovation and outside in perspective into the chapter to grow and motivate the team.
Presentation: Agile Business Analyst’s contributions from ideation to execution
Agile BAs contribute across all stages in the lifecycle from the time an idea is generated until the feature is delivered to the end user. They work at value stream level as well as squad level to effectively contribute towards delivery.
- Idea Identification: BAs assist the idea generators who are typically the Product managers or Business users in documenting the business need as a high level as-is statement and a desired state. They help with the outcome hypothesis to ensure the idea has measurable benefits. They help in drafting scope including processes, systems, and customer impacts.
- Funnel Process: BAs can also provide inputs to the Product Managers in reviewing the assessment including high level benefits, costs, regulatory impacts, and any non-financial metrics. They can contribute towards prioritisation of ideas to be taken into discovery.
- Discovery: Discovery brings together cross-functional skills to focus on understanding the problem, designing the most valuable solution, and validating it before committing to delivery. BAs can assist with creating a Lean Business Case articulating business and user value, as well as the features that it is comprised of (MVP and additional features).
- Feature Refinement: BAs help product managers refine the features by listing the acceptance criteria’s and linking then to the key results. Feature is split into high level stories, sized, and placed in the backlog.
- Delivery: When the feature is picked up in a program increment, stories are refined to deliver the functionality to the end user. BAs develop acceptance criteria for user stories and enabler stories and shipped for development.