The Dolt’s Guide to Self-Organization – Jurgen Appelo

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

The dolt’s guide to self-organization

by Jurgen Appelo @ AgileIL11

In agile software development “self-organization” is often referred to as a best practice. This is strange, because it is actually the default practice of complex systems. Self-organization has relationships with anarchy, emergence, evolution, and self-direction. But none of those are the same. Complexity science can teach us what the differences are.

The Darkness Principle and the Conant-Ashby Theorem are two examples of scientific concepts that explain why we do things the way we do in agile teams, and why delegation and empowerment are crucial.

There are different ways of delegating work to a self-organizing team. First of all, people’s level of experience with empowerment is important. Second, there are 7 authority levels that can be selected per task. Third, one can choose between delegating to teams vs. delegating to individuals. Fourth, the order (time dimension) of the delegation of work is important. There is a handy checklist for making sure you’ve properly delegated work to a self-organizing team.

After delegating work to an empowered team, a team leader or development manager is responsible for managing himself, managing top-level management, managing the empowered team members, and managing the environment. All stakeholders may have to change their attitudes to make self-organization work.

Finally, we can distinguish 4 types of trust between a manager/leader and team members. They all have to be in place, or else self-organization may fail.

TOPIC

Self-organization lies at the heart of Agile. Yet, few people really understand what it means, and perhaps even fewer people know what is needed to make self-organization actually work.

OBJECTIVES

What self-organization is from a scientific viewpoint
What the important choices are when delegating work to a self-organizing team
How to manage all stakeholders to make sure that they work with and not against the self-organizing system.

Subscribe for Email Updates:

Categories:

Tags:

Pomodoro Technique
Daily Scrum
Portfolio for Jira
Introduction to ATDD
Agile
LeSS
Limiting Work in Progress
Quality Assurance
Lean-Agile Budgeting
Nexus vs SAFe
Frameworks
Continuous Deployment
LAB
Jira admin
Atlaassian
Atlassian
SAFe Release Planning
Kanban Kickstart Example
Legacy Code
speed @ scale
QA
Agile and DevOps Journey
Professional Scrum with Kanban
Presentation
DevOps
Professional Scrum Master
Covid19
Applying Agile Methodology
Principles of Lean-Agile Leadership
ALM Tools
Product Ownership
Release Train Engineer
Tips
Acceptance Test-Driven Development
SAFe
SPC
Agile Assembly Architecture
Agile for Embedded Systems
Agile Testing Practices
Scrum Guide
Artificial Intelligence
Webinar
Agile Mindset
LPM
Elastic Leadership
Certification
Scrum Primer
Agile Project
Agile in the Enterprise
Confluence
Value Streams
Risk Management on Agile Projects
Nexus
Professional Scrum Product Owner
Lean Agile Leadership
Perfection Game
AI
Agile Outsourcing
Rovo
Entrepreneurial Operating System®
Agile Development
Agile Program
The Agile Coach
TDD
Scrum Values
SAFe DevOps
RTE Role
predictability
POPM
Kaizen Workshop
Systems Thinking
Engineering Practices
Agile Risk Management
Lean Budgeting
Lean Agile Management
Scrum
Reading List
Lean Agile Basics
Development Value Streams
PI Planning
Continuous Integration
ARTs
Lean-Agile Software Development
Planning
Agile Release Planning
Sprint Retrospectives
Test Driven Development
Lean and Agile Principles and Practices
Scrum Master
NIT
Business Agility
Agile Product Development
BDD
ATDD
Legacy Enterprise
Agile Games
What Is Kanban
Jira Cloud
An Appreciative Retrospective
RSA
Continuous Improvement
Tools
ScrumMaster Tales
Implementing SAFe
chatgpt
ART Success
Nexus and Kanban
Enterprise DevOps
Risk-aware Product Development
Implementation of Lean and Agile
Agile Project Management
Self-organization
Agile Basics
Risk Management in Kanban
Agile Product Ownership
Lean Agile Organization
Built-In Quality
A Kanban System for Software Engineering
Software Development
Hybrid Work
Scrum Master Role
SA
Advanced Roadmaps
Achieve Business Agility
Scaled Agile Framework
Operational Value Stream
Managing Risk on Agile Projects
System Team
Nexus Integration Team
Process Improvement
Code
GanttBan
Coaching Agile Teams
Lean Software Development
ATDD vs. BDD
Kanban Basics
RTE
PI Objectives
Software Development Estimation
Managing Projects
User stories
AgileSparks
Continuous Planning
Releases Using Lean
Lean Risk Management
Agile Israel
Continuous Delivery
Amdocs
Lean and Agile Techniques
Program Increment
AI Artificial Intelligence
Agile Techniques
Agility
Product Management
Introduction to Test Driven Development
The Kanban Method
Scrum With Kanban
Rapid RTC
Agile Release Management
Agile Israel Events
Lean Agile
Nexus and SAFe
agileisrael
speed at scale
System Integration Environments
Kaizen
Team Flow
Kanban
ROI
Story Slicing
Kanban Game
Agile India
Jira Plans
Video
lean agile change management
Slides
Spotify
Large Scale Scrum
Agile Exercises
Effective Agile Retrospectives
Scrum and XP
Scrum.org
Jira
Change Management
Retrospectives
Agile Community
WIP
Sprint Iteration
Kanban 101
Sprint Planning
Keith Sawyer
Iterative Incremental Development
Accelerate Value Delivery At Scale
Games and Exercises
Manage Budget Creation
Lean Startup
Agile Contracts Best Practices
IT Operations
System Archetypes
EOS®
Agile Marketing
Agile Delivery
Agile Games and Exercises
transformation
AgileSparks
Logo
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart