1

SERIOUS ABOUT SOFTWARE

Developing the Test OrganizationTUT 2.11.2009

2

3

•North America•Headquarters: San Jose, California

•Solution Center:›San Jose, CA›Washington DC

•Sales Office:›Boston, MA›Chicago, IL›Dallas, TX›Los Angeles, CA

•Europe•Headquarters: Tampere, Finland

•Adv. R&D Center:›Oulu, FIN›Stockholm, SWE

• Solution Center:• Gothenburg, SWE• Helsinki, FIN• Kuopio, FIN• Lahti, FIN• Malmö, SWE• Salo, FIN• Stockholm, SWE

•Asia•Headquarters: Beijing, China

•Global Dev. Center:›Beijing, CHN›Chengdu, CHN›Hangzhou, CHN›Taipei, TWN›Dhaka, BGD

•Sales Office:›Shanghai, CHN›Tokyo, JPN

Key Type of Center Focus Area Configuration

Client Solution Center Requirements gathering, executive briefing 2-5000 sq. ft

Advanced Research & Design Center Design, engineering staff 5000-20,000 sq ft

Global Development Center Larger scale, secure lab spaces, long term dedicated teams 10,000 – 100,000 sq ft

Sales Office

4

GLOBAL & REGIONAL HEADQUARTERS

Beijing, China Tampere, Finland San Jose, USA

PROFESSIONALS ~ 1,400

TOP 5 CLIENTS Ericsson NokiaIBM PayPalMicrosoft

BACKGROUND › Deep technology & industry expertise with strong focus on user experience

› Globally integrated delivery models in the US, Europe & Asia

› Scalable & cost effective offshore resources in China

› Created by former executives from IBM and Nokia

› Diverse global management team

QA, Testing & Globalization

• QA Consulting

• Process Development

• Test Architecture

• Test Outsourcing

• Internationalization

• Localization

5

Test & Measurement Systems

• Test & Measurement Systems

• Test Frameworks

• Test Automation

• Test Infrastructure

• Mostly done with LabVIEW

6

Skill profile

7

Management

• Learn the basic principles and techniques of testing.

• Learn to use them in different domains.

• Agile methods don’t say much about testing.

• Negative testing, non-functional testing and test automation are coming more important than ever.

8

Management

• Set general objectives for the test organization.

• Explain testing to your managers and customers.

• Tell your team the project objectives and align the test activities accordingly.

• Use metrics for reporting, but also ask questions from your team.

9

Management

• Let a tester be a tester, reward ingenuity.

• Independent thinkers are sometimes hard to manage.

• Find the ways to collaborate with project stakeholders.

• Beware of the quality guillotine!

• Diversity of the test team is the key to success.

10

Management

• Work together with your team.

• Be flexible and ready for changes.

• Follow what is happening at the testing community.

• Follow new development trends, tools and methods.

• Use a reference model to develop the organization.

11

Customers

• Testing has one or more customers (internal or external) and it’s a service.

• Develop services for your customers:

• Review service

• Internal training

• Agile testing team

• Defect management

• Performance evaluation

12

Metrics

• Test organization should have a couple of metrics which are used in every project:

• Normal project metrics (e.g. effort, costs)

• Size (e.g. LOC, number of requirements, use case, user stories, components)

• Test cases (ok / not ok / na)

• Defects

• Support for estimations

• Data should come out automatically from used tools.

13

Certifications

• Customers can demand certified project personnel.

• ISEB/ISTQB testing certifications

• Examples of others:

• CISSP computer security certification

• SSBB Six Sigma Black Belt

14

Towards QA

• QA should be proactive; prevent defects and measure quality.

15

Standards, regulations, methodology

• ISO 9001: Quality management systems – Requirements

• ISO 13485: Medical devices -- Quality management systems -- Requirements for regulatory purposes

• ISO 14971: Medical devices -- Application of risk management to medical devices

• IEC 60601: Medical Electrical Equipment

• IEC 62083: Medical Electrical Equipment - Requirements for the Safety of Radiotherapy Treatment Planning Systems FDA part 8.20

• AQAP 2110 - NATO quality assurance requirements for design, development and production

• CAPA: Corrective and Preventive Actions

• CMMi: Capability Maturity Model Integration

• FMEA: Failure Mode and Effect Analysis

• FTA: Fault Tree Analysis

• Six Sigma: risk management method

• TMap: Test Management approach

• TPI: Test Process Improvement

16

17