ITnews had an article recently on startups. It examines what to look for in a startup, and also how to minimise the risks. Here’s an excerpt:

‘A startup’s immaturity will be reflected in the quality and capabilities of its product. As you would when considering an established vendor, a CIO must conduct technical due diligence….You can minimize these risks in several ways. First, do extensive pilot testing, and start with a small deployment’

A good freelance software tester can provide real benefit to startups by verifying and/or validating software at a reasonable price. This builds confidence in a product and is useful for promotional purposes. Its also useful to demonstrate third party verification of technical claims when seeking additional funding.
This is how a freelance software tester can reduce cost yet still provide a quality service.

Freelance software testers are ‘on-demand’

The nature of software testing demands flexibility as the testing effort often fluctuates throughout a software development life cycle.

At the beginning of an SDLC, test planning, scheduling and scoping of tests takes place. It can be a very busy time for testers, scoping out whats to be tested, prioritising tests, planning and creating test cases, organising the test environment, the list can go on..

However, there’s often a lull after the initial frantic test planning. This is where all test cases are written, the test environments is ready, and testing is ready to start. The trouble is, often the software to be tested is not.

Even when the software testing starts, it can be a start, stop, start affair as major problems are found and require fixing. These are not necessarily related to code, but can be in installation, configuration etc. A tester isn’t always needed but should be on call for when testing does begin.

It goes without saying that a software tester is available during the test execution phase, and perhaps due to time demands, needs to test beyond normal work hours.

A freelance software tester works only when its needed, this is a big saving in cost. This way you can still afford a quality software tester at a lesser price.

Freelance software testers listen to the customer

A good freelance tester, will be a good listener. By understanding the demands on a business, a freelance software tester is able to adapt the testing to meet the needs. This can be a great cost saving, as needs are met first and foremost. See my post on http://www.blog.testingtimes.com.au/?p=25 for the types of questions a freelance software tester should ask.

Freelance software testers are flexible in approach

A good freelance software tester understands the three key demands placed on any software project, namely, cost, time and quality. They have the liberty to be flexible in approach to testing in order to balance quality against its natural enemies; time and cost. If time is an issue, a freelance tester is able to prioritise the testing to ensure key functionality is tested. Budgets can be effectively managed by using ‘on-demand’ testing and fast-tracking planning where possible.

Freelance software testers need to you succeed

Like any other freelancer, reputation is paramount. A freelance software tester’s reputation is built on getting excellent customer referrals. They don’t rely on big marketing budgets or a platoon of sales people for their next job. They need their client to succeed and be profitable. That way, not only does word spread, but they get repeat business. It’s in our interest to ensure that you have the best quality product to sell.

Of course many of the attributes I have described in this article can be found in software testers everywhere. However, a freelancer has the added advantage of passing these cost savings on directly to the client, without the commitment of long term contracts.

The full ITnews article can be found at http://www.itnews.com.au/News/59326,opinion-startup-fundamentals.aspx

Anne-Marie Charrett runs a software testing company that specialises in testing software for high-tech companies and startups.

Starting a freelance software testing project is similar in many ways to any other project. It requires rigorous planning, well thought out tests, and excellent communication. As a freelancer however, you may feel more responsible in making sure that your client is happy with your work. This way, you have a better chance of getting more work from them.

Think first then ask

Before you start anything, you want to clarify with your client as much as possible. This means you can provide them the biggest return for their money.

Clarify:

• Why did they hire you?
  What do they expect to get out of this piece of work? A report to take to customers?, confidence their application? Information about their application?
• Your test approach
  Provide guidance here. Give a basic approach on how you intend to test the application. Then get some feedback on it.
• Application
  Get as much information on the application they want you to test.
• test environment
  Ask who will be responsible for the test environment (They may be expecting you to own it). If the client is to maintain the environment, what access will be provided to you?
• the test scope
  Never assume the type of testing your client wants. Spell out what you intend to test. A spreadsheet is good for this. Briefly list the areas you think require testing and send this to your client.
• Test Tools
  Ask your client if they use any test tools? If not suggest the ones you are most comfortable with.
• reporting
  Give the client some idea of how and what you will be reporting. Is a weekly email sufficient or do they want daily communication. This will have an impact on the cost of the work involved.
• schedule
  Do they have a schedule or time frame in mind when this testing has to be completed? If the time frame is fixed, this may be the deciding factor in how much testing you can do
• budget
  Talk to the customer about money. Be upfront about payment conditions, when you expect to be paid and how.

I like to base my quote following most of this information exchange. Its an upfront cost I wear as I like to provide accurate quotes to my client that are tailored to meet their needs and provide greatest benefit to them.

Your quote can be fixed price or time and materials. Fixed price is great when the effort is quantifiable. Otherwise you can go for time and materials. This can be an hourly or daily rate. Deciding on your rate is tricky and will require you to do some investigating. If you have a friendly recruitment agent, they may be able to provide you with some pointers.

If you really have no idea how much be upfront with your client and ask them what their budget is and then work out what you can provide for that.

Once you have agreed on the scope of work, the schedule, the cost put it in writing. Include risks and assumptions such as;

Assumptions

• You will receive the application on time
• You will be paid thirty days after completion
• Completion of the project is delivery of a final report
• No retesting is involved in the cost

Risks

• What happens if the project is abandoned, will you be paid for the work you do?
• If the testing takes longer than you expected, how will this be managed?
• What happens if requirements change halfway through testing?

Be prepared….

Make sure you have everything you need to test. If you are testing remotely, do you have suitable bandwidth, hardware, software to support the testing required. Do this as early as possible, as it may take time to setup the test environment.

Have a process for backing up your testing nightly. Be meticulous about this.

I think its unfair to ask a customer to pay for you to ‘learn as you go’. So, know the basics of software testing. Have templates ready for all stages of your testing, this will also help with your branding.

Now all thats required is to start your test approach.

Above all;

• keep communicating with your client,
• be upfront on any issues that arise
• Be knowledgeable and provide guidance
• Don’t forget to ask the customer their opinion.

Good luck on your project

This blog is the result of an email requesting advice on starting a freelance software test job.