Many companies are currently going through Agile Transformation or thinking about making the transition to agile. While moving to agile can create great opportunity for organizations, the journey to get there can be highly challenging. If you don’t have the right people, process and tools in place, the true benefits of agile may not be recognized. In this webinar, Andrew Stickland, Head of Client Services, for Clearvision and Kevin Dunne, VP of Business Development and Strategy for QASymphony will discuss the best practices for making the agile transformation. In this webinar, we will try to answer the following questions: - Who are the people I need in place? - What are the core processes that I need to change? - What tools do I need? View the On-Demand webinar here: http://pi.qasymphony.com/agile-transformation-best-practices-webinar-lp060?utm_source=slideshare&utm_medium=slideshare&utm_campaign=Agile%20Transformation%20Webinar

1. September 25, 2015
Introduction to
QASymphony for [INSERT
COMPANY NAME]
#AgileTransformation
Agile Transformation:
People, Process and Tools to Make
Your Transformation Successful
#AgileTransformation
The audio for this webinar is delivered through your computer. There is no dial-in
number. Make sure your speakers are turned up or use a pair of headphones.

2. #AgileTransformation
HOW TO WATCH THIS WEBINAR
• Audio for this webinar is delivered through your computer.
Make sure your speakers are turned up or use a set of
headphones.
• If your audio quality is choppy, it could be your internet
connection.
• You can customize your webinar viewing experience by
increasing, decreasing or minimizing the size of the widgets on
your screen.
• If you have questions, enter them in the widget on the right.

3. #AgileTransformation
• This webinar will be recorded and available on-demand tomorrow.
You will get an email when it is available.
• Join the conversation on Twitter using the hashtag
#AgileTransformation
• Use the Q&A widgets to ask questions during the webinar.
• At the end of the webinar, you will be asked to take a short survey.
HOUSEKEEPING

4. #AgileTransformation
Robust test management platform purpose-built to help agile teams
accelerate software testing
ABOUT QASYMPHONY

5. #AgileTransformation
World Leading Software Experts - Collaborate more, increase productivity
and stay ahead with the leading software solutions.
ABOUT CLEARVISION

6. #AgileTransformation
OTHER WEBINARS & RESOURCES
WWW.QASYMPHONY.COM/RESOURCES

7. #AgileTransformation
STAR EAST– MAY 4-5 IN ORLANDO
• Visit QASymphony booth #18
• Schedule a meeting with us at
calendly.com/stareast
• Check out Mike Cooper’s presentation at
3pm on Thursday, May 5th.
• Get more information at
stareast.techwell.com.

8. #AgileTransformation
PRESENTERS
Kevin Dunne
VP, Strategy and Business Development
QASymphony
@KevinDunneQA
Andrew Stickland
Global Head of Client Services
Clearvision
@afstcklnd

9. #AgileTransformation
WATERFALL COULD WORK…
Conceptually you could design and build software
like you design and build a car
• Fully scoped requirements
• Detailed engineering design
• Build to specification
Do it right and it would work!

10. #AgileTransformation
WATERFALL COULD WORK…
However doing it right means…
• Every copy of a piece of software would cost £1000s
• Not meeting the social
expectation that software
changes rapidly
And it has rarely been done right

11. #AgileTransformation
SO WE NEED SOMETHING BETTER…
Many things were tried
• Computer Aided Software
Engineering (CASE)
• Rapid Application Development
(RAD)
• Structured Systems Analysis and
Design Method (SSADM)

12. #AgileTransformation
SO WE NEED SOMETHING BETTER…
And we have now ‘settled’ on Agile
• Quick feedback
• Fail fast
• Visibility
• Risk Management
• Flexibility (and so on)

13. #AgileTransformation
WATERAGILEFAIL!
So you implement Scrum, Kanban, XP in your Dev
team and what have you really achieved? Nothing!
• OK, you get some “internal”
visibility, etc.
• But it’s your customers that
are important
• And they need the new features
- otherwise why bother?

14. #AgileTransformation
WATERAGILEFAIL!
Going Agile without Delivery is pointless
• Imagine a Dev Team completing 5 user features
every 2 weeks
• Not uncommon for release
cycles to still be quarterly –
commonly due to testing
methods and tools
• 30 user features not delivered

15. #AgileTransformation
WATER(SCRUM)FAIL!
Agile transformation has to have an organisation
wide impact
• Top Down adoption
• Culture
• Process
• Training
• Transformation

16. #AgileTransformation
WHAT TO TRANSFORM?
People – at all levels
• Testers, Release and/or Deployment teams,
Operations, Stakeholders, Managers, Directors
• Training and Culture change

17. #AgileTransformation
WHAT TO TRANSFORM?
Process – from start to finish
• Automate, automate,
automate
• If it needs manual
intervention it’s probably
a blocker
• End 2 End Integrated

18. #AgileTransformation
WHAT TO TRANSFORM?
Tools – drop the barriers
• Integration, visibility,
traceability, granularity
• Use those that fit the
philosophy, that are
adaptable and flexible
• Continuous Deployment

19. #AgileTransformation
WHAT IS SPECTRUM?
• End 2 End Integrated Stack
• Best Practice Processes
• Administration Tools
- Process Manager
• Self Service
- Project Wizard
• Behind the Firewall, Cloud or Hybrid

20. #AgileTransformation
A KEY BARRIER TO TRUE AGILE
• Tools & Process blocking change
• Delivery - operational barriers - go
- DevOps DevOps is about people and
culture and tools can help
- But…
• Testing - most tools & methods are not
Agile
- So let’s take a deeper look at that...

21. #AgileTransformation
TESTING CAN BECOME A BOTTLENECK
When testing cannot match the speed of Agile
planning and development, it becomes a risk where all
features may not be tested:
Agile Design Agile Dev
Agile
Deployment
Features that couldn’t be
tested, so not deployed.
Waterfall
Testing

22. #AgileTransformation
WILL WE TEST LESS TO KEEP UP
Given a fixed testing capacity , if we don’t change
anything else, we will be forced to perform less testing
on each feature to keep up
Design Code Deploy
Reduced depth of testing
on features
Test

23. #AgileTransformation
WATERFALL IS BUILD TO BE SLOW & MEASURED
Waterfall was created to overcome some of the assumed
limitations of the traditional development landscape:
Environment
Creation
Code Merges
On-Premise
Prevalence
Desktop
Focus
Lack of
Collaboration
Off-Shore
Development

24. #AgileTransformation
TECHNOLOGY ALLOWS US TO DO MORE WITH LESS
By taking advantage of technology trends, we can build a new
process that allows us to test more with the same amount of effort:
Containers have simplified the process dramaticallyEnvironment Creation
Git has replaced Subversion as the industry standardCode Merges
Cloud adoption is at an all time high, increased securityOn-Premise Prevalence
Prevalence of Web, Mobile, Internet of thingsDesktop Focus
Increase in teamwork, chat and collaboration technologyLack of Collaboration
Shifts towards rural sourcing, onshoring of laborOff-Shore Development

25. #AgileTransformation
AUTOMATING EVERYTHING IS A MYTH
There is a myth that automating every test is the way to make the testing
process more efficient, and therefore more agile. But this is NOT the case for
most, if not all organizations. Why?
It is impossible to believe that creating an automated test would be the most
efficient approach in all scenarios. Let’s think of some examples:
• Tests being used one time
• Tests on difficult parts of an application
• Tests for parts of the system that change frequently
Ultimately, manual testing still needs to be done to achieve agile collaboration

26. #AgileTransformation
WHY TRADITIONAL MANUAL TESTING FAILS IN AGILE
Manual test execution can be optimized by implementing exploratory
testing. A 2007 controlled study found that:
• Testing with test cases vs. exploratory testing take almost 7 times longer, due to
the amount of time needed to write the tests and report on them – TEST FASTER
• Testing with test cases vs. exploratory testing doesn’t find any more defects, and
does not miss many (if any) critical or severe defects in comparison to test case
testing – TEST BETTER
• Testing with test cases causes more false defect reports vs. exploratory testing –
TEST SMARTER
Study link: http://bit.ly/citeseerx

27. #AgileTransformation
ITERATIVE TESTING TO MATCH ITERATIVE DEVELOPMENT
Unlike traditional testing techniques, planning, design, and execution
happen concurrently, allowing efficiencies of time as well as flexibility in
approach
Plan Design Execute Report Report
Plan
DesignExecute
WATERFALL WAY ITERATIVE WAY

28. #AgileTransformation
THE LEGACY APPROACH TO AUTOMATION IS BROKEN
UI automation should be only be used for key features and functionality, given the
following limitations:
• SPEED – tests take much longer to run when waiting for pages to load, objects to
interact, etc.
• RELIABILITY – tests break frequently for reasons besides failing functionality (like
renamed or moved objects)
• MAINTENANCE – tests require frequent updating as UI elements are changed,
requiring more maintenance
• COST – many UI automation tools are expensive and based on perpetual
licensing

29. #AgileTransformation
UPDATE YOUR AUTOMATION STRATEGY FOR AGILE
The ideal testing pyramid would look like the following:
5% Effort
10% Effort
20% Effort
65% Effort

30. #AgileTransformation
Q&A
Questions?

31. Thank You
#AgileTransformation
PLEASE TAKE OUR SHORT SURVEY