Test Planning

After completion of test initiation for Product Owner, corresponding scrum master can prepare test plan document by following IEEE829.

a. Team level changes if required:
In general test planning process can start with team level changes if required. As per sprint backlog user stories, team level changes were needed some times with respect to complexity in those user stories. So
the selection of user stories for sprint depends on size of user stories, importance of user stories (Priority) and complexity in user stories to finish selected user stories development and testing in 30 days, scrum master can try to change team size if required.

b. Identify Tactical Risks:
After completion of team level changes scrum master can concentrate on risks identifications.
Example:
 Lack of times
 Lack of resources
 Lack of documentation
 Lack of skills
 Lack of communication
 Delay in delivery (Unexpected problem)
 Lack of seriousness to developers
 Sudden changes in user stories/Requirements
c. Prepare Test plan:
After completion of team level changes and risks identification, corresponding scrum master can prepare test plan document like shown below:-

1. Test Plan document:
   Unique number or name for feature reference.
2. Introduction:
   The about current sprint or software.
   What to Test?
3. Features or Modules:
   List of all modules in current sprint or software
4. Feature not to be tested:
   Features already tested in pervious sprint.
5. Features to be tested:
   Features yet to test in current sprint.
   How to test?
6. Test strategy:
   Attach test strategy given by product owner.
   Strategy is a part of plan.

7. Test Environment:
   Required hardware and software for testers in current sprint software test.
8. Test Deliverables:
   List of document to be prepared by testers in current sprint or software testing.
   Example: Test scenarios, Test cases, Test data, Defect reports, Automation script, and sprint burn down chart and traceability matrix.
9. Entry Criteria: (To start test execution)
    Test design completed. (Test scenarios, Cases and test data)
    Test environment established.
    Sprint Build released from developers.
10. Suspension criteria: (To interrupt testing)
     Test environment abounded.
     Major bug in sprint (Show stopper)
     More minor bugs in pending (Quality gap)
11. Exit Criteria:
     Test duration excided.
     All Major closed.
     All reasonable tests finished.
    What to test?
12. Staff:
    Names of testers in scrum team.
13. Responsibility:
    Scrum master can allocate work to testers in two ways such as modules wise allocation and topics wise allocation

When to test?
14.Schedule:
Dates and time for testers. Example: 30 days schedule for current sprint.

15. Risks and Assumptions:
    List of previously analyze risks and solution to overcome those risks.
16. Approvals:
    Signatures of scrum master, Product owner, Stakeholders.
    Note1: Scrum master can follow above like test plan document format while preparing test plan for each sprint or software testing. The above format is in IEEE829 format.
    Note2: Test plan document preparation by specifying entry criteria, suspension criteria, exist criteria is mandatory active for scrum master in every sprint test life cycle.
    Note3: Test plan document classified four parts such as:

1. What to test?
2. How to test?
3. Who to test?
4. When to test?
   d. Review test plan:
   After completion of test plan document preparation corresponding scrum master can take approval from product owner and stake holders on that plan. Sometimes scrum master can change plan with respective suggestion of product owner and stakeholders and request from scrum team testers.