Agile Glossary

Open Space

What is Open Space?

When you bring together a group of folks, empower them to co-create their own learning, provide just enough structure to ensure progress, and hit the Start button – that’s Open Space, a style of self-organized “un-conference.” Open Space is the perfect match for Agile values.

In Open Space meetings, events, or conferences, participants create and manage their own agenda of parallel sessions around a specific theme. Open Space is a straightforward way to create participant-driven events to address a specific question or theme. After being introduced to the principles and practices of open space, participants are invited to build the event schedule, just-in-time. Individuals propose sessions they’d like to lead or sessions they’d like to see someone else step up and lead. Quickly, almost if by magic, a schedule emerges, composed of sessions around topics people feel passionate about pursuing.

Open Space is a process that allows everyone to participate in sessions with others whom they may not normally have a chance to talk with. Like Agile itself, Open Space Technology sessions operate under a small set of guiding principles. These principles are deceptively simple, yet provide just enough structure for spontaneous discussions:

  • Whoever comes are the right people.
  • Whatever happens, is the only thing that could have.
  • Whenever it starts is the right time.
  • Whenever it’s over, it’s over.
  • Wherever it happens is the right place.

Additionally, there is one law—The Law of Personal Mobility: If you find yourself where you can’t learn or contribute, move yourself to a place where you can.


Also Known As

Most people simply call it Open Space. However, if you want to search for more information on the Internet, you might want to Google “Open Space Technology,” the name given to it by its inventor, Harrison Owen.


Origins

In 1983, Harrison Owen observed during a conference he had organized that most of the meaningful conversations and active learning seemed to take place outside of the formal presentations. After giving that some thought, Owen went on to originate Open Space Technology, an approach to organizing meetings that allows groups of all sizes to self-organize, create their own agenda, and collectively work together to solve complex problems. Since then, groups of 5 to 2000 members across a host of disciplines have used Open Space meetings to address complex and varied themes.

Agile Open Space conferences have been held for over 10 years. The earliest Agile Open Space was a two-day event jointly organized by Belgium and Dutch Agilists held in 2005 in Belgium. Today Agile Open Space conferences are held around the world.


Further Reading

Open Space World

Open Space Technology: A User’s Guide Third Edition

The Agile Alliance has an Agile Open Initiative to encourage and support Open Space Technology events around the topic of Agile Software Development.

Thank you to our Annual Partners​

Join us today!

Agile Alliance offers many online and in-person events and workshops for our members. If you’re not currently a member, you can join now to take advantage of our many members-only resources and programs.

Get the latest Agile news!

  • This field is for validation purposes and should be left unchanged.

By subscribing, you acknowledge the Agile Alliance Privacy Policy, and agree to receive our emails.

Additional Agile Glossary Terms

The Kanban Method is a means to design, manage, and improve flow systems for knowledge work. The method also allows organizations to start with their existing workflow and drive evolutionary change. They can do this by visualizing their flow of work, limit work in progress (WIP) and stop starting and start finishing.
An iteration is a timebox during which development takes place. The duration may vary from project to project and is usually fixed.
Continuous deployment aims to reduce the time elapsed between writing a line of code and making that code available to users in production. To achieve continuous deployment, the team relies on infrastructure that automates and instruments the various steps leading up to deployment, so that after each integration successfully meeting these release criteria, the live application is updated with new code.
Acceptance Test Driven Development (ATDD) involves team members with different perspectives (customer, development, testing) collaborating to write acceptance tests in advance of implementing the corresponding functionality.
A basic task board is divided into three columns labeled "To Do," "In Progress," and "Done." Cards are placed in the columns reflecting the current status.
In the context of software development, build refers to the process that converts files and other assets under the developers' responsibility into a software product in its final or consumable form. The build is automated when these steps are repeatable, require no direct human intervention, and can be performed at any time with no information other than what is stored in the source code control repository.
Mock Objects (commonly used in the context of crafting automated unit tests) consist of instantiating a test-specific version of a software component.

Help us keep the definitions updated

Ready to join Agile Alliance?

Unlock members-only access to online learning sessions, Agile resources, annual conference discounts, and more! And when you join, you’ll be supporting our member initiatives, regional events, and global community groups.

Privacy Preference Center

IMPORTANT: We have transitioned to a new membership platform. If you have not already done so, you will need to SET UP AN ACCOUNT on the new platform to establish your user profile. Your previous login credentials will not work until you do this set up.

When you see the login screen, choose “Set up Account” and follow the prompts to create your new account. You can choose to log in using your social credentials for either Google or Linkedin (recommended), or you can set up your account using an email address.