Atlas Patterns
  • Welcome to Atlas Patterns! 🤓
  • What's a Pattern?
  • A Bit of Background
  • Patterns
    • Organic Growth
    • Maturity Analysis
    • Championing
    • Embracing Change
    • Empathic Governance
    • Tool Performance
    • Scaling Excellence
    • Air & Ground War
    • Scaling What You Don't Have
    • Provide Context
    • Co-Create
    • Change Takes Time
  • Antipatterns
    • Supporting a Single Methodology
    • Processes Over Tools
    • Tools Over Processes
    • Processes Over Tools
    • Resisting Change
    • Just an Air War
    • Poor Tool Performance
    • Separate Digital Identities
    • Unbounded Politics
    • Ignoring Anonymity
    • Quick! Make Haste
    • Dictate
    • Governance?
  • Personas
    • Agile Coach
    • Developer
    • Tester
    • Middle Manager
    • C-Suite Executive (CxO)
    • Business Analyst (BA)
    • Conservative Project Manager (PM)
    • Scrum Master (SM)
Powered by GitBook
On this page

Was this helpful?

What's a Pattern?

PreviousWelcome to Atlas Patterns! 🤓NextA Bit of Background

Last updated 6 years ago

Was this helpful?

We use the term Pattern to refer to design patterns, which are general, reusable solutions to commonly occurring problems within given contexts.

One can think of them as formalized best (and worst) practices that can be used to solve (or cause) common problems within the domain they describe.

The patterns that are described on Atlas Patterns relate to the domain of digital collaboration tools, and often mentioning Jira and Confluence because they're the tools we at Atlancers work with the most.

Source: The above description is somewhat paraphrased from .

https://en.wikipedia.org/wiki/Software_design_pattern