3.3.3 Project execution

Now that you have an initial plan in place, and students have defined their tasks, you can actively engage in the Agile learning cycle, which involves the daily work conducted by students to advance their projects within a period referred to as a Sprint. A Sprint typically spans from 2 weeks to 1 month and aims to produce a deliverable. This deliverable can be either a version of the final product or project, or the end result itself, depending on the project's stage of execution.

For instance, if you've planned a project to be completed in 2 months and decided to have biweekly sprints, at the end of the first sprint, which is after just 2 weeks, the student would have created and shared the first version of the result. After 4 weeks, version 2 is shared, after 6 weeks, version 3 is shared, and so on. This process continues until the second month when the student shares the final result of her project, which would be version 8 at sprint 8.

To effectively visualize and monitor progress during the Sprints, it's crucial to have daily meetings at the beginning and end of each day. These meetings serve to track the Agile learning cycle, which involves:

1. Setting intentions for the day.

2. Engaging in the creation or completion of tasks.

3. Reflecting, either individually or as a group, on what has been accomplished and how the process unfolded.

4. Sharing the achievements and progress made during the day.

These daily meetings help keep everyone aligned, informed, and on track throughout the project's development.

The frequency and format of your meetings should be adaptable based on the type of school and the time allocated for projects. Your Agile learning cycle might be longer or shorter, which can necessitate adjustments to your meeting schedule. The nature of your school environment, whether it primarily focuses on project-based learning or offers limited project time, can also impact your meeting strategy.

For example, if you work in a school where projects are the central mode of instruction, you might be able to have daily meetings with your students. In such cases, you can choose to hold a single morning meeting, such as a Stand-Up meeting similar to the software Scrum framework or eduScrum framework , to set intentions for the day. Alternatively, you can opt for two daily meetings, like those used in Agile Learning Centers: a morning scrum and stand-up meeting to set daily intentions and an afternoon meeting for reflections.

However, if you're in a school where project-based learning occurs once a week for a limited duration, like a two-hour session, daily meetings might not be practical. In this scenario, a weekly meeting to track progress and offer guidance could be more suitable. The key is to customize your boards and meeting rituals to align with the specific context and needs of your school.

Ultimately, the design of your daily cycle is a flexible choice, influenced by the group's needs, your personal preferences as a facilitator or teacher, and the school's specific requirements. Adaptability is a fundamental aspect of being Agile.

To keep these meetings short and focused, students should remain silent for most of the time and use hand signals to participate. Only one student should speak at a time. Hand signals can provide the group with instant feedback without interrupting the current speaker, helping maintain an efficient and structured meeting.

Twinkle fingers up

Twinkle fingers up / “This friend speaks my mind” - this signal is done with wiggling fingers and demonstrates strong resonance with what is being spoken.

Twinkle fingers down

Twinkle fingers down - this signal signifies disagreement or a negative response, without implying disapproval of the speaker. It enables real-time feedback on the conversation without confrontation, allowing individuals to express their perspective.

Delta

Delta / Change-up - a call to attention that the group process may need to be GameShifted or that the current process agreements are not being honored. A person can give this hand signal so others can have a chance to wrap up what they’re saying before they say what change-up they see is needed.Sometimes the sign is enough to shift people’s awareness and behavior back on the intended track.

Focus

Focus - this signal serves as a reminder for the group to regain concentration when the conversation drifts away from its initial purpose. It's a means to prevent undesired tangents and enhance efficiency in discussions that have strayed from their original intent.

Clarity

Clarity - this signal is a way for individuals to indicate their questions or express their confusion about certain aspects of the conversation. It is crucial for the group to maintain a shared understanding, and when this is lacking, the facilitator and team members need to be aware to address the issue effectively.

Feel free to introduce and use new signals for shifting and signaling dynamics as needed within your learning community. These signals can help maintain a productive and organized meeting. Signals such as "Stay on Focus," "Trust the Group," "Clarification Question," "Slow Down," or "Direct Response" can be introduced and displayed on your Gameshifting board or another visible place where they will be easily accessible to working groups.

You can read more about the hand signals in the following sources:

• ALCs Starter Kit
• Handbook of the project result 1 for the Erasmus+ project Agile4Collaboration
• Videos of the project result 1 for the Erasmus+ project AgileXR:

Hand Signals