|Duration:||Classroom - 2 Days|
|Why Take This Course:||
This two days comprehensive course builds your knowledge and skills in the agile approach to defining and analyzing requirements. You will learn about the role of the business analyst on agile projects, and how to write user stories, which are the most common method of representing requirements in agile methods. You will learn techniques for building and managing a Product Backlog of user stories, and techniques for prioritizing requirements for releases and iterations.
You will learn the conditions of success for agile methods, how to scale the agile approach for large teams, and how to adapt your current business analysis methods to become more agile.
The agile method Scrum will be used as a reference method during the course, but the techniques described also apply to other agile methods.
You will apply what you learn in a series of hands-on activities using a realistic case study that takes you through the agile requirements process, with example solutions.
This course can also be taught on-site for a project team. The team’s project can be used as the basis for the course activities, resulting in the creation of key artifacts, such as the Product Backlog, the selection and prioritization of themes and stories for releases and iterations, and release and iteration plans.
|Learn How To:||
The course will help you practically learn on the following areas:
Defining Agile Requirements
Analyzing and Prioritizing Customer Needs
Planning Releases and Iterations
Adapting and Scaling Agile
|Format:||To help assimilate the tools and techniques learned, there is a mixture of group and team exercises throughout the course. The use of a realistic case study will help reinforce concepts learned. Students will need to be prepared for a high level of participation. Each participant will receive a comprehensive student guide complete with examples and workshop solutions.|
|Who Should Attend:||This course is valuable for all agile team members: business analysts, Product Owners, customer, users, Scrum Masters or project coaches, testers, developers and architects – anyone on a project who is involved in eliciting, defining, analyzing, and validating business needs and requirements in order to transform them into working software.|
|Prerequisites:||An awareness of agile and business analysis methods is helpful, but not required.|
Business Analysis Planning and Monitoring
Project Scope Management