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:

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