This document outlines an agenda and content for a workshop on continuous integration, continuous delivery, and overcoming obstacles. The workshop includes presentations on key concepts, exercises for participants to collaborate in different roles and provide feedback, and discussions on challenges and experiments to try back at work. The goal is to help participants shift their mindset and learn techniques through interactive exercises to enable continuous delivery of software.

1. Nathan
Feltch
and
Lisa
Crispin
Copyright
2014,
Lisa
Crispin
and
Nathan
Feltch

6. • Mindset
changes
• Con5nuous
Integra5on
–
CI
• Con5nuous
Delivery
• Con5nuous
Deployment
6

7. • Some
slides
and
story-­‐telling
• Learning
through
exercises
and
discussions
• CD
will
NOT
stop
bugs
• How
do
we
get
beFer
at
a
task?

8. • In
your
table
groups,
write
down
obstacles
to
“going
green”,
one
per
s5cky
note.
• Post
on
the
wall,
group
similar
ones
• Dot
vote
to
choose
top
3
to
share
8

9. How
can
we
think
differently
to
overcome
those
obstacles?
9
?

10. • Collaborate
within
and
across
roles
10

11. 11
Experiment:
Itera5on
1
§ In
your
table
groups,
each
choose
a
role:
programmer,
tester,
customer/PO,
observer
§ Programmer
and
tester
sit
back
to
back
§ Tester
gets
drawing
which
needs
to
be
replicated
§ Tester
tells
the
programmer
what
to
draw
§ Programmer
draws
the
shapes
based
on
what
the
tester
explained.
§ No
talking
during
‘coding’!
No
ques5ons!
§ Tester
“tests”
the
drawing,
tester
reports
“bugs”
on
index
cards
§ Programmer
fixes
the
“bugs”
§ Show
the
finished
drawing
to
the
customer/PO
§ Timebox:
5
minutes!

12. 12
Experiment:
Itera5on
2
§ Collaborate!
§ Tester
tells
programmer
what
to
draw,
watches
the
programmer
draw,
points
out
‘defects’
for
programmer
to
fix
immediately.
Customer/PO
answers
ques5ons
§ Show
drawing
to
customer/PO
a_er
each
shape
done
§ (Don’t
show
the
programmer
the
drawing,
that
makes
it
too
easy,
we’re
trying
to
simulate
real
coding)
§ Same
5
minute
5me
box
Thanks
to
the
members
of
the
agile-­‐games
group
and
Kane
Mar
for
ideas
&
pictures
for
this
game

13. • How
long
does
it
take
to
CERTIFY
a
build
for
produc5on?
• How
long
do
you
monitor
the
produc5on
environment
a_er
deployment?
• How
many
hours/days
are
taken
performing
“hodixes”
for
produc5on?
◦ Instant
rollbacks
vs.
quick
fixes
13

14. • Dedicated
test
systems
for
each
dev/deployable
• Fakes
for
those
hard
to
test
scenarios
• Dev/Test
collabora5on
• Examples
of
shortened
5meframes
14

15. • CI
and/or
CD
Tools
◦ Jenkins
◦ TeamCity
◦ GO
◦ …
• Provisioning
tool
◦ Vagrant/Ansible
◦ CHEF
◦ Puppet
◦ …
• Package
Repository
◦ NuGet
◦ Maven
◦ Gem
◦ …
15

16. • Do
you
have
a
story
on
how
your
team
shortened
your
feedback
loop?
16

17. • Provisioning
scripts
checked
into
code
base
• Build
tool
for
provisioning
environments
◦ Development
◦ Stage/Pre-­‐produc5on
◦ Produc5on
• Tips
and
tricks,
costs
17

18. 18
What
can
we
learn
to
improve
CD?
In
your
table
groups,
brainstorm
ideas
for
what
you
and
your
team
might
need
to
learn
to
be
able
to
green
up
your
CI
and
move
towards
con5nuous
delivery.
For
example,
learning
paFerns
for
crea5ng
maintainable
regression
tests.
One
per
s5cky
note,
put
on
wall
chart

19. 19
Challenge
Yourself
!
What
experiments
will
you
try
back
at
work?

20. • Or
experiments
you
will
try
next
week!
20

21. Agile
TesEng:
A
PracEcal
Guide
for
Testers
and
Agile
Teams
Coming
soon:
More
Agile
TesEng:
Learning
Journeys
for
the
Whole
Team!
By
Lisa
Crispin
and
Janet
Gregory
www.agiletester.ca
www.lisacrispin.com
Email:
lisa@lisacrispin.com
TwiFer:
@lisacrispin
21

22. • ConEnuous
Delivery:
Reliable
SoOware
Releases
through
Build,
Test
and
Deployment
AutomaEon,
2010
◦ Humble,
Jez
and
David
Farley,
• Steve
Smith
Atlassian
Blogs
◦ hFp://blogs.atlassian.com/2014/04/prac5cal-­‐con5nuous-­‐deployment/
• mindset,
the
New
Psychology
of
Success:
How
we
can
learn
to
fulfill
our
potenEal,
2007
◦ Carol
Dweck