PointZERO Enabling the right first time principle

(1)

PointZERO

Enabling the ‘right first time’ principle

Consumerization of IT

Big data b l Social Mobility

(2)

Major causes of both cost and time overruns

Unrealistic project cost estimates and

schedules Unrealistic project cost estimates and

schedules Weak communication and ineffective decision making Weak communication and ineffective decision making Lack of effective executive project sponsorship Lack of effective executive project sponsorship schedules

schedules decision makingdecision making sponsorshipsponsorship

Insufficient user involvement Insufficient user

involvement

Poorly written and/or changing requirements Poorly written and/or

changing requirements

Late ‘failure warning’ signals Late ‘failure warning’

signals

Unclear priorities

Unclear priorities Insufficient risk Insufficient risk _management_management

Undisciplined, inflexible development practices/processes. Undisciplined, inflexible development practices/processes.

What are today’s challenges?

• Instant reaction by the consumers • High impact of failures due to “chains”

• Image of companies impacted by social mediaImage of companies impacted by social media • Competitive market

Quality

Traditional testing is not sufficient anymore! When do we need to achieve this quality? When is the quality good enough? What is quality?

(3)

PointZERO

®

_{is …}

(definition)

A

vision

aimed at

increasing

business success

by

increasing

business success

by

parallel

and

step-by-step

improvement

across

the application lifecycle,

to

shorten time to market

,

avoid

d

reduce cost

avoid

and

reduce cost

,

eliminate risk

, and

(4)

What is ”success”?

Wikipedia: Achievement of a Goal;

the opposite of Failure

pp

When is your business successful?

• Project ready in time?

• IT Quality meets standards?

• Business value is created? • Clients are happy!!

Why is “success” important?

Why do you need an information system?

• …

(5)

Application Lifecycle model

Most people accept “Testing” as a fact of life But often they are not happy about it

The IT problem

• Often delivered too late

• Cost (a lot!) more than expected

’ ( l l ) l h bl

• Don’t (completely) solve the problem

(6)

So we performed a TPI NEXT assessment to assess the test maturity

Conclusion: There’s nothing wrong with testing Client said:

“Testing costs too much time & money”

Conclusion: There’s nothing wrong with testing

The fixing and rework is the real problem!

Fixing phase

“Why do we need a fixing phase”? “Can’t they build it right first time”?

(7)

Defect distribution Capers Jones (2011)

8%

10%

Acceptance Change Analysis

Why don’t we build it

right first time?

8% 15% 10% 26% 22% 19% Testing Development Requirements © Sogeti

58%

of defects originate from

early lifecycle

activities !!

Design

What often happens

ll ll

Defect inserted in activity

Requirements

Requirements DesignDesign DevelopmentDevelopment TestingTesting AcceptanceAcceptance ImplementationImplementation MaintenanceMaintenance

Requirements

(8)

Defect fixing

The well-known Boehm curve still applies

Quality can’t be ‘tested in’ t th d

Three key principles

at the end

Faults must be prevented; Frontload the process with quality measures

People are fallible Î People are fallible Î perform early reviews

(9)

No faults forward

to the next activity

Requirements

Defect inserted in activity

Requirements

Defect detected and fixed in activity

Does “Agile” solve this?

For whom “Agile” has solved all problems?

Agile = QD

• Quality Development • Quick Development • Quick and Dirty

Q it Di t • Quite a Disaster

(10)

What often happens

Development

Testing

Problem grows:

the later the sprint, the lower the velocity, because of the backlog of defects to be fixed

No separate testing

Development

(11)

Implement measures Î

right first time

To enable “right first time” & “no faults forward”: Shift the quality focus to early lifecycle activities

(12)

Shift focus from time & cost

to

quality & risk

This should be © Sogeti no surprise in an agile context, but often still is!!

Framework for PointZERO

Quality Measures

• Business Case Workshop • Business Case Review • Business Case Management • Risk Analysis • Business Analysis

• Business _• _{Risk Analysis} • Requirements Workshop • Requirements Inspection • Requirements Traceability • Requirements Validation • Quality • End-2-end testing Business Acceptance Management artifacts • Supervision • Collaboration of people & artifacts • Quality Supervision • Evaluations (Inspections & Reviews) • Model Based Reviewing • Model Driven Development • System g • TPI & TMap • Test Automation • Model Based Test Design • TPaaS • Virtual Testing

(13)

Example:

Quality & Risk activities in Scrum

Evaluate backlog items and

communicate Determine product

risk of each backlog item and record it on

the (story) card communicate obscurities with product owner the (story) card

(input for planning poker, assigning story points)

Collaborate:

handover based on criteria

Collaboration at handover of artifacts (quality gates) Collaboration of

all

parties involved

for example: don’t forget the maintenance people

A quality gate is not a point in the process where everything comes to a stand-still, on the contrary: it must be a smooth handover based on previously agreed and monitored criteria

(14)

Quality Gates in a traditional application lifecycle

Select a limited number of handover points

Quality Gates for Scrum

The handovers in Agile are accomplished by teamwork and common ownership.

It is no longer a mere transfer of documents or deliverables. It is common responsibility.

(15)

Previously agreed criteria

Collaborate towards smooth handover

based on common responsibilities and

p

previously agreed criteria

What does this sound like?

Indeed, a Definition of Done!!

Including criteria on the

quality needed and the

risks to be covered

Definition of Done includes

quality and risk criteria

Examples of quality and risk criteria in the DoD:

• Review requirements and design(or do a role-play of the process)

– Depending on the risk involve more people in quality check • Unit testing performed

– How much coverage? (Statements, Decisions, Conditions, …) • System testing performed

– Functionality covered? – Non-functionals covered? • Regression testing performed

– Results from previous sprints still stable?

T t d f t i t i l d d?

– Test procedures of current sprint included? • Acceptance testing performed

– Business process covered? • The ultimate check:

(16)

Gradual changes in testing activity

through

Modelization

Initial: Manual testing

Step 1: Industrialization Î Automated execution

St 2 I d t i li ti Î M d l B d T ti (MBT) Step 2: Industrialization Î Model Based Testing (MBT) Parallel: Quality Î Early (model based) reviews & early

tests make late-lifecycle testing unnecessary Step 3: Smart inspiration Î Combination of

MBT & automated execution

Step 4: Smart insp.Î Model Driven Development

p p p

annihilates design, development and testing

No more fixing:

the ultimate goal

No more testing?

• Not as a separate activity in the lifecycle

ll d h l l f l

• Fully integrated in other application lifecycle activities

And of course Acceptance will remain in one way or another

Testing will remain as a role, not necessarily a functiony

Right first time!

(17)

A mountain can’t be moved

in one day

• Maturing is a long process of small steps forward • Parallel & step-by-step improvementParallel & step by step improvement

• Kaizen: continuous improvement • Using the “improvement backlog” • Start improving at the “weak spots”

Don’t change too much at one time

When ambitions for change are set high, It takes too much time takes too much time before the actual savings are realized

(18)

PointZERO is a gradual stepwise

move towards a goal

PointZERO is about

parallel and step-by-step

i t ith ll

improvement, with small but measurable effects

Tip:3 improvements

in parallel

L t L t Long term Long term

If you don’t start now it will never

Medium term Medium term Useful improvement with high outcome Quick win Quick win

Good feeling with fast progress

Medium term Quick win Quick win

now it will never get ready

(19)

How to start the PointZERO quest

Pinpoint client issues Aft i k

(Pre-)Sales/Delivery PointZERO

After quick scan Elaborate roadmap towards

increased business success

PointZERO Principal

(e.g. RCA, TPI, QOS, …)

Improvement backlog Quality improvement plan

Roadmap of approaches, measures, methods and tools PointZERO _Team

Industrialization

propositions Quality & Collaborationpropositions Smart inspirationpropositions

90%

_83%

Effective

waste

reduction

by doing things right from the very first moment

of defects found before testing activity has even started

83%

less incidents after go-live

22%

minimal time to market reduction on the application lifecycle

Looking not only at the project, but it is a

comprehensive view encompassing a shift in approach that goes across the overall application lifecycle

(20)

Success factors

Commitment of top management

• not a staff program

Focus on clear results

• Iterative approach on improvements

Improve all areas bit for bit

• Change culture/attitude – Continuous Improvement

Implementing Quality Gates as

Implementing Quality Gates as Collaboration Points

Continuous Return on Investment (ROI) calculation

What’s the difference with

traditional quality assurance?

PointZERO optimizes and works towards a

new way of collaboration

between people and artifacts

across the application lifecycle,

and improves the overall lifecycle activities

in order to

avoid rework

.

This can now be achieved with the

approaches, measures, methods and tools

(21)

What’s new?

Supervisionfor a complete and comprehensive viewencompassing Supervisionfor a complete and comprehensive viewencompassing Collaboration across allactivities

of the application lifecycle and also

Collaboration across allactivities

of the application lifecycle and also

No fenced off phases by frontloadingthe application No fenced off phases by frontloadingthe application © Sogeti p g a shiftin approach that goes across

the overall application lifecycle

p g a shiftin approach that goes across

the overall application lifecycle

y

between allparties and artifacts

involved y

between allparties and artifacts involved pp lifecycle with quality measures instead of checking

the quality at the end pp

lifecycle with quality measures instead of checking

the quality at the end

What’s new?

Key principles of Right First Time, Fit

For Purpose, and No Faults Forward

Key principles of Right First Time, Fit

For Purpose, and No Faults Forward

Effective waste reduction by doing things right from the

very first moment Effective waste reduction by doing things right from the

very first moment

Shortertime to market, avoidand

reducecost, eliminaterisk and

h fit f Shortertime to market, avoidand

reducecost, eliminaterisk and

h fit f reach fit for purposequality by

shifting management focus

from Time and Cost to Quality and Risk

reach fit for purposequality by

shifting management focus

from Time and Cost to Quality and Risk

(22)

Change

“Other approaches

t k

th

take you over the

first hurdle,

PointZERO will

cut

the path through

the obstacle”

PointZERO

The result

Reduced effort for the lifecycle as-a-whole and Focus shifted to early lifecycle activities

No more wasting time and money

by focusing on Quality & Risk

(23)

Increasing business success

Questions?

www.PointZERO.info www.TMap.net [email protected] [email protected]

(24)

If you don’t have time to do it right, When will you have time to do it over?

- John Wooden