OrgPatterns

was Jim Coplien's wiki-then-book (WikiEbook?): Pattern Language for Software Development Organization Design

http://web.archive.org/web/20061012032103/http://www.easycomp.org/cgi-bin/OrgPatterns

in print as Organizational Patterns of Agile Software Development ISBN:0131467409
There are two equally valid views of this book: as a guide to organizational improvement, and as a record of the "best typical" Software Development structures of the fourth social paradigm of software development
- The first style of software development goes back to the first computers that were programmed manually with console switches. The second style came with the advent of programming languages that allowed scientists to work individually or in small teams, interacting with the machine through a language. In the third style, what we learned from hardware design and manufacturing carried over into software. Formal processes drove development, management was visible and explicit, and both the system and the organizations that worked on the system were highly hierarchical. Now we are in the fourth style: one that breaks down hierarchy, that features dynamic social structures and communication paths, and that values immediacy. This fourth style often bears the label "agile," but that is just one of many characterizations of a broad new way of developing software that has emerged over the past decade.

http://web.archive.org/web/20180107214309/http://orgpatterns.wikispaces.com/

Top10 patterns https://sites.google.com/a/gertrudandcope.com/info/Publications/Patterns/TopTenPatterns

Book table of contents

PART I History and Introduction

An Overview of Patterns and Organizational Patterns
- What Are Patterns?
  - Team Per Task**
- What Are Pattern Languages?
- Organizational Pattern Languages
  - The Structure of Social Systems
  - The Multiple Structures of Social Systems
  - Pattern Languages and Sequences
How the Patterns Came to Us
- Gathering Organizational Data
  - Introspection in and Analysis of Organizations
  - Shortcomings of State of the Art
  - The CRC Card Methodology
  - Analyzing Roles and Relationships
- Creating Sequences
  - Why Sequences Are Important
  - Our Sequences
- History and Related Work
How to Use This Book
- Reading the Patterns
  - The Form
  - Understanding the Models Behind the Patterns
  - Stories and Pictures in the Patterns
  - Finding Your Way
- Applying the Patterns
  - Sequences
  - Which Patterns?
  - Human Concerns
- Updating the Patterns
- Who Should Use This Book?

PART II The Pattern Languages

Organization Design Patterns
- Project Management Pattern Language
  - Community of Trust **
  - Size the Schedule **
  - Get On with It **
  - Named Stable Bases *
  - Incremental Integration **
  - Private World **
  - Build Prototypes **
  - Surrogate Customer
  - Take No Small Slips **
  - Completion Headroom **
  - Work Split *
  - Recommitment Meeting *
  - Work Queue *
  - Informal Labor Plan **
  - Development Episode *
  - Implied Requirements
  - Developer Controls Process **
  - Work Flows Inward **
  - Programming Episodes **
  - Someone Always Makes Progress*
  - Team Per Task **
  - Sacrifice One Person *
  - Day Care *
  - Mercenary Analyst *
  - Interrupts Unjam Blocking **
  - Don't Interrupt an Interrupt *
- Piecemeal Growth Pattern Language
  - Community of Trust
  - Size the Organization **
  - Phasing It In **
  - Apprenticeship *
  - Solo Virtuoso *
  - Engage Customers **
  - Surrogate Customer *
  - Scenarios Define Problem *
  - Firewalls **
  - Gatekeeper **
  - Self-Selecting Team **
  - Unity of Purpose **
  - Team Pride **
  - Skunk Works *
  - Patron Role **
  - Diverse Groups *
  - Public Character **
  - Matron Role *
  - Holistic Diversity *
  - Legend Role *
  - Wise Fool *
  - Domain Expertise in Roles **
  - Subsystem by Skill *
  - Moderate Truck Number
  - Compensate Success **
  - Failed Project Wake *
  - Don't Interrupt an Interrupt
  - Developing in Pairs **
  - Engage Quality Assurance **
  - Application Design Is Bounded by Test Design *
  - Mercenary Analyst
  - Group Validation *
Organization Construction Patterns
- Organizational Style Pattern Language
  - Community of Trust
  - Few Roles **
  - Producer Roles *
  - Producers in the Middle **
  - Stable Roles *
  - Divide and Conquer **
  - Conway's Law **
  - Organization Follows Location **
  - Organization Follows Market *
  - Face to Face Before Working Remotely **
  - Form Follows Function
  - Shaping Circulation Realms *
  - Distribute Work Evenly *
  - Responsibilities Engage
  - Hallway Chatter *
  - Decouple Stages
  - Hub, Spoke, and Rim
  - Move Responsibilities *
  - Upside-Down Matrix Management *
  - The Watercooler *
  - Three to Seven Helpers Per Role
  - Coupling Decreases Latency *
  - Standards Linking Locations
- People and Code Pattern Language
  - Community of Trust
  - Conway's Law
  - Architect Controls Product **
  - Architecture Team *
  - Lock'em Up Together *
  - Smoke-Filled Room
  - Stand-Up Meeting **
  - Deploy along the Grain **
  - Subsystem by Skill
  - Architect Also Implements **
  - Generics and Specifics
  - Standards Linking Locations **
  - Code Ownership **
  - Feature Assignment *
  - Variation Behind Interface **
  - Private Versioning **
  - Loose Interfaces **
  - Subclass Per Team
  - Hierarchy of Factories
  - Parser Builder *
  - Incremental Integration
  - Private World
  - Named Stable Bases

PART III Foundations and History

Organizational Principles
- Priming the Organization for Change
  - Dissonance Precedes Resolution
  - Team Burnout
  - Stability and Crisis Management
  - The Open/Closed Principle Of Teams
  - Team Building
  - Building on the Solid Core
- Piecemeal Growth
  - The Fundamental Process
  - When Do I Apply These Patterns?
  - Writing Your Own Patterns
  - Master Planning and the Theory of Constraints
  - Communication and Organizational Learning
- Some General Rules
  - Make Love, Not War
  - Organizational Patterns Are Inspiration Rather than Prescription ....
  - It Depends on Your Role in Your Organization
  - It Depends on the Context of the Organization
  - Organizational Patterns Are Used by GroupsRather Than by Individuals
  - People Are Less Predictable Than Code
  - The Role of Management
Anthropological Foundations
- Patterns In Anthropology
- Beyond Process to Structure and Values
  - The Shortcomings of Process
  - Structure
  - Values: The Human Element
- Roles and Communication
- Social Network Analysis
- Distilling the Patterns
  - CRC Cards and Roles
  - Social Network Theory Foundations
  - Scatterplots and Patterns

PART IV Case Studies

Borland Quattro Pro for Windows
- Introduction to the QPWCase Study
- Origins and Description of QPW
- Analysis of QPWData
- Personal Excellence and Integrity
- Do One Thing and Do It Well
- A Piecemeal Architecture Process
- Personality and Development
- No Wine Before Its Time
- Create Rather Than Conform
- California Gold Rush?
- Introspection by the Team
- Process and Quality
- Concluding Thoughts about QPW
A Hyperproductive Telecommunications Development Team
- The Culture
- The Development Process
- The Pasteur Analysis of the Process
- The Human Side
  - Engineering People Issues into the Process
  - Code Ownership and Programming Anthropomorphism
  - Growing a Garden
  - Rewarding Excellence
- The Small Team Spirit
- Process Improvement Opportunities
- Thoughts and Conclusions

Appendix A: Summary Patlets

Edited: 2022-07-18 14:55:59.484536 | Tweet this! | Search Twitter for discussion

Bill Seitz