Wiki source code of Human-Agent Teamwork

Last modified by Clara Stiller on 2022/04/01 12:51

version	line-number	content
2.1	1
	2	=== Teamwork concepts:===
	3
	4	* Joint activities
	5	** Interpredictability
	6	ability, to predict what others will do (foresee if someone needs help e.g. exit the train with a baby stroller)
	7	** Common ground
8.1	8	team has to have mutual knowledge, beliefs, and assumptions about others' skills or capabilities -> related to the Ontology in our project
2.1	9	** Directability
8.1	10	individuals can modify actions of the others, as well as conditions and priorities
2.1	11	one can influence others, they react to the influence
	12
	13	* shared mental model
	14	** Mental Model
	15	*** = internal representation of the world, which is used to describe, explain and predict
	16	*** related to 'theory of mind'
	17	*** a theory of mind enables the ability to attribute mental states (beliefs, intentions, emotions, desires) that are different from one's own
8.1	18	//example: Richard believes that Mary intends him to persuade Albert that...//
2.1	19	** Shared mental Model
18.1	20	[[image:mental_model.png\|\|height="250"]]
2.1	21	*** 'overlap' of individual mental models, knowledge representation shared by team members
8.1	22	***same use as a mental model, but for team behavior (describe, explain, predict)
2.1	23	*** allows coordination and adaption of changes
	24
	25
8.1	26	* Team Structures
	27	** Teams with key members (manager)
	28	** Teams with subteams
	29	** Teams with changing team members (!avoid loss if knowledge)
18.1	30	[[image:key_member.png\|\|height="200"]] [[image:spread.png\|\|height="200"]]
2.1	31
10.1	32
	33	=== Our Team structure:===
	34
18.1	35	[[image:group5.png\|\|height="150"]]
8.1	36	In our group, we had a dynamic change of responsibility and workload. Normally we split the work during the week into smaller parts and shared it between all 6 group members or divided it into smaller teams. At the beginning of next week, we shared our progress within the XWiki or in a short meeting to be back on the same level. Using this team structure all of us were able to continue working on each part and we were flexible enough to take care of personal difficulties (almost everyone of us was sick during the quarter or had urgent submissions).
2.1	37
10.1	38	The XWiki helped to share knowledge between the team members. Also, it was a good possibility to re-read what others wrote down and add more details. Throughout the quarter we changed, corrected and improved almost each page in an iterative process.
2.1	39
8.1	40
11.1	41	=== Conceptions and Knowledge process===
8.1	42
11.1	43	* Transactive Memory System (TMS)
	44	** memory system, that is distributed across different team members
	45	** not everyone has to know all, but has to have knowledge about who knows what and own expertise
	46	** is supposed to predict team performance
	47
	48
	49	* Situation awareness
	50	** //Is the perception of elements in the environment within a volume of time and space
10.1	51	the comprehension of their meaning and
	52	the projection of their status in the near future.//
11.1	53	** //activated// knowledge about //current// situation (focusing on perception, cognition and action) is used to describe, explain and predict team performance
	54	** if situation awareness is missing, accidents can happen
	55	** important in domains with high information load and high costs of errors
	56	** examples where SA is needed:
	57	*** when tasks are transferred from AI/ Machine to human (e.g. autonomous driving, flying)
	58	*** awareness for resilience (e.g. policemen wearing smartwatch to connect with team members)
10.1	59
11.1	60	* **Team shared situation awareness
	61	Team SA
	62	** every team member has their own subgoal (that is part of teamgoal)
	63	** every team member has SA for its own responsibility (to reach subgoal)
	64	* Shared SA
	65	** team members have SAME SA
10.1	66
11.1	67	Example
	68	Robot Assisted Disaster Response
	69	* used for Earthquakes in Italy, Industrial fire
18.1	70	[[image:situation_awareness.png\|\|height="400"]]
11.1	71	a shared situation report (like a map with markings) can improve the performance of the team
10.1	72
11.1	73	=== Task Management===
	74
	75	coordination of dependencies between activities to accomplish team goal/ harmonious combination
10.1	76	Types of coordination:
	77	1. Bottom up coordination
	78	Flocking behavior of birds
	79	1. Top down coordination
	80	hierarchy in companies
	81
	82
11.1	83	Workload
10.1	84	1. cognitive load (e.g. time occupied, level of info processing)
	85	1. physical load
	86	1. affective load (expected cognitive load, severity level of current task)
	87	1. physical state
	88	1. emotional state (arousal, valence)
	89	* workload needs to be balanced; e.g. robot can cope with more physical load than human
	90	* Feedback on emotional and physical state helps to improve the team performance, but team member privacy should be considered, always balance between the team performance and the individual team member privacy! (for example with information sharing policies)
	91	* use notifications, to inform team members about an overflow of workload
	92
18.1	93	//remark on types of workload: only physical and cognitive workload is represented in the team design patterns (boxes that are carried over the head). The affective load is not shown, maybe because it's subjective and hard to measure, but it should be considered in the design process as well //
10.1	94
	95
	96
	97