Infuse Capability Model Lite Assessment

Thank you for undertaking the Infuse Capability Model (ICM) Lite survey, the purpose of the ICM Lite is to get an insight into the current maturity capability of the testing process currently within the team. This is accomplished by asking 10 very specific and extremely relevant questions covering the wide scope of the project testing capability and should take roughly 3 minutes to complete. They are all in a multi-choice format, arranged to be a statement and a series of responses, please match the closest response that applies to your situation.

There are no wrong or right answers here, so please be as honest as possible

Question Title

* 1. We have an established Testing Community of Practice that supports Testing practices.

This is not something we have , nor do we plan to do this

We identify individuals as experts, they often work cross project

We have dedicated teams for each project, but they work in silos

We have a structured practice governing the make up of teams and experience levels across all projects

Question Title

* 2. We prioritize feature testing according to business need.

We don't prioritize, its more a first come first served or who has the loudest voice approach

Priorities are rapidly changing as they are structured around deadlines and achievable success

Risk has been considered and priority levels allocated in line with requirements

Features are examined and weighed for priority, we use tools to track progress and define the priority as they are defined. We use a risk evaluation principles in this selection

Question Title

* 3. The organisation supports testing practices. Continuous improvement and governance are in place.

Testing is either non existent or ad-hoc in nature. There are no formalized testing process and testers are allocated from an existing pool of employees

We have a test team in place, they are allocated testing tasks once the application is stable and the testing is mostly done in silos

We attempt continuous testing practices, we have deployed a CI server and test builds when there is sufficient code to do so

We have fully embraced the continuous testing approach, squads work collaboratively, builds are continuously tested and processes is reviewed on a regular basis

Question Title

* 4. We in the team understand that standard work practices are in place and we share them among the team

We follow a very ad-hoc approach, we are directed by rough guidelines and managed throughout

There is a documented set of practices that guide our work effort

We have a structured set of active work practices that are stored and maintained centrally and available to all

We have our own dedicated methodology that controls our work practices, it utilizes collaborative online tools.

Question Title

* 5. Each phase of the build process is automated

No, we don't have any automation

We have started to look at the tools and technologies to have build automation in place

We have build automation in place but it requires some manual intervention

We are completely automated throughout the build process

Question Title

* 6. We track each activity from requirement to release

We currently do not do this end to end

We have some ideas to put this in place, but they have not been acted upon yet

We have a process implemented to do this

We track all activities end to end and we keep this process in check

Question Title

* 7. Test progress is reported against the relevant feature with overall Test progress reported using relevant lifecycle management tools

The lack of fast, accurate and concise test reporting is one of our pain points

We do this but currently struggling to find the right management tools to make this more productive

We do this and get the right information for an intended target audience

We have live reporting tooling and tech in place which have pre-defined reporting capabilities to achieve this with full transparency

Question Title

* 8. We maintain a set of non functional requirements, we have a set of non-functional test specifications and have a structured test execution process for them

This is not something we really do, we treat each project as a new venture

We have a set of non-functional test specifications but it is not very well maintained

We do maintain a set of non functional requirements

We have a structured practice governing the maintenance of non functional requirements. We review these frequently to ensure the contents remain relevant

Question Title

* 9. We actively test the resilience of the architecture by monitoring and measuring recovery time after forced failures

We currently have no process or guidelines in place to start with this

We are at an early stages of determining the feasibility of the recovery process and verification of the backup facilities

We have good recovery testing architect in place but struggle with maintaining and updating the recovery plan at regular intervals

We have a well developed and efficient automated set of tests that demonstrating the ability of our system to recover from all critical failures

Question Title

* 10. We have a structured feed back mechanism to retest and tune the architecture

We are very bad at doing this, it is a real pain point causing issues

We are in a process of setting this up. We have rough ideas, but they are not fully formed

The structure is defined in the strategy and we have specific resources allocated to this process

We are constantly retesting, assessing and fine tuning the architecture based on the performance feedback

Question Title

* 11. Details

Name:

Email:

Mobile:

Position:

Company:

"Disclaimer"

In accordance with GDPR it is important you have transparency around how we use your data. By submitting your information to register to the ICM lite you agree for Infuse to process your data in the following ways;

The right to process your information in align with ICM parameters to create your maturity rating
The right to use said information to increase our Industry standard benchmark data (company details will remain anonymous)
The right to receive marketing and sales materials containing relevant information

Infuse will not:
- Share your information with any third party of outside organisation
- Use your Information for any reason other than the ones listed earlier in this disclaimer
- Keep your information on record past the point of your consent

If you wish to have your information removed from the Infuse ICM database, all you need to do is inform us and said information will be permanently deleted. Please note this means your ICM score will also be deleted, to obtain a score after this point you will need to retake the ICM

You can find out more about GDPR by by visiting the Infuse Privacy Policy webpage