Really interested to document all the useful things I'm learning like tools, methods, frameworks and processes as modules. Preferably with appropriate meta-data. Let's see how that goes.
This is a collection of modules for the creation and maintenance and florescence of organizations, sustainably. The rationale is that each project is unique and thus may have unique requirements. Turning everything into modules allows for a quick way to identify useful elements and mix them together. Fragmenting larger modules, like frameworks, allows for even greater modularity (i.e. Scrum can be represented as a framework module as well as artifact, event and role modules.)
Please, keep it brief and comment before deleting!
In this section; Panel |
---|
|
Expand |
---|
| GroupsA constellation of one or more individuals - Individual: 1
- Pair: 2
- Small group: 3 - ~7
- Large group: ~8 - ~30
- Huge group: ~31+
ArtifactsThe work or value produced by groups. - Backlog
- Sprint backlog
- Increment
Small activities which facilitate events and do not stand alone. (e.g. fast consensus) - Kanban
- systemic consensus
- discussional consensus
- plurality voting
EventsActivities which lead to to the production or alteration of artifacts. - retrospective
- review
- general meeting
- evening round
- daily scrum
RolesA set of responsibilities or accountabilities given to an individual or group. - Scrum master
- Product owner
- Developer
FrameworksCohesive or coherent arrangements of some or all of groups, artifacts, tools and events. |
|
How I see this fitting together;
Center |
---|
Gliffy |
---|
name | Mod_org_rationalization |
---|
Panel |
---|
title | Modules in this section |
---|
|
|
Organisational modulesModules for sustainable organization |
| |