In traditional ‘waterfall’ style software development projects, the activities that fall under the banner of ‘testing’ are well defined and understood. However, on an Agile Projects start with their requirements. How those requirements are documented or expressed has a tremendous influence on the rest of the project. The technique of expressing requirements as user stories is one of the most significant approaches introduced by Agile Methodologies.

Workshop Overview

The technique of expressing requirements as user stories is one of the most significant approaches introduced by Agile Methodologies.

User Stories are a great way to build software that meets users’ needs. They are simple, clear, brief descriptions of functionality that will be valuable to real users. In this practical, workshop we look at all aspects of gathering, writing and validating user stories. Participants will learn what makes a great user story, how to create it or ways to gather user stories. After compiling the user stories, workshop focuses on how to organize them, prioritize them, estimate them and use them for planning, management, and testing.

In this practical workshop we look at all aspects of testing in an Agile project to  decide what changes are needed to  testing process to enable Agile Testing to be successful. The workshop looks at testing throughout the entire life-cycle of an Agile project from ‘developer testing’ right through to ‘end-user testing’ with all the intermediate steps that fall under the heading of ‘IT’ or ‘Independent Testing’.

Workshop Content

Day 1 – Introduction to Agile & User Stories, Estimation and Planning

  • Introduction to Agile Methodology
    • Agile Manifesto, principles and practices.
    • Scrum methodology
  • Approach for capturing user requirements in Agile project environment
  • Understanding the concept of user stories
  • Write/gather stories
    • Techniques for developing user stories – story-writing workshops
    • Understand the attributes of user stories and validate them
    • Acceptance test stories
  • Prioritization of User Stories
  • Benefits of User stories
  • User story estimation and factors to consider for time boxing the iteration
  •  Plan iterations and releases
  • Measure and monitor velocity
  • Challenges with User Stories

Day 2 – Agile Test Strategies

  • Traditional Vs Agile Testing
    •  Impact on current testing process and team structure
    •  Role of an independent tester in an Agile project
  • Testing in Agile project environment
  • Unit and Component Tests
    • Unit and Component Tests
    • Functional tests
    • User Acceptance tests
    • Performance tests
  •  Need for Test automation
  • Case studies and Conclusion

Who Should Attend

The target audience for the program are Agile project team members involved in capturing Business/product requirements, system and solution architecting, Development and Testing