Contactar
About this course:
Agile environments are causing a shift in how a business analysis professional works. There are some new rules. While some agile teams do not have a formal role called Business Analyst, business analysis skills are needed on agile teams. BAs possess unique skills including clear communication, organization, facilitation, requirements elicitation, critical thinking, and requirements analysis and management skills. Additionally agile teams often expect team members to cross over and perform tasks traditionally done by other specialized roles. Since most business analysis professionals are experienced at assisting in extra responsibilities and are trained collaborators, they can make excellent agile project team members.This course is designed to show how business analysis fits in an agile environment and highlights the reality that business analysis activities are absolutely necessary. For the Business Analysis practitioner you will understand how the skills you have will help you become a valued agile team member.
Students will gain knowledge and skills by practicing techniques and soft skills needed to operate effectively in a requirements-driven agile environment.
At course completion:
After completing this course, students will be able to:Agile approaches, key principles, practices and terminology focusing on Scrum.
How to transfer traditional skills, techniques and tasks of a Business Analyst to an agile environment to add value to the team.
How the entire team gets engaged with requirements and how the BA facilitates this process.
The importance of planning in an agile environment and how to assist product owner and team during each of the levels of agile planning
How to assist the product owner to develop and prioritize the product backlog and how changes are managed.
How to facilitate eliciting the appropriate level of requirements detail pre-iteration, during an iteration, and post iteration.
To develop user story requirements and specify acceptance criteria to assist the product owner, domain stakeholders, and the team to build a quality product or system
To use formal and informal methods of communication requirements, adjusting the level of detail and elaborating requirements iteratively as needed while developing “just enough” documentation.
New techniques that are useful for agile environments such as, commitment based planning, product visioning, user story writing workshops, estimating with story points, purpose based leadership and more.
Audience profile:
This course is designed for business analysts, systems analysts, product owners, project managers or any other project team member involved with requirements on an agile project. This course may also be appropriate for individuals who manage business analysts and need a more in-depth understanding of the process and skill set a business analyst can bring to an agile project.Before attending this course, students must have:
This is an advanced class. We recommend students first attend our Core classes or have equivalent experience.Faculty:
Our team of highly qualified instructors combine training activities with the development of their profession as experts in the field of TIC. Professionals certified by the major manufacturers capable of transferring an enjoyable and easy to understand technical concepts more abstract.Documentation:
A copy of the official B2T Documentation.Certification:
Lets get the B2T official diploma of the course "JIS 413 - Business Analysis in an Agile Enviroment".Course outline:
Introduction
1.1 Review common project approaches.
1.2 Discuss solution requirements efforts for various types of projects.
1.3 Review requirements categories and classifications.
The Agile Environment
2.1 Overview of agile principles, methodologies and terminology.
2.2 Learn values and principles from Agile Manifesto.
2.3 Learn how plan-driven (traditional) vs. change-driven (iterative, agile)
development approaches impact business analysis tasks and priorities.
2.4 Discuss business and IT benefits for using a light agile framework.
2.5 Workshops:
· Scrum simulation.
· Create list of challenges and benefits moving from a traditional
environment to an agile environment.
Roles in an Agile Environment
3.1 Understand the various roles in an agile environment.
3.2 Understand what activities are performed by the roles used in an
agile environment.
3.3 Workshop: Comparison of roles and activities in traditional and agile
environments.
Writing User Stories
4.1 Learn how to write user stories.
4.2 Write user stories at the appropriate level of detail following guidelines of 3 Cs (card-conversation–confirmation) - and INVEST techniques.
4.3 Develop a Product and Sprint Backlog.
4.4 Learn how to identify non-functional requirements and acceptance criteria in an agile environment.
4.5 Workshops: Multiple workshops on writing and organizing user stories.
Agile Planning and Estimating
5.1 Learn the levels of agile planning and how the business analyst is involved.
5.2 Learn the difference between traditional planning and agile planning.
5.3 Define the product vision and project purpose.
5.4 Learn how to estimate on agile projects using story points and planning poker.
5.5 Conduct iteration planning meetings.
5.6 Workshops:
· Create a product vision.
· Release and iteration planning.
· Planning poker session to estimate size of stories.
Applying BA Skills in the Agile Environment
6.1 Learn to develop and maintain a product backlog.
6.2 Learn how to use face-to-face communication to replace formal requirements documents where appropriate.
6.3 Use informal models to communicate requirements.
6.4 Learn to transfer traditional BA Skills to an agile environment.
6.5 Workshops:
· Create list of ideas how a business analyst can best be utilized on an
agile project based on scenarios.
· Deriving user stories from traditional models.
· Use examples to elaborate requirements and generate acceptance
criteria.
6.6 Develop an Action Plan with next steps on the student's current project.