Get in Touch

Course Outline

Where do requirements come from?

  • Traditional Business Analysis
  • Use Cases, Scenarios, and Tests
  • Non-functional requirements
  • Performance
  • Conformance
  • UML in Business Analysis

Introduction to testing

  • Functional Tests
  • Regression Tests
  • User Acceptance Testing (UAT)
  • Unit Tests
  • Usability Tests
  • Non-functional Tests
  • Performance tests
  • Load tests
  • Stress tests
  • Soak tests

Deciding whether to test

  • Who decides what to test?
  • The cost of testing irrelevant items
  • Calculating ROI (considering potential analysis failures)
  • The role of the Test Manager

The testing process

  • Testing as a process and strategy
  • Identifying testing needs
  • Gathering requirements (use cases, user stories)
  • Scoping (selecting and prioritizing scenarios)
  • Designing tests
  • Preparing data
  • Preparing the environment
  • Creating or recording tests
  • Executing the test
  • Analysis and reporting
  • Conclusions and improvements
  • Knowing when to "stop"

The product owner and tests

  • The customer representative and test priority
  • Prioritizing tests
  • Writing effective stories for UAT
  • Acceptance criteria
  • Group exercise to produce customer requirements, write stories based on those requirements, and create tests

The sprint

  • Sprint backlog and user stories for tests
  • Group exercise to plan a sprint

Concluding a sprint

  • The Scrum review meeting serves as a test

Is Agile and Scrum suitable for you?

  • Review of the Scrum process
  • Comparison with other methodologies
  • Benefits of pair programming
  • Question and Answer session

Requirements

None.

 14 Hours

Testimonials (2)

Related Categories