A big part of the Agile manifesto and history of it coming together has to do with the need and desire to respond to change, adaptability being achieved by replacing project phases with short iterations, a strong quality foundation enabling teams to change direction and adjust to customer feedback. We've come a long way and now realise that making software softer isn't enough, software development is complex and systemic. This talk is a reflection on the frontiers of agility, at its outer bounds. It's about further softening the edges and improving the effectiveness of software by truly empathising with those whose lives it touches.

1. Empathyfrom Agility
marcelloduarte
@_md

2. https://en.wikipedia.org/wiki/Vrindavan#/media/File:Madanmohan_Mandir_Vrindavan.JPG @_md

3. softwareisaboutpeople

4. it’speoplewho
useit
{ @_md

5. it’speoplewho
useit
developit
{ @_md

6. it’speoplewho
useit
developit
orderit
{ @_md

7. it’speoplewho
{
useit
developit
orderit
acceptit
...
@_md

8. Muchsoftwareisdesignedandbuilt
withlittleconsiderationforhowitwill
beusedandhowitcanbestsupportthe
workitsuserswillbedoing.
“ —Constantin&Lockwood,1999

10. empathy |ˈɛmpəәθi|
the ability to understand and share the
feelings of another.
noun [ mass noun ]

11. empathyisatypeofattention

12. Principles behind the Agile Manifesto
We follow these principles:
Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.
Welcome changing requirements, even late in
development. Agile processes harness change for
the customer's competitive advantage.
Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.
Business people and developers must work
together daily throughout the project.
Build projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done.

13. Principles behind the Agile Manifesto
We follow these principles:
Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.
Welcome changing requirements, even late in
development. Agile processes harness change for
the customer's competitive advantage.
Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.
Business people and developers must work
together daily throughout the project.
Build projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done.

14. The most efficient and effective method of
conveying information to and within a development
team is face-to-face conversation.
Working software is the primary measure of progress.
Agile processes promote sustainable development.
The sponsors, developers, and users should be able
to maintain a constant pace indefinitely.
Continuous attention to technical excellence
and good design enhances agility.
Simplicity--the art of maximizing the amount
of work not done--is essential.
The best architectures, requirements, and designs
emerge from self-organizing teams.
At regular intervals, the team reflects on how
to become more effective, then tunes and adjusts
its behavior accordingly.

15. valuelisten

16. agile
{
value
adapt
deliver,adapt&repeat
changeenablingquality
@_md

17. @_md

18. https://www.flickr.com/photos/samhames/4699360569
@_md

19. productbacklogsand
expectationsaroundrequirements
@_md

20. mostagileprojectsusescrum
“54% said they use Scrum
in combination with
other practices, while
42% reported exclusive
use of Scrum.”
— The 2015 State of Scrum Report

21. scrum
{inspect
adapt
transparency
@_md

22. xp
{tdd
refactoring
continuousintegration
@_md

23. agilepracticeshashelpedmakesoftwaresofter
@_md

24. scrum
{ @_md

25. scrum
{
commitment
@_md

26. scrum
{
commitment
estimation
@_md

27. scrum
{
commitment
estimation
acceptancecriteria
@_md

28. scrum
{
commitment
estimation
acceptancecriteria
independentstories
@_md

29. scrum
{
commitment
estimation
acceptancecriteria
independentstories
productownership
@_md

30. scrum
{
commitment
estimation
acceptancecriteria
independentstories
productownership
engineeringpractice
@_md

31. valuesmotivateprocesses,
thenweforgetthevalues...
@_md

32. managedagility
coachedagility
ownedagility
@_md

33. managed
agility
{ @_md

34. managed
agility
{wiifm,formaltraining
@_md

35. managed
agility
{wiifm,formaltraining
newprocesses
@_md

36. managed
agility
{wiifm,formaltraining
newprocesses
champions
@_md

37. managed
agility
{wiifm,formaltraining
newprocesses
champions
“justtelluswhattodo”
@_md

38. coached
agility
{ @_md

39. coached
agility
{show,don’ttell
@_md

40. coached
agility
{show,don’ttell
focusonconfidence
@_md

41. coached
agility
{show,don’ttell
focusonconfidence
principlesoverprocesses
@_md

42. coached
agility
{show,don’ttell
focusonconfidence
principlesoverprocesses
askinggoodquestions
@_md

43. owned
agility
{ @_md

44. owned
agility
{empathy
@_md

45. owned
agility
{empathy
challengeprocesses
@_md

46. owned
agility
{empathy
challengeprocesses
contextualise
@_md

47. owned
agility
{empathy
challengeprocesses
contextualise
systemic
@_md

48. softwaredevelopmentdrivingforces
@_md

49. softwaredevelopmentdrivingforces
@_md

50. softwaredevelopmentdrivingforces
I WANT EVERYTHING I WANT IT CHEAP!
I WANT IT NOW!
@_md

51. softwaredevelopmentdrivingforces
WE NEED DOCKER
SYNTAX SUGAAAR!
WE NEED DDD

52. softwaredevelopmentdrivingforces
SUSTAINABILITY
MAINTAINABILITY
WE NEED QUALITY
@_md

53. empathy
@_md

54. usersusers
@_md

55. empathy
customers users
sales developers
maintainers
@_md

56. usecases
@_md

57. releasemission
usecases
{
@_md

58. developersempathytowardsbusiness

59. https://www.flickr.com/photos/hdptcar/2530986852

60. usecases
releasemission
{thebusiness:techratio
@_md

61. businessempathytowardsdevelopers

63. releasemission
thebusiness:techratiousecases
{
@_md

64. releasemission
thebusiness:techratiousecases
{
@_md

65. releasemission
thebusiness:techratio
3:1
usecases
{
@_md

66. releasemission
thebusiness:techratio
TDD/DDD/BDD,butno££
usecases
{
@_md

67. releasemission
thebusiness:techratio
TDD/DDD/BDD,butno££
usecases
{
ModellingbyexampleBusinessworkshops
@_md

68. challengeprocesses
@_md

69. isitpossibletodeliversoftwarewithoutestimation?

70. challengethevalue
estimation
requirements
planning
acceptancecriteria
lessonslearned
@_md

71. estimation==costidentificationtechnique
@_md

72. estimation==costidentificationtechnique
forecast
empirical
PERT historical
#noestimates cycletime
planningpoker
@_md

73. requirements
@_md

74. @_md

75. Principles behind the Agile Manifesto
We follow these principles:
Our highest priority is to satisfy the customer!
through early and continuous delivery!
of valuable software.
@_md

76. Principles behind the Agile Manifesto
We follow these principles:
Our highest priority is to satisfy the customer!
through early and continuous delivery!
of valuable software.
@_md

77. @_md

78. products
@_md

79. products
experiments
@_md

80. requirements
@_md

81. requirements
hypothesis
@_md

82. Examples:Eliminatingofficewaste andunnecessarycosts
@_md

83. usinghypothesisinsteadofuserstories
@_md[Jeffrey L. Taylor, 2011]

84. Hypothesis
I believe [target market]!
will [behave some way]!
because [this reason]!
UserStory
In order to [some business goal]!
As a [user]!
I’d like [behaviour]!
@_md

85. Motivation:Eliminatingofficewaste andunnecessarycosts
Experiment:Getemployeestodotheirowntravelrequest
@_md

86. Motivation:Eliminatingofficewaste andunnecessarycosts
Experiment:Getemployeestodotheirowntravelrequest
Ibelieveouremployeeswillbehappytodotheirowntraveland
accommodationarrangementswithinbudgetbecausetheywillhave
morefreedomofchoiceandwinloyaltypointswiththeircards.
@_md

87. measure!
@_md

88. Test:
-Chooseasubsetofemployees
-Agreethebudgetwithrelevantstakeholders
-Gatherfeedbackaftertheengagement
@_md

89. empathise
measure
learn
build
@_md

91. bitstrips.com

92. requirements
MoSCoW
backlog
WBS candidate
queue justintime
canonical
RFPsexperiments
@_md

93. contextualise
@_md

94. contextualise
Whatestimationapproaches?
Howmuchrequirements?
Howmuchplanning?
Howmuchconversationoverfeatures?
Whatrolesdoweneed?
Whatprocessesandtoolscanweuse?{ @_md

95. agilityhasopenedupsoftwaredevelopment
@_md

96. ithelpedmakesoftwaresofter
@_md

97. butsoftwareisn’taboutcode
@_md

98. ittouchespeople’slife
@_md

99. there’sempathyinagile
@_md

100. weforgetvaluesveryquickly
@_md

101. let’sownouragility
@_md

102. andconnectwiththerealneeds
@_md

103. @_md
marcelloduarte

104. thankyou!
@_md