xpday keynote 2014
DESCRIPTION
Back in the day, I was in the first flurry of software developers who got excited about eXtreme Programming (XP). The practices of writing automated tests and pair programming were radical at the time. After years of being stuck in waterfall hell, we got to speak to real users and deliver code – it was a wonderful time to be a developer! Extreme Tuesday Club was a place where enthusiasts would get together in the pub to discuss how we could apply XP at work. Fifteen years later, it seems that early burst of energy around being extreme programmers has fizzled out. Agile meetups are now full of project managers and business analysts with hardly a developer in sight. It’s becoming harder to tell that “Agile” was originally about how we approach software development. Post-agile generation developers even roll their eyes when they hear the A-word mentioned, they’ve become detached from a movement that seems to be about dragging them into more meetings and away from their beloved code. Meanwhile the community of developers who count themselves as XP practitioners and software craftsmen has settled into a comfortable version of XP that often equates to practicing TDD under the direction of business analysts with an occasional spot of refactoring. An evening at Extreme Tuesday Club is more often like a depressing episode of the TV show “Grumpy Old Men/Women” bemoaning the state of the industry than a refreshing debate of new ideas about how we can approach software development. Despite this apparent complacency, most organisations have an increasingly yawning gap between software developers and the business they work for. In my keynote at XPDay, I’ll be reminding you all that XP was originally about programmers working directly with customers to deliver software iteratively. Courage is a core value in XP and I’ll argue we need to revive this value and attempt to bridge this gap in our current work situations. Assuming we care about delivering value over retreating from business people to polish code, are we bold enough to stop navel gazing and try to make a difference? If so, how do we make a start?”TRANSCRIPT
Extreme Programming Revisited
@rachelcdavies
#xpdaylon
WHO’S HERE?
AGILE COACH
X EXTREME
DIALS UP TO CONTINUOUS If X is good practice, can we do it all the time?
EARLY EXTREMES
Discipline makes daring possible
DISCIPLINE
PROCESS EXPLOSION
Erik Meijer – recent talk
Agile is a cancer that we need to eliminate from our industry
b AGILE BACKLASH
Oppression & Rules
Freedom & Choice
Hacker? Agile?
HACKER WAY
Making Making Manifesto (Beck, 2014)
FEEDBACK
Sweet spot
BROADER TAKES LONGER?
BUILD-MEASURE-LEARN
BALANCING ACT
Business Developers
NOT MY JOB
PROGRAMMING MISREPRESENTED
Coping stances (Sa/r)
CONGRUENCE
Self!
Other!
Context!
Self
Other Context
PROGRAMMING IS HARD
DEEP REFLECTION
COLLABORATION
EXPERIMENT
LET’S MOB
THANKS & AnY Questions?
www.slideshare.net/RachelDavies @rachelcdavies