Please enable JavaScript.

Coggle requires JavaScript to display documents.

Test Maturity Diagnostic - Coggle Diagram

- - - - Test strategy maturity is not fully understood, but there is a plan in place to identify
    - - These have not yet been agreed and a standard practices need to be agreed to provide valid cross team metrics
    - - Where is the business quality policy?
    - - Test Strategy not fully implemented
  - - - Definition of ready in place, which includes everything a tester needs to successfully test
        Q - Is the acceptance criteria on the Stories/Bugs sufficient to understand the behavior expected and write the tests
    - - Some teams do - Dependent upon interaction between team, PO and end user.
        Q- Is there support within the team to answer questions and provide additional detail about the importance of the story to the product
    - - no test plan created currently
    - - there is a risk assessment for the delivery, but not sure about the effect is has on testing
    - - Done within teams at the start of the sprint - not sure if it needs a documenting
        Q - Are storied prioritised to take into account the product risk and the testing effort required?
    - - no specific process in place during sprint planning - depend on team
  - - - RW - Questions; 1. Do you follow the process defined in confluence 2. Does a test script review happen between all stakeholders. 3. Are the test cases all linked to an actual sprint
    - - RW - Questions: 1. How many defects were created 2. How many defects were fixed/closed 3. What were the priorities of the defects 4. Where were most defects found
    - - RW - Questions: 1 . Are these clearly defined processes available on confluence 2. Are all practices being followed
    - - RW - Question: 1 does a defect burn-down chart exist 2. Are these reviewed regularly 3.
    - - RW Questions; 1. Defects are assigned to developer 2. Defect priority agreed 3. Do all defects get resolved 4. Do defects get closed with reasons
    - - RW Questions: 1. Are informal reviews on requirements specification performed 2. Are high level walkthroughs performed 3.Has cyclomatic complexity been measured to ascertain the number of paths affected.
    - - RW - Question: 1. Have any risks been identified 2. Have any actions been initiated as part of the risks highlighted 3. Are these acted upon and reviewed.
  - - - Current practice on some teams
        Q - Is the sprint scheduled in a way to allow scripts to be written and executed.
    - - Current practice on some teams 3 Amigos session etc
        Q - Are the testers included in 3 amigos session to agree the acceptance criteria prior to being accepted onto a Sprint.
    - - Process currently being defined. Some teams are doing regression testing per sprint.
        Q - Does the team collate test sets based on risk to cover relevant user journeys as part of the regression
    - - Current practice on some teams
        Q - Are test scripts reviewed to verify the understanding
        Q - Are existing functional regression scripts reviewed and updated when changes take place
    - - Current practice on some teams
        Q -Does continual regression/Integration testing take place during the sprint to verify the behaviour
- - - - SP 5.3.1 AG -Test improvements are assessed and reviewed in the retros and shared across teams
        Q does the test guild create and share knowledge?
    - - SP AG- Standard templates , best practices and checklists are used consistently through the test process.
        Q -Are you aware of a general repository for best practice, templates and checklists?
    - - SP AG - Career paths are documented and used in 1-2-1s for feedback
        Q - Are you aware of a established career path for a tester?
  - - - SP - provide Training
        Q- Are you provided with training courses or on the job coaching to enable you to perform your role effectively and efficiently
      - SP - time is allocated within the sprint for upskilling and mentoring
  - - - Test Sets & Test Cycles exist
    - - SP AG Tester have a common way of working
        Q - Does the test process have a common way of working?
    - - SP AG The testing and development is a collaborative process and testing is performed at all stages of the sprint.
        Q -Is there test input at all stages of the sprint?