# data[].attributes.body
We are a language high school, part of a PASCH ‘partner schools for the future’ network an initiative of the Goethe-Institut.

The Goethe-Institut is the cultural institute of the Federal Republic of Germany. It is an association that serves to promote the German language in the world and to boost Germany's image.

Our project is called ‘Talk ohne Grenzen - The new confrontation format’.

# data[].attributes.body
The central objective of this innovative format is to promote the communicative and expressive skills of young people and presupposes a predefined context, a predetermined division of roles at the outset. We work with Scrum by promoting an environment in which students work in teams to achieve common learning objectives through short work cycles and continuous improvement.

# data[].attributes.body
The four topics for the preparation of our talk are:

Technology and Social Media: How young people are redefining communication and information.

Sustainability: Gen Z's commitment to the environment and climate change movements.

Inclusion and Diversity: The younger generation as promoters of a fairer and more inclusive world.

Work Challenges: Gen Z's approach to the world of work and their expectations of companies.

# data[].attributes.headline
Why we use Padlet and Scrum in our school Marco Polo?

# data[].attributes.subject
Why we use Padlet and Scrum in our school Marco Polo?

# data[].attributes.body
We use Padlet in combination with the Scrum framework for our school project to stimulate collaboration, teamwork and work organisation. Scrum is suitable for our project because it requires a lot of interaction between team members. Padlet, on the other hand, is a digital tool that allows us to create collaborative noticeboards, where students can upload documents, pictures, comments and links.

# data[].attributes.body
1. Researching the main topic 3 hrs.

a thoroughsearch is made on the topic of the talk in order to provide relevant and up-to-date information.

2. Defining the aims of the talk 2 hrs.

Description: Establishing the objectives of the presentation (e.g. inform, educate, motivate). Decide which key messages are to be conveyed to the audience.

3. Creating the structure of the talk 2 hrs.

A clear structureis created with an introduction, main body, and conclusion to make the talk fluid and understandable.

4. Search for sources and supporting data 2 hrs.

Collect statistical data, real-life examples, and reliable sources to strengthen my arguments.

5. Exposure rehearsals 1 hrs.

Rehearse exposition to improve the timing and tone of the presentation.

6. Preparation of final questions 1 hrs.

anticipate possible questions from the audience and prepare appropriate answers.

7. Verification of visual and audio material 1 hrs.

check that all audio and visual devices are working properly to avoid technical problems.

8. Defining roles during the talk1 hrs.

Clearly assign who will present each part and who will handle the slides or videos.

9. Making a video 1 hrs.

create a video with a duration of 5-7 minutes for participation in the competition.

# data[].attributes.body
The product owner can prioritise these activities according to importance and available time, with the most crucial activities such as research and talk structure at the top of the list.

This list can be continuously updated and adapted as the team progresses in the preparation of the talk.

# data[].attributes.body
Break down tasks: Each task should be broken down into smaller tasks, so that they are easier to handle during the Sprint.

Clearly define roles: Ensure that each task has a manager. If more than one person is involved, assign responsibilities.

Estimates: It is important that the estimates are accurate in order to respect the planned time for the Sprint.

Priority: Some tasks may have a higher priority than others (e.g. research and writing are more important than technical tests, which can be done at the end).u can add tasks during the Sprint.

# data[].attributes.attachment_caption
Summary diagram of roles:Role Key Responsibilities

# data[].attributes.body
Product Owner Prioritise work, manage the Product Backlog, communicate the vision

Scrum Master Ensure adherence to Scrum practices, remove obstacles, facilitate Scrum events

Development Team Realise the work planned in the Sprint, self-organise, deliver increments

# data[].attributes.body
In Scrum, there are three key roles that work together to ensure project success. Each of these roles has specific responsibilities and contributes to different aspects of the process. Here are the details:

1. Product Owner

The Product Owner is the person responsible for maximising the value of the product and the work of the development team. He or she ensures that the team works on the right priorities, focusing on what generates the most value for the stakeholders.

Main responsibilities:

Managing the Product Backlog: Creates, updates and prioritises backlog items, which are the activities, functions or improvements needed.

Defining the product vision: Represents stakeholder interests and communicates the overall project vision to the team.

Managing stakeholder expectations: Keeps stakeholders informed about the progress of the product and negotiates the prioritisation of functionalities.

Accepting or rejecting completed work: Decides whether the work delivered by the development team meets requirements.

2. Scrum Master

The Scrum Master is the facilitator of the Scrum team and ensures that the Scrum framework is followed correctly. His main goal is to help the team remove obstacles and continuously improve.

Main responsibilities:

Team guidance and support: Help the development team to comply with Scrum practices and maintain a smooth workflow.

Removal of impediments: Works to identify and resolve issues that hinder the team, such as technical or organisational issues.

Facilitating Scrum events : Organise and facilitate Scrum events, such as Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective.

Scrum Coach: Trains the development team, Product Owner and stakeholders on the effective use of Scrum.

3. Development Team

The Development Team consists of professionals who do the actual work to develop the product. It is a self-organised team that decides for itself how to complete the work within a Sprint.

Main responsibilities:

Delivery of the increment: Create the product according to the goals set by the Sprint. At the end of each Sprint, the team delivers a working increment of the product.

Self-organisation: The team decides independently how to achieve the objectives of the Sprint, without micro-management.

Collaboration: Team members work together transparently and share responsibility. They may have specialised competences, but all work together to achieve the Sprint objective.

Planning and review: They actively participate in all Scrum ceremonies, such as Sprint Planning, Daily Scrum, and Sprint Retrospective, to plan and review the work.

# data[].attributes.body
Add your Name!

Product Owner:

Scrum Master:

Development Team:

# data[].attributes.body
Choose the roles for the four groups. Each group belongs to a topic!

# data[].attributes.body
Add your Name!

Product Owner:

Scrum Master:

Development Team:

# data[].attributes.body
Add your Name!

Product Owner:

Scrum Master:

Development Team:

# data[].attributes.body
Add your Name!

Product Owner:

Scrum Master:

Development Team:

# data[].attributes.body
Scrum is a framework for a specific type of project management. It is characterised by lean processes, step-by-step development and regular feedback loops.

# data[].attributes.body
Sprints are short work cycles lasting 1-4 weeks, during which the team focuses on a specific objective.

# data[].attributes.body
The Product Backlog is a prioritised list of functionalities, tasks or objectives to be completed.

# data[].attributes.body
The Sprint Backlog contains all tasks selected from the Product Backlog that the team intends to complete during the current Sprint.

# data[].attributes.body
the end of each Sprint, when the team should evaluate the work done:

Check that the tasks in Done are completed correctly.

# data[].attributes.body
At the end of the Sprint, a Sprint Retrospective is organised to understand what went well and what to improve for future projects:

What worked well in the teamwork?

What were the difficulties?

What can we improve in the next project?

# data[].attributes.headline
Research and collection of sources 3 hrs.

# data[].attributes.subject
Research and collection of sources 3 hrs.

# data[].attributes.body
T1

Description: Each group finds at least 5 reliable sources that elaborate on their talk topic.

# data[].attributes.headline
Content writing (introduction and main contents) 3 hrs.

# data[].attributes.subject
Content writing (introduction and main contents) 3 hrs.

# data[].attributes.body
T2

Write 3-4 key topics to be covered.

Add concrete examples and supporting data.

# data[].attributes.body
name of team leader:

# data[].attributes.body
name of team leader:

# data[].attributes.body
The objective of this sprint was to finalise the draft of the talk line-up and assign the main roles to the students.’

# data[].attributes.body
Perform a complete test of the talk.

Time the talk to ensure that the duration is within the allotted time.

# data[].attributes.body
name of the team leader:

# data[].attributes.headline
Control of technical devices and recording 1 hrs.

# data[].attributes.subject
Control of technical devices and recording 1 hrs.

# data[].attributes.body
Check all technical equipment (slides, microphone, computer) and resume talk

heck technical devices and resume 4 talk

# data[].attributes.body
name of the team leader:

# data[].attributes.body
Research the main topics and resources for talk show content.

Appoint team leaders for each Sprint

Draft of the talk schedule

# data[].attributes.body
We completed the choice of topics for the talk, assigned roles to each pupil and created a draft of the set list.

# data[].attributes.body
We have completed

the assignment of the main roles. We have a presenter, two guests and a technical team.

The draft agenda, which includes the main questions for each topic and guest.

# data[].attributes.body
Our Scrum Board with three main columns: To Do, In Progress and Done, which displays tasks for the preparation of aour school talk show.

# data[].attributes.attachment_link.title
DALL·E 2024-10-23 23.03.18 - A Scrum board divided into three main columns_ 'To Do,' 'In Progress,' and 'Done.' Each column contains sticky notes representing tasks related to the

# data[].attributes.body
Criteria

Collaboration

Planning

Communication

Meeting deadlines

Feedback and improvement

Creativity and innovation

End result