- The TMMi Model is comprised of different components, falling into three categories:
- Required Components
- Specific Goals
- Generic Goals.
- Specific Goals
- Expected components
- Specific Practices
- Generic Practices.
- Specific Practices
- Informative components
- Sub-practices
- Typical work products
- Notes
- Examples
- References
- Elaborations
- Sub-practices
- Required Components
- Generic Goals are components that directly address the institutionalisation of a process across the organisation. Institutionalisation can be viewed as the process of establishing a practice as a norm in an organisation or culture
- Institutionalisation is relevant to the level of maturity.
- At Level 2, processes can be institutionalised in each project, but different processes can be defined for different projects.
- At Level 3, the processes are centrally managed and all projects conform to a single standard (with some agreed tailoring)
- At Level 2, processes can be institutionalised in each project, but different processes can be defined for different projects.
- Generic Practices describe activities addressing aspects of institutionalisation. There are CMMI Process Areas that support the implementation of Generic Practices
- Generic Goal 3 is only applicable when trying to reach Maturity Level 3 or higher.
- When assessing a Process Area it is necessary to review the elaboration of the Generic Practice that is appropriate for that Process Area.
- A defined process is a managed process that is tailored from the organisation’s set of standard processes according to the organisation’s tailoring guidelines
- Although TMMi can be used and implemented in isolation, it is also designed as a complementary model. CMMI process areas can support a TMMi implementation.
The TMMi Model in detail – Section Summary
Overview of Level 2: Managed
- At TMMi Level 2 testing is a process that is managed and separate from debugging.
- The main objective of testing is to verify that products satisfy their specified requirements.
- Testing may be perceived as a project phase that only starts once coding is finished.
- An organisation- or programme-wide test strategy is established.
- Testing is monitored and controlled.
- Testing may start relatively late in the development life cycle.
Level 2 Specific Practices
Process Area 2.1: Test Policy and Strategy | |
2.1.1.1 | Define test goals |
2.1.1.2 | Define the test policy |
2.1.1.3 | Distribute the test policy to stakeholders |
2.1.2.1 | Perform a generic product risk assessment |
2.1.2.2 | Define test strategy |
2.1.2.3 | Distribute the test strategy to stakeholders |
2.1.3.1 | Define test performance indicators |
2.1.3.2 | Deploy test performance indicators |
Process Area 2.2: Test Planning | |
2.2.1.1 | Define product risk categories and parameters |
2.2.1.2 | Identify product risks |
2.2.1.3 | Analyse product risks |
2.2.2.1 | Identify items and features to be tested |
2.2.2.2 | Define the test approach |
2.2.2.3 | Define entry criteria |
2.2.2.4 | Define exit criteria |
2.2.2.5 | Define suspension and resumption criteria |
2.2.3.1 | Establish a top-level work breakdown structure |
2.2.3.2 | Define test life cycle |
2.2.3.3 | Determine estimates for test effort and cost |
2.2.4.1 | Establish the test schedule |
2.2.4.2 | Plan for test staffing |
2.2.4.3 | Plan stakeholder involvement |
2.2.4.4 | Identify test project risks |
2.2.4.5 | Establish the test plan |
2.2.5.1 | Review test plan |
2.2.5.2 | Reconcile work and resource levels |
2.2.5.3 | Obtain test plan commitments |
Process Area 2.3: Test Monitoring and Control | |
2.3.1.1 | Monitor test planning parameters |
2.3.1.2 | Monitor test environment resources provided and used |
2.3.1.3 | Monitor test commitments |
2.3.1.4 | Monitor test project risks |
2.3.1.5 | Monitor stakeholder involvement |
2.3.1.6 | Conduct test progress reviews |
2.3.1.7 | Conduct test progress milestone reviews |
2.3.2.1 | Check against entry criteria |
2.3.2.2 | Monitor defects |
2.3.2.3 | Monitor product risks |
2.3.2.4 | Monitor exit criteria |
2.3.2.5 | Monitor suspension and resumption criteria |
2.3.2.6 | Conduct product quality reviews |
2.3.2.7 | Conduct product quality milestone reviews |
2.3.3.1 | Analyse issues |
2.3.3.2 | Take corrective action |
2.3.3.3 | Manage corrective action |
Process Area 2.4: Test Design and Execution | |
2.4.1.1 | Identify and prioritise test conditions |
2.4.1.2 | Identify and prioritise test cases |
2.4.1.3 | Identify necessary specific test data |
2.4.1.4 | Maintain horizontal traceability with requirements |
2.4.2.1 | Develop and prioritise test procedures |
2.4.2.2 | Create specific test data |
2.4.2.3 | Specify intake test procedure |
2.4.2.4 | Develop test execution schedule |
2.4.3.1 | Perform intake test |
2.4.3.2 | Execute test cases |
2.4.3.3 | Report test incidents |
2.4.3.4 | Write test log |
2.4.4.1 | Decide disposition of incidents in configuration control board |
2.4.4.2 | Perform appropriate action to fix the test incidents |
2.4.4.3 | Track the status of test incidents |
Process Area 2.5: Test Environment | |
2.5.1.1 | Elicit test environment needs |
2.5.1.2 | Develop the test environment requirements |
2.5.1.3 | Analyse the test environment requirements |
2.5.2.1 | Implement the test environment |
2.5.2.2 | Create generic test data |
2.5.2.3 | Specify test environment intake procedure |
2.5.2.4 | Perform test environment intake test |
2.5.3.1 | Perform system management |
2.5.3.2 | Perform test data management |
2.5.3.3 | Co-ordinate the availability and usage of the test environments |
2.5.3.4 | Report and manage test environment incidents |
Overview of Level 3: Defined
- Level 3 builds on the solid foundations provided in Level 2 to build an increasingly mature and capable test process.
- Level 3 is looking to add to the framework by ensuring:
- There is a conscious approach to professional test organisation and resources
- That the organisational test framework is managed by test professionals
- That test training is identified and made available as required
- That testing is fully integrated with the overall delivery life cycle activities
- Specific elements of testing are implemented.
- There is a conscious approach to professional test organisation and resources
Level 3 Specific Practices
Process Area 3.1: Test organisation | |
3.1.1.1 | Define the test organisation |
3.1.1.2 | Obtain commitments for the test organisation |
3.1.1.3 | Implement the test organisation |
3.1.2.1 | Identify test functions |
3.1.2.2 | Develop job descriptions |
3.1.2.3 | Assign staff members to test functions |
3.1.3.1 | Define test career paths |
3.1.3.2 | Develop personal test career development plans |
3.1.4.1 | Assess the organisation’s test process |
3.1.4.2 | Identify the organisation’s test process improvements |
3.1.4.3 | Plan test process improvements |
3.1.4.4 | Implement test process improvements |
3.1.5.1 | Deploy standard test process and test process assets |
3.1.5.2 | Monitor implementation |
3.1.5.3 | Incorporate lessons learnt into organisational test process |
Process Area 3.2: Test Training Program | |
3.2.1.1 | Establish the strategic test training needs |
3.2.1.2 | Align the organisational and project test training needs |
3.2.1.3 | Establish an organisational test training plan |
3.2.1.4 | Establish test training capability |
3.2.2.1 | Deliver test training |
3.2.2.2 | Establish test training records |
3.2.2.3 | Assess test training effectiveness |
Process Area 3.3: Test Lifecycle and Integration | |
3.3.1.1 | Establish standard test processes |
3.3.1.2 | Establish test lifecycle model descriptions addressing all test levels |
3.3.1.3 | Establish tailoring criteria and guidelines |
3.3.1.4 | Establish the organisation’s test process database |
3.3.1.5 | Establish the organisation’s test process asset library |
3.3.1.6 | Establish work environment standards |
3.3.2.1 | Establish integrated lifecycle models |
3.3.2.2 | Review integrated lifecycle models |
3.3.2.3 | Obtain commitments on the role of testing within the integrated lifecycle models |
3.3.3.1 | Perform product risk assessment |
3.3.3.2 | Establish the test approach |
3.3.3.3 | Establish test estimates |
3.3.3.4 | Define the organisation for testing |
3.3.3.5 | Develop the master test plan |
3.3.3.6 | Obtain commitment to the master test plan |
Process Area 3.4: Non-functional Testing | |
3.4.1.1 | Identify non-functional product risks |
3.4.1.2 | Analyse non-functional product risks |
3.4.2.1 | Identify non-functional product risks to be tested |
3.4.2.2 | Define the non-functional test approach |
3.4.2.3 | Define the non-functional exit criteria |
3.4.3.1 | Identify and prioritise non-functional test conditions |
3.4.3.2 | Identify and prioritise non-functional test cases |
3.4.3.3 | Identify necessary specific test data |
3.4.3.4 | Maintain horizontal traceability with non-functional requirements |
3.4.4.1 | Develop and prioritise non-functional test procedures |
3.4.4.2 | Create specific test data |
3.4.5.1 | Execute non-functional test cases |
3.4.5.2 | Report test incidents |
3.4.5.3 | Write test log |
Process Area 3.5: Peer Reviews | |
3.5.1.1 | Identify the work products to be reviewed |
3.5.1.2 | Define peer review criteria |
3.5.2.1 | Conduct peer reviews |
3.5.2.2 | Testers review the test basis documents |
3.5.2.3 | Analyse peer review data |
Overview of Level 4: Measured
- In TMMi Level 4 organisations, testing is a thoroughly defined, well-founded and measurable process.
- Testing is perceived as evaluation.
- It consists of all life cycle activities concerned with checking products and related work products.
- This includes constant measurement of product quality throughout the life cycle as well as implementing advanced reviews that inform other elements of the test life cycle.
Level 4 Specific Practices
Process Area 4.1: Test Measurement | |
4.1.1.1 | Establish test measurement objectives |
4.1.1.2 | Specify test measures |
4.1.1.3 | Specify data collection and storage procedures |
4.1.1.4 | Specify analysis procedures |
4.1.2.1 | Collect test measurements data |
4.1.2.2 | Analyse test measurements data |
4.1.2.3 | Communicate results |
4.1.2.4 | Store data and results |
Process Area 4.2: Product Quality Evaluation | |
4.2.1.1 | Identify product quality needs |
4.2.1.2 | Define the project’s quantitative product quality goals |
4.2.1.3 | Define the approach for measuring progress toward the project’s product quality goals |
4.2.2.1 | Measure product quality quantitatively throughout the lifecycle |
4.2.2.2 | Analyse product quality measurements and compare them to the products’ quantitative goals |
Process Area 4.3: Advanced Reviews | |
4.3.1.1 | Relate work products to items and features to be tested |
4.3.1.2 | Define a coordinated test approach |
4.3.2.1 | Define peer review measurement guidelines |
4.3.2.2 | Define peer review criteria based on product quality goals |
4.3.2.3 | Measure work product quality using peer reviews |
4.3.3.1 | Analyse peer review results |
4.3.3.2 | Revise the product risks as appropriate |
4.3.3.3 | Revise the test approach as appropriate |
Overview of Level 5: Optimisation
- At TMMi Maturity Level 5, an organisation is capable of continually improving its processes based on a quantitative understanding of statistically controlled processes.
- Improving test process performance is carried out through an incremental and innovative process with associated technological improvements.
- Testing methods and techniques are optimised and there is a continuous focus on fine-tuning and process improvement.
Level 5 Specific Practices
Process Area 5.1: Defect Prevention | |
5.1.1.1 | Define defect selection parameters and defect classification scheme |
5.1.1.2 | Select defects for analysis |
5.1.1.3 | Analyse causes of selected defects |
5.1.2.1 | Propose solutions to eliminate common causes |
5.1.2.2 | Define action proposals and submit improvement proposals |
Process Area 5.2: Quality Control | |
5.2.1.1 | Establish test process performance objectives |
5.2.1.2 | Establish test process performance measures |
5.2.1.3 | Establish test process performance baselines |
5.2.1.4 | Apply statistical methods to understand variations |
5.2.1.5 | Monitor performance on the selected test processes |
5.2.2.1 | Develop operational profiles |
5.2.2.2 | Generate and execute statistically selected test cases |
5.2.2.3 | Apply statistical test data to make stop-test decisions |
Process Area 5.3: Test Process Optimisation | |
5.3.1.1 | Collect and Analyse test process improvement proposals |
5.3.1.2 | Pilot test process improvement proposals |
5.3.1.3 | Select test process improvements for deployment |
5.3.2.1 | Identify and Analyse new testing technologies |
5.3.2.2 | Pilot new testing technologies |
5.3.2.3 | Select new testing technologies for deployment across the organization |
5.3.3.1 | Plan the deployment |
5.3.3.2 | Manage the deployment |
5.3.3.3 | Measure improvement effects |
5.3.4.1 | Identify re-usable test assets |
5.3.4.2 | Select test assets to be added to the re-use library |
5.3.4.3 | Deploy re-usable test assets |
5.3.4.4 | Apply re-usable test assets in projects |
TMMi Model – Maturity Level 5
TMMi Model – Maturity Level 4
TMMi Model – Maturity Level 3
TMMi Model – Maturity Level 2
Specific Goals and Specific Practices
In previous lessons we covered Maturity Levels and the Process Areas contained in each Level.
- Each Process Area contains Specific Goals (required components)
- Each Specific Goal is supported by
- Specific Practices (expected components)
- Typical work products (informative components)
- Sub-practices (informative components)
- Notes (informative components)
- Examples (informative components)
- Specific Practices (expected components)
In order to understand each process, the model provides a hierarchy of detail as follows:
Maturity Levels and Process Areas
The Maturity Levels and Process Areas provide the grouping of capabilities.
Purpose, introductory notes and scope of Process Areas.
These are informative components.
Specific Goals
A number of definitions of elements that must be present and implemented within the organisation. They are required components and must be successfully demonstrated.
Specific Practices
To assist in identifying whether a Specific Goal is satisfied or not, the model provides a number of Specific Practices describing features, activities and deliverables that are part of the Specific Goal. These are expected to be present.
Informative components
To assist in understanding Specific Practices, a number of Informative components are defined. These help to ensure that Specific Practices are satisfied. They are:
- Sub-Practices
- Notes
- Examples
- Typical Work Products
The hierarchy is illustrated by the diagram below, which we have seen in an earlier lesson:
Alternative view
Another way to view this hierarchy is to understand that using the notes, examples, Sub-practices and references, the Specific Practices are evaluated as being appropriately implemented by projects across the test organisation.
- If all Specific Practices are present (and carried out sufficiently well) then the associated Specific Goal has been demonstrated as being implemented – at least largely.
- If all Specific Goals are demonstrated as being (at least largely) implemented , then the associated Process Area is achieved
Learning objectives for TMMi Model in detail
For this section of the course (TMMi Model) there are eight learning objectives:
- LO 5.1 [K2] Summarise the TMMi Level 2 Process Areas (Test Policy and Strategy, Test Planning, Test Monitoring and Control, Test Design and Execution and Test Environment) and Specific Goals
- LO 5.2 [K1] Recognise the Specific Practices of the TMMi Level 2 Process Areas (Test Policy and Strategy, Test Planning, Test Monitoring and Control, Test Design and Execution and Test Environment)
- LO 5.3 [K2] Summarise the TMMi Level 3 Process Areas (Test Organisation, Test Training, Test Life-cycle and Integration, Non-functional Testing and Peer Reviews) and Specific Goals
- LO 5.4 [K1] Recognise the Specific Practices of the TMMi Level 3 Process Areas (Test Organisation, Test Training, Test Life-cycle and Integration, Non-functional Testing and Peer Reviews)
- LO 5.5 [K2] Summarise the TMMi Level 4 Process Areas (Test Measurement, Software Quality Evaluation, Advanced Reviews) and Specific Goals
- LO 5.6 [K1] Recognise the Specific Practices of the TMMi Level 4 (Test Measurement, Software Quality Evaluation, Advanced Reviews) Process Areas
- LO 5.7 [K2] Summarise the TMMi Level 5 Process Areas (Quality Control, Defect Prevention and Test Process Optimisation) and Specific Goals
- LO 5.8 [K1] Recognise the Specific Practices of the TMMi Level 5 Process Areas (Quality Control, Defect Prevention and Test Process Optimisation)
In a classroom-based situation, the syllabus for this course expects this section of the training to take approximately 270 minutes, but I recommend you spend about double that time on it as it is the largest and most detailed part of the course.
Generic Goals
TMMi Model hierarchy
The diagram below illustrates the hierarchy of the TMMi Model.
The TMMi Model has 5 Maturity Levels, 4 of which contain Process Areas.
Each Process Area contains Specific Goals and Generic Goals
Each Specific Goal has a number of Specific Practices and each Generic Goal has Generic Practices.
Specific Practices consist of:
- Sub-practices
- Typical work products
- Other informative comments may be included:
- notes
- examples
Generic Practices may contain informative components:
- Elaboration
- Notes
- Examples
- References
Component categories of TMMi
Learning objectives for the structure of TMMi
For this section of the course (Structure of the TMMi) there are nine learning objectives:
- LO 4.1 [K2] Summarise the components of the TMMi model
- LO 4.2 [K2] Explain the difference between a required, expected and informative component
- LO 4.3 [K2] Categorise the components of the TMMi model by type (required, expected, informative)
- LO 4.4 [K2] Summarise the Generic Goals of the TMMi model
- LO 4.5 [K2] Understand the two levels of institutionalisation related to the Generic Goals GG2 and GG3
- LO 4.6 [K1] Recognise the Generic Practices of both GG2 and GG3
- LO 4.7 [K2] Summarise the relationship between TMMi and CMMI
In a classroom-based situation, the syllabus for this course expects this section of the training to take approximately 70 minutes, but I suggest you take at least 120 minutes.
TMMi Level 5 Process Areas
TMMi Level 4 Process Areas
TMMi Level 3 Process Areas
In this section we will continue our high-level look at the Process Areas, this time for Maturity Level 3. As with Level 2, we begin with a review of the overall purpose of the Maturity Level, then examine at each of the Level’s Process Areas, considering their main purpose, scope, and some points to consider when assessing a test organisation for TMMi compliance or when deploying new or improved processes and procedures.
I know I keep saying this, but you will have seen some of this content in previous lessons and topics, but this is intentional, as we are attempting to improve your knowledge of the model incrementally, using repetition as one of the methods of reinforcing memory.
TMMi Level 2 Process Areas
We’ve now come to the part of the course where we will be looking in more detail at the TMMi Process Areas. We will go through each Maturity Level in turn, starting with Level 2 (since there are no Process Areas associated with Level 1). We will begin with a review of the overall purpose of the Maturity Level, then look at each of the Level’s Process Areas, considering its main purpose, what it is meant to cover (in other words, its scope) and some points to consider when assessing a test organisation for compliance of the Process Area or deploying new or improved processes.
You will have already seen, in previous lessons, some of the content we are going to cover, but as has already been indicated, this is intentional, as we are building up your knowledge of the structure and content of the model slowly and carefully, using repetition as one of the ways to ensure you remember the important points for the exam.
Example of the TMMi structure
The diagram below illustrates the main structure of the TMMi Model using Specific Goal 1 (Establish a test policy) of Process Area 2.1 – Test policy and strategy – as an example.
Maturity Level 2 has five Process Areas, including Process Area 2.1 – Test policy and strategy.
Process Area 2.1 in turn contains Specific and Generic Goals. For clarity we have only illustrated the Specific Goals here.
Each Specific Goal is supported by several Specific Practices. Each Generic Goal is supported by several Generic Practices. Again, we have omitted the Generic Practices to keep the diagram simple.
Specific Goal 1 has three Specific Practices, SP 1.1, 1.2 and 1.3.
Specific Practice 1.1 – Define test goals – This says what needs to be achieved in simple, high-level terms. Under the Specific Practices in the model, at the lowest level in the TMMi structure, are the Sub-practices. There are five of them for the Specific Practice ‘Define test goals’. They provide examples of the activities that could be carried out in order to achieve the associated Specific Practice.
The high-level structure of TMMi
The diagram below illustrates the main structure of the TMMi Model.
Each of the five Maturity Levels indicates a test process capability. Each Maturity Level (except Level 1) contains Process Areas covering groups of test activities that can be evaluated together.
Each Process Area is associated with several Specific and Generic Goals. These Goals must be achieved to demonstrate that the organisation is capable of undertaking the activities within the Process Area.
Each Specific Goal is supported by Specific Practices and each Generic Goal is supported by Generic Practices. The Practices describe the things that need to be implemented so as to achieve the associated Goals.
All Specific Practices (apart from just two) have associated Sub-practices. The Sub-practices provide a more detailed description of the associated Practice, giving guidance for how it should be interpreted or implemented – in other words, how a test organisation can undertake the activities described in the Practice.
Maturity Level definitions
There are 5 Maturity Levels defined in the TMMi Model.
The descriptions below provide a progressive road map to higher levels of process capability.
- Level 1 – Initial
- A chaotic and undefined process often seen as part of the development process
- When pressure is applied, any existing practices tend to be abandoned and ad-hoc processes are employed
- Level 2 – Managed
- Testing is a process that is managed and clearly separated from development
- In times of stress existing practices are carried out as normal
- Practices are retained from project to project
- Level 3 – Defined
- Testing is no longer a phase which simply follows coding
- It is fully integrated into the project life cycle with testing involvement starting as early as requirements definition
- Level 4 – Measured
- The testing organisation is thoroughly designed, well-founded and measured, with established quantitative objectives for product quality.
- The testing organisation is thoroughly designed, well-founded and measured, with established quantitative objectives for product quality.
- Level 5 – Optimisation
- A fully-defined and continually self-improving process, clearly fulfilling its improvement objectives.
- Capable of controlling the cost and effectiveness of testing
TMMi Process Areas by Maturity Level
- TMMi has 5 Levels of Maturity
- Apart from Level 1, each Maturity Level contains several Process Areas. A Process Area is a group of activities which can be evaluated together.
- Level 1 has no Process Areas and is awarded without any due process. If you test in any way, no matter how badly or inconsistently, you automatically achieve Level 1 (although you don’t get a certificate and you won’t be listed on the TMMi Foundation’s website).
- Each Level above 1 is empirically validated, in other words, measured based on solid evidence seen or experienced by assessors.
- TMMi is a staged model – in essence this means that to gain certification at higher levels of maturity the lower Levels must also be achieved. So, to achieve Level 4 you must also achieve Levels 2 and 3 (Level 1 is ignored for this purpose).
- While each Process Area deals with a specific set of activities, there are still relationships between them – both in the same Maturity Level and other Levels. You can think of it as building a house: The Process Areas at Level 2 are the solid foundations on which to put your house. Once these foundation blocks are in place and working well, then look to develop the next floor (the next level of maturity).