Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

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:

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