1. Test management in SCRUM:
Main testing documentation/artifacts,
tools, approach to test management
Vladimir Primakov KUADRIGA

2. Vladimir Primakov
QA manager and Automator with 9 years experience
in software testing.
The main current activity: Evaluation and startup of
new software testing projects, testing processes and
infrastructure setup, test management in the Kuadriga
company.
Enjoy photography, sports, and self-improvement
Profile in Linkedin: http://www.linkedin.com/in/vladimirprimakov
Email: v.v.primakov@gmail.com
Skype: vladimir.primakov

3. Test Basis
Testing Artifacts/Documents/Tools

4. Test Basis
User stories, epics
Vision
Architecture
Sprint/Milestone backlog
Prototypes Old Product
Workflows

5. Testing/QC Documentation/Artifacts
?

6. Testing/QC Documentation/Artifacts
Test Strategy Testing Sprint Plan Test Case Test Suite Script (Suite)
Defect Report Quality Report Dev. Infrastructure Auto Test Policy

7. Main Testing Artifacts
Test Strategy Test Sprint Plan Test Case Test Suite
Defect Report Quality Report Dev. Infrastructure

8. Testing Artifacts to Discuss
Test Strategy Test Sprint Plan Test Suite
Quality Report

9. Master Test plan Testing Strategy

10. Master Test plan Testing Strategy
Products, their parts Technologies, and Tools Test Environments Testing types
Testing & Dev. Integration Product & Project risks Team Initial Schedule

11. Planning Testing Sprint
&

12. Planning Testing Sprint
Dev. Sprint

13. Planning Testing Sprint
Dev. Sprint QA Sprint

14. Planning Testing Sprint
Dev. Sprint QA Sprint
User story

15. Planning Testing Sprint
Dev. Sprint QA Sprint
User story

16. Planning Testing Sprint
Dev. Sprint QA Sprint
User story QA Task

17. Planning Testing Sprint
User story QA Task

18. Planning Testing Sprint
User story QA Task
Note: A field of the Label type

19. Planning Testing Sprint
QA Task
User story

20. Planning Testing Sprint
QA Task
User story

21. Planning Testing Sprint
QA Task
User story

22. Planning Testing Sprint
QA Sprint
QA Task

23. Planning Testing Sprint
Time Estimated < Time Available
QA Sprint
Create and
Add to sprint

24. Planning Testing Sprint
Time Estimated < Time Available
(e.g.: Test planning
Test reporting, etc.)
QA Sprint
Create and
Add to sprint

25. Planning Testing Sprint
Time Estimated < Time Available
QA Sprint
Create and
Add to sprint

26. Planning Testing Sprint
Time Estimated < Time Available
QA Sprint
Create and
Add to sprint

27. Planning Testing Sprint
Time Estimated < Time Available
QA Sprint
Create and
Add to sprint

28. Planning Testing Sprint
Time Estimated < Time Available
QA Sprint
Create and
Add to sprint

29. Planning Testing Sprint
Time Estimated < Time Available
QA Sprint
Create and
Add to sprint

30. Planning Testing Sprint
Time Estimated < Time Available
QA Sprint
Create and
Add to sprint

31. Planning Testing Sprint
Time Estimated < Time Available
QA Sprint
Create and
Add to sprint

32. Planning Testing Sprint
Time Estimated < Time Available
QA Sprint
Create and
Add to sprint

33. Planning Testing Sprint
Time Estimated < Time Available
QA Sprint
Create and
Add to sprint

34. Planning Testing Sprint
Time Estimated < Time Available
QA Sprint
Create and
Add to sprint

35. Planning Testing Sprint
Time Estimated < Time Available
QA Sprint
Create and
Add to sprint

36. Planning Testing Sprint
Time Estimated < Time Available
QA Sprint
Create and
Add to sprint

37. Planning Testing Sprint
Time Estimated < Time Available
QA Sprint
Create and
Add to sprint

38. Planning Testing Sprint
Time Estimated > Time Available

39. Planning Testing Sprint
Time Estimated > Time Available
QA Sprint

40. Planning Testing Sprint
But

41. Planning Testing Sprint
is Obligatory!

42. Planning Testing Sprint
Exploratory testing
Session-based testing
= Error Guessing
Experience-based testing
Ad Hoc testing
Smoke testing

43. Planning Testing Sprint
QA Task Tester
Dividing
tasks
among
Testers

46. Regression (Test Suite)

47. Regression (Test Suite)

48. Monitoring
Tracking testing by a whole team

49. Monitoring
Tracking testing by a QA Manager

50. Monitoring
Tracking testing by a QA Manager
Burndown and project summary

51. Monitoring
Tracking testing by a QA Manager
Regression Test coverage
Time Spent by certain testers

52. Может Хватит!?

53. Может Хватит!?
Да, блин, ещё чуть, чуть!...

54. Reporting
1. Defects by severity/priority (and their status)

55. Reporting
2. Defect distribution by components (and their status)

56. Reporting
3. List of bugs that perceived to be obligatory fixed
before release.
4. List of bugs recommended to be fixed before
release.
Key Summary Assignee Priority Status
ID-535 Bla-bla-bl-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla- Bruce Lee Urgent Open
bla-bla-bl
ID-525 Bla-bla-bl-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla- Bruce Lee Major Open
bla-bla-bla-bla-bla-bla-bla-bla-bla
ID-440 Bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla- Bruce Lee Normal Resolved
bla-bla-bla-bla-bla-bla-bla-bl
ID-150 Bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla- Batman Normal Resolved
bla-bla-bla-bla-bla-bla-bla-bla-bla-bla-bla

57. Reporting
5. Regression test coverage

58. Reporting
6. Test deepness for user stories or regression test cases:
• Very thought out detailed tests
• Detailed tests
• Deep smoke test
• Smoke test
• Nothing 
7. Obligatory Types of Testing performed / not performed
8. Obligatory Test Environments covered / not covered

59. Documentation Storage

60. Use Templates!

61. Vladimir Primakov
Email:
v.v.primakov@gmail.com
Skype:
vladimir.primakov