Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Bridging The Communication Gap, Fast

1,085 views

Published on

Konstantin puts it to you that one of the biggest problems in the software industry manifest from the gaps in shared understanding. This leads businesses to make technological choices with limited knowledge of technology impacts, or worse, technology delivery teams to make business choices without business guidance. Inevitably this leads to products being built badly, or the wrong products being built.

Agile, and BDD in particular, try to solve this problem through steady and deliberate discovery. What if you don't have time to be steady? What if you need to start bridging this gap very quickly with a new customer at the beginning of a new project, almost every week? Enter the project discovery - a way to get on the same page with many businesses in an agency-like environment.

This talk will present a collaborative process built on top of Agile and BDD practices aimed to replace requirements gathering and contract negotiation processes with Agile delivery planning.

Published in: Technology

Bridging The Communication Gap, Fast

  1. 1. Bridging the communication gap, fast
  2. 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. 3. Disclaimer 4 Road so far 4 Actual experience 4 No silver bullets 4 Still evolving
  4. 4. @everzet communication designer
  5. 5. Norilsk, Russia
  6. 6. 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
  7. 7. PHP developer
  8. 8. Hack'n'Forget development
  9. 9. Agile
  10. 10. You can not be agile without focusing on quality
  11. 11. doing now vs doing later
  12. 12. Building the thing wrong
  13. 13. Cucumber
  14. 14. Why do we need it?
  15. 15. Who will benefit from it?
  16. 16. Can you give me an example?
  17. 17. It is not them! it is me!
  18. 18. Building the wrong thing
  19. 19. Behaviour Driven Development
  20. 20. Because it is in the agreed scope
  21. 21. Your learning is always limited by your commitments
  22. 22. Building for the wrong reason
  23. 23. @INVIQA
  24. 24. Scrum
  25. 25. Example Workshops
  26. 26. Building the right thing Building the thing right
  27. 27. How much?
  28. 28. Building for the wrong reason
  29. 29. What if businesses do not actually care about the features?
  30. 30. What if businesses do not actually care about the cost?
  31. 31. What if the only thing businesses care about is their business?
  32. 32. What if businesses care about the features and the cost only because we do not care about their business?
  33. 33. What if it is not them? What if it is us?
  34. 34. What is it you want exactly?
  35. 35. The Discovery 1.0 "the way we calculate the project cost"
  36. 36. Sharing understanding
  37. 37. The Discovery 1. Identify Business Goals 2. Explore Options 3. Choose Options to make Commitment
  38. 38. The Discovery Part 1: Business Goals
  39. 39. Hunt for value
  40. 40. If we achieve these goals with the app on an ATM machine, do you care?
  41. 41. The only thing businesses care about is their business
  42. 42. The Discovery Part 2: Options
  43. 43. We need to explore options of how to achieve set goals
  44. 44. But options have more to do with people than with the software
  45. 45. The Discovery Part 3: Commitment
  46. 46. Time to make choices ...
  47. 47. ... based on the insight
  48. 48. Are we there yet?
  49. 49. goals & budget vs scope & cost
  50. 50. I.I.I.
  51. 51. Ignorance Investment Innovation
  52. 52. Insight
  53. 53. Most businesses today do not have enough insight to support 100% of software decisions
  54. 54. What happens when you try to plan something you never did before?
  55. 55. When you do not have an insight you should invest in creating one
  56. 56. Failing fast
  57. 57. Learning cheap
  58. 58. doing now vs doing later
  59. 59. delivering predictably vs delivering innovation
  60. 60. Project archetypes
  61. 61. Enabler Differentiator Liability
  62. 62. Enabler
  63. 63. Find the cheapest commodity solution
  64. 64. Differentiator
  65. 65. Keep options open Delay commitment
  66. 66. Liability
  67. 67. "Lift & Shift"
  68. 68. Push for value parity over feature parity
  69. 69. The Discovery 2.0 "the way we manage the project risks"
  70. 70. Enabling understanding
  71. 71. The Discovery 2.0 1. Identify Needs and Risks 2. Discuss Constraints 3. Explore Options 4. Decide Strategy
  72. 72. The Discovery Part 1: Identify needs
  73. 73. Identify needs Brainstorm goals
  74. 74. Identify needs Group goals & add measurements
  75. 75. Identify needs Arrange goals into milestones
  76. 76. The Discovery Part 2: Discuss constraints
  77. 77. Discuss current processes Discuss deadlines Discuss budget
  78. 78. The Discovery Part 3: Explore options
  79. 79. Explore options
  80. 80. The Discovery Part 4: Decide strategy
  81. 81. Decide strategy
  82. 82. Needs Constraints Options Strategy
  83. 83. Communication
  84. 84. Software Design - the art of communicating with other human beings under constraints of a computer system
  85. 85. Facilitation - the art of communicating with other human beings under constraints of a business system
  86. 86. The biggest risk in software development is building a software that will not be used
  87. 87. Making sure you build software that people will want to use requires talking with people
  88. 88. Engagements over projects
  89. 89. 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
  90. 90. Thank you for your time! Questions?

×