Team Building¶
- https://en.wikipedia.org/wiki/Leadership_development
- https://en.wikipedia.org/wiki/Organization_development
- https://en.wikipedia.org/wiki/Tuckman’s_stages_of_group_development
- “From Comfort Zone to Performance Management” White (2008) http://www.academia.edu/460313/From_Comfort_Zone_to_Performance_Management
- https://en.wikipedia.org/wiki/Kaizen
Personal Development¶
Golden Rule¶
Emotional Intelligence¶
https://en.wikipedia.org/wiki/Contrasting_and_categorization_of_emotions
https://en.wikipedia.org/wiki/Motivation
https://en.wikipedia.org/wiki/Psychological_manipulation
https://en.wikipedia.org/wiki/The_Five_Dysfunctions_of_a_Team
https://en.wikipedia.org/wiki/Coping_(psychology)
https://en.wikipedia.org/wiki/Defence_mechanisms#Level_4:_Mature
https://en.wikipedia.org/wiki/Positive_psychology#Broad_theories
Collaboration Engineering¶
https://en.wikipedia.org/wiki/Collaboration
“Collaboration Engineering: Foundations and Opportunities” de Vreede (2009) http://aisel.aisnet.org/jais/vol10/iss3/7/
Collaboration Engineering focuses on mission-critical collaborative tasks. A mission-critical task is one that creates substantial value, or that reduces the risk of a substantial loss of value for organizational stakeholders. Collaboration Engineering further focuses on processes for mission-critical tasks that are recurring and must be executed frequently.
Seven Layer Model of Collaboration¶
“A Seven-Layer Model of Collaboration: Separation of Concerns for Designers of Collaboration Systems” Briggs (2009) http://aisel.aisnet.org/icis2009/26/
- Goals
- Products
- Activities
- Patterns of Collaboration
- Techniques
- Tools
- Scripts
Six Patterns of Collaboration¶
“Defining Key Concepts for Collaboration Engineering” Briggs (2006) http://aisel.aisnet.org/amcis2006/17/
- Generate
- Reduce
- Clarify
- Organize
- Evaluate
- Build Consensus
ThinkLets¶
“ThinkLets: Achieving Predictable, Repeatable Patterns of Group Interaction with Group Support Systems (GSS)” http://www.academia.edu/259943/ThinkLets_Achieving_Predictable_Repeatable_Patterns_of_Group_Interaction_With_Group_Support_Systems_GSS_
Collaborative Software¶
Features | X_n | X_1 | X-2 |
---|---|---|---|
Core capabilities | |||
Data contributions | |||
Data relationships | |||
Data limits | |||
Data persistence | |||
Actions | |||
Synchronicity | |||
Identifiability | |||
Access Controls | |||
Roles | |||
Awareness indicators | |||
Interruption alerts | |||
Instructions |
“Toward a Taxonomy of Groupware Technologies” (2008)
“Classification of Collaboration Technology” (2013)
See also:
The same page¶
“On the same page”
https://wrdrd.github.io/docs/consulting/team-building#the-same-page (Sphinx, Git
Source, Edit, History, Annotate sidebar links
Group Support Systems¶
https://en.wikipedia.org/wiki/Electronic_meeting_system
https://en.wikipedia.org/wiki/List_of_collaborative_software
Text Templates¶
- [ ] Collaboration with Etherpad Lite and Thinklets: “As ____, we need to ____ because _____” (copy from the Prompts at the top)
Collaboration Checklist¶
[X] Read https://wrdrd.github.io/docs/consulting/team-building
[ ] Collaboration Plan (Seven Layer Model of Collaboration)
- [ ] Goals
- [ ] Products
- [ ] Activities
- [ ] Patterns of Collaboration
- [ ] Techniques
- [ ] Tools
- [ ] Scripts
[ ] Collaborate
[ ] Generate new list(s) of {problems, solutions}
[ ] Reduce
[ ] Clarify
[ ] Organize
[( )] Evaluate options from [ordered] set { A, B, [or] C }
@usernameX: A, B, C because (e.g. [ ] code compiles, [ ] tests pass, [ ] docs look great)
Relevant Resources with URLs:
@usernameY: C, B, A because (e.g. [ ] code compiles, [ ] tests pass, [ ] docs look great)
Relevant Resources with URLs:
@usernameZ: criteria:x = 400, criteria:y = 100, criteria:z = 5
[ ] Build Consensus
- Runoff Voting
- A = (3+1) = 4
- B = (2+2) = 4
- C = (1+3) = 4
- Weighted Criteria
- criteria:x = 400
- criteria:y = 100
- criteria:z = 5
- A = {x, y}, B = {y,z}, C = {x,y,z}
- A = 500, B = 105, C = 505
- Runoff Voting
See also: