Merge pull request #7 from infopulse/content/matrix

Grammar and spelling corrections

matrix/01. planning.md

@@ -1,34 +1,39 @@
 # Test Planning
-Estimations, tasks prioritization, test documentation, test management, risk management
+Estimations, task prioritization, test documentation, test management, risk management
+
 ## Trainee
-- Has basic theoretical knowledge of what is estimation, prioritization: able to estimate simple task and explain it
+- Has basic theoretical knowledge of what estimation and prioritization are: able to estimate simple tasks and explain them
 - Requests task priorities from N+1
 - Knows types of test documents and their purpose
-- Escalates in case of blockers, wrong estimations
+- Escalates in case of blockers or wrong estimations
+
 ## Junior
-- Has practical testing experience and understanding of the Testing process
-- Сan read and understand current test plan (own activities and current approach) with some guidelines
-- Able to estimate non-complex tasks with acceptable level of precision (in hours, story-points whatever)
+- Has practical testing experience and understanding of the testing process
+- Can read and understand the current test plan (their own activities and the current approach) with some guidelines
+- Able to estimate non-complex tasks with an acceptable level of precision (in hours, story points, etc.)
 - Has an understanding of task prioritization and decomposition
 - Clearly understands the difference between severity and priority
+
 ## Middle
-- Can read and understand Test Strategy and Test Pan
-- Can actualize or contribute to existing Test Plan
-- Provides estimation for tasks of medium-complexity level
-- Able to identify major risks and report them to a person, responsible for risk-management
+- Can read and understand Test Strategy and Test Plan
+- Can actualize or contribute to an existing Test Plan
+- Provides estimation for tasks of medium complexity level
+- Able to identify major risks and report them to a person responsible for risk management
 - Able to make decomposition and estimation of complicated tasks
+
 ## Senior
 - Autonomously prioritizes and estimates tasks of high complexity
-- Able to do high level estimation for project, knows different approaches
-- Can create test documentation (Test plan, Test strategy) using best practices
-- Able to identify and describe risks, provide mitigation plan
+- Able to do high-level estimation for projects and knows different approaches
+- Can create test documentation (Test Plan, Test Strategy) using best practices
+- Able to identify and describe risks, and provide a mitigation plan
+
 ## Expert
 - Knows and uses different estimation approaches (expert, work breakdown, weighted, 3-point)
-- Can independently, from the scratch create Test Plan, Test Cases, Test Suite, CheckList, Test Report, etc
-- Has experience in planning and estimating complete set of testing activities on 3+ projects
-- Can prioritize testing tasks at the project and convince customer
-- Can identify quality risks and provide plan to mitigate them, has real-life risk-based testing experience on 2+ projects
-- Knows what is ROI and calculated it 2+ times
-- Knows formal models of process improvement and able to apply (like TMMi, TPI, ASPICE)
-- Created at least 5+ test plans/test strategies, agreed with customer, used in testing
-- Able to explain/sell the benefits of selected testing approach to stakeholders
+- Can independently create from scratch Test Plan, Test Cases, Test Suite, CheckList, Test Report, etc.
+- Has experience in planning and estimating a complete set of testing activities on 3+ projects
+- Can prioritize testing tasks for the project and convince the customer
+- Can identify quality risks and provide a plan to mitigate them, and has real-life risk-based testing experience on 2+ projects
+- Knows what ROI is and has calculated it 2+ times
+- Knows formal models of process improvement and is able to apply them (like TMMi, TPI, and ASPICE)
+- Created at least 5+ test plans/test strategies, agreed with the customer, and used them in testing
+- Able to explain and sell the benefits of the selected testing approach to stakeholders

matrix/02. design.md

@@ -1,34 +1,39 @@
 # Test Design
-Test case creation, test analysis, check list creating
+Test case creation, test analysis, checklist creation
+
 ## Trainee
-- Knows the structure of Test Cases and difference with Check List
-- Knows the main Test Design Techniques (Equivalence Partitioning (EP), Boundary Value (BV), Decision Table (DT), State-Transition (ST) -  knows 1 or 2)
-- Can create Test Cases and Check Lists with help and directions from senior colleagues on positive and some negative cases
-- Knows the difference between:
+- Knows the structure of Test Cases and their difference from Checklists
+- Knows the main Test Design Techniques (Equivalence Partitioning (EP), Boundary Value (BV), Decision Table (DT), State-Transition (ST)) - knows 1 or 2
+- Can create Test Cases and Checklists with help and directions from senior colleagues on positive and some negative scenarios
+- Knows the differences between:
   - Test levels: Unit Testing, Integration Testing, System Testing, Release Testing, Acceptance Testing
   - Test types: Functional and Non-functional
+
 ## Junior
-- Understands most commonly used test design techniques (EP, BV, DT, ST) and uses common test-design approaches when choosing test data
+- Understands the most commonly used test design techniques (EP, BV, DT, ST) and uses common test-design approaches when choosing test data
 - Can do test design of readable test cases on positive and negative scenarios
-- Knows how to investigate the issue and can provide the examples of:
+- Knows how to investigate the issue and can provide examples of:
   - Test levels: Unit Testing, Integration Testing, System Testing, Release Testing, Acceptance Testing
   - Test types: Functional and Non-functional
+
 ## Middle
-- Able to identify and balance test-coverage
-- Understands concept of test-levels and test-types
-- Able to identify which test-cases are more reasonable to put on each test-level
-- Can do test design on positive and all negative cases
-- Knows IEEE standard for test design (29119 p4)
-- Uses most common test design techniques (EP, BV, DT, ST)
+- Able to identify and balance test coverage
+- Understands the concept of test levels and test types
+- Able to identify which Test Cases are more reasonable to put at each test level
+- Can do test design on positive and all negative scenarios
+- Knows the IEEE standard for test design (29119 p4)
+- Uses the most common test design techniques (EP, BV, DT, ST)
 - Can define test data
-- Able to approach Non-Functional aspects of product by suggesting NFT approaches
+- Able to approach non-functional aspects of the product by suggesting NFT approaches
+
 ## Senior
-- Can review test cases/checklists of colleagues and mentoring/consulting them, has relevant experience
-- Able to perform test-design based on a given requirements, or according to common sense and experience if exact requirements are missing
-- Optimizes amount of test data required for Test Case execution
-- Involves risk-based approach while test design
-- As a plus - has preferred approach to the test analysis 
+- Can review test cases/checklists of colleagues and mentor/consult them, has relevant experience
+- Able to perform test design based on given requirements, or according to common sense and experience if exact requirements are not provided
+- Optimizes the amount of test data required for Test Case execution
+- Involves a risk-based approach in test design
+- As a plus, has a preferred approach to test analysis
+
 ## Expert
-- Identifies which test-design technique could be used in a specific case, based on experience and risks
-- Supervises colleagues on different test design techniques, optimal approaches
-- As a plus - has own approach to the test analysis and test design which is proven in 3+ projects
+- Identifies which test design technique could be used in a specific case, based on experience and risks
+- Supervises colleagues on different test design techniques and optimal approaches
+- As a plus, has their own approach to test analysis and test design which is proven in 3+ projects

matrix/03. reporting.md

@@ -1,30 +1,35 @@
 # Test Reporting
 Test metrics
+
 ## Trainee
 - Has basic theoretical knowledge of test reporting.
-- Can report own activities for day, week, sprint (tests created, tests executed, bugs created, other activities).
+- Can report their own activities for the day, week, and sprint (tests created, tests executed, bugs created, other activities).
+
 ## Junior
 - Understands 1st level metrics (number): # of defects, # of TCs passed/failed, # of defects by their criticality, etc.
-- Сan explain what is Test Coverage, Test effort, Defect distribution, Test execution, Requirements and requirement coverage etc.
-- Able to supply a report, based on a given template
+- Can explain what Test Coverage, Test Effort, Defect Distribution, Test Execution, Requirements, and Requirement Coverage are, etc.
+- Able to supply a report based on a given template
+
 ## Middle
-- Able to provide clear structural status for testing activities under own responsibility.
-- Able to read report and understand current product quality.
-- Understands 1st and 2nd level metrics (relative): pass/fail rate per module/feature, defects leakage rate (e.g. found on PROD/total found * 100%), etc.
-- Creates different diagrams for completeness of the quality of testing using metrics.
+- Able to provide a clear structural status for testing activities under their own responsibility.
+- Able to read a report and understand the current product quality.
+- Understands 1st and 2nd level metrics (relative): pass/fail rate per module/feature, defect leakage rate (e.g., found on PROD/total found * 100%), etc.
+- Creates different diagrams to illustrate the quality of testing using metrics.
+
 ## Senior
-- Provides clear high and low levels structural overview of testing status for project. 
-- Able to differentiate details of reports depending on the level of the target audience.
-- Reports Product quality.
-- Provides certain, precise, narrative and easy to understand the information in reports.
-- Regularly collects metrics in daily work, analyses existing ones for improvements, implements them for practical usage.
-- Understands 1st, 2nd and 3rd level metrics (distribution): defects leakage dynamics over iterations, dependency between # of defects and # of changes over iterations, etc...
+- Provides a clear high and low-level structural overview of the testing status for the project.
+- Able to differentiate the details of reports depending on the level of the target audience.
+- Reports product quality.
+- Provides certain, precise, narrative, and easy-to-understand information in reports.
+- Regularly collects metrics in daily work, analyzes existing ones for improvements, and implements them for practical usage.
+- Understands 1st, 2nd, and 3rd level metrics (distribution): defect leakage dynamics over iterations, dependency between the number of defects and the number of changes over iterations, etc.
 - Collects information for metrics from different sources.
+
 ## Expert
-- Able to define reporting standards and templates applicable for different deliveries, supervise others on the subject.
-- Has own approach and style to report/present the quality, proven with good feedback in 3+ projects.
-- Highlights the key things and gives a quick understanding of an information essence.
-- Assures reports are highlighting only valuable information
-- Can apply 1st, 2nd and 3rd level metrics to the current project, understands well how to collect them and how to use.
-- Identifies gaps in reporting process and provides approaches based on test metrix for improving QA process and quality of tested application/product.
-- Has practical experience of metrics alignment with stakeholder, implementation in 3+ projects.
+- Able to define reporting standards and templates applicable for different deliveries, and supervise others on the subject.
+- Has their own approach and style to report/present the quality, proven with good feedback in 3+ projects.
+- Highlights the key things and gives a quick understanding of the essence of the information.
+- Assures that reports highlight only valuable information.
+- Can apply 1st, 2nd, and 3rd level metrics to the current project, and understands well how to collect and use them.
+- Identifies gaps in the reporting process and provides approaches based on test metrics for improving the QA process and quality of the tested application/product.
+- Has practical experience of metrics alignment with stakeholders, and implementation in 3+ projects.

matrix/04. sdlc.md

@@ -1,27 +1,32 @@
 # SDLC
 Methodologies (Agile family, traditional), Build/Deploy Environments
+
 ## Trainee
-- Has basic theoretical knowledge of SDLC and a concept of environments
+- Has basic theoretical knowledge of SDLC and the concept of environments
+
 ## Junior
-- Has theoretical knowledge of Traditional and Agile SDLCs, has practical experience (with at least with 1)
-- Knows the stages of SDLC and can describe the activities for each stage with examples from practice
-- Understands what is the build and deployment process
+- Has theoretical knowledge of Traditional and Agile SDLCs, and practical experience (with at least one)
+- Knows the stages of the SDLC and can describe the activities for each stage with examples from practice
+- Understands what the build and deployment process is
+
 ## Middle
 - Can describe the advantages and disadvantages of different SDLC models
-- Able to describe each stage on project-specific SDLC in details
-- Knows which environments are used for
+- Able to describe each stage of a project-specific SDLC in detail
+- Knows which environments are used for what
 - Understands principles of environment and configuration management
-- Knows common test-activities and artifacts for each SDLC stage
-- Can setup build/deploy/test environment/test tools
+- Knows common test activities and artifacts for each SDLC stage
+- Can set up build/deploy/test environments and test tools
+
 ## Senior
-- Has strong knowledge of various SDLCs (knows proc and cons of each, benefits, challenges), has wide practical experience
-- Has a knowledge about the Environment lifecycle, from creation till shutdown
-- Able to use CI/CD tools, configure them and set up new flows
-- Manages test infrastructure, holds responsibility of the full testing lifecycle
-- Identifies gaps in the process, proposes new approaches to increase speed/quality or reduce resources utilization
+- Has strong knowledge of various SDLCs (knows the pros and cons of each, benefits, challenges), and has wide practical experience
+- Has knowledge about the environment lifecycle, from creation to shutdown
+- Able to use CI/CD tools, configure them, and set up new flows
+- Manages test infrastructure, holds responsibility for the full testing lifecycle
+- Identifies gaps in the process, and proposes new approaches to increase speed/quality or reduce resource utilization
 - Can introduce methodology practices
+
 ## Expert
-- Participates in SDLC selection for project, can revise processes and suggest effective ideas for improvements, works in continuous improvements mode
-- Able to adjust QA process to a current specific SDLC, including project-specific options
-- Can setup the QA process starting from Static testing and ending with test closure activities
-- As a plus -  experience and skills are enough to set agile/scrum project processes and ceremonies from 0
+- Participates in SDLC selection for the project, can revise processes and suggest effective ideas for improvements, and works in continuous improvement mode
+- Able to adjust the QA process to the current specific SDLC, including project-specific options
+- Can set up the QA process starting from static testing and ending with test closure activities
+- As a plus, experience and skills are enough to set up agile/scrum project processes and ceremonies from scratch

matrix/05. troubleshooting.md

@@ -1,30 +1,35 @@
 # Issue Investigation
 Bug Reporting, defects localization, issue investigation
+
 ## Trainee
-- Has theoretical knowledge of what is bug's structure and its life cycle
-- Able to create bug report (fill all required fields), read it and reproduce the issue in the tracking system
-- Knows the difference between: verification and validation
+- Has theoretical knowledge of the structure of a bug and its life cycle
+- Able to create a bug report (fill in all required fields), read it, and reproduce the issue in the tracking system
+- Knows the difference between verification and validation
+
 ## Junior
-- Able to create structured bug report with all required information
+- Able to create a structured bug report with all required information
 - Understands the difference between severity and priority
 - Can perform defects localization
-- Uses available tools to investigate the issue (logs, DBs, console and DevTools)
-- Understands software structure and able to assume root cause reasons
+- Uses available tools to investigate the issue (logs, DBs, console, and DevTools)
+- Understands software structure and is able to assume root cause reasons
+
 ## Middle
 - Able to identify reasonable priority/severity
-- Able to create structured bug report (additionally provides bug meta information: links, tags, builds, modules, childs, parents and details like logs, screenshots, used test data, etc.)
+- Able to create a structured bug report (additionally provides bug meta-information: links, tags, builds, modules, children, parents, and details like logs, screenshots, used test data, etc.)
 - Can investigate the issue and localize a bug without supervision
-- Knows tools to assist on root cause analysis
+- Knows tools to assist with root cause analysis
+
 ## Senior
-- Able to analyze impact of priority/severity
-- Can localize defect in integrated systems
+- Able to analyze the impact of priority/severity
+- Can localize defects in integrated systems
 - Understands software structure and can investigate the root cause
-- Cooperates with development team for analysis, follows-up on issue fixing progress
-- Can read even poorly described bug reports and reproduce the issue
-- Performs systematization of defects at the end of iteration
+- Cooperates with the development team for analysis, follows up on issue fixing progress
+- Can read poorly described bug reports and reproduce the issue
+- Performs systematization of defects at the end of an iteration
+
 ## Expert
-- Does deep level investigation for the root cause; defines and mitigates potential weak areas ahead etc
-- Participates in business issues investigation. Provides full information about bug location, including code refrences and related issues from the past
-- Able to perform localization in unknown environment by collecting needed information
-- Has deep understanding of systems logic and defect localization principles
-- Performs systematization of defects at the end of iteration to contribute to lessons learned
+- Does deep level investigation for the root cause; defines and mitigates potential weak areas ahead, etc.
+- Participates in business issues investigation. Provides full information about the bug location, including code references and related issues from the past
+- Able to perform localization in an unknown environment by collecting needed information
+- Has a deep understanding of systems logic and defect localization principles
+- Performs systematization of defects at the end of an iteration to contribute to lessons learned