Scrum 2010 NZ

Increase productivity and quality and drop projects costs

Certified Scrum Master

Certified Scrum Product Owner

hands-on half day workshops on Test Driven Development, Continous Integration, Testing on Agile Projects and Writing User Stories throughout NZ in March and April

[details here]

 

What clients are saying

"I have found Clarus’ service an extremely beneficial and responsive business enabler. Having worked in the IT industry and spent time in the trenches, they intimately understand the sort of people we need. Typically I will have a list of three of four outstanding Clarus Members on my desk within a couple of days and can often have someone starting a few days later."

Chaley Warne, Resource Pool Manager (Retail), Meridian Energy



 
 

Testing

Testing is about providing information to people to make informed project decisions.

Project information tends to have a very short half life, therefore the role of the tester is to measure and report information that is both pertinent to needs now and immediate future needs.

Clarus has a dedicated software testing capability. Our lead tester is a Board member of the Australian and New Zealand Testing Board and is actively involved in planning, writing and reviewing testing certification exams

We provide a broad range of professional Testing services:


Test Management Test analysis Test automation
TMO establishment.
Testing best practices Application testing
Bespoke Software testing
Performance Testing Tool selection
Web (including cloud services and security) Process review and improvement

Approach

Our philosophy is simple. We ask basic questions to under your needs.

What to test

We recommend that the first things to test are the items that are worth the most, in terms of business value. For example, on an e-commerce site test that credit cards work as this is how customers pay.

We then look at whatever will uncover the most relevant information at that time in the project. For example, what are the most riskiest pieces of technology on the project?

When to test

Early - testing early is extremely important - but not too early. There is no point kicking off testing when the business case hasn't been completed. However, the requirements stage is a great time to kick off testing.

Continuously - we are advocates of automated, continuous testing. Your project is constantly evolving, as is the technology. Wouldn't it be nice if you could automatically run a continuous testing cycle? Ask us how.

When not to test

Some companies suggest you test everything. We don't. When the results or information do not help the company, or the marginal cost of testing exceeds the marginal benefit, then stop testing.

How to test

There are a myriad of approaches to testing - too many to record here. The key aspects remain the same however. It is all about measuring and reporting in a timely, clear manner to decision makers. We therefore apply whatever method leads to the most accurate ad useful information from the least number of activities.

 
RocketTheme Joomla Templates