Wiki source code of Human-Agent Teamwork
Last modified by Pierre Bongrand on 2022/04/05 20:55
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | = Joint Activity = | ||
| 2 | |||
| 3 | == Interpredictability == | ||
| 4 | * Ability to predict what others will do | ||
| 5 | * Not just actions, but the coordination itself | ||
| 6 | * The suitcase example | ||
| 7 | |||
| 8 | == Common ground == | ||
| 9 | * Mutual knowledge, beliefs, and other skills and capabilities | ||
| 10 | |||
| 11 | == Directablity == | ||
| 12 | * Modify the actions when conditions change | ||
| 13 | * Respectiveness of each participants | ||
| 14 | |||
| 15 | == Theory of mind == | ||
| 16 | Humans are inclined to ascribe agency characteristics, like intentions to (self-)moving objects. A theory of mind helps to improve the social world, i.e. it helps to understand, explain, predict or manipulate others' behavior. | ||
| 17 | |||
| 18 | == Shared mental model == | ||
| 19 | Knowledge shared by team members. It is used to describe, explain and predict team behavior and allows team members to coordinate with each other. | ||
| 20 | |||
| 21 | == Types of knowledge to share == | ||
| 22 | * Task-related vs Team-related knowledge | ||
| 23 | * Facts vs Intentions | ||
| 24 | |||
| 25 | |||
| 26 | = Different team structures = | ||
| 27 | 1. Teams with key members (managers, that know more than others) | ||
| 28 | 1. Teams with subteams (each responsible for their own task) | ||
| 29 | 1. Teams with changing team members (where it is important to avoid loss of knowledge) | ||
| 30 | |||
| 31 | We are a team with key members because key members in our team know more about the project. Actually, it is a good team structure because it is better to have someone who knows the whole project and divides tasks for other team members. | ||
| 32 | |||
| 33 | How much is the XWiki helpful? Who is responsible for updating the XWiki? | ||
| 34 | XWiki is really helpful because we could know what others are doing and the process of the project. In our team, we are responsible for updating different parts of XWiki. | ||
| 35 | |||
| 36 | |||
| 37 | = Transactive memory system = | ||
| 38 | We should face a transactive memory system (TMS) that is distributed across different team members. Each of the team members has knowledge about who knows what. | ||
| 39 | |||
| 40 | |||
| 41 | = Task Management = | ||
| 42 | |||
| 43 | == Coordination == | ||
| 44 | |||
| 45 | 1. Manage dependencies between activities | ||
| 46 | 1. Temporal sequencing of behaviors among team members | ||
| 47 | 1. To act in a harmonious combination | ||
| 48 | |||
| 49 | In our team, we maintain an online sheet to track all the tasks that need to be accomplished. We put specific team members' names to indicate who is going to do the task. Besides, we use different colors to indicate the state of tasks. For example, red means "not done", orange means "needs to be improved", blue means "fine but can be improved", and green means "good". In this way, we know what each other is doing and the progress of tasks. | ||
| 50 | |||
| 51 | |||
| 52 |