Agile Transformation: People, Process and Tools to Make Your Transformation Successful

of 31/31
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.
  • date post

    11-Apr-2017
  • Category

    Software

  • view

    583
  • download

    1

Embed Size (px)

Transcript of Agile Transformation: People, Process and Tools to Make Your Transformation Successful

AGENDA

Agile Transformation: People, Process and Tools to Make Your Transformation Successful

#AgileTransformationThe 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.

September 25, 2015Introduction to QASymphony for [INSERT COMPANY NAME]#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.

#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

#AgileTransformation

Robust test management platform purpose-built to help agile teams accelerate software testingABOUT QASYMPHONY

#AgileTransformation

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

#AgileTransformation

OTHER WEBINARS & RESOURCES

WWW.QASYMPHONY.COM/RESOURCES

#AgileTransformation

STAR EAST MAY 4-5 IN ORLANDOVisit QASymphony booth #18

Schedule a meeting with us at calendly.com/stareast

Check out Mike Coopers presentation at 3pm on Thursday, May 5th.

Get more information at stareast.techwell.com.

#AgileTransformation

PRESENTERS

Kevin DunneVP, Strategy and Business [email protected] SticklandGlobal Head of Client Services [email protected]

#AgileTransformation

WATERFALL COULD WORKConceptually 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!

#AgileTransformation

WATERFALL COULD WORKHowever doing it right meansEvery 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

#AgileTransformation

SO WE NEED SOMETHING BETTERMany things were triedComputer Aided Software Engineering (CASE) Rapid Application Development (RAD) Structured Systems Analysis and Design Method (SSADM)

#AgileTransformation

SO WE NEED SOMETHING BETTERAnd we have now settled on AgileQuick feedback Fail fast Visibility Risk Management Flexibility (and so on)

#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 its your customers that are important And they need the new features- otherwise why bother?

#AgileTransformation

WATERAGILEFAIL!Going Agile without Delivery is pointlessImagine 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

#AgileTransformation

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

#AgileTransformation

WHAT TO TRANSFORM?People at all levels Testers, Release and/or Deployment teams, Operations, Stakeholders, Managers, Directors Training and Culture change

#AgileTransformation

WHAT TO TRANSFORM?Process from start to finish Automate, automate, automate If it needs manual intervention its probably a blocker End 2 End Integrated

#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

#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

#AgileTransformation

A KEY BARRIER TO TRUE AGILETools & 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 lets take a deeper look at that...

#AgileTransformation

TESTING CAN BECOME A BOTTLENECKWhen 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 couldnt be tested, so not deployed.

Waterfall Testing

#AgileTransformation

WILL WE TEST LESS TO KEEP UPGiven a fixed testing capacity , if we dont change anything else, we will be forced to perform less testing on each feature to keep up

Design

Code

DeployReduced depth of testing on featuresTest

#AgileTransformation

WATERFALL IS BUILD TO BE SLOW & MEASUREDWaterfall 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

#AgileTransformation

TECHNOLOGY ALLOWS US TO DO MORE WITH LESSBy 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 dramatically

Environment Creation

Git has replaced Subversion as the industry standard

Code Merges

Cloud adoption is at an all time high, increased security

On-Premise Prevalence

Prevalence of Web, Mobile, Internet of things

Desktop Focus

Increase in teamwork, chat and collaboration technology

Lack of Collaboration

Shifts towards rural sourcing, onshoring of labor

Off-Shore Development

#AgileTransformation

AUTOMATING EVERYTHING IS A MYTHThere 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. Lets 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

#AgileTransformation

WHY TRADITIONAL MANUAL TESTING FAILS IN AGILEManual 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 doesnt 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

#AgileTransformation

ITERATIVE TESTING TO MATCH ITERATIVE DEVELOPMENTUnlike traditional testing techniques, planning, design, and execution happen concurrently, allowing efficiencies of time as well as flexibility in approach

Plan

Design

Execute

ReportReport

Plan

Design

Execute

WATERFALL WAYITERATIVE WAY

#AgileTransformation

THE LEGACY APPROACH TO AUTOMATION IS BROKENUI 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

#AgileTransformation

UPDATE YOUR AUTOMATION STRATEGY FOR AGILEThe ideal testing pyramid would look like the following:

5% Effort

10% Effort

20% Effort

65% Effort

#AgileTransformation

Q&A

Questions?

#AgileTransformation

30

PLEASE TAKE OUR SHORT SURVEY

Thank You#AgileTransformation