Open Offices don’t really work!
Colocation is the agile thingy!
Yay…No process, No tools!
OK, testing gone, build gone, deployment
gone…but I can still fix bugs…or not?
And what is this?
In 2015 Andrej Karpathy, now
director of AI at Tesla and a
Stanford Computer Science Ph.D.
student, used Recurrent Neural
Networks to generate code. He took
a Linux repository (all the source
ﬁles and headers ﬁles), combined it
into one giant document (it was
more than 400 MB of code) and
trained the RNN with this code.
He left it running for the night. In
the morning, he got this!
Implications for agility
✤ Agile isn’t agile enough anymore!
✤ Infra, Tech and AI enable remote work, automation and even
programming in the future!
✤ Working software means customers buy, use, renew & even refer it!
✤ Actionable insights from customer data constitutes collaboration
✤ Digital leaders believe in thrive by initiating change
✤ Possibly, Agile Manifesto is (still) necessary, but clearly not
The Context for Agility Manifesto for
✤ Customer is the sole Purpose: a team exists to solve customer’s pain. Writing
software is only incidental to it!
✤ Software solution exists for Business: Software might drive business, but
software exists because there is a business!
✤ Winning Teams create their own agile process: Teams exist to write software.
They inherit the systemic constraints, not impose it!
✤ Machines and AI augment human capabilities: As the capabilities and
economics of AI overtake human ones, we are more likely to see “mixed teams”
✤ One size still doesn’t ﬁt all: All models are still basically wrong, but some
manage to be more useful in a given context!
The Agility Manifesto for