Embed Size (px)
DESCRIPTION
The main goal of IT is to create an increase in your Business Success. In Agile development various activities take place, such as requirements elaboration, design, development, testing and acceptance. Testing is often a separate phase, even in agile projects. Many people involved in IT think of testing as “a fact of life”. They don’t challenge its existence but just want it to be as cheap and quick as possible. When stakeholders complain to me that testing takes too long or is too expensive I often have to explain to them that it is not the testing that takes so long but the fixing of defects and the subsequent retests (in a recent project we had an average of 6 retests!!). So I tell them that in their future projects they should rename the testing phase to the “fixing phase”. As soon as I suggest this they say “hey, but we don’t want a fixing phase”. And that of course is true! How can we get rid if this “fixing phase”? By doing all lifecycle activities right the first time so no faults will go forward. We must prevent defects from the start, not fix them at the end. This will ask for special attention in the collaboration of all people and artifacts involved, not only in the Agile team but also in the entire organization. Also this requires a focus on quality and risk from the very moment an idea for an IT-change arises. During this presentation Rik elaborates on the vision on how to increase the business success by properly applying Agile principles, for example from the Scrum method.
Citation preview
11-‐11-‐2013
1
© Sogeti
Collaborate to get rid of the fixing phase!
Amsterdam, 14 November 2013 Rik Marselis
Increase your Business Success
© Sogeti
Welcome
What is “success”? Wikipedia: Achievement of a Goal;
the opposite of Failure When is your business successful? • Project ready in time? • IT Quality meets standards? • Business value is created? • Clients are happy!!
11-‐11-‐2013
2
© Sogeti
Increased Business Success
From To
Needs
Agile might be an option But be careful…
© Sogeti
Agile is always “QD”
Agile = Quality Development
Agile = Quick Development
Agile = Quick & Dirty
Agile = Quite a Disaster
What is your QD ???
11-‐11-‐2013
3
© Sogeti
What often happens
Development
Testing
Result: the later the sprint, the lower the velocity, because of the backlog of defects to be fixed
© Sogeti
The Application Lifecycle model
Most people accept “Testing” as a fact of life But often they are not happy about it
This lifecycle shows activities.
These activities can be done
sequentially (e.g. waterfall) or
in parallel (e.g. agile).
Each activity is important, you can’t skip any.
DevOps
11-‐11-‐2013
4
© Sogeti
The IT-problem: too late & too expensive
Many solutions are delivered too late Many solutions cost (a lot!) more than expected Many solutions don’t (completely) solve the problem
This is NOT “right first time”
© Sogeti
So we performed a TPI NEXT assessment (for Agile) to assess the test maturity
Conclusion: There’s nothing wrong with testing
The fixing and rework is the real problem!
Client said: “Testing costs too much time & money”
11-‐11-‐2013
5
© Sogeti
We introduced: “the fixing-phase”
Now something interesting happened; the stakeholder asked:
“Why do we need a fixing phase”? “Can’t they build it right first time”?
Fixing phase
© Sogeti
No separate testing !!
Development
Testing
Collaborate in the team(s) !!
11-‐11-‐2013
6
© Sogeti
Where do defects originate?
58% of defects originate from early-lifecycle activities !!
Source: Capers Jones, 2011
© Sogeti
Three key principles
Adequate quality, not too little, not too much
Faults must be prevented; Frontload the process with quality measures
People are fallible perform early reviews and collaborate to improve
And remember: Quality can’t be ‘tested in’ at the end
11-‐11-‐2013
7
© Sogeti
Implement measures right first time
To enable “right first time” & “no faults forward”: Shift the quality focus to early lifecycle activities
Frontload the
lifecycle with
quality measures
© Sogeti
Shift focus from time & cost to quality & risk
This should be no surprise
in an agile context,
but often still is!!
11-‐11-‐2013
8
© Sogeti
Overview testing activities in scrum
Evaluate backlog items and communicate obscurities with product owner
Determine product risk of each backlog item and record it on the (story) card (input for planning poker, assigning story points)
© Sogeti
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
Definition of “Done”
11-‐11-‐2013
9
© Sogeti
Quality Gates for Scrum
The handovers in Agile are accomplished by teamwork and common ownership.
Is is no longer a mere transfer of documents or deliverables. It is common responsibility.
Doing Agile well will ensure that nothing gets ‘lost in translation’
© Sogeti
Pragmatic demand – supply model
• The demand side often uses a phased approach • The supply side often uses an agile approach • Good supervision, using quality gates, can glue them
together in a pragmatic manner
Demand
Supply
REGIE
11-‐11-‐2013
10
© Sogeti
Agile is always “QD”
Collaborate, to make sure:
Agile = Quality Development
© Sogeti
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
11-‐11-‐2013
11
© Sogeti
The goal: increasing business success
The Books
www.ict-books.com
Questions?
www.PointZERO.info www.TMap.net
www.Sogeti.nl
11-‐11-‐2013
12
If you don’t have time to do it right, When will you have time to do it over? - John Wooden
PointZERO®
© Sogeti
About the speaker: Rik Marselis
Management Consultant Quality & Testing at Sogeti in the Netherlands Over 30 years in IT Over 15 years in testing & quality assurance Involved in TestNet and BNTQB Advisor/coach at many organizations Author of many books and articles Speaker at many conferences TMap & ISTQB accredited trainer Prince2 practitioner, CMMI & CISA
