I'm seeking advice and any links describing how successful teams orient BA's when they are on Kanban delivery teams. Specifically how BA's can develop a deep understanding and relationship with business departments, while being on teams that are NOT dedicated to a business department's work.
An organization has five teams. Each team has 2+ developers, QA, BA, PM, and Ux. In theory any team should be able to pull a story submitted by any internal department, which are in a prioritized portfolio queue. The teams are NOT product/department focused. Since there are a wide variety of departments whose work can be pulled, can the BA's in this scenario adequately provide in depth business related analysis as they move from request to request among several departments?
Thanks.
Hi JMJ,
If you are part of the Agile/SCRUM team you are part of the group charged with the delivery of the actual product. It should not be your job to know everything there is to know about the business. That should be the role of the "Product Owner" or "Business Stakeholder". Most likely, as a BA, your focus should be on writing clear use stories and acceptance criteria based on collaboration with the product owner or business stakeholder. There are areas in which the BA can add value without having deep business domain experience: collaborate with horizontal teams/roles such as architecture and user experience, perform unit testing for stories in a given sprint, etc.
Adrian
brought to you by enabling practitioners & organizations to achieve their goals using:
enabling practitioners & organizations to achieve their goals using: