Stable

Description of this level: the team has developed a comfortable rhythm so that the basic practices of OpenAgile are done consistently and without effort or anxiety.

Ten Cycles completed (at least)
The team needs at least ten Cycles to prove that it is stable. Stability indicates that the team has put in place and maintained all the rules from the Formed and Launched levels, as well as built capacity to understand the process, apply it with discipline, and use the process to grow.

Key performance metric for Goal is defined and measured
The team implements one metric that will give them a clear way of seeing their progress towards their Goal. This metric may combine a number of measurements (e.g. ROI is a metric that includes measures of both costs and returns). This performance metric should be updated at least once every Cycle.

All Team members are at the “Team Member” level
Team members have read the Team Member manual, attended a Team Member training, scored 100% on the OpenAgile Team Member test, confirmed their references, received mentoring, and agreed to the OpenAgile code of ethics (all details available online at http://www.openagile.com).

One Team member is at the “Process Facilitation” level
Process Facilitation requires strong knowledge and understanding of OpenAgile as well as excellent facilitation skills. Building these capacities requires reading, training and mentoring, similar to the Team Member level (details available online at http://www.openagile.com).

One Team member is at the “Growth Facilitation” level
Growth Facilitation requires strong knowledge and understanding of capacity-building and of value vs. waste, as well as excellent facilitation skills. Building these capacities requires reading, training and mentoring, similar to the Team Member level (details available online at http://www.openagile.com).

For “projects”, Work Cycle is at most 1/5th duration of overall effort
Projects have a definite start and end. Not all work done with OpenAgile will be project work. This item is not applicable to teams doing ongoing management or operations.

Cycle Engagement Meeting is timeboxed
Every Cycle, a fixed amount of time is set aside for the Engagement Meeting whose outcome is a Cycle Plan. Timeboxing is a discipline where regardless of the state of the meeting, it is closed at the end of the time allocated for it. For example, a meeting that is timeboxed to 2 hours, will end at the 2 hour point even if there are unresolved items on the agenda.

Engagement meeting includes Reflection
Inside the Engagement Meeting, the team sets aside time to deliberately review events, feelings and results from the Cycle that just concluded. Reflection is participatory and may include stakeholders. Participants in reflection are aware that the capacity for detachment helps make reflection more effective.

Engagement meeting includes Learning (focused on Value Drivers)
Inside the Engagement Meeting, the team sets aside time to deliberately identify what has been learned over the past Cycle, including skills, concepts, and feedback from outside the team. Learning is participatory and may include stakeholders. Participants in learning are aware that the capacity for search helps make learning more effective.

Engagement meeting includes Planning (choosing Value Drivers to work on)
Inside the Engagement Meeting, the team sets aside time to deliberately create a plan that is based on learning. The plan includes Value Drivers and Tasks. Planning is participatory and may include stakeholders. Participants in planning are aware that the capacity for love helps make planning more effective.

The whole Team commits to the Cycle Plan
All the members of the Team are aware of the details of the Cycle Plan and both individually and collectively agree to execute the plan. Stakeholders cannot exert pressure on the Team Members to either limit their commitment or over-commit.

Team holds Progress Meeting at regular intervals at least four times per Cycle
The members of the Team get together to verbally share their status with each other. At this level, no particular structure is required for Progress Meetings. However, there must be at least four Progress Meetings every Cycle, and they must be evenly spaced.

Non-leveled OpenAgile rules adoption level at 50% for at least 3 Cycles in a row
There are several details of OpenAgile that must eventually be adopted. However, these “non-leveled” items can be adopted by a team based on need, comfort and capacity. For this level, half of those items must have been evaluated at full score collectively for at least 3 Cycles in a row.

Team agrees to work towards Performing (Level 4)
All the individuals on the team are aware of the requirements for the Performing level and are in verbal agreement that they would like to work on satisfying those requirements. This does not require a specific plan or timeline.