1 PDU per
Session
CONCURRENT S E S S I O N S
Thursday, June 11, 3:00pm
AGILE DEVELOPMENT
AT10
AT11
DEVOPS
AT12
DT4
AGILE LEADERSHIP
AGILE TECHNIQUES
AGILE TEST & QA
DEVOPS & TESTING
Teaching PointyHaired Bosses
to be Agile
Enablers
Building
Agile Teams
in a Global
Environment
Test Automation
in Agile: A
Successful
Implementation
Continuous
Testing: A Key
to DevOps
Success
Ryan Ripley,
AgileAnswerMan.com
Betsy Kauffman and
Oscar Rodriquez,
Agile Pi
Melissa Tondi, Denver
Automation and Quality
Engineering
Sujay Honnamane,
Cognizant Technology
Solutions
Many agile teams
have experienced
big problems
when
implementing
test automation. For example,
they may discover that a
purchased tool is often seen as
a “silver bullet” and feel forced
to use it even though better
options may exist. Melissa
Tondi discusses who is affected
by automation, where it
belongs in the development
lifecycle, and when it should
start. In addition, Melissa
thoughtfully presents common
pitfalls—unattainable metrics,
tooling missteps, and
transitioning a manual test
team—that get in the way of a
successful implementation and
shares recommendations on
how to address each of these
pitfalls. Find out ways to quickly
move up the learning curve
from manual testing to
automation and take back
guidelines on what to automate
and when. Don’t throw in the
towel on test automation—it’s a
critical and required part of all
successful agile
implementations.
As IT
organizations
adopt a DevOps
strategy,
continuous testing
(CT) becomes a key ingredient
of the DevOps ecosystem. CT
enables faster release cycles,
more changes per release,
upfront isolation of risks, and
reduced operations costs. The
approach to scale the traditional
automation testing
infrastructure, test environments,
and test data management
requires a culture shift using new
tools and techniques. Sujay
Honnamane discusses a CT
strategy for aspiring and already
implemented DevOps
organizations. Sujay shares
examples of tools, techniques,
and practical solutions that
include continuous integration
using the Jenkins CI server,
service virtualization through CA
Lisa tools, automated code
coverage analysis to create
impact-based tests, automated
test script load balancing for
effective use of test
environments, and faster test
cycles, providing a holistic
approach/workflow for CT. Sujay
and his teams have successfully
implemented CT for several
clients in their DevOps journey
to achieve a repeatable and
highly predictable software
delivery process.
Ryan Ripley says
that Scrum
failures can often
be traced back to
management not
understanding their role in an
agile world. What gets
managed during an agile
project? How is success
measured? Will I keep my job in
the transition? Managers have
all these questions and more
during an agile transformation.
Unfortunately, these fears are
not covered during the two-day
certification courses. Agile
coaches need a plan for how to
talk with managers and teach
them the best ways to
contribute to agile projects. To
better understand managers’
concerns, Ryan introduces the
concept of personas,
representing different
managers. He explores ways to
“coach up” management and
help them get past their
concerns and issues. Ryan
shares his insights on where
managers can improve agile
projects, how they can add
value in a newly transformed
organization, and help pave the
way for agile teams to succeed.
34
Many organizations use teams
spread worldwide to develop
valuable business applications.
These organizations expect the
teams to work as one
harmonious unit without
missing a beat—or should we
say, a story point. A few
organizations do it well; many
not so well. Betsy Kauffman and
Oscar Rodriquez share their
experiences in working with
globally distributed teams,
discussing team models
implemented in many
organizations. They discuss how
to transition from a model that
may not be optimal (developers
onshore and testing offshore) to
a model where teams work
together to deliver high quality
working software regardless of
their location. Along the way,
explore “non-negotiables” and
sustainable software
engineering practices, i.e.,
DevOps and managing/
maintaining solid team health,
needed for building strong
teams. Leave with a set of
guiding principles you can
implement day one that
encompass agile leadership
qualities, common sprint
cadences, and “rules” to build
strong successful teams.
T O R E G I S T E R C A L L 8 8 8 . 2 6 8 . 8 7 7 0 O R 9 0 4 . 2 7 8 . 0 5 2 4 O R V I S I T A D C - B S C - W E S T.T E C H W E L L . C O M