While Scrum avoids role labels such as Business Analyst (BA), the career BA often plays a critical role in the success of agile project teams.
There are different opinions on how a BA can best contribute to a team, including repurposing the role into product owner.
Many agile teams write stories and rely completely on conversations about those stories for elaboration. This can be problematic when building complex systems. Often, underlying business rules are difficult to communicate clearly and accurately, and a bridge is needed between the story and acceptance criteria. Additionally, understanding team members’ different learning styles can help determine the best practices for describing requirements on a team.
This session provides a description of key skills and tools that skillful BA’s often use, aligns those skills and tools with typical agile software development frameworks such as Scrum and Kanban, and offers best practices for maximizing the value of your BA.
The session also introduces a Visual, Aural, Read/write, and Kinesthetic (VARK) learning style assessment and describes requirements elaboration practices best suited to each learning style.
