The document outlines plans to improve testing processes in several areas: renewing test strategies, involving testers earlier in projects, providing more requirements details, and discussing plans with developers. It also suggests enhancing communication through a printed test newsletter, live meetings, and clarifying involvement responsibilities. Additionally, it recommends growing testing knowledge in specific modules, pursuing training and certifications, and integrating more automated tests into the build process while linking test tools together.

1. Projects
•Renew Test Strategy
•Go / Not to Go recommendation
•Involve testers into pre-analysis and
planning phases
•More requirements and expected results
provided
•Discussions with Developers and
Functional Architects about requirements
•Various development approaches
Communication
•Test Newsletter. Involve more
departments. Printed version
•Live meetings
•More information about involvement
and responsibilities in projects
•Reduce amount of places where data
is stored
•Ensure requirements and
functionality are described for future
Growth
•Developer in Test still needed
•Knowledge in Claims and L&P
modules
•Courses and certificates, participate
in conferences
Test Tools
•Link test tools (Alm – Jira, SoapUi,
Oats)
•Expand coverage of automated tests,
including forms
•Integrate automated tests into build
Closer to Customers
•Analysis from support issues and
Customers Survey
•Visit Customer (thing how to give
benefit for him too) e
•Participate in Demo’s
•Ask feedback and fix usability cases
TIA Technology
29-01-2014
1