Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Hyper Agylity - way of working based on hackathons

Hyper Agylity - way of working based on hackathons

Telefonica Developer Conference 2016. This presentation shows how hackathons can be applied to software projects to exhibit Agility.
From Agile methods today to the root of what developing software should be about : programming.

Ruben Gonzalez Blanco

June 07, 2016

More Decks by Ruben Gonzalez Blanco

Other Decks in Programming


  1. Dealing with SoEware - Evolu7on SoEware Crisis So6ware Engineering No

    Silver Bullet Agile Manifesto Cra6smanship Manifesto CraEing Incremental 1960 1970 1980 1950 1990 2000 2010 Waterfall Itera7ve Rapid Prototyping CMM Evolu7onary Agility?
  2. Trough of Disillusionment with “Agile” AGILE is DEAD DARK SIDE

    OF AGILE hGp://programming-motherXYZ.com/ Dave Thomas hZps://pragdave.me/blog/2014/03/04/7me-to-kill-agile/ PROGRAMMING MOTHER FXYZ
  3. The problem we have (I think): NOT A MATCH create

    systema7c approaches = “Procedures” and “Methodologies” for developing soEware
  4. ProvocaTon : If you do not PROGRAM then your role

    is not Fundamental when it comes to create products and services based on soEware Probably your role is important, but not fundamental Managers UX Designer Analysts Solu7on Architects Business Developers …
  5. FACTS A team made of Managers, Analysts, UX Designers, Solu7on

    Architects… etc can define a Product based on soEware, but they can not deliver it … EXCEL PPT VIDEO UI SKETCH PAPERWARE
  6. FACTS A team made of So6ware Programmers only, can define

    and deliver a Product based on SoEware Google Facebook TwiZer SOFTWARE Florian Weber Jack Dorsey tw#r facemash Mark Zuckerberg googol Sergey Brin Larry Page
  7. HW calcula7on power is higher than Humans Picture: from Hans

    Moravec 1997, When will computer hardware match the human brain? hZp://www.transhumanist.com/volume1/moravec.htm
  8. Perhaps Programming SoEware in a Team is like Jazz Original

    Dixieland Jass Band Melodies are improvised/created on top of a shared Harmony created by a composer (so?ware architect) Everybody is a Composer The Harmony (architecture) provides consistency
  9. INSIGHT 5 SoEware Programming is full of Complexity Inherent complexity

    RelaTve to the Problem/Hardware Accidental complexity created by Humans
  10. Provoca7on: You, Programmer, can easily be an Accidental Complexity generator

    Libraries, Frameworks, Technologies, Paradigms, Style, Tools, …
  11. INSIGHT 6 Both the Problem and its SoluTon have to

    be figured out at the same 7me!! Both Problem definiTon and one of its SoluTon EMERGE in parallel
  12. INSIGHT 8 A SoEware Program is a form of Knowledge

    Reflects the prac7cal understanding of Problem and one of its Solu7ons
  13. INSIGHTS SUMMARY 1.  SoEware development is about Programming !!!! 2. 

    SoEware program execu7on is uncertain 3.  SoEware programming is a creaTve ac7vity 4.  SoEware has structure and dynamic (runTme) dimensions 5.  SoEware development is full of complexity 6.  Both the problem and a soluTon have to be figured out in parallel 7.  Requirements, Plans, Designs must be treated as IntenTonal 8.  SoEware code is a Form of Knowledge (code is an asset) 9.  SoEware development requires high skilled, high knowledge, crea7ve and passionate PROGRAMMERS
  14. hZp://www.wired.com/2012/02/ff_hackathons/all/1 A hackathon (also known as a hack day, hackfest

    or codefest) is an event in which computer programmers and others involved in soEware development and hardware development, including graphic designers, interface designers and project managers, collaborate intensively on so6ware projects
  15. From Sprint Planning to Sprint Hackaning No Sprint “Planning” ,

    instead start with a Hackathon (2-3days) that delivers a MVP (working soEware) Sprint Hackaning Sprint Planning
  16. The Sprint Hackaning delivers a real MVP (working soEware) that

    is grown and hardened over the next days and weeks M T W T F Hackathon M T W T F ISRF Cycles RELEASE 0 MVP S S Growing and/or Hardening(features, architecture, design, quality) Hackaning
  17. From Planned Sprints to MicroSprints (Weekly) (make soEware emerge) M

    T W T F S S M T W T F S S M T W T F S S …. …. M T W T F S S M T W T F S S MSP-N Week1=MSP1 MSP2 MSP3 MVP Hackathon Weekly Review Weekly Review Weekly Review RELEASE M T W T F S S Delivery Hackathon MSPN-1 MVP RFS MVP Hackathon MVP •  Release docs •  Checkout, Install, Run •  Opera7on procedures •  Set Context •  Targets & Priori7es •  Issues & Risks This is an Example!!!
  18. Hacking + Growing AND/OR Hardening M T W T F

    S S M T W T F S S M T W T F S S …. …. M T W T F S S M T W T F S S MSP-N Week1=MSP1 MSP2 MSP3 MVP Hackathon Weekly Review Weekly Review Weekly Review RELEASE M T W T F S S Delivery Hackathon MSPN-1 MVP RFS MVP Hackathon MVP Growing Hardening Growing and Hardening Hacking This is an Example!!!
  19. Type of Hackathons (Sample) •  MVP Hackathon •  Integra7on Hackathon

    •  DevOps Hackathon •  Architecture Hackathon •  … Uncertainty? Hackathon!!!
  20. From Control Roles to Suppor7ng Roles From Product Owner to

    Customer/User Proxy From Program Manager (Control) to Program Facilitator From Architect to others programmers Enabler
  21. Making the soEware Emerge in an “environment” not aware of

    SoEware ISOLATION/TRANSLATION LAYER ROADMAP LAYER (PROGRAMMING CENTERED) Business Stakeholders Customers ENABLING LAYER Tech Architects Release Management Opera7ons Program Management Business Development Product Management Tools Solu7on Architects