Glanz: aiMOOC über GPT aiMOOC Action erstellt

2026-08-31T13:20:01Z

aiMOOC über GPT aiMOOC Action erstellt

Neue Seite

{{T}}
[[Category:English]]
[[Category:Team Roles in Projects]]

{{BR}}
= Introduction =

'''Team Roles in Projects''' is about understanding who does what, who decides, who gives specialist input, and how people coordinate their work so that a project can reach its goal. In vocational education, you may meet project work in a workshop, office, construction environment, care setting, laboratory, IT department, retail business, logistics operation, hospitality setting, or community organisation. The job titles will differ, but the need for clear responsibilities is the same.

A project team is more than a collection of people. Team members depend on one another, contribute different knowledge and skills, communicate about progress, and work toward a shared result. Clear roles help prevent duplicated work, forgotten tasks, slow decisions, and unsafe assumptions. They also make it easier for you to ask for help, report a problem, and explain your own contribution.

[[File:Teamwork in Action.jpg|500px|frameless|center]]

In this course, you will learn to distinguish '''formal project roles''', '''task responsibilities''', and '''behavioural contributions'''. You will practise using a RACI matrix, team charters, simple planning tools, and communication routines. You will also examine what happens when authority and responsibility do not match.

For apprentices and trainees, one principle is especially important: a role assignment never replaces required supervision, competence checks, permits, safe working procedures, or legal responsibilities. If you are not trained or authorised to perform a task, the project plan must reflect that limitation.

{{BR}}
== Learning Goals ==

By the end of the aiMOOC, you should be able to explain why role clarity matters, identify common roles in different projects, assign responsibilities to tasks, interpret a RACI matrix, communicate role expectations, recognise role conflicts, and reflect on the contribution you make to a project team.

{{BR}}
= What Is a Team Role? =

A '''role''' is a set of expected contributions, responsibilities, decisions, or behaviours connected with a position in the team. A role is not the same as a person. One person may perform several roles, and one role may be shared by several people when the project design allows it.

[[File:Team Meeting.jpg|500px|frameless|center]]

It is useful to distinguish three layers:

# [[English:Project role|Formal project role]]: A recognised position such as project sponsor, project manager, workstream lead, project team member, or subject-matter expert.
# [[English:Responsibility assignment matrix|Task responsibility]]: A task-level assignment that states who performs, approves, advises on, or receives information about a particular piece of work.
# [[English:Teamwork|Behavioural contribution]]: A way of helping the team work effectively, for example coordinating, generating ideas, checking quality, supporting colleagues, or building external contacts.

These layers can overlap, but they answer different questions. Your job title may tell people where you sit in the organisation, while a task matrix tells them what you must do for a particular deliverable. A behavioural role describes how you tend to contribute while working with others.

{{BR}}
= Common Formal Roles in Projects =

Project structures vary by sector, organisation, project size, and level of risk. The following roles are common patterns rather than universal job titles.

{{BR}}
== Project Sponsor or Project Owner ==

The sponsor represents the business or organisational need for the project. The sponsor helps establish why the project matters, supports major decisions, provides or secures authority and resources, and remains concerned with whether the project continues to deliver useful value. In many organisations, the sponsor is senior to the project manager.

For a trainee, the sponsor may be a department manager, training manager, customer representative, senior engineer, service manager, or business owner. You may not speak to the sponsor every day, but you should know what decisions require sponsor-level approval.

{{#ev:youtube|https://www.youtube.com/watch?v=2q59DOqynMc|500|center}}

{{BR}}
== Project Manager or Project Lead ==

The project manager coordinates the day-to-day management of the project. Typical responsibilities include planning work, managing the schedule and resources, monitoring risks and quality, coordinating communication, supporting the team, managing changes, and keeping the project focused on agreed outcomes.

In a small vocational project, a trainer, supervisor, apprentice, or trainee may act as project lead for learning purposes. The person should still have a clear route for escalation when a decision is outside their authority.

{{BR}}
== Workstream Lead or Task Lead ==

A large project is often divided into workstreams or task groups. A workstream lead coordinates one part of the project, turns overall objectives into manageable tasks, checks progress, and reports issues to the project manager.

For example, in an event project, one person might lead venue preparation while another leads communications. In a manufacturing improvement project, one person might lead data collection while another leads layout changes.

{{BR}}
== Project Team Member ==

Team members complete project work and contribute technical, operational, creative, or administrative skills. They should understand the expected result, relevant standards, deadlines, dependencies, and who can approve or change their work.

A good team member does more than wait for instructions. You should communicate early when a task is blocked, ask when expectations are unclear, share useful information, and take responsibility for the work you have accepted within your competence and authority.

{{BR}}
== Subject-Matter Expert ==

A subject-matter expert provides specialist knowledge. This person may advise on technical standards, customer needs, materials, legal requirements, digital systems, quality, accessibility, or another field. The expert may be consulted without being responsible for completing the whole task.

In vocational projects, a qualified technician, instructor, engineer, nurse, chef, electrician, IT specialist, accountant, or safety professional may act as a subject-matter expert depending on the project.

{{BR}}
== Customer, User, or Stakeholder Representative ==

Projects exist for people or organisations that have needs, expectations, or influence. A customer or user representative helps the team understand requirements and may review whether a result is useful. Other stakeholders may need consultation or information even when they do not work on the project directly.

{{BR}}
== Quality, Safety, or Compliance Role ==

Some projects need a person who checks whether agreed standards, safety controls, regulations, documentation, or quality criteria have been met. This role must have appropriate competence and authority. In regulated or safety-critical work, a project team must follow the employer's approved procedures rather than inventing its own substitutes.

{{BR}}
= Role Clarity and Responsibility =

Role clarity means that people understand the work they are expected to perform, the decisions they may make, the information they need, the people they must communicate with, and the point at which they must escalate an issue.

A useful role description answers five questions:

# [[English:Task|Task]]: What result or deliverable are you expected to produce?
# [[English:Authority|Authority]]: What decisions may you make without asking someone else?
# [[English:Resources|Resources]]: What time, tools, information, budget, or access do you need?
# [[English:Communication|Communication]]: Who must you coordinate with, consult, or update?
# [[English:Escalation|Escalation]]: Which problems must be passed to a supervisor, project lead, sponsor, or specialist?

When responsibility is high but authority is low, a team member can become stuck. When authority is high but responsibility is unclear, decisions can become inconsistent. Good project design aims to make the two fit.

{{BR}}
= The RACI Matrix =

A '''RACI matrix''' is a responsibility assignment tool that links tasks or deliverables to project roles. RACI stands for '''Responsible, Accountable, Consulted, and Informed'''.

[[File:RACI responsibility assignment matrix diagram.svg|500px|frameless|center]]

{| class="wikitable"
! RACI role
! Practical meaning
! Communication pattern
|-
| '''Responsible'''
| The person or people who do the work needed to complete the task.
| Active coordination while the work is being done.
|-
| '''Accountable'''
| The role that is ultimately answerable for the task or approves its completion.
| Clear decision or sign-off point.
|-
| '''Consulted'''
| A person whose knowledge or opinion is requested before or during the task.
| Two-way communication.
|-
| '''Informed'''
| A person who needs an update about progress, completion, or a decision.
| Mainly one-way communication.
|}

A good RACI discussion is not about filling a table with letters as quickly as possible. It is about making expectations explicit. A task needs someone to do the work, and the team should know who has final accountability. Too many consulted people can slow a task, while too few can cause important knowledge to be missed.

{{#ev:youtube|https://www.youtube.com/watch?v=xc5NbJ8VgTI|500|center}}

{{BR}}
== Example: Improving a Workshop Storage System ==

Imagine a vocational project to introduce a clearer labelled storage system for shared tools and consumables. The exact responsibilities would depend on your workplace, but a simplified matrix might look like this:

{| class="wikitable"
! Task
! Supervisor or sponsor
! Trainee project lead
! Team member
! Safety or quality adviser
! Workshop users
|-
| Agree project requirements
| A
| R
| I
| C
| C
|-
| Create the proposed layout
| I
| A
| R
| C
| C
|-
| Prepare labels and location list
| I
| A
| R
| C
| C
|-
| Check the completed arrangement
| A
| R
| C
| R
| C
|-
| Explain the new system to users
| I
| A
| R
| C
| I
|}

This example shows why the matrix must be discussed rather than copied. If the workplace requires a qualified person to approve a safety-related change, the matrix must reflect that rule. If two people appear accountable for the same decision, clarify how final approval actually works.

{{BR}}
= Behavioural Contributions in a Team =

Formal roles explain structure, but teams also need different kinds of behaviour. Some people generate ideas, some organise, some question assumptions, some build relationships, and some focus on completion. These patterns can change with the task and with experience.

One well-known framework is the '''Belbin Team Roles''' model. It describes nine clusters of team behaviour grouped broadly into social, thinking, and action-oriented contributions. Belbin's own materials describe these as behavioural roles rather than fixed personality types. Most people can contribute in more than one way, and a project does not need nine people simply because the model describes nine roles.

[[File:Belbin team role categories diagram.svg|500px|frameless|center]]

{{#ev:youtube|https://www.youtube.com/watch?v=eFsA4wUf3I0|500|center}}

You can use such a framework as a prompt for reflection: Which behaviours does the project need now? Which strengths are already present? Which contribution is missing? Avoid using a role model to label a colleague permanently or to excuse poor performance. Roles should support teamwork, not become stereotypes.

{{BR}}
= Team Charters and Working Agreements =

A '''team charter''' or working agreement records how the team intends to work together. It can be short. For a small vocational project, one page may be enough.

Useful items include the project purpose, team members, role descriptions, decision rules, meeting rhythm, communication channels, document location, quality expectations, safety rules, response times, and escalation route.

[[File:Team workshop.jpg|500px|frameless|center]]

A working agreement is strongest when the team creates it together. You should be able to point to a rule and explain why it helps the project. For example, a rule such as "blocked tasks are reported on the same working day" is more useful than a vague statement such as "communicate well."

{{BR}}
= Planning Work Around Roles =

Roles become practical when they are connected to real tasks, dates, dependencies, and deliverables. Two common visual tools are Kanban boards and Gantt charts.

{{BR}}
== Kanban Board ==

A Kanban-style board makes work visible by moving task cards through stages such as to do, in progress, review, and done. Cards can show the task owner, due date, priority, blocker, or reviewer. The board does not replace role agreements, but it makes current responsibility easier to see.

[[File:Basic-team-kanban-board.png|500px|frameless|center]]

When you use a board, check that every active task has a clear owner and that review or approval responsibilities are also visible where needed. A card that sits in progress without an owner is a warning sign.

{{BR}}
== Gantt Chart and Schedule ==

A Gantt chart shows tasks across time. It is useful when the team needs to understand sequence, overlap, milestones, and dependencies. Role information can be added through owner columns or linked task lists.

[[File:Wikimedia Foundation project gantt chart.png|500px|frameless|center]]

A schedule can reveal role overload. If the same specialist is expected to complete or approve several critical tasks at the same time, the team may need to reschedule, add support, or change the plan.

{{BR}}
= Communication Between Roles =

Good project communication is purposeful. Different roles need different information at different times. A sponsor may need a concise decision or exception report, while a team member may need detailed task instructions and a specialist may need technical information for a review.

Useful routines include short progress check-ins, action logs, handover notes, decision records, issue lists, and milestone reviews. The team should agree which channel to use for urgent matters and which channel is appropriate for normal updates.

When you hand work to another role, use a clear handover: state what has been completed, what remains open, what evidence or files are available, what risks or constraints exist, and what the next person is expected to do. Ask the receiver to confirm anything that is uncertain.

{{BR}}
= Role Problems and How to Respond =

Common role problems include '''ambiguity''', when nobody is sure who owns a task; '''duplication''', when two people unknowingly do the same work; '''gaps''', when everyone assumes somebody else will act; '''overload''', when one person has too many critical responsibilities; and '''authority mismatch''', when someone is held responsible for a result but cannot make the decisions or obtain the resources needed.

If you notice a role problem, describe the task and the decision that are unclear rather than blaming a person. A useful question is: "Who is responsible for the next action, and who can approve it?" Update the task list, RACI matrix, or team charter so the solution becomes visible to everyone.

Role conflict can also be healthy when it reveals a real difference in priorities. For example, a project lead may push for speed while a quality role asks for more checking. The solution is not to silence one side. The team should return to the agreed requirements, risks, standards, and decision authority.

{{BR}}
= A Practical Role-Assignment Process =

You can use the following process for a school, training, or workplace project:

# [[English:Project objective|Project objective]]: Define the result, customer or user need, boundaries, and success criteria.
# [[English:Work breakdown structure|Break down the work]]: List the main deliverables and tasks.
# [[English:Project team|Identify people and constraints]]: Note skills, availability, required supervision, authority, and dependencies.
# [[English:Responsibility assignment matrix|Assign responsibilities]]: Decide who is responsible, accountable, consulted, and informed for important tasks.
# [[English:Team charter|Agree ways of working]]: Set communication, meeting, document, quality, and escalation rules.
# [[English:Project monitoring|Review regularly]]: Revisit roles when the scope, team, risk, or schedule changes.

This process is iterative. Projects change, people become unavailable, apprentices develop new competence, and stakeholders may change their requirements. Role clarity should be maintained throughout the project rather than discussed only at the beginning.

{{BR}}
= Interactive Tasks =

{{BR}}
== Quiz: Test Your Knowledge ==

{{MC}}

'''What is the main purpose of clear project roles?'''
(To make responsibilities and decisions easier to understand)
(!To remove the need for communication)
(!To guarantee that every project finishes early)
(!To ensure that one person performs all important tasks)

{{E}}
<br>

{{MC}}

'''Which statement best describes a project sponsor?'''
(A role that supports project purpose governance and major decisions)
(!A person who must complete every technical task)
(!A team member who only writes meeting notes)
(!A person who has no interest in project outcomes)

{{E}}
<br>

{{MC}}

'''What does Responsible mean in a RACI matrix?'''
(The person or people who do the work)
(!The person who only receives updates)
(!The person who is never consulted)
(!The person who owns every project in the organisation)

{{E}}
<br>

{{MC}}

'''What does Accountable mean in a RACI matrix?'''
(The role ultimately answerable for the task or approval)
(!Every person who attends a meeting)
(!Anyone who gives informal advice)
(!The person who only receives a final message)

{{E}}
<br>

{{MC}}

'''Which RACI role normally involves two way communication for advice?'''
(Consulted)
(!Informed)
(!Unassigned)
(!Archived)

{{E}}
<br>

{{MC}}

'''Why is a team charter useful?'''
(It records agreed ways of working and role expectations)
(!It replaces all workplace procedures)
(!It removes the need for project planning)
(!It gives every team member unlimited authority)

{{E}}
<br>

{{MC}}

'''What is a warning sign of role overload?'''
(One person owns several critical tasks at the same time)
(!Tasks have clear owners and realistic deadlines)
(!Specialists are consulted when needed)
(!Team members report blockers early)

{{E}}
<br>

{{MC}}

'''How should a trainee respond to a task outside their competence or authority?'''
(Escalate it through the agreed supervision or project route)
(!Hide the issue and continue without support)
(!Approve the task on behalf of a manager)
(!Delete the task from the project plan)

{{E}}
<br>

{{MC}}

'''What is the best description of a behavioural team role?'''
(A pattern of contribution that can support team progress)
(!A permanent label that defines a person's personality)
(!A legal job title that never changes)
(!A substitute for technical competence)

{{E}}
<br>

{{MC}}

'''What should a team do when project roles become unclear after a change?'''
(Review and update responsibilities with the affected people)
(!Continue using the old plan without discussion)
(!Assume the newest team member will decide)
(!Wait until the project is finished)

{{E}}
<br>

{{BR}}
== Memory Game ==

<div class="memo-quiz">
{|
|-
| Project sponsor || Supports project purpose governance and major decisions
|-
| Project manager || Coordinates the day to day management of the project
|-
| Subject matter expert || Provides specialist knowledge for decisions or work
|-
| Responsible || Performs the work required for a task
|-
| Accountable || Is ultimately answerable for the task or approval
|-
| Consulted || Gives input through two way communication
|}
{{E}}
<br>

{{BR}}
== Drag and Drop ==

<div class="lueckentext-quiz">

{| class="wikitable"
! Match the correct terms.
! Topic
|-
| '''Project sponsor'''
| Supports the business need and major project decisions
|-
| '''Project manager'''
| Coordinates day to day project work
|-
| '''Team member'''
| Completes assigned project work and reports progress
|-
| '''Subject matter expert'''
| Provides specialist knowledge
|-
| '''Stakeholder representative'''
| Brings user customer or organisational needs into the project
|}
{{E}}

<br>
...
<br />

{{BR}}
== Crossword Puzzle ==

<div class="kreuzwort-quiz">
{|
|-
| Sponsor || Which role supports the project purpose and major decisions
|-
| Coordinator || Which word describes someone who organises people and activities
|-
| Stakeholder || What is a person or group with an interest in the project called
|-
| Specialist || What is a person with deep subject knowledge called
|-
| Accountability || What term describes being ultimately answerable for an outcome
|-
| Communication || What process keeps roles aligned through information exchange
|}
{{E}}
<br>

{{BR}}
== LearningApps ==

<iframe> https://learningapps.org/index.php?s=Team+Roles+in+Projects </iframe>

{{BR}}
== Cloze Text ==

<quiz display=simple>
{'''Complete the text.'''<br>
|type="{}"}
A project role describes expected { responsibilities } within the team. The project { sponsor } supports the purpose and major decisions. Day to day coordination is commonly handled by the project { manager }. In a RACI matrix the person doing the work is { responsible }. The role ultimately answerable for a task is { accountable }. A specialist whose advice is requested can be marked as { consulted }. A team charter records agreed ways of { working }. When a task is outside your authority you should use the agreed { escalation } route.
</quiz>

<br>

{{BR}}
= Open-Ended Tasks =

{{BR}}
=== Easy ===
# [[English:Role Spotting|Role Spotting]]: Easy — Choose a familiar workplace or training project and identify four roles that would probably be needed. Explain the purpose of each role in one sentence.
# [[English:Mini RACI|Mini RACI]]: Easy — Create a RACI matrix for five simple tasks in a small project such as organising a training display or preparing a class event, then explain one assignment to a partner.
# [[English:Role Interview|Role Interview]]: Easy — Interview a classmate, trainer, or colleague about a project role they have performed and summarise what they were responsible for, what decisions they could make, and who they reported to.
# [[English:Team Role Poster|Team Role Poster]]: Easy — Create an image or poster that shows the difference between a formal project role, a task responsibility, and a behavioural contribution.

{{BR}}
=== Standard ===
# [[English:Team Charter Workshop|Team Charter Workshop]]: Standard — Work with a small group to create a one page team charter covering purpose, roles, communication, decisions, quality expectations, and escalation.
# [[English:Project Handover Video|Project Handover Video]]: Standard — Produce a short instructional video demonstrating a clear handover between two project roles, including completed work, open issues, files or evidence, and the next action.
# [[English:Role Conflict Case Study|Role Conflict Case Study]]: Standard — Write a case study in which two roles overlap or leave a gap, then propose a revised responsibility assignment and explain why it is better.
# [[English:Workplace Role Map|Workplace Role Map]]: Standard — With permission, observe or visit a workplace, workshop, office, laboratory, site, shop, or service setting and create a diagram showing how project information moves between at least five roles.

{{BR}}
=== Advanced ===
# [[English:Responsibility Audit|Responsibility Audit]]: Advanced — Analyse a real or simulated project plan, identify ambiguous, overloaded, duplicated, or missing responsibilities, and redesign the role structure with evidence for each change.
# [[English:Stakeholder Communication Plan|Stakeholder Communication Plan]]: Advanced — Build a communication plan that connects project roles to stakeholder information needs, channels, frequency, decision points, and escalation routes.
# [[English:Role Design Experiment|Role Design Experiment]]: Advanced — Run the same short team challenge twice with different role assignments, record observations about coordination and decision speed, and compare the results without claiming that one arrangement works in every context.
# [[English:Vocational Project Portfolio|Vocational Project Portfolio]]: Advanced — Lead or co-lead a small approved project in your training context and produce a portfolio containing the charter, RACI matrix, schedule, meeting evidence, role reflections, change log, and final evaluation.

{{:Open Task - Create a MOOC}}

{{BR}}
= Learning Assessment =

# [[English:Responsibility Analysis|Responsibility Analysis]]: Given a project scenario with missed tasks and duplicated work, diagnose the role problems and redesign the responsibilities so that ownership, consultation, approval, and information flow are clear.
# [[English:Authority and Accountability|Authority and Accountability]]: Explain what could happen when a trainee is made responsible for an outcome without enough authority, competence, time, or access to resources, and propose a safe escalation path.
# [[English:RACI Evaluation|RACI Evaluation]]: Evaluate a supplied RACI matrix, identify at least three weaknesses, and justify changes based on task needs rather than personal preference.
# [[English:Role Transfer|Role Transfer]]: Compare team roles in two different vocational sectors and explain which role principles transfer well and which responsibilities depend on sector specific rules.
# [[English:Project Change Response|Project Change Response]]: A key specialist becomes unavailable halfway through a project. Revise the role plan, communication plan, and schedule while protecting quality and required supervision.
# [[English:Reflective Teamwork Evidence|Reflective Teamwork Evidence]]: Use evidence from a completed project to explain how your own contribution supported the team, where role clarity helped or failed, and what you would change next time.

<br>
<br>

{{BR}}
= Evidence of Learning =

Evidence of learning should show more than correct definitions. Strong evidence demonstrates that you can apply role concepts to real work, communicate them clearly, and adapt them when conditions change.

{| class="wikitable"
! Evidence area
! What strong evidence can show
|-
| '''Knowledge'''
| You can distinguish formal roles, task responsibilities, behavioural contributions, RACI categories, authority, accountability, and escalation.
|-
| '''Skills'''
| You can assign work, clarify expectations, communicate handovers, consult specialists, report blockers, and revise roles when a project changes.
|-
| '''Products'''
| You can produce a useful team charter, RACI matrix, project schedule, role map, communication plan, decision record, or reflective project portfolio.
|-
| '''Professional behaviour'''
| You work within competence and authority, follow required procedures, communicate early about risk or uncertainty, and treat colleagues' contributions respectfully.
|-
| '''Transfer'''
| You can adapt role principles from one project or vocational context to another while recognising that job titles, regulations, and approval routes may differ.
|}

<br>
<br>

{{BR}}
= OERs on the Topic =

The following open and professional learning resources can extend your study:

# [https://en.wikipedia.org/wiki/Teamwork Wikipedia: Teamwork]: An overview of teamwork as coordinated effort toward a shared goal.
# [https://en.wikipedia.org/wiki/Responsibility_assignment_matrix Wikipedia: Responsibility assignment matrix]: An explanation of RACI and related responsibility models.
# [https://www.open.edu/openlearn/mod/oucontent/view.php?id=147921 OpenLearn: Working in teams]: A free course from The Open University on teamwork and employability.
# [https://www.apm.org.uk/jobs-and-careers/career-path/what-does-a-project-manager-do/ Association for Project Management: What does a project manager do?]: A professional overview of project manager responsibilities.
# [https://www.apm.org.uk/resources/what-is-project-management/what-is-sponsorship/ Association for Project Management: What is project sponsorship?]: A professional explanation of the sponsor role.
# [https://www.belbin.com/about/belbin-team-roles Belbin: Team Roles]: The official description of the behavioural team role framework used in this course.

<iframe> https://en.m.wikipedia.org/wiki/Teamwork </iframe>

<br>

{{BR}}
= Linked Learning Areas =

{| align=center
{{:D-Tab}}
'''[[English:Team Roles in Projects|Team Roles in Projects]]'''
# [[English:Project management|Project management]]
# [[English:Teamwork|Teamwork]]
# [[English:Responsibility assignment matrix|Responsibility assignment matrix]]
# [[English:Communication|Communication]]
# [[English:Stakeholder management|Stakeholder management]]
# [[English:Project planning|Project planning]]
# [[English:Quality management|Quality management]]
# [[English:Vocational education|Vocational education]]
|}

These learning areas connect role clarity with practical planning, communication, quality, employability, and professional responsibility. You can apply them in many sectors, but the exact authority and compliance requirements must always match the workplace and project context.

{{BR}}
= aiMOOC Projects =
[[Category:English]]
[[Category:Team Roles in Projects]]
[[Category:Vocational Education]]
[[Category:Project Management]]
[[Category:Teamwork]]
[[Category:Communication]]
[[Category:Employability Skills]]
[[Category:Apprenticeships]]
[[Category:AI_MOOC]]
[[Category:GPT aiMOOC]]
{{MT}}

English:Team Roles in Projects - Versionsgeschichte

Glanz: aiMOOC über GPT aiMOOC Action erstellt