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

Anarchy in The IT

Anarchy in The IT

How Proudhon's Anarchy ideas were successfully proven by the agile software development methods and how organizations and the society can learn from that.

439e623c5d770ae0da8e61ec08452032?s=128

Vinicius Gomes

May 21, 2012
Tweet

Transcript

  1. Anarchy  in  The  IT   Vinicius  Gomes  

  2. Anarchy  !=  chaos  

  3. None
  4. None
  5. None
  6. Basic   assump7on:  

  7. None
  8. Anarchy  

  9. None
  10. Absence  of:  

  11. None
  12. Compulsory   government  

  13. Coercive  authority  

  14. The  assump7on   now  is:  

  15. None
  16. Individuals  

  17. Self-­‐organizing   groups  

  18. Coopera7ves  

  19. Mutualism  

  20. Voluntary   associa7ons  

  21. No  private   proper7es  

  22. OK.  

  23. It  was  never   effec7vely   proven…  

  24. …  before  these  guys  

  25. Agile  =  Anarchy  

  26. Individuals  

  27. Individuals   Trust   Mul7-­‐func7onal   Learning  

  28. Self-­‐organizing   groups  

  29. Self-­‐organizing   groups   Self-­‐managed   Adap7ve   Ra7onal  

  30. Coopera7ves  

  31. Coopera7ves   Problem-­‐focused   Small  scale   Partnership  

  32. Mutualism  

  33. Mutualism   Pair   Knowledge  Transfer   Sustainable  Pace  

    Learning   Business  involvement  
  34. Voluntary   associa7ons  

  35. Voluntary   associa7ons   Freedom   Honesty   Nego7ated  Scope

     Contracts  
  36. No  private   proper7es  

  37. No  private   proper7es   Collec7ve  Ownership   No  specialists

      Sustainable  profit  sharing  
  38. None
  39. What  about  the   society?  

  40. Barriers:  

  41. industry  by   industry  

  42. Ambi7on  

  43. The  Enterprise  

  44. Future?  

  45. Programmer   Anarchy   by  Fred  George  

  46. Anarchy  in  The  IT   Vinicius  Gomes