We are really proud to be able to announce that Experimentus are the first TMMi Service Provider outside of China to have been accredited as a Gold Status TMMi Assessment Service Provider. The gold status indicates a highly active TMMi Assessment Service Provider that regularly performs many TMMi assessments.
This is a recognition of our position as a global leading provider of TMMi services.
The Test Maturity Model integration (TMMi) is the world’s leading test process improvement and certification framework. We have worked with numerous organisations, using it to make their test processes more effective and efficient and to certify them when required.
Experimentus FSQS accreditation is renewed
Experimentus have had their Financial Services Qualification System (FSQS) accreditation renewed.
FSQS is a benchmark that financial services companies use when vetting potential vendors to work with. To become FSQS accredited, a company has to complete a rigorous audit process to prove that they meet requirements against key compliance and security areas. The information supplied is validated to ensure that financial institutions can make informed decisions when choosing suppliers.
Why is test process improvement necessary?
Typical reasons for conducting test process improvement
In the first of a short series of blogs on test process improvement, we look at why test process improvement is vital to the evolution of an organisation’s practices.
There are several reasons why test process improvement is needed. For a start, many organisations have tough business objectives, including:
- Reducing the time it takes to get software products from the drawing board to the customer
- Minimising production costs in order to maintain profit margins while competing in a market where reduced prices are being paid, particularly at the on-line checkout
Apart from these direct business objectives, other factors make test process improvement essential, including that:
- There is an expectation from customers of more functionality, better performance and increased reliability
- The number of end-users is typically increasing quickly – so there is a larger crowd liable to uncover problems in actual use
- As a consequence of adding increased functionality and complexity to software and hardware, the chance of introducing defects is ever greater
- Testing needs to keep up with the new methods, techniques and tools that are becoming available to support development and maintenance
- And many applications are co-developed, or use completely outsourced development organisations, making both the development process and testing process more complicated and difficult to manage
For all these reasons, it is becoming ever-more challenging to create and build applications and testing needs to be proportionately more effective and efficient. Test process improvement activities help this to be achieved.
It is an increasingly competitive world, and organisations need to make money and grow in a tough climate. It is certain that there are many more reasons for conducting test process improvement, but it is clear there is a demand to improve.
Systems and applications are playing an ever-increasing part of every-day life (both personally and in business). There is a greater need for development to focus on quality aspects. Customers and users are becoming more demanding – software failures are much more visible now and can have major impact on day-to-day activities – economically, socially and internationally.
Testing is becoming (even more of) a key activity for helping to improve both product quality and the performance of the development process.
Industry is undergoing a fast pace of change! To see how we can help you to manage that change, take a look at our test process improvement page and contact us.
Agile vs sequential testing approaches
In the first of a series of blogs on Testing in Agile, featuring excerpts from our ISTQB Foundation Agile Tester course, we discuss how the approach to testing on an Agile team differs from that of testing on a project using a sequential methodology.
Certain test activities are related to specific development activities. This means that the testing that takes place in different lifecycles may also be different. For testers to be able to work efficiently and effectively It is important to understand the differences between testing in traditional, lifecycle models (such as the sequential waterfall and V-model, or the iterative Rational Unified Process) and Agile lifecycles.
Agile methodologies differ in many ways including:
- How testing and development activities are integrated
- The nature of project work products produced
- Names given to particular work products
- The entry and exit criteria definitions used for various levels of testing
The way dev/test lifecycles are implemented in different organisations can vary significantly. Not all organisations adhere strictly to the ideals or all the principles of Agile. The digression or divergence from absolute adherence to the Agile principles may be a result of appropriate adaptation and customisation.
Adapting and adjusting to the special context or needs of a particular project or product, is something that developers need to do, and it most likely follows that testing (and testers) will also need to modify their practices as a result. The clue is in the name “Agile”. Testing needs to be agile in being able to change its organisation and processes when necessary.
There is little point in adhering 100% to Agile principles and practices if the product fails or is too late at the end of the day. Developers and testers need to be pragmatic. This “agility”, being able to adapt, is a key success factor for testers. However it’s also important to note that being agile doesn’t mean doing whatever you want in an unstructured way and labelling it as “Agile” to avoid structuring or documenting work. True agility relies on discipline (ask any Yoga or Martial Arts expert!) and teams can’t be disciplined if they don’t share common goals and practices that are well understood and socialised.
For more information on our self-paced learning, check out our available courses
Telekom Malaysia, Intelligence Software Testing, SMQ (GITD) attain a TMMi Level 5 certification!
A TMMi assessment team, led by Lead Assessor Simon Frankish of Experimentus has certified Telekom Malaysia, Intelligence Software Testing, SMQ (GITD) to Level 5 of TMMi.
This builds on the Level 3 certification that was achieved in 2018 and is a testimony to the hard work and dedication of all involved in the TMMi journey.
To see more about TMMi and how it could help you, take a look at our TMMi page