0%

Book Description

Get a unique collection of radically collaborative patterns for building software with others. In this mini-encyclopedia, third-generation programmer Matthew Parker introduces you to 27 successful patterns used in organizations that follow distinctive methodologies such as Scrum, Extreme Programming, SAFe (Scaled Agile Framework), and others.

Each short essay in this report describes why a particular pattern is useful and helps you understand just how radical each one really is. Because the patterns in this guide are differentiated but integrated, none of them can be described without referring to others. Rather than read this book from cover to cover, choose patterns that stand out for you and move around the chapters from there.

You’ll explore:

  • High-level patterns: Autonomy of Space, Collocation, Communal Breakfast, Free Snacks, Outsider-In, Play Space, and Workspace Standup
  • Team-wide patterns: Balanced Team, Collaborative Story Acceptance, Discovery and Framing, Facilitation, Information Radiator, Team Standup, User Stories, Velocity, and more
  • Patterns specific to specialized roles: Continuous Integration/Continuous, Deployment, Pair Programming, Promiscuous Pairing, Test-Driven Development, and more

Table of Contents

  1. Radically Collaborative Patterns for Software Makers
    1. Introduction
    2. Autonomy of Space
    3. Balanced Teams
    4. Collaborative Story Acceptance
    5. Collocation
    6. Communal Breakfast
    7. Continuous Integration/Continuous Deployment
    8. Discovery and Framing
    9. Facilitation
      1. Point A to Point B
      2. Connecting with One Another as Human Beings
      3. From Many, to One
      4. No Laptops, No Phones
      5. Silent Generation
      6. Self-Edit
      7. Working at the Wall
      8. Affinity Groups
      9. Materials and Space
      10. Introducing Facilitation into Your Organization
    10. Free Snacks
    11. Information Radiator
    12. Iteration Planning Meeting
    13. Outsider-In
    14. Pair Programming
    15. Play Space
    16. Promiscuous Pairing
    17. Relative Complexity Estimates
    18. Rotation
    19. Retrospective
    20. Team Standup
    21. Test-Driven Development
      1. Fast
      2. Clean
      3. Confidence
      4. Freedom
      5. The Great Balancing Act
    22. Top of Backlog
    23. User-Driven Architectures
      1. Architecture, Generally
      2. Software Architecture, Specifically
      3. But Why Is Software Architecture “Architecture”?
      4. When Do RC Engineers “Architect”?
      5. How Do RC Engineers “Architect” Before Development?
      6. How Do RC Engineers “Architect” During Development?
    24. User Stories
    25. Value-Stream Map
    26. Velocity
    27. Volatility
    28. Workspace Standup
    29. Conclusion
18.118.184.237