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

How microteams change the way we collaborate. Again.

How microteams change the way we collaborate. Again.

Introducing the next evolution in autonomous collaboration.

Over the years the way projects and teams operate in software development has changed quite a bit. From projects were teams were sliced vertically per discipline, to multi-disciplinary and cross-functional teams in agile approaches and frameworks. Now, as a consequence of increasing velocity, DevOps, DevSecOps and continuous delivery, we are on the move again. In Sander's vision, teams that will be even smaller than in agile, and much more fluent.

Sander has been experimenting with collaboration in teams for years and reasons about this next evolution of collaboration as areas, collectives, and microteams. This talk illustrates how organizations and teams doing software and product development can transition to focus on delivering value using the ever-evolving and self-organizing power of microteams and how to get there using a combination of models, such as Cynefin, the Golden Circle, innovation funnels and backlogs, autonomy, and fewer rules.

Sander Hoogendoorn

May 22, 2019
Tweet

More Decks by Sander Hoogendoorn

Other Decks in Programming

Transcript

  1. How microteams change the way we collaborate. Again. Introducing the

    next evolution of autonomous collaboration Sander Hoogendoorn Founder at ditisagile.nl Chief architect at Quby @aahoogendoorn @aahoogendoorn | How microteams change the way we collaborate. Again.
  2. Sander Hoogendoorn Freelance new-agile coach, trainer, programmer, speaker, author, traveler,

    dad Currently Chief Architect Quby Before CTO ANVA CTO Klaverblad Verzekeringen Global agile thoughtleader Capgemini sanderhoogendoorn.com aahoogendoorn aahoogendoorn [email protected] Next @aahoogendoorn | How microteams change the way we collaborate. Again.
  3. A short history of thinkers and workers @aahoogendoorn | How

    microteams change the way we collaborate. Again. Submit
  4. Click here Craftsmanship Organizing work in earlier days @aahoogendoorn |

    How microteams change the way we collaborate. Again.
  5. Click here Industrialization changed everything Even the way we do

    our work today @aahoogendoorn | How microteams change the way we collaborate. Again.
  6. Click here What we are all looking for, however, is

    the readymade, competent man; the man whom some one else has trained. It is only when we fully realize that our duty, as well as our opportunity, lies in systematically cooperating to train and to make this competent man, instead of in hunting for a man whom some one else has trained, that we shall be on the road to national efficiency. Frederick Taylor @aahoogendoorn | How microteams change the way we collaborate. Again. Scientific management
  7. Click here Thinkers and workers Efficiency through standardization and simplification

    @aahoogendoorn | How microteams change the way we collaborate. Again.
  8. Click here The carrot and the stick A fair day's

    pay for a fair day's work @aahoogendoorn | How microteams change the way we collaborate. Again.
  9. Click here Why is it every time I ask for

    a pair of hands, they come with a brain attached? Henry Ford @aahoogendoorn | How microteams change the way we collaborate. Again. Give me monkeys, please
  10. Click here “Building” software Using the wrong metaphors @aahoogendoorn |

    How microteams change the way we collaborate. Again.
  11. Read more … Software development as an assembly line We

    build software Centralized decision making Detailed linear processes Thinkers versus doers Micro-management of individual tasks Little creativity
  12. Click here Linear software development So far, the project has

    cost 220M Euro, which is an overrun of over 200M Euro, compared to the original 7M Euro project.
  13. The Times They Are a-Changin' Much faster than you think

    @aahoogendoorn | How microteams change the way we collaborate. Again. Continue
  14. Read more … Moore’s Law The number of transistors in

    a dense integrated circuit doubles approximately every two years.
  15. 1981 The IBM Personal Computer 5150 The simplest configuration has

    16K on-board RAM and uses an audio cassette to load and save data. A floppy drive is optional. A hard drive was not supported. A system for home or school with a memory of 64K bytes, a single diskette drive and its own display, was priced around $3,000. @aahoogendoorn | How microteams change the way we collaborate. Again.
  16. 2006 Amazon EC2 Amazon launched its Elastic Compute cloud (EC2)

    as a commercial web service that allows small companies and individuals to rent computers on which to run their own computer applications. @aahoogendoorn | How microteams change the way we collaborate. Again.
  17. More … Fintech challenges @aahoogendoorn | How microteams change the

    way we collaborate. Again. Apple announces Apple Card credit card
  18. We live in a world where anyone can enter any

    market, from anywhere at any time @aahoogendoorn | How microteams change the way we collaborate. Again. Continue
  19. Click here Welcome to the world of small moveable parts

    @aahoogendoorn | How microteams change the way we collaborate. Again.
  20. Click here Even shorter cycles Continuous flow Small services Features

    over projects Even smaller teams Self-organizing and autonomous Even smaller components Microservices and serverless @aahoogendoorn | How microteams change the way we collaborate. Again.
  21. Click here Even shorter cycles Continuous flow Small services Features

    over projects Even smaller teams Self-organizing and autonomous Even smaller components Microservices and serverless @aahoogendoorn | How microteams change the way we collaborate. Again.
  22. Click here “We are operating in a new and fast

    moving market. Nobody has invented a profitable business model for this market yet.” Arnoud Snijder Quby Where are we? @aahoogendoorn | How microteams change the way we collaborate. Again.
  23. Click here “In a chaotic context, searching for right answers

    would be pointless: the relationships between cause and effect are impossible to determine because they shift constantly and no manageable patterns exist — only turbulence. This is the realm of unknowables.” Dave Snowden Chaotic contexts “The chaotic domain is nearly always the best place for leaders to impel innovation.” @aahoogendoorn | How microteams change the way we collaborate. Again.
  24. Favor delivering small and continuously over executing projects @aahoogendoorn |

    How microteams change the way we collaborate. Again. Continue
  25. Small monetizable services Account API Product API Check Waste Schedule

    API Org API Account API 2.0 Asset API Contract API Weather API Product API 2.0 Waste API Product API 3.0 Notify Leakage Notify Schedule Reset Account Hue API Q1 Q2 Q3
  26. Click here Even shorter cycles Continuous flow Small services Features

    over projects Even smaller teams Self-organizing and autonomous Even smaller components Microservices and serverless @aahoogendoorn | How microteams change the way we collaborate. Again.
  27. Click here Even shorter cycles Continuous flow Small services Features

    over projects Even smaller teams Self-organizing and autonomous Even smaller components Microservices and serverless @aahoogendoorn | How microteams change the way we collaborate. Again.
  28. Even shorter cycles Agile beyond Scrum ceremonies @aahoogendoorn | How

    microteams change the way we collaborate. Again. Continue
  29. Click here The agile manifesto To satisfy the customer through

    early and continuous delivery of valuable software
  30. Click here The agile manifesto To satisfy the customer through

    early and continuous delivery of valuable software
  31. Stop sprinting But rather simplify, standardize, automate @aahoogendoorn | How

    microteams change the way we collaborate. Again. Next
  32. Click here Even shorter cycles Continuous flow Small services Features

    over projects Even smaller teams Self-organizing and autonomous Even smaller components Microservices and serverless @aahoogendoorn | How microteams change the way we collaborate. Again.
  33. Click here Even shorter cycles Continuous flow Small services Features

    over projects Even smaller teams Self-organizing and autonomous Even smaller components Microservices and serverless @aahoogendoorn | How microteams change the way we collaborate. Again.
  34. Click here Autonomy and self-organization Issue 0 @aahoogendoorn | How

    microteams change the way we collaborate. Again.
  35. Click here Working 9-to-5 ? Issue 1 What a way

    to make a livin’ @aahoogendoorn | How microteams change the way we collaborate. Again.
  36. Click here The programmers mind Issue 2 @aahoogendoorn | How

    microteams change the way we collaborate. Again.
  37. Click here Low availability of “resources” Issue 3 @aahoogendoorn |

    How microteams change the way we collaborate. Again.
  38. Read more … Gig workers T-shaped There when wanted Remote

    when needed Gets the work done Personal productivity Often freelance Recharge on their own conditions Continuously learn and mature Technology enabled Feel free to experiment Collaborative at heart
  39. Click here Communication is hard Issue 4 @aahoogendoorn | How

    microteams change the way we collaborate. Again.
  40. Click here Too many meetings, too many rituals Sprint planning

    Refinements Daily stand-ups Management meetings Demo’s Retrospectives Skype calls Guild meetings Backlog grooming T-shirt sizing Planning poker Open floor plans
  41. We don’t need more collaboration, we need better collaboration @aahoogendoorn

    | How microteams change the way we collaborate. Again.
  42. Click here We suck at estimation Issue 5 @aahoogendoorn |

    How microteams change the way we collaborate. Again.
  43. Click here Software development is too complex for Scrum teams

    Issue 7 @aahoogendoorn | How microteams change the way we collaborate. Again.
  44. Click here The programmer has to be able to think

    in terms of conceptual hierarchies that are much deeper than a single mind ever needed to face before. Edsger Dijkstra @aahoogendoorn | How microteams change the way we collaborate. Again.
  45. Click here No two work items require the same skillset

    Architect Domain expert Back-end QA Architect Front-end
  46. Click here The framework doesn’t work Issue 8 @aahoogendoorn |

    How microteams change the way we collaborate. Again.
  47. Click here Find your own way! Don’t just copy someone

    else’s model @aahoogendoorn | How microteams change the way we collaborate. Again.
  48. Optimize for speed, agility and adaptability The innovation board and

    the funnel @aahoogendoorn | How microteams change the way we collaborate. Again. Continue
  49. Click here The dot at the horizon? “We aim to

    become the most sought-after consultancy in Europe”
  50. Click here Why do you exist? What do you want

    to be? How are you going to get there? What is it you will do / produce to get there? Simon Sinek The Golden Circle Who do you do it for? Who are your customers? @aahoogendoorn | How microteams change the way we collaborate. Again.
  51. Portfolio meetings Waste Energy Water Is it actionable? Is it

    too big? Does it help us reach our goal? Do we need this now? Someyday maybe?
  52. More … The innovation board and the funnel @aahoogendoorn |

    How microteams change the way we collaborate. Again.
  53. Introducing collectives and microteams Towards smaller, shorter, faster @aahoogendoorn |

    How microteams change the way we collaborate. Again. More …
  54. Read more … The microteam recipe 1. Pick 2. Form

    3. Discuss 4. Work 5. Report as done 6. Disband 7. Repeat
  55. Read more … What about leadership? Leaders are not necessarily

    managers Managers are not necessarily leaders Take steps to give up control Think in flow, not in continuity Leadership is contextual Trust your people Trust the group
  56. Read more … Why microteams? Leadership is contextual Less but

    better communication Broaden your skills fast Stop sprinting Fewer estimates Stop refinements Work where and when you want
  57. Click here Even shorter cycles Continuous flow Small services Features

    over projects Even smaller teams Self-organizing and autonomous Even smaller components Microservices and serverless @aahoogendoorn | How microteams change the way we collaborate. Again.
  58. Click here In retrospective Some final thoughts @aahoogendoorn | How

    microteams change the way we collaborate. Again.
  59. Find your own way! Don’t just copy someone else’s model

    @aahoogendoorn | How microteams change the way we collaborate. Again.
  60. It only takes one person to start a change @aahoogendoorn

    | How microteams change the way we collaborate. Again.
  61. And never forget to have fun @aahoogendoorn | How microteams

    change the way we collaborate. Again. Next
  62. Click here References and questions www.sanderhoogendoorn.com aahoogendoorn aahoogendoorn [email protected] quby.com/careers

    We are hiring! sanderhoogendoorn.com/decks-and-handouts @aahoogendoorn | How microteams change the way we collaborate. Again.