the elements below can help you deploy a Parkour program.
to create the right conditions for the deployment of the Parkour approach, and define its thematic or functional scope. This perimeter can be defined using tags that list the priorities or strategic issues served by the Parkour program.
to set the program, to initiate the process, and to monitor and develop it.
each focusing on a specific issue, subject or project. As soon as an XP team is set up, it can start.
Each XP team builds its own itinerary, at its own pace, in the order best suited to its needs and project. To do so, they chose different short activities called beacons, which are as many steps in the innovation journey that they build.
Some beacons can be mandatory crossing points if the context so requires. A directory specifies the intentions of each beacon as well as the practical ways and means for carrying it out.
After each beacon, the XP team formalizes its progress and shares its learning in a publication addressed to the whole community concerned.
At any time, an XP team can request for some help from a Parkour Coach. Either to better choose the next beacon, or to learn how to conduct a difficult beacon. This is done face to face or remotely.
There are different families of beacons, each representing an essential dimension of an innovation path. Teams are invited to cover all the families little by little, so as not to neglect any dimension.
As early as possible, the teams deliver a basic and viable solution on a limited perimeter, a minimal assembly of elements that will bring value to users.
Parkour can be deployed in different ways. For example, one or several half-day or full-day workshops can be planned, during which several XP teams do a series of beacons in parallel. Alternatively, each team can plan its beacons according to its availability, or invent any other method that seems relevant.
The following roles can be assigned to lead a Parkour program:
they provide governance and protect the overall program. They define the thematic perimeter, the strategic imperatives and the players involved in the program.
this is the team that works on ensuring that the program is properly implemented.
they are a resource to support the teams, i.e. they remain available and accessible to be requested by the XP teams, without ever deciding for them. They take the initiative to intervene only if they detect difficulties in a team.
2 or 3 participants form a team around a subject, an issue or a project. Over time, they can invite other members to join them if necessary, carefully maintaining a good collective dynamic. An XP team can choose a leader. Ideally, an XP team interacts regularly with other XP teams.
they are experts on the subjects dealt with by XP teams, they can be mobilised by a team to share their knowledge, point at resources, inspire or stimulate the team...
Teams create their own journey by choosing one beacon after another.
The beacons come by families. Each family of beacons covers an essential dimension of an innovation program. Each beacon bears a specific intention.
Here is an example of a sequence of beacons:
Here is everything you could use in deploying a Parkour program
giving rhythm (accelerating or slowing down) to the overall program or to the work of a specific team.
keywords used to convey the strategic imperatives of the organisation, to which XP teams must contribute with their solution.
a result developed by an XP team in the form of a product, service, offer, experience or process for users, beneficiaries or customers.
strategic or operational responsibility for an innovation or transformation program in Parkour mode.
communication by an XP team of elements of progress of its course, with the intention of sharing or requesting.
basic and early prototype of a solution, made using simple materials and tools, to facilitate the collection of feedback
regular or impromptu moments of sharing, feedback and cross contributions between XP teams.
digital interface to give access to all information, inputs and deliverables, and to facilitate interactions between teams.
function performed by the operational sponsors to ensure fluidity and quality of execution in the deployed program.
playground of a Parkour program, delimiting the subjects, stakes, priorities and players involved.
monitoring of the whole program, of each of the teams, and of the progress and relevance of the projects.
coach for one or more XP teams, to help them choose and undertake beacons.
presents the various proposed beacons, and for each beacon an assignment specifying how to carry it out.
physical or digital space to find the tools needed (canvas, maps, tutorials, supplies, etc.) to undertake a beacon.
the way strategic sponsors of the program define the scope, include stakeholders, and give autonomy.
participants already familiar with the Parkour approach support new XP teams starting up.
digital or analogical tool for visual management, to monitor the program and the progress of each team.
after each beacon, an XP team communicates on its team dynamics and the progress of its project.
collaborative work moment that brings together one or more XP teams to accelerate their projects.
small group of participants involved in a Parkour program, around a subject, a project or an issue.
short activity carried out by an XP team, to focus on one aspect of its project.
