The document discusses bridging communication gaps and the evolution of agile processes. It describes the speaker's journey into behavior driven development (BDD) and how agile processes have changed at their company, Inviqa. It emphasizes that discovering business needs, exploring options, and making commitments are important for software development. Building the right thing, building it right, and building for the right reasons are highlighted.

1. Bridging
the communication gap,
fast

2. Roadmap
4 My personal and professional journey into BDD
4 Evolution of Agile processes at Inviqa
4 Deliberate discovery in the agency environment

3. Disclaimer
4 Road so far
4 Actual experience
4 No silver bullets
4 Still evolving

4. @everzet
communication designer

6. Norilsk, Russia

7. 4 North of Siberia
4 Polar night 9 months a year
4 Record low temperature of −53.1 degrees celsius
4 "Heavy metal pollution is so severe that mining the
surface soil is now economically feasible"
4 Was closed in November 2001 to all non-Russians

8. PHP developer

9. Hack'n'Forget
development

10. Agile

11. You can not be agile
without focusing on quality

12. doing now
vs
doing later

13. Building
the thing
wrong

14. Cucumber

18. Why do we need it?

19. Who will benefit from it?

20. Can you give me an
example?

21. It is not them!
it is me!

22. Building
the wrong
thing

23. Behaviour
Driven
Development

24. Because
it is in
the agreed scope

25. Your learning is always
limited by your
commitments

26. Building for
the wrong
reason

27. @INVIQA

28. Scrum

29. Example Workshops

30. Building the right thing
Building the thing right

32. How much?

33. Building for
the wrong
reason

34. What if businesses do not
actually care about the
features?

35. What if businesses do not
actually care about the
cost?

36. What if the only thing
businesses care about is
their business?

37. What if businesses care
about the features and the
cost only because we do not
care about their business?

38. What if it is not them?
What if it is us?

39. What is it you want
exactly?

40. The Discovery 1.0
"the way we calculate the project cost"

41. Sharing understanding

42. The Discovery
1. Identify Business Goals
2. Explore Options
3. Choose Options to make Commitment

43. The Discovery
Part 1: Business Goals

44. Hunt for value

46. If we achieve these goals
with the app on an ATM
machine, do you care?

47. The only thing businesses
care about is their business

48. The Discovery
Part 2: Options

49. We need to explore options
of how to achieve set goals

50. But options have more to
do with people than with
the software

52. The Discovery
Part 3: Commitment

53. Time to make choices ...

54. ... based on the insight

56. Are we there yet?

57. goals & budget
vs
scope & cost

58. I.I.I.

59. Ignorance
Investment
Innovation

60. Insight

61. Most businesses today do
not have enough insight to
support 100% of software
decisions

62. What happens when you
try to plan something you
never did before?

63. When you do not have an insight
you should invest in creating one

65. Failing fast

66. Learning cheap

67. doing now
vs
doing later

68. delivering predictably
vs
delivering innovation

69. Project archetypes

70. Enabler
Differentiator
Liability

71. Enabler

73. Find the cheapest commodity solution

74. Differentiator

76. Keep options open
Delay commitment

77. Liability

79. "Lift & Shift"

80. Push for value parity over
feature parity

81. The Discovery 2.0
"the way we manage the project risks"

82. Enabling understanding

83. The Discovery 2.0
1. Identify Needs and Risks
2. Discuss Constraints
3. Explore Options
4. Decide Strategy

84. The Discovery
Part 1: Identify needs

85. Identify needs
Brainstorm goals

86. Identify needs
Group goals & add measurements

87. Identify needs
Arrange goals into
milestones

88. The Discovery
Part 2: Discuss constraints

89. Discuss current processes
Discuss deadlines
Discuss budget

90. The Discovery
Part 3: Explore options

91. Explore options

92. The Discovery
Part 4: Decide strategy

93. Decide strategy

94. Needs
Constraints
Options
Strategy

95. Communication

96. Software Design - the
art of communicating with
other human beings under
constraints of a computer
system

97. Facilitation - the art of
communicating with other
human beings under
constraints of a business
system

98. The biggest risk in
software development is
building a software that
will not be used

99. Making sure you build
software that people will
want to use requires
talking with people

100. Engagements over projects

101. Image Credits
- norilsk.jpg - http://www.amusingplanet.com/2014/06/the-depressing-industrial-city-of.html
- developing.jpg - https://flic.kr/p/bHLu96
- risk.jpg - https://flic.kr/p/3cNs2
- comms.jpg - https://flic.kr/p/6PtfXL
- commitment.jpg - https://flic.kr/p/4pjbDr
- requirements.jpg - http://blogs.msdn.com/b/strim/archive/2010/03/08/9975217.aspx
- flipchart-meeting.jpg - https://flic.kr/p/5uywvK
- story.jpg - https://flic.kr/p/pg4euS
- pair-programming.jpg - https://flic.kr/p/QNdeB
- money.jpg - https://flic.kr/p/s6895e
- analytics.png - https://flic.kr/p/3NU5Fu

102. Thank you for your time!
Questions?