Presented By: Brian Adkins & Rick Smith
Leadership Track: 2:45pm-3:45pm
Presentation Materials: Download
The Product Owner and Scrum Master are important to the success of an Agile team for different reasons. Explore the distinct responsibilities of each role, the skills and attributes necessary for success, and learn best practices to address questions like: Can a single person serve as Product Owner and Scrum Master? Is a Scrum Master the same as a project manager? Can a developer also be the Product Owner? Can the roles be rotated among the team?
Presented By: Susan Fojtasek & Tonya Guadiz
Leadership Track: 1:30pm-2:30pm
Presentation Materials: Download
The Business Analyst and Quality Assurance analyst are important to the success of an Agile team. Explore the distinct responsibilities of each role, the skills and attributes necessary for success, and learn best practices to address questions like: Can a single person serve as both BA and QA? What are the BA/QA responsibilities in an Agile team? What are common pitfalls with these roles and how can they be avoided?
Presented By: Mike Stout & Jay Packlick
Leadership Track: 9:45am-10:45am
Presentation Materials: Download
Successful projects depend on deeply understanding users needs. Too often though, during the transition from traditional methods to Agile, teams move too far to the left interpreting “working software over comprehensive documentation” as an excuse to abandon capturing and communicating requirements. User Stories can be an extremely effective technique to communicate requirements, but they require the disciplined application of new skills. The good news is those skills can be acquired with a little guidance.
Join Mike and Jay as they share their experience from the trenches coaching teams to achieve proficiency in this technique. They’ll be covering the fundamentals such as
• Why you should care about User Stories
• How to write and use them effectively without resorting to ‘comprehensive documentation’
• Simple techniques you can apply so that teams understand what ‘done’ means
• Common pitfalls and how to avoid them
• What to do when your team’s situation doesn’t mirror the agile ideal
In true agile form, you’ll have an opportunity to submit your own ‘requirements’ for the session so that we can address the most pressing questions and concerns about User Stories.
