Achieving Swarming in
Agile Teams
Bojan Spasic - Agile Corner Consulting
Every idea or intention
is a theory unless proven.
X
X
X X
X
poor
optimal
X
X
X
X
X
poor
optimal
X
X
X
X
poor
optimal
X
X
X
X
poor
optimal
X
X
X
X
poor
optimal
Shorten Feedback Loops
SPRINT
DAILY SCRUM
CONTINUOUS
INTEGRATION
UNIT
TESTING
PAIR
PROGRAMMING
BRAINSTORM
Problem solving progress
Knowledgeaboutproblem
solutioninparticularmoment
Induced
Knowledge
SCRUM
80%
75%
90%
65%
85%
Time’s up!
Nothing done!
✔︎
✔︎
✔︎
✔︎ It's better to have 80% of
the features 100% done,
instead of having 100%
of the features 80%
done.
First
SWARMING
Opportunity
WHAT?
HOW?
SECOND
SWARMING
Opportunity
To Do
In
Progress Done
Design
Ready
QA Deploy
PO
AcceptedXDeVELOP
WHAT?
HOW?
THIRD
SWARMING
Opportunity
XX
X
KANBAN
A B
C
D
E
F
G
H
C
D
E
F
G
H
A
B
C
D
E
F
G
H
A
B
E
F
G
H
C
D
A
B
I K
J
E
F
G
H
A
C
D B
I K
J
! ! !
E
F
G
H
A
C
D B
I K
J
! ! !
E
F
G
H
A
C
D B
I K
J
! ! !
E
F
G
H
A
D B
I K
J
! ! !
C
E
F
G
H
A
D B
I K
J
! ! !
C
In the end...
… benefits of swarming:
- Innovation
- Low handover cost
- Higher quality (continuous introspection, challenges, just-in-time code reviews, just-in-
time debugging)
- Increased ownership
- Shared knowledge and shared understanding
Thank you
bojan.spasic@gmail.com
http://agilecorner.consulting
https://www.linkedin.com/in/spasic/
https://twitter.com/bojanspasic

Swarming in agile teams

Editor's Notes

  • #4 Mravi su “glupi”, kolonija je pametna Matica ne upravlja kolonijom u svakom trenutku, kolonija prikuplja i distribuira informacije i na osnovu toga donosi odluku o daljem delovanju Rojenje je kao udruživanje poznato na svim nivoima evolutivnog razvoja - od jednoćeliskih do najkompleksnijih organizama