The State of Agile Software in 2018 (Martin Fowler) ("the battle"…
The State of Agile Software in 2018 (Martin Fowler)
'Oh, yeah, we're doing agile already'
Our challenge at the moment isn't making agile a thing that people want to do,
it's dealing with what I call faux-agile
Ron Jeffries often refers to it as "Dark Agile", or specifically "Dark Scrum"
It's not about getting agile respectable enough
it's realizing that a lot of what people are doing and calling agile, just isn't
3 main problems
Get rid of the Agile Industrial Complex and the idea of imposing stuff on teams
In particular, one of the really central things that impressed me very much about the early agile advocates was this realization that people are operating at the best when they choose how they want to work.
Individuals and Interactions over Processes and Tools
You need to find good people that work together at a human level
The choice of what tools they use or what process they should follow is second order
A team should not only choose its process, but continue to evolve it
The retrospective is really such a central part of the practice
it actually doesn't matter whether you actually have a formal retrospective
Taylor: His view of the average worker was that they were lazy, venal, and stupid. Therefore you didn't want them to decide how they should make a particular piece of machinery, but somebody else, somebody who was a more intelligent and educated, they should figure out exactly the best way to do it.
At the heart of this notion was that the people who are doing the work should not decide how to do it
That even means if the team doesn't want to work in an agile way, then agile probably isn't appropriate in that context, and [not using agile] is the most agile way they can do things in some kind of strangely twisted world of logic.
So that's the first problem: the Agile Industrial Complex and this imposition of one-best-way of doing things. That's something we must fight against.
Raise the importance of technical excellence, and never forget that when writing software, the technology side is really vital
the primacy of the team
our ability to change rapidly, to be able to deal with change easily
Kent Beck summarizes this. "When you want to make a change, first, make the change easy. (Warning, this may be hard.) Then make the easy change"
Don't add features you don't need. Refactor. Test. Deliver frequently.
Organize around products
Products over projects:
Small, focused teams
When [at Snowbird] we were talking about names for agile software development, Kent Beck suggested "conversational", because there should be an ongoing conversation between software developers, business people, and anybody involved in making that customer experience better