No edit summary |
|||
(10 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
=Activity= | <small>[[Enterprise Elements]] | [[Base Elements]]</small> | ||
={{element|Element-Activity|Activity}}= | |||
<span class="Def">What is being done or going on in our enterprise or its ecosystem.</span> | |||
==Description== | ==Description== | ||
An activity represents something happening that is relevant to our [[enterprise]]. It can be something done by [[people]] individually or collectively, such as work, sports, or performances, for example. An activity can also be used to refer to something that simply happens, without specifying who is doing what. There are many [[events]] or [[processes]] unfolding within our enterprise that are relevant in themselves, without having to specify any actors involved. Activities capture the behaviours and movements of our enterprise. This enables us to model and map the dynamic nature of our enterprise and its [[organisation|organisation(s)]]. | |||
enterprise. | |||
collectively | ==Activity Map== | ||
also refer to something | [[File:EDGY-Activity-Map.png|EDGY Activity Map / Roadmap / Activity Model / Project Plan]] | ||
our enterprise | |||
capture the | Depicting a [[flow]] relationship. Also known as Activity Model, Project Plan or Roadmap. | ||
==Examples== | ==Examples== | ||
*A car manufacturer describes the automated and manual activities needed to produce a car. | |||
*An inbound call centre describes how agents can handle customer calls. | |||
*Two partnering companies work together and decide each one's contribution as a set of activities. | |||
*The police department defines the set of allowed activities of the officer in case of given violent [[events]]. | |||
==Use== | ==Use== | ||
*Provide your vision as a future [[story]]. | |||
*Try to understand [[customer]] behaviour by modelling [[journeys]]. | |||
*Understand and design what [[people]] or machines are (supposed to be) doing. | |||
*Map collaboration, [[processes]] and who does what. | |||
*Develop roadmaps or other planning documents. | |||
==Related== | ==Related== | ||
* | *{{element|Element-People|people}} and {{element|Element-Object|objects}} perform {{element|Element-Activity|activities}} | ||
* | *{{element|Element-Activity|activities}} lead to {{element|Element-Outcome|outcomes}} | ||
* | |||
* | ==Facet elements== | ||
*[[ | *{{element|Id Element-Story|stories}} tell about an enterprises' {{element|Element-Activity|activities}} | ||
*{{element|Ar Element-Process|processes}} are a set of related {{element|Element-Activity|activities}} | |||
*{{element|Ex Element-Journey|journeys}} represent {{element|Element-People|people}}'s {{element|Element-Activity|activities}} | |||
==Suggested Labels== | |||
*plan, [[action]], [[event]], decision ([[tagging|tag]]) | |||
*short, medium, long ([[tagging|tag]]) | |||
*duration ([[metric]]) | |||
*probability ([[metric]]) | |||
== | {{#seo: | ||
|keywords=EDGY,Activity Map,Roadmap,Activity Model,Project Plan | |||
|description=In EDGY, an outcome is what is being done or going on in our enterprise or its ecosystem. EDGY is Intersection Group's Open Source tool for co-creating better enterprises. | |||
|image=EDGY-Activity-Map.png | |||
|image_alt=EDGY Activity Map | |||
}} |
Latest revision as of 18:13, 8 June 2023
Enterprise Elements | Base Elements
Activity
What is being done or going on in our enterprise or its ecosystem.
Description
An activity represents something happening that is relevant to our enterprise. It can be something done by people individually or collectively, such as work, sports, or performances, for example. An activity can also be used to refer to something that simply happens, without specifying who is doing what. There are many events or processes unfolding within our enterprise that are relevant in themselves, without having to specify any actors involved. Activities capture the behaviours and movements of our enterprise. This enables us to model and map the dynamic nature of our enterprise and its organisation(s).
Activity Map
Depicting a flow relationship. Also known as Activity Model, Project Plan or Roadmap.
Examples
- A car manufacturer describes the automated and manual activities needed to produce a car.
- An inbound call centre describes how agents can handle customer calls.
- Two partnering companies work together and decide each one's contribution as a set of activities.
- The police department defines the set of allowed activities of the officer in case of given violent events.
Use
- Provide your vision as a future story.
- Try to understand customer behaviour by modelling journeys.
- Understand and design what people or machines are (supposed to be) doing.
- Map collaboration, processes and who does what.
- Develop roadmaps or other planning documents.
Related
- people and objects perform activities
- activities lead to outcomes
Facet elements
- stories tell about an enterprises' activities
- processes are a set of related activities
- journeys represent people's activities
Suggested Labels
- plan, action, event, decision (tag)
- short, medium, long (tag)
- duration (metric)
- probability (metric)