lê trọnghiệp (henry) · •board member of agile vietnam 2012-2015 •recently allocate to...
TRANSCRIPT
Extreme Programming Should Be Dead.
Here is why!
Lê Trọng Hiệp (Henry)
About Me
• Very normal developer
• 10 years of producing software
• Board Member of Agile Vietnam 2012-2015
• Recently allocate to Singapore to be a Consultant
Extreme Programming Should Be Dead
Programming
Not only programming
• Designing• CRC
• Architectural Spike
• System Metaphor
• Coding• Test First
• Pair programming
• Collective Code Ownership
• Testing• 100% test coverage
• Write tests before fix bug
• Acceptance test
• Planning• User Stories
• Release planning, release schedule
• Small Iteration, Iteration planning
• Managing• Daily Standup
• Velocity
• Sustainable pace
• Retrospective
• Move people around (whole team)
(This part really looks like Scrum, doesn’t it?)
Extreme
XP stories in the 90s
Kent Beck Mike Cohn Michael Feathers
• RAM: 8Mb
• PC: 33MHz
• Hard drive: 400Mb – 1000 Mb
• Modem: 28.8kb
Their workstation
2017?
Our toolset have evolved fully and bigly
And our almighty IDEs
Extreme ~ uncomfortable
• You’re a parent, a decent parent.
• Got a super busy job with high pressure
• Constantly worries about your business
• One night, during dinner, your child asks:
Picture this
Papa/mama, I want to go
Extreme Camping this
weekend! You want to go with me?”
Picture this
• Extreme Programming is
• Not only about programming
• Should no longer be considered extreme in 2017
• Extreme ~ Uncomfortable
In conclusion
• Embrace XP naturally
• Call it Rainbow Development
• Or Very Normal Development
• And We can all be Very Normal Developer
What should we do?
• Extremeprogramming.org
• Google Images for Agile Legends
• Google Images for Sigmund Freud unconscious mind
References
• Id: instinct
• Super-ego: ideal, best version of self
• Ego: reason, logic, compromise the Id and Super-ego needs
Sigmund Freud
• Deploy while typing if passed all tests?
• End customer code?
• Extreme Goal?
What should be considered Extreme now?