ALM - Getting Testing done in a Sprint

2,882 views

Published on

Agile teams find it hard to get the testing effort in sync with the other development activities. Not only development tests are executed during sprints, all other kind of testing activities are part of done. This session will give guidance how Microsoft Visual Studio ALM tools can support agile teams. How to run sprints and get testing done in a sprint.

Published in: Technology, Education
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,882
On SlideShare
0
From Embeds
0
Number of Embeds
1,315
Actions
Shares
0
Downloads
17
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • DEMO
  • DEMO
  • ALM - Getting Testing done in a Sprint

    1. 1. Agile ALM and TestingGetting testing done in a sprint
    2. 2. Clemens Reijnenwww.clemensreijnen.nl@clemensreijnenclemens.reijnen@sogeti.nlwww.youtube.com/clemensreijnenwww.slideshare.net/clemensreijnen
    3. 3. Agile ALM and Testing
    4. 4. an iterative, incremental approach to optimizepredictability and control risk.
    5. 5. work together__with work packages__on alm artifacts
    6. 6. Magic Quadrant for Application Life Cycle Management Driven by cloud and agile technologies, the ALM market is evolving and expanding. Although support for agile is important, the challenge is that the tools that work best for agile projects lack requirements definitions and management.http://www.gartner.com/technology/reprints.do?id=1-1ASCXON&ct=120606&st=sb
    7. 7. work together connected with ALM tools to deliver a done increment within iteration Agile ALM and Testing
    8. 8. Getting Testing Done in a Sprint 10 TIPS
    9. 9. 1 get a Team
    10. 10. 2 backlog items need a risk classificationProduct Backlog items have the attributes of adescription, priority, and estimate. Priority isdriven by risk, value, and necessity. There aremany techniques for assessing these attributes.http://www.scrum.org/scrumguides/
    11. 11. “no risk,no test”
    12. 12. 3 create logical test cases during release planning meeting
    13. 13. 4 define test tasks during sprint planning meeting
    14. 14. 5 team focus on a product backlog item
    15. 15. 6 undone work
    16. 16. DEMO
    17. 17. 7 automation is a must, but not everything
    18. 18. TIP for get testingdone in a sprintTest Automation Levels 0 No automation 1 Shared Steps with action recording 2 Test Cases with action recording 3 Generated Coded UI 4 Customized Coded UI
    19. 19. Test Automation Levels Number of test cases per level in a sprint.
    20. 20. 8 No Double, Triple Testing
    21. 21. 9 The Test Branch
    22. 22. 10 BUGS
    23. 23. DEMO
    24. 24. DONE
    25. 25. www.ClemensReijnen.nl@ClemensReijnen

    ×