Requirements to Code
EXCUTIVE DECISON – NON–TECHNICAL Track
1:10 PM - 2:00 PM
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 will provide a description of key skills and tools that skillful BAâ€™s often use. These will be aligned with the approach used in typical agile software development methods such as Scrum and Kanban, and best practices for maximizing the value of your BA will be offered. Participants will complete a VARK learning style assessment and learn requirements elaboration practices that are best suited to each learning style.