Purpose: To demonstrate how productivity can improve by engaging testers from the very first day of a sprint

 

Questions to ask yourself:

  1. Does your team receive all the features at the end of the sprint for testing?
  2. Do you have the concept of code freeze in your project?
  3. Does your sprint usually spill over because testing is not completed?
  4. Do you demonstrate features to your stakeholders that have not been tested?
  5. and many more testing paradox...

If your answer to any of the above questions is YES, then it's time to fix these problems.

In this session, not only will I demonstrate how you can engage your testing team from the very first day in order to start (that's right, start) testing your application, but also help you achieve this by means of some simple exercises.

 
1 favorite thumb_down thumb_up 1 comment visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

General guidelines to play the testing game:

  1. We will run 3 sprints with different goals
  2. Each sprint will be followed by a retrospective for feedback and learnings
  3. We'll measure the outcome to check if we have improved productivity
  4. We'll see how the testing team can be engaged sooner and sooner every sprint

Learning Outcome

  1. Learn some simple testing agreements that improves productivity
  2. Testing can begin earlier, practically on day one
  3. Velocity can improve drastically

Target Audience

Anyone interested in improving the productivity of their software (testing) teams

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Ashish Mishra
    By Ashish Mishra  ~  1 year ago
    reply Reply

    1. Please share the time breakdown of your session

    2. Will there be an actual application sprints to simulate dev/testing?

    3. How will you make testers realize their contribution from day1?