1. Process
1.1. Testing Process Definition
1.2. Triage meetings decision (Daily, weekly, etc)
1.3. Communications
1.3.1. Email
1.3.1.1. Determine the recipients - Who is it intended for?
1.3.1.2. Level of detail - Is it enough for the recipient
1.3.2. Testing Updates - Stand up (Internal and External)
1.3.3. Raising Impediments
1.4. Defect Logging Process and Lifecycle
1.4.1. Internal
1.4.2. External (Maersk/Production Defects)
1.5. Testing Approach (Sprint wise plan - conducting functional and automation testing)
1.6. Scope Changes (How are they being handled?)
1.7. DOD and DOR Definitions - Are they clear and being followed?
1.8. Requirement Traceability Matrix
1.9. Defect Traceability (To Test Case and in turn User Story available?)
1.10. Metrics
1.11. Testing Summary - What all information to include
1.12. Sprint Demos
1.13. Azure DevOps (CI/CD pipelines etc)
1.14. Dashboard
1.15. DHR Portals, DX Reviews
1.16. Learnings from current sprints and process refinements in future sprints
2. Testing
2.1. Types of Testing Involved
2.1.1. Functional (UI, API, ETL, etc)
2.1.1.1. Buddy Testing
2.1.1.2. Feature Testing
2.1.1.3. Integration Testing
2.1.1.4. BVT and Sanity Testing
2.1.1.5. Regression Testing
2.1.2. Automation (UI + API)
2.1.2.1. Framework Decision
2.1.2.1.1. Keyword driven
2.1.2.1.2. Hybrid
2.1.2.1.3. BDD
2.1.2.1.4. Page Object Model
2.1.2.2. Automation Strategy
2.1.3. Performance
2.1.4. Security
2.1.5. Localization (Countries involved?)
2.1.5.1. China
2.1.5.2. Netherlands
2.1.5.3. Any other countries?
2.1.6. Compatibility (Browser and Device if any)
2.1.6.1. Browser
2.1.6.1.1. Chrome
2.1.6.1.2. Firefox
2.1.6.1.3. IE
2.1.6.1.4. Edge
2.1.6.2. Device
2.1.6.2.1. iOS
2.1.6.2.2. Android
2.1.7. Regression - When and how often
2.1.8. Report
2.2. Testing Schedule
2.2.1. Initial Schedule
2.2.2. Scope Changes vs Schedule Changes
2.2.3. Schedule impacts due to Regression
2.2.4. Does Ramp up impact Schedule - if yes, by how much?
2.3. Risks and Mitigation Plan - Continual process
2.4. Dependencies
2.5. Assumptions
2.6. Scope - Are they Updated regularly with scope change and sent for approval?
2.6.1. In
2.6.2. Out
2.7. Entry and Exit Criteria (Definition by phases) - Are they meeting?
2.8. Tools and License requirements
2.8.1. VSTS
2.8.2. Selenium
2.8.3. Postman
2.8.4. DevOps
2.8.5. AppInsights
2.8.6. Defect Management and Testing Tasks Monitoring Tools
2.8.6.1. JIRA
2.8.6.2. VSTS
2.8.6.3. Any other tool options if available
2.9. IP Reuse?
3. Clarifications or Queries
3.1. Tool or Technology
3.1.1. Identify the forums
3.1.2. DLs
3.2. Business
3.2.1. Knowledge Transfer sessions
3.2.2. Q & A sessions
3.3. Product - Who to reach out to for product issues or queries if any
3.3.1. Azure Team
3.3.2. DB Team (Cosmos Product Team)
3.3.3. Visual Studio
4. Project Reference Documents
4.1. SOW
4.2. Compass
4.3. Virtuoso
4.4. Architecture Documents
4.5. Resource Loading
5. Methodology
5.1. Agile
5.1.1. Sprint Planning
5.1.2. Backlog Refinement and Prioritization
5.1.3. Daily Stand Ups
5.1.4. Sprint Retrospectives
5.1.5. Sprint Demos
5.2. Waterfall
5.3. Iterative
5.4. Watergile
6. Requirements
6.1. Functional
6.1.1. Epics
6.1.2. Features
6.1.3. User Stories
6.1.3.1. Requirement Analysis and Gap identification
6.1.3.2. Review
6.1.3.3. User Story Update to close identified gaps
6.1.4. Change Requests
6.2. Non Functional
6.2.1. Performance
6.2.1.1. Benchmarks Defined?
6.2.2. Security
6.2.3. Usability
6.2.4. Disaster Recovery
6.2.5. Others applicable?
7. Characteristics
7.1. Interpersonal
7.1.1. Bold
7.1.2. Upfront
7.1.3. Diplomatic
7.1.4. Understanding
7.1.5. Gels well with team (Dev and Test)
7.2. Ethical
7.2.1. Follows Process
7.2.2. Admits to mistakes or misses if any
7.2.3. Does not let friendship or interpersonal relations get in the way of work or process
7.3. Qualities
7.3.1. Assertive
7.3.2. Conflict Management
7.3.2.1. Internal
7.3.2.2. External
7.3.3. Customer Centric
8. Product/Application
8.1. Different Systems (internal and external) Interacting with the current application
8.2. Identifying Gaps (if any) through the understanding of the interaction points
8.3. Areas the developed applications are touching upon (Application, API, Data, UAM, etc)
8.4. Identifying Software/System dependencies
8.5. Is the Product/Application built for Maersk meeting MS vision? How to merge business requirement with MS roadmap and vision
9. Project Resourcing (Origin, UAM, Data, etc.)
9.1. Internal
9.1.1. Resource Requirements (Functional, Automation, Performance, etc.)
9.1.2. Team Structure
9.1.3. Escalation Process (Internal)
9.1.4. Reviewers
9.1.5. Approvers
9.1.6. Resource Planning post production?
9.1.7. Roles and responsibilities
9.1.8. Review and Revisit Resource Loading
9.1.9. Team Management
9.1.10. Expectation Setting
9.1.11. Resource Skillset assessment
9.1.12. Performance Trakcing and Feedback
9.2. External (with Maersk)
9.2.1. Team Structure
9.2.2. Escalation Process (People to reach out to) - External
9.2.3. Introductory Sessions with Team Members
9.2.4. Reviewers and Approvers
9.2.5. Roles and responsibilities
10. Business (Supply Chain Management)
10.1. Business Understanding
10.1.1. Challenges faced earlier
10.1.2. What is the application trying to achieve
10.1.3. How is the business problem being solved
10.2. Identifying or understanding upcoming scope
10.3. Stakeholders involved
10.3.1. Origin
10.3.1.1. Stakeholder Management
10.3.1.2. Communication Plan
10.3.2. UAM
10.3.2.1. Stakeholder Management
10.3.2.2. Communication Plan
10.3.3. Other areas?
10.4. User base (Types of Users)
10.4.1. Admins
10.4.2. End Users
10.4.3. Others?