Course Outline

Where Do Requirements Originate?

  • Traditional Business Analysis for Government
  • Use Cases, Scenarios, and Tests
  • Non-Functional Requirements
  • Performance
  • Conformance
  • UML in Business Analysis for Government

Introduction to Testing for Government

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

To Test or Not to Test?

  • Who Makes Decisions About What to Test?
  • The Cost of Testing Irrelevant Items
  • Calculating ROI (What If Something Fails Analysis?)
  • The Role of the Test Manager for Government

The Process of Testing for Government

  • Testing as a Process and Strategy
  • Identifying Testing Needs
  • Gathering Requirements (Use Cases, User Stories)
  • Scoping (Choosing and Prioritizing Scenarios)
  • Designing Tests
  • Preparing Data
  • Preparing Environment
  • Creating or Recording Tests
  • Performing the Test
  • Analysis and Reports
  • Conclusions and Improvement
  • Determining When to Stop Testing

The Product Owner and Tests for Government

  • 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 the Requirements, and Create Tests

The Sprint for Government

  • Sprint Backlog and Test User Stories
  • Group Exercise to Plan a Sprint

Finishing a Sprint for Government

  • Scrum Review Meeting as a Test

Is Agile and Scrum Suitable for Your Organization?

  • Review of the Scrum Process for Government
  • Comparison with Other Methodologies
  • Benefits of Pair Programming
  • Question and Answer Session

Requirements

There are no entries for government at this time.

 14 Hours

Number of participants


Price per participant

Testimonials (2)

Upcoming Courses

Related Categories