Finding The Invisible Gorilla At Your Product Development Journey

This is the deck I presented at Agile Turkey's Agile Talk Meetup. I touched the points we usually miss during agile adoption.

Transcript

1. the invisible gorilla
   at your product development journey
   lemi orhan ergin
   

   View Slide

2. View Slide

3. View Slide

4. Building software is a journey
   from complexity
   to generate business value
   

   View Slide

5. expertise in programming languages
   domain driven design
   monoliths /microservices
   evolutionary architecture, emergent design
   hexagonal architecture / ports and adaptors
   branching mechanisms / trunk based development
   automated tests (unit, integration, functional, etc)
   pair & mob programming
   code review, team standards
   continuous integration and cd pipeline
   design patterns & refactoring
   test driven development (tdd, bdd, atdd)
   expertise in frameworks
   oop and functional paradigms
   consumer driver contract testing
   transaction management
   code quality and static code analysis
   event handling / messaging
   non-blocking io, data streaming
   monitoring & traceability
   resilient architecture
   asynchronous communication
   cache management
   rest / grpc api management
   

   View Slide

6. idea PLAN DEVelop RELEASE
   going
   live
   harnessing
   development
   started
   idea
   prioritized
   idea
   emerge
   

   View Slide

7. idea
   prioritized
   development
   started
   harnessing
   going
   live
   idea
   emerge
   What business understands about agility
   

   View Slide

8. idea
   prioritized
   development
   started
   harnessing
   going
   live
   idea
   emerge
   What engineering understands about agility
   

   View Slide

9. idea
   prioritized
   development
   started
   harnessing
   going
   live
   idea
   emerge
   What agility is totally about
   

   View Slide

10. idea
    prioritized
    development
    started
    harnessing
    going
    live
    idea
    emerge
    Product development requires
    doing fast experiments
    for learning fast
    

    View Slide

11. AGILITY
    DEV-SEC-OPS
    CONTINUOUS DELIVERY
    LEAN STARTUP PROCESS
    TARGET
    ENABLER
    THE RIGHT WAY
    RIGHT PRODUCT
    THE MINDSET SOFTWARE CRAFTSMANSHIP
    

    View Slide

12. Agile doesn’t cure INCOMPETENCE.
    You can coach teams to be more engaged and
    collaborative, but NO Agile framework, method,
    or mindset can save you from BLATANT FAILURE
    if your development team is INCOMPETENT in
    basic engineering practices.
    Technical excellence is a MUST!
    Mike Beedle
    @mikebeedle
    7:48 PM · Mar 21, 2018
    https://twitter.com/mikebeedle/status/976500772438409216
    Mike Beedle (died at March 23, 2018)
    Agile Manifesto co-creator
    proposed the term “agile” to manifesto co-creators
    introduced “Enterprise Scrum” and “Business Agility”
    

    View Slide

13. Many Agile adoptions have treated technical
    practices as secondary compared to the
    management and team practices that some Agile
    frameworks emphasize.
    Our research shows that technical practices play
    a vital role in achieving these outcomes.
    Nicole Forsgren PhD, Jez Humble, et al.
    Accelerate: The Science of Lean Software and DevOps: Building
    and Scaling High Performing Technology Organizations
    https://www.amazon.com/dp/B07B9F83WM
    

    View Slide

14. AGILE
    

    View Slide

15. View Slide

16. You work on projects, not products.
    You don't know how to build high quality products.
    You optimize things first that do not matter for customer.
    You change organizational schema before architecture.
    You cannot experiment, fail, learn, repeat.
    You do a piece of your product, totally blind for others.
    You have a formula for success.
    You don't know what your teammates are doing.
    You do nothing but complaining.
    

    View Slide

17. @craftbaseio
    craftbase.io
    LEMi ORHAN ERGiN
    @lemiorhan
    

    View Slide