"What does analysis mean in a Continuous Delivery environment?" This is the presentation that Danilo Sato and I used in our talk at Agile Brazil 2012, in São Paulo, Brazil. http://submissoes.agilebrazil.com/2012/sessions/516

1. THE ROLE OF AGILE ANALYSIS
IN CONTINUOUS DELIVERY
Jenny Wong, Danilo Sato
teresafranco

2. Jenny Wong
@jenny_wong
rockstar business analyst
Danilo Sato
@dtsato
Developer, Architect, Coach, DevOps, Trainer

4. We are hiring!
join.thoughtworks.com

5. what is
CD?
principles
of
analysis &
engineering
practices
&
the role

6. WHAT IS CONTINUOUS DELIVERY?

7. development deployment
WHAT IS CONTINUOUS DELIVERY?

8. development deployment
WHAT IS CONTINUOUS DELIVERY?
business
&
product

9. Agile breaks this tradition
Smithers, we are going to build a giant
domain platform to take over the world,
I need you to find men to design, develop
and test before we roll it out to users.
Excellent...

10. Agile breaks this tradition
design
analysis
develop
test
deploy

11. Agile breaks this tradition
design
analysis
develop
test
deploy

12. Agile breaks this tradition
design
analysis
develop
test
24 months later deploy

13. Agile breaks this tradition
design
analysis
develop
test
24 months later deploy
AAaarrrrrrrrgggghhhhhhh
this isn’t what I want!!
Anybody recognises this?

14. AGILE 101
“Agile” team
analysis + design
development
customer testing + showcase
iteration 0 1 2 3 4

15. AGILE 101
“Agile” team
analysis + design IT operations
centralised QA
development QA + integration release + operation
customer testing + showcase
iteration 0 1 2 3 4

16. AGILE 101
“Agile” team
analysis + design IT operations
centralised QA
development QA + integration release + operation
customer testing + showcase
The “Last Mile”
iteration 0 1 2 3 4

17. AGILE 101
“Agile” team
analysis + design IT operations
centralised QA
development QA + integration release + operation
customer testing + showcase
The “Last Mile”
iteration 0 1 2 3 4
AAaarrrrrrrrgggghhhhhhh
this is still too slow!!

18. CONTINUOUS DELIVERY
customer
delivery
team
constant flow of new features into production

19. CONTINUOUS DELIVERY
customer
delivery
team
constant flow of new features into production
Software always production ready
Build quality in
Releases tied to business needs, not operational constraints

20. CONTINUOUS DELIVERY
customer
delivery
team
constant flow of new features into production
Software always production ready
Build quality in
Releases tied to business needs, not operational constraints

21. The path to ...
BUILD THE RIGHT THING

22. The path to ...
BUILD THE RIGHT THING
no
build
? no
build
yes
? no
build
yes
?
build
yes
?

23. The path to ...
BUILD THE RIGHT THING
no
build
? no
build
yes
? no
build
yes
?
build
2 years yes
?
10 months
1 quarter
MUCH shorter feedback cycle
Less guesswork, cost to adapt

24. WHY CD?
Build the right thing
Risk reduction
The only real measure of progress

25. PRINCIPLES
OF
ANALYSIS AND ENGINEERING

26. HOW WILL YOUR FEATURE BE TESTED?
Not just QA tested
How will you know whether this feature is successful?

27. THINK BEYOND WORKING SOFTWARE
Used by customers, real people
Generates profit
Helps your employees
Want customers to like you

28. SMALL, INCREMENT STEPS
XP principle “What is the simplest thing that could possible work?”
Blur monitoring and testing

29. CONTINUOUS PRODUCT MANAGEMENT
You are not DONE when the feature is released
Engineering R&D intersects product development
Continuous feedback from existing features in production

31. PLAN TO RETIRE
Removing features that are no longer valuable
Morphing existing into new
You don’t want to maintain bloated product with stale features

32. VALUE ≠ COMPLETE-NESS

33. VALUE VS. COMPLETE-NESS

34. VALUE VS. COMPLETE-NESS
Do the least to get feedback Do all that I could think of

35. VALUE VS. COMPLETE-NESS
Do the least to get feedback Do all that I could think of
R&D, not first release! Binary approach

36. VALUE VS. COMPLETE-NESS
Do the least to get feedback Do all that I could think of
R&D, not first release! Binary approach
Future is guided by feedback Do & test everything at once

37. VALUE VS. COMPLETE-NESS
Do the least to get feedback Do all that I could think of
R&D, not first release! Binary approach
Future is guided by feedback Do & test everything at once
Innovation No research, blind development

38. VALUE VS. COMPLETE-NESS
Do the least to get feedback Do all that I could think of
R&D, not first release! Binary approach
Future is guided by feedback Do & test everything at once
Innovation No research, blind development
Step-by-step validation Assumes feature complete-ness as
success criteria

39. VALUE VS. COMPLETE-NESS
Do the least to get feedback Do all that I could think of
R&D, not first release! Binary approach
Future is guided by feedback Do & test everything at once
Innovation No research, blind development
Step-by-step validation Assumes feature complete-ness as
success criteria
Lower costs Risks opportunity costs

40. VALUE VS. COMPLETE-NESS
Do the least to get feedback Do all that I could think of
R&D, not first release! Binary approach
Future is guided by feedback Do & test everything at once
Innovation No research, blind development
Step-by-step validation Assumes feature complete-ness as
success criteria
Lower costs Risks opportunity costs
?
W hat if I get it wrong

41. VALUE VS. COMPLETE-NESS
Do the least to get feedback Do all that I could think of
R&D, not first release! Binary approach
Future is guided by feedback Do & test everything at once
Innovation No research, blind development
Step-by-step validation Assumes feature complete-ness as
success criteria
Lower costs Risks opportunity costs
?
W hat if I get it wrong

42. PRACTICES & THE ROLE

43. LESS IS MORE
Release thin segments to test
Use vertical slicing technique

44. http://bit.ly/slicing-stories

45. USE MVP WELL
MVP = Minimum Viable Product

46. BACKLOG RANT
Start thinking your backlog is essentially a set of assumptions
You must validate assumptions

47. PRUNE, DON’T GROOM
your backlog

48. FEATURE, REDEFINED
functionality

49. FEATURE, REDEFINED
capture
functionality
feedback

50. FEATURE, REDEFINED
X users have clicked on Peak time usage
this in the past week vs. off-peak usage
capture
feedback
X seconds less to
X% of entire online
complete task
customer base have used this

51. BUILD TOOLS TO GATHER FEEDBACK
Product level metrics
Feature level metrics
Dashboards

52. A DIFFERENT APPROACH
User research
Guerrilla testing
Data analytics
Collaborate, collaborate, collaborate

53. ANALYSIS, XD, ENGINEERING
They all go hand-in-hand
Engineering = code + test
Ops too!

54. GET AWAY FROM BIG BANG
BIG BANG planning
• Big analysis to build big backlogs
• BDUF (Big Design Up-Front)
BIG BANG release
• Big ta-da approach to business stakeholders

55. GET AWAY FROM BIG BANG
BIG BANG planning
• Big analysis to build big backlogs
• BDUF (Big Design Up-Front)
What is ta-da?
BIG BANG release
• Big ta-da approach to business stakeholders

57. PRUNE EXISTING FEATURES
What features are not used?
Which features do not contribute to the business value?
Remove technical debt to make you go faster

58. http://bit.ly/manage-tech-debt

59. LEVERAGE FEATURE TOGGLES

60. LEVERAGE FEATURE TOGGLES
Dev WIP toggle

61. LEVERAGE FEATURE TOGGLES
Dev WIP toggle
Ops toggle

62. LEVERAGE FEATURE TOGGLES
Dev WIP toggle
Ops toggle
Business toggle

63. SUMMARY
what is
CD?
principles
of
analysis &
engineering
practices
&
the role

64. Q&A
Danilo Sato @dtsato
Jenny Wong @jenny_wong

65. Danilo Sato @dtsato
Jenny Wong @jenny_wong

66. Danilo Sato @dtsato
Jenny Wong @jenny_wong