agile: velocity without sacrificing quality...2015 release calendar 36 per app 2020 release calendar...

© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

Agile: Velocity Without Sacrificing Quality

Jon Bailey, HP Software Michael Cooper, HP Software

© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 2

About the HP Software Speakers

Michael Cooper, QA and Testing Evangelist, CSM Twitter: @QACooper LinkedIN: http://www.linkedin.com/in/qacooper Blog: The Future of Testing

Jon Bailey, Director - Applications Product Marketing LinkedIN: www.linkedin.com/pub/jon-bailey/0/784/a69 Blog: Application Transformation and ALM


Modern apps require a quicker response Huge projects are risky and fail far too often

Today’s Reality

“I can’t take another fire-drill or working weekend”

“We spend all our time on docs & admin”

“Quality is too often an afterthought”

“Requirements constantly change”

Pressures of Modern Delivery The Business

“This isn’t what we asked for” “We need to innovate faster”

Apps teams


Velocity is the New Normal

2010 Release Calendar 4 per app



30 X increase in releases

SOURCE: HP Enterprise 2020 research


“Velocity is killing quality.”

- Jim Highsmith, Coauthor of the Agile Manifesto


True Agility Demands Velocity AND Quality


World Quality Report What test difficulties do your Agile teams encounter?


“HP’s approach to manage and test Agile projects?”


A Recipe for Agility

1 SPRINT N SPRINT 2 SPRINT 1

Challenge: Accelerated pace requires immediate feedback on changes

2 - 4 weeks


Continuous Integration for Immediate Feedback

Discover defects earlier •  Change is fresh in developer’s mind.

Context switching and re-familiarization not needed.

•  Changes are isolated; no need to analyze what caused the defect.

•  Constant testing, ensures stable code and a higher-quality release.

CI Build & Test Feedback

Code check-in


Common Practices and Tools Used in HP Agile Projects Continuous integration for faster feedback

Developer code check-in

Automated build

Deploy app

Provision environment

Security Code Scan Fortify Source Code Analysis

Continuous Delivery Automation (CDA)

Continuous Delivery Automation (CDA)

(e.g. Jenkins)

Test results

Run test cases ALM Lab Management UFT / BPT / LoadRunner

Tear down environment Continuous Delivery Automation (CDA)

ALM




CI CI CI

Challenge: Unit test isn’t enough. Changes need to be verified, but the code is still too unstable for automation.


Mine Sweeping analogy

Exploratory Testing Mine

Fix

Repeatability alone won’t clear the field

Repeatability and variability are key


“Any tests that can be scripted should be automated. We don’t need humans doing something that a machine can do. What we do want the human testers doing is exploratory testing. Exploratory testing is a creative endeavor in which human testers explore the behavior of the system in an attempt to characterize its behaviors, both documented and undocumented.” – Dr. Robert C. (“Uncle Bob”) Martin


Exploratory Testing

Accelerate manual testing •  Audit trail for exploratory test repeatability •  Auto-authoring of tests (manual or automated)

•  Defect scanners spelling, broken links, W3C compliance, colors, localization

•  Data injection to minimize time & errors •  Screen annotation tools to clearly show issue •  Mirror test multiple environments

simultaneously

HP Sprinter




CI CI CI

ET ET ET

Challenge: Test automation is the only way to keep pace with development, but code isn’t stable until the end of the sprint


The “s+1” Rule of Test Automation

Test automation never lags by more than one sprint


Sprint 1 automation

Sprint 2 automation

1.  Automation should begin as early as possible.

2.  Time must be explicitly allocated for test automation in each sprint.

3.  Test automation goals must be co-equal to development objectives.




CI CI CI

ET ET ET

Sprint 1 automation

Sprint 2 automation

Challenge: This may work for a small, co-located team, but how do you scale to the enterprise?


Using Agile to Deliver HP Agile Manager

“HP Agile Manager, together with ALM provides increased

visibility across application development and testing for better collaboration

and risk control.” - Jason Taylor, Director IT Applications and Quality,

Specsavers


A Recipe for Enterprise Agility


CI CI CI

ET ET ET

Sprint 1 automation

Sprint 2 automation

PLANNING & COLLABORATION Visibility | Backlog & Task Mgmt. | Analytics

Challenge: True agility is more than just building the apps quickly


A Recipe for Enterprise Agility


CI CI CI

ET ET ET

Sprint 1 automation

Sprint 2 automation

PLANNING & COLLABORATION Visibility | Backlog & Task Mgmt. | Analytics

ITERATE IDEATE EVALUATE

Portfolio planning Feedback from production


Recap – Delivering Velocity AND Quality 1.  Exploratory testing is perfectly suited to the evolving, unstable

components in an Agile project

2.  Time must be explicitly allocated for test automation in each sprint.

3.  Automation should begin as early as possible and shouldn’t lag by more than one sprint.

4.  When assessing the results of a sprint, the automation goals must be considered as vital as the development objectives.

5.  Identify the things that slow you down and systematically remove


Learn More Agile Manager Forrester: Factors

Drive Agile success

World Quality Report

Free Trial hpagilemanager.com

Download worldqualityreport.com

Try the IPAD App: myWQR2013 Download

hp.com/go/agile


Thank you

agile: velocity without sacrificing quality...2015 release calendar 36 per app 2020 release calendar...

Documents