July flash sale
A Community of Practice is not another reporting meeting
A Community of Practice brings people who share a domain or professional concern together to learn, solve problems, and improve practice. Communities help knowledge move across team and ART boundaries without creating a centralized approval function. Participation should be intrinsically useful and sufficiently voluntary that the community earns attention through value.
Establish domain, community, and practice
| Element | Working question |
|---|---|
| Domain | What shared capability or problem gives the group identity? |
| Community | How will members build relationships and learn together? |
| Practice | Which methods, stories, tools, patterns, and assets will improve? |
| Connection | How will learning reach teams, ARTs, roles, and leaders? |
| Support | Which time, platform, facilitation, and sponsorship are needed? |
Design participation beyond presentations
- Case clinics on current problems.
- Peer review of techniques and artifacts.
- Practice labs, simulations, and pairing.
- Experience reports including failed approaches.
- Working groups producing optional reusable assets.
- External learning translated into local context.
Keep standards separate from community learning
A community may recommend patterns and contribute to standards, but mandatory governance requires clear authority and accountability outside voluntary participation. If members fear that questions expose noncompliance, learning contracts. Mark assets as experiments, recommendations, or required policies so teams understand the distinction.
Health signals without vanity metrics
- Members return and contribute across organizational boundaries.
- Questions receive useful peer response.
- Shared practices change based on evidence.
- Teams adopt assets voluntarily and report benefit.
- New practitioners gain confidence and relationships.
- The community stops activities that no longer help.
Leadership support that does not take over
Protect time, recognize contribution, remove access barriers, and listen to systemic insights. Do not set the entire agenda, demand attendance, or use the community as unpaid change delivery. A sponsor can connect issues to authority while facilitators and members retain ownership of learning.
SAFe Advanced Scrum Master training supports cross-team facilitation and improvement. ICP-ACC Agile Coaching certification training develops community-building, facilitation, and learning skills.
Review purpose and participation each PI or quarter. A small community solving real problems can be healthier than a large channel counting attendance without changing practice.
Worked example: test automation community
Engineers from four ARTs form a community around unreliable integration tests. They compare failure data, run a contract-testing lab, and publish an optional diagnostic pattern. Two ARTs adopt it and reduce false failures; another finds its main constraint is environment contention and does not adopt. The community records both results, connects the environment issue to platform leadership, and revises the pattern instead of enforcing one answer.
Community roles without hierarchy
| Role | Contribution |
|---|---|
| Sponsor | Protects time and connects systemic issues to authority |
| Facilitator | Supports participation, cadence, and healthy dialogue |
| Core members | Maintain continuity and shared assets |
| Participants | Bring problems, experiments, and experience |
| External experts | Introduce perspective without owning local decisions |
Plan for renewal. Rotate facilitation, invite new practitioners, archive stale assets, and periodically ask whether the domain still warrants a community. Closing or merging a community whose purpose has faded is healthy stewardship, not failure.
