1 PDU per
Session
CONCURRENT S E S S I O N S
Thursday, June 11, 1:30pm
AGILE DEVELOPMENT
AT7
AT8
DEVOPS
AT9
DT3
AGILE LEADERSHIP
PRODUCT DEFINITION
AGILE TEST & QA
DEVOPS CASE STUDY
Leadership
Styles for a
Successful Agile
Transformation
User Stories:
From Fuzzy to
Razor Sharp
Integrate V&V
within Scrum:
How Does That
Work?
Chris Sims, Agile
Learning Labs
User stories are
the basis for
products built
using agile
development.
User stories are relatively short,
comprised of enough
information to start the
development process, and are
designed to initiate further
conversation about details.
Short doesn’t necessarily mean
useful. Ambiguous stories are
“mysteries wrapped in an
enigma”—potentially leading
us to develop the wrong
product. Phil Ricci explores
ways to turn fuzzy user stories
into sharply focused stories
from their inception. That
involves addressing questions
of Are we talking with the right
people? and Are we asking the
right questions? Phil shares a
four-step process—Review
Description, Clarify User Role,
Check for Discrepancies,
Critically Review Acceptance
Criteria—that sharpens the
stories. Setting up a story
maintenance schedule
sponsored by the Product
Owner with guidance from the
ScrumMaster ensures that
stories remain useful
throughout their lifetime.
Huawei’s
Journey to
DevOps and
Continuous
Delivery
Transforming an
organization to
become more
agile requires
leadership. But
what kind of leadership? Who
does the leading? When? How?
Chris Sims guides you through
the process of mapping the
styles of leadership needed at
various points in your
company’s agile transformation.
Chris explores the six
leadership styles Daniel
Goleman described in his
Harvard Business Review Study
Leadership That Gets Results
and learn when each style is
effective. He mixes in the Satir
Change Model that describes
how people and organizations
process their way through
change. Work in small groups
to synthesize these two models,
creating a map for applying
different leadership styles at
points along the change curve
of an agile adoption. There is
no one correct answer. Each
group creates a map based on
their experiences and their
organizations. Chris facilitates a
final review of the maps created
to share insights and create
deeper understanding.
32
Phil Ricci, Agile-Now
Kathryn Aragon and
Julie Bo