Video: Agile Schizophrenia - Fred George
December 3rd, 2020
Agile Schizophrenia - Fred George
(https://www.youtube.com/watch?v=jh7du2TfCQU)
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/06f567f2-8ef1-43f8-b89c-dbda2377d09f/e641ac50a623ca80ee6ba2a6b7eb6a28/screenshot.png)
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/172f1b60-23ac-4459-b4cc-a2e580cd0e50/2043f720b64d6657f4f2a08193e922a8/screenshot.png)
disruptor: challenges thinking in a organisation
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/1ebc6169-ce01-4d9a-a8c6-0767b75d3b34/133d2eb43d787e267b6ac40bdc8f5ca3/screenshot.png)
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/07e8416d-410a-4c58-b455-96cb5c22ed53/4facda3afc17a07ff14afd75eb3cae5f/screenshot.png)
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/7588dde6-b730-454d-9875-cb3f196d4598/adcc6360ea768084ea69545f64d8c151/screenshot.png)
teams that are different
---
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/d991a3c1-1f36-411c-9c23-2f9eb61418fe/13012edcb42e883817c15d90863f3b7e/screenshot.png)
misalignment
Model: Uncertainty of requirements defines whether to work waterfall, agile or beyond agile
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/8f25dbd7-051e-4e3e-acf5-c17a79323217/25c8a5687e8a29eae2ea8cb315d53da8/screenshot.png)
graveyard: agile does not work
"if a project was in the graveyard I walked away"
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/1b70007a-2891-4482-b551-dbad7404fc8b/85ac087f57a5516e9f4943adea7d45ca/screenshot.png)
simple
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/cc3acd75-6a4f-4697-b4e7-96485161c5d5/efdca65da586aba809745b34f630f6a9/screenshot.png)
managers teach the best practices
agile has no value here
Complicated problems
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/3e7aeb67-dd48-4b46-ad3d-82e8e1979eda/fb608892628ae1147819cbfc4b86e697/screenshot.png)
experts are expensive
get a team to do what the experts tell
"harvest their knowledge, turn it into stories"
Complex problems
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/dfa0ca74-b625-4b55-8c69-cd5434a3d682/7d679fe8b3140a3d18dddadda2b5d09c/screenshot.png)
there are no experts
"hire a bunch of bright people, turn them loose and say: figure it out"
try something, try something else
if something stops working, try something else
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/767bc319-4971-42cb-917e-fc112d2e72c9/940014df6391205389e212a62745213a/screenshot.png)
we're learning to solve fuzzy problems
Model: Agile Processes are a temporary tool to break old habits and for new ones
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/166c52eb-98f2-47f0-b99f-1c446b9a9ea5/73f706c30a7681ff49eb9ba7b669cdbd/screenshot.png)
process to break 'bad habits' from waterfall
but once those habits are broken, we want to remove those processes
Agile practices:
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/277d034c-122a-4fa1-bd7f-eaa118ff9db5/01ba759c3b987c9753e5986ec4bf2a4f/screenshot.png)
purpose: get used to regularly delivering software
problem: let's pick a task that fit's in the rest of the slot
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/1cb89544-c378-4061-93ea-80d5eeda7467/fa4115679b6792f1c6ea2401c1d594b5/screenshot.png)
group tasking a story, but only 1-2 people will work on it
fear: estimates (depends on who I work with)
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/cf408b81-bdab-4d55-9afd-9334b03db482/76389c1036a55ede75f59811eed96407/screenshot.png)
improve today!
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/b535f968-da6a-4488-9111-86a7dfe1b48e/5f007dce64d68d072ac3d07f1cc87f2c/screenshot.png)
once you get into the habit of taking work from a kanban wall, you don't need a standup anymore
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/c61930b5-29e9-47f7-82d0-6922f65da640/c147e47fe27c806526a90b82d189d26b/screenshot.png)
everyone makes mistakes
microservice of only 100 lines of code
how certain are you about the requirements
fuzzy or very solid?
how experienced is my team at agile
does it need all the practices to get used to the processes?
or has it learned all those processes and can we start to relax them
What type of problem do I have
What type of team do I have?
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/ab9a8b14-4992-454a-853a-fa41ff7b8dec/895e9e14e4e74a5d317cbefeb7b45cdf/screenshot.png)
slightly fuzzy, novice team
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/acbf4d81-c2d7-48c9-af56-4e4a5280d9a9/e664e7a42acfe0b248a147fbd4fde913/screenshot.png)
fuzzy: recomendation engines, google adverbs, financial markets
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/3d4bdb36-1440-4367-bb1e-ce498421ae99/58fab166d7982ccb5d21b3f6f9def0c6/screenshot.png)
payroll, supply chain
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/4ec5b8ef-f66e-4c77-ae9d-e40cb1e49e68/54aa21371cc588cb01aeb3de50073b11/screenshot.png)
larger companies
full range of problems
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/fe1b507e-af7d-4b64-8014-198c0e587fd6/4f8660009351199bc18b778aa198eb68/screenshot.png)
We're assuming everyone is novice
We're assuming it's traditional agile
fuzzy on the edges, not really pinned down
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/ed103f0b-dc79-41bb-899c-a90ef675a364/f86011afefd6dd656faaed173df863f8/screenshot.png)
hardened the edges
very precise process
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/b6876dc2-1f8f-4d5c-9050-28863e654ebf/9ec1cf681ad38b918458b59a90c47776/screenshot.png)
where is your velocity chart
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/db7b8f34-be9e-409c-8555-dc20fcea98e8/f0decf8fce1e6efbc75f2fbf9ade7a0d/screenshot.png)
mismatch
multiple teams:
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/6b2d536b-77e6-45b0-95a9-7be7300089dd/093b7591ddfddb4711c67c4e7a60d459/screenshot.png)
How do we solve this mismatch?
Back to the basics
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/a7e436c6-6422-4937-97d6-7d98f9f56d15/af0180bab3ee75af30f40944ea7e5d98/screenshot.png)
then cause practices and roles
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/94ad20e5-e024-4090-bf62-86fa97f28e1a/53d8714c53bff65aff86e44fdf478404/screenshot.png)
fuzzy domains
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/8fd5cf98-9df4-488b-ae98-b06ad511a4e5/896717af03470f72f07befcd635a0d4b/screenshot.png)
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/1febe223-e987-4eb2-98b9-9731dd0c8cf7/14fcc8468c03ed782cc658133f210871/screenshot.png)
story level
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/41a483a8-cf84-4daa-a1bb-42b00a51580e/00fa40c37f9d007d5a6c904ba1c45e59/screenshot.png)
agile lives here
works well for traditional problems
does not work for fuzzy problems
feature level
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/a700ff4b-5c7f-4111-95f1-ff3d29a4fe0c/053889938c8baa96f37e10a9c953e311/screenshot.png)
customer: teach the domain
what is important
what does success mean?
I can test for that, measure that
teach us the problem to solve, not what to do next
---
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/38216d49-380b-48d2-8938-409683ad678c/065650af3babcaaeed610bf9b8729613/screenshot.png)
experiment constantly
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/399e14bf-47e2-43d7-9201-30c832a08dd1/cdfa44a0945c4fbde25260c609909c3b/screenshot.png)
don't wait for retro
when failures happen, we go faster
less processes
Cycle time
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/d351b38a-23e7-4ddf-8428-b442ebea78a4/306eb8e93c25a2245c3ee0c93f32b502/screenshot.png)
avg team size = 1 dev
avg project length = 4 hours
Testing
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/d50274b2-6164-4a92-a344-9b38363ae63b/e76dbdde889592db91ccf20035d06086/screenshot.png)
no bugs => production system
nobody would die
we may lose some sales, we may lose some google ads
continuous delivery
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/e7aadb25-6fde-4387-b6c1-e580d8c0863b/9fba9e513e70be6f07fee6c31dbffc9a/screenshot.png)
new set of processes
still matching same principles
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/6a8ccd98-2d7d-4c07-8622-bf06ce6e5880/da718e52df7fd571f3e023b45f33bb95/screenshot.png)
what really happened:
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/1aa8282f-576f-409c-98bd-c18d21f0247c/5bc8b8ad4e07b9740c7e21673cf49f89/screenshot.png)
BA: you don't need me anymore
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/8142bbc8-92f5-4d80-a39b-adee98133a29/fcee2cb6866d238ed1e49c9ae4dfac00/screenshot.png)
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/504ad69f-8f8a-4ed3-8391-cfe433038585/3c3add921f15f632234b7740566f215e/screenshot.png)
no experts in fuzzy problems
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/ff216941-462a-42a2-a433-d0b76c566475/d033881cc0bc5c653acee5355974062a/screenshot.png)
helped recruit in a competitive market
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/e76bbada-e876-4e46-8927-55102103b769/91910137746a5e969901a859e3ba1a96/screenshot.png)
next level agile
"in XP pushing everything to the extreme"
traditional
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/974383e4-a912-4bad-9b3e-dcc4338f3519/98aa7c12cd737e6ac5ed2c27af18cf11/screenshot.png)
fuzzy
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/186ff96c-1c97-4027-bb85-5ad44bd94333/bff6e976f9db943fe089054637b5b2da/screenshot.png)
---
case
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/bceeb7eb-cf49-4fd5-9346-05ed56a1c283/5a4daa1892a6d7078546a491c04f306d/screenshot.png)
traditional team
supply chain
transactions
=> waterfall
traditional agile
iterations
ship every 2 weeks
=> traditional agile
kiosk in the store
"scan clothes and send to your house"
ship twice a day
=> fuzzy
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/52fd51d0-2547-423c-9682-4a6ff0c74a53/02024bf5bbdbaef408dae68f1467b4f7/screenshot.png)
---
case: recommendation engine
very fuzzy
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/83c904d0-d557-4134-90cc-0d1092bb8dbd/acf09a28175abce436b97ffde50cda9e/screenshot.png)
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/53a34b26-84ba-477f-a82b-f8d1037958a0/3f1b8be12c9aba4d047647529e5b9d18/screenshot.png)
new team, new people => pair, standups
after a while, these processes need to get more fuzzy
![no description for image available](http://images.ctfassets.net/p2rtto0i6kcn/edd2ab82-5583-4383-98b3-e538ca1d9e10/b1a15e5017df90596b766acd7bf010f6/screenshot.png)
different teams have different processes, matching their environment
---
Q&A
Across a large org, lots of different processes, does that work?
it works quite well
teams need to be visible about their processes
novice teams, need help selecting processes to fit their context
Very fuzzy, hard to convince that time boxing is not that easy
in fuzzy problems, competitive advantage is always going faster
deployment process, metrics, ...
not fond of timeboxing, innovation is very difficult with timeboxing
why did we run out of time?
timeboxing for experimenting with new technology
Team Envy: comparing processes, interesting tasks, freedom
you need to blow apart high performing teams with highest experience after a while
how well are you in pairing, and those things?
tomorrow that could be you if you work hard at it
Past, every programmer was an expert in the business domain. Is this still possible now?
yes
we are capable of understanding the business domain
not everyone in the team needs to
fuzzy problems: what are the metrics for success? (eg. google ads = ratio value of keywords, not hard to understand)
hard domain: particle physics -> teach physicists to be programmers
This post was referenced in: