1. Collaboration with Developers
1.1. Helps to understand and sync with tasks requirements from end-user prospective
1.2. Assists with automated tests within TDD/BDD
1.3. Collaborates during development process
1.4. Outlines needs and expectations of features/user stories to be developed
1.5. Participates in "ii it a bug or feature" discussions
1.6. Plans and discusses upcoming testing activities
1.7. Provides
1.7.1. Bug reports
1.7.2. Bug verification result
1.7.3. Scope, Features, User stories testing results
1.7.4. QA Reports
1.7.5. Lists improvements and suggestions
2. Collaboration with Dev. Team Lead
2.1. Helps to improve collabaration with developers
2.2. Assists with leadership and coaching activities
2.3. Discusses the project and team objectives
2.4. Facilitates problem solving and collaboration
2.5. Analyzes task accomplishment, issues and status
2.6. Improves QA - Developer communications
2.7. Provides,reviews, discusses and finalizes testing approach, strategy and plans
2.8. Outlines possible "week points" in development process
2.9. Makes suggestions regarding strengthening the team
2.10. Removes, escalates and facilitates conflict situations
2.11. Assists in meetings with client, stakeholders and product owner
2.12. Helps to define scenarios for DEMO-meetings
3. Collaboration with PM
3.1. Helps to improve collaboration within team
3.2. Assist with Scrum process optimization
3.3. Introduces suggestion for "DEMO" to the client
3.4. Outlines communication gaps
3.5. Prvides
3.5.1. Testing Approach
3.5.2. QA Estimation tables
3.5.3. QA Satus
3.5.4. Testing Risks
3.5.5. QA Reports
3.5.6. Test Artifacts
3.5.7. Requirements suggestions
3.5.8. Lists of points to be clarified
3.5.9. Lists of questions to the client, product owner or stakeholders
4. Collaboration with Business Analyst
4.1. Assists and participate in requirements analysis
4.2. Helps to have more critical view on requirements
4.3. Provides
4.3.1. Requirements analysis results
4.3.2. Suggestions and improvements for requirements
4.3.3. Found gaps and inconsistencies
4.3.4. Testable / not testable statements for requirements
4.4. Gets
4.4.1. Requirements to be analyzed
4.4.2. Business and market requirements for a product
4.4.3. Target audience and user portraits
4.4.4. Needs and goals product should achieve