Preetha Shreekanth who is an Expert QA Engineer, CSM, SAFe Agilist, took a Session on "Best Practise for Successful SAFe in Test" at Global Testing Retreat #ATAGTR2018 please refer our linkedin post for session details https://www.linkedin.com/pulse/best-practise-successful-safe-test-automation-preetha-alliance/

1. #ATAGTR2018
Best Practice for Successful SAFe Agile Testing
Preetha Padinjaremuttikkal
27th September 2018

2. #ATAGTR2018
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
• SAFe
• System Team Composition
• System Team Work Flow
• System Team Roles
• Takeaways
• Reference
Contents

3. #ATAGTR2018
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
SAFe

4. #ATAGTR2018
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
System Team Composition
Atleast one member from each location.

5. #ATAGTR2018
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
System Team Workflow

6. #ATAGTR2018
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Architect
• Maintenance of the product
• Code/Solution Reviews
• Rollback strategy confirmation
• Check merges to integration branch
• Check for unit tests and nightly tests - still running
• Automated build process
• High-level estimates on work items
• Fortify scan results analysis
ST Roles
Test Engineer
• Manage task board
• Organize Team & Cross team meetings
• Metrics / Master Test Plan / Questionnaire template mgmt.
• High-level estimates on backlog
• Bug Master for integration sprints, RCA process
• General TFS work item oversight and upkeep
• Hotfix test planning and reviews & regression lead

7. #ATAGTR2018
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
ST Roles contd..
Automation Engineer
• Collect up scripts from the
sprint teams
• Run automation during each integration sprint
• Help promote automation standards, document
• Validating refreshes for all environments
• Regression backlog automation & maintenance
Performance Engineer
• Performance Reports
• Application new and baselines performance
• Creation of new performance scripts
• Maintenance of performance regression suite
• Run baseline scripts during each integration sprint
• Ongoing investigation of problem areas

8. #ATAGTR2018
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
Promote quality
1.System Team acting as a consistent resource across the release to
promote a global approach to quality: architecture, performance,
automation, regression, security
2.System Team will engage in planning meetings / questionnaire
discussions and encourage ongoing collaboration across the
release
3.System Team will “Test early, test often” / promote lower-cost
bug detection earlier vs later in release cycle
4. System Team and Sprint Teams will provide ongoing automation
development / maintenance to enable early integration to testing
/ ensure working software throughout the release
5. Reduce / eliminate need for other test cycles, e.g. potential to
minimize the number of HIP and/or eliminate HIP0
6. Achieve higher goal of no critical or high bugs found during HIP
testing as well as production
Takeaways

9. #ATAGTR2018
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)
https://www.data.cam.ac.uk/data-management-guide/
http://thecreativehaus.co.uk/
http://ajbee.me/
http://www.appknights.com/
https://www.quora.com/
https://www.scaledagileframework.com/
References

10. #ATAGTR2018
As a author of this presentation I/we own the copyright and confirm the originality of the content. I/we allow Agile testing alliance to use the content for social media
marketing, publishing it on ATA Blog or ATA social medial channels(Provided due credit is given to me/us)