Tester: Practices

Here are practices for the Tester. In some of these practices, other roles are also involved:

  • Planning
    • Developing estimates at beginning of iteration and in story points
    • Decomposing features into stories and Tasks
    • Committing to the backlog
    • Understand the context for the project and help others to make informed decisions based on this context.
    • Help the business analyst create acceptance tests up front.
    • Developing the testing plan. The testing plan must
  • Ecosystem
    • Working within the team’s project environment to ensure it meets the needs of the team
    • Configuring tools for ATDD, TDD, testing, and continuous integration
  • Produce code that meets acceptance criteria
    • Working with the Product Owner and Business Analysts to implement Acceptance Test-Driven Development
    • Working with the developers to ensure code is tested and that code passes all Types of Tests.
    • Facilitating the team in using continuous integration including tools, process, and usage
    • Ensuring stories are Done-Done-Done which means:
      • The system runs on the developer’s computer as expected.
      • The system is verified by running unit tests on a common machine.
      • The system is validated as being of deliverable quality with functional tests.
  • Assuring flow of work
    • Swarming with other team members on stories and task as needed
    • Managing WIP
    • Working with the Team Agility Master to maintain the kanban board or Agile life-cycle tool and to update the team backlog
  • At the end of the iteration.
    • Participating in the Product Demonstration. See also Product Demonstration and Review Checklist in Checklists.
    • Attending to Carry-Over Work.
    • Participating in the Iteration Meeting. See also Iteration Planning Meeting Checklist in Checklists.
    • Participating in the Iteration Retrospective.
    • Working with Release Management
    • Helping the team to know how much testing resource is available in the next iteration.
    • If testing has not been finished by the end of the iteration, then working to move testing early in the iteration.
  • Help the team improve continuously.