- Course Topics
- Client testimonials
Who the course is for:
- Product Owners
- Business (System) Analysts (BSA or BA)
- Scrum Masters
- Senior IT Project Managers
- IT Specialists
- Scrum Team Members
- Compare Agile Methods and Roles to Traditional Waterfall Methodology
- Define processes for gathering requirements in an Agile environment
- Use Visioning to start the development of an Agile Project
- Break down methods for Agile Requirements gathering
- Learn about prioritization techniques in an Agile environment
- Managing Agile changes
- Testing in an Agile environment
- Access to applicable tools
- Consistent professional terminology in the field of project management
- An international expert available for consultation (during and after the training course)
- Sharing experience with other participants and opportunity for business networking
- Improving your business English skills
After the training, the participant receives a certificate of its completion.
Recommended books from our Bookstore:
Requirements gathering has been a major bottleneck for many companies, agencies and organizations around the world in their efforts to develop and deploy projects.
When do you start, how much do you gather right away and how much do you obtain later? The Waterfall Methodology has developed clear guidelines on what needs to be gathered and when.
This course focuses on defining requirements gathering processes in an Agile environment as well as teaching you how to use tools and techniques to help you execute these processes.
You will learn how to create project Visions and the level of requirements gathering you will have to perform for each stage of the fluid Agile development process.
This is an interactive course where you will learn about the principles and processes first and practice them later in several case studies to ensure you fully understand the meaning and purpose.
Large (not broken down) requirements or not clearly defined requirements can have a significant negative effect on a project’s successful realization.
Make sure you know how to define and document requirements in an Agile project environment and supporting the successful development and deployment of your Agile Project.
1. High Level Overview of Agile
- History of Agile
- Manifesto for Agile Software Development
- Principles behind the Agile Manifesto
- Agile Frameworks
- Agile Value Proposition
- Paradigm Shift
- Agile Lifecycle
- Scrum High Level Overview
- Defined Roles
- Statistics - a survey
2. Product Vision
- Values - Breaking it down
- What and Why
- Main components
- When is the Project Done?
- Conditions of Satisfaction - Sample
- User Roles
- Personas Examples
- Product Backlog
- Product Backlog Prioritization
- Kano Prioritization
- Product Roadmap
- Release Plan
3. Requirements (High Level)
- Requirements - Best Practices
- Stakeholder Engagement
- Stakeholder Engagement - Six Stages
- Stakeholders Analysis
- Requirements - Best Practices
- Requirement Levels
- Techniques to Identify Requirements
- High Level Use Case Diagrams
- User Stories vs High Level Use Case Diagrams
- Use Case Diagram (example)
- User Interface Flow Diagram
- Technical Debt
4. Breaking down Requirements
- Requirements Breakdown
- User Stories - Definition
- Good User Stories
- User Stories - Template (User Voice form)
- User Stories – INVEST
- User Stories – Tasks
- User Stories - Definition of Done
- Definition of Done - Example
- Story Mapping - Six Steps
- Story Mapping - Example
- Discussion Story Mapping
- Epic and Story Splitting
- Complex and Compound Stories
- Complex Stories
- Splitting Compound Stories
- Patterns for Splitting Stories
- How to Split a User Story
- Non-Functional Requirements
- Other types of stories
- Discussion Writing Technical Stories
5. Acceptance Criteria and Testing
- Story Details
- Successful Testing
- Acceptance Criteria
- Agile Testing Quadrants
- Acceptance Test Strategy
- Acceptance Tests in Agile
- Business Rules
- Testing Types
- Testing What Why Where When Who
- Test Driven Development - TDD
- Behavior Driven Development- BDD
6. Architectural Epics
- Agile Architectural Epics
- Business Drivers
- Scaling Agile Requirements
- Scaling - Product Owner Role
- Scaling - Scrum Master Role
- Scaling - Architect Role
- 8 Principles of Agile Architecture
7. Final Case Study
No client testimonials about this training
- IIBA® , BABOK® and Business Analysis Body of Knowledge® are registered trademarks owned by International Institute of Business Analysis.
- CBAP® and CCBA® are registered certification marks owned by International Institute of Business Analysis.
- Endorsed Education Provider, EEP and the EEP logo are trademarks owned by International Institute of Business Analysis.
- PMI is a registered mark of the Project Management Institute, Inc.
- The PMI Registered Education Provider logo is a registered mark of the Project Management Institute, Inc
- PMBOK is a registered mark of the Project Management Institute, Inc.
- PMP and PMI-ACP are registered marks of the Project Management Institute, Inc.